From owner-freebsd-questions Mon Oct 23 4:35:33 2000 Delivered-To: freebsd-questions@freebsd.org Received: from vidle.i.cz (vidle.i.cz [193.179.36.138]) by hub.freebsd.org (Postfix) with ESMTP id AB3EB37B479 for ; Mon, 23 Oct 2000 04:35:29 -0700 (PDT) Received: from ns.i.cz (brana.i.cz [193.179.36.134]) by vidle.i.cz (Postfix) with ESMTP id 4935230704; Mon, 23 Oct 2000 13:35:23 +0200 (CEST) Received: from woody.i.cz (woody.i.cz [192.168.18.29]) by ns.i.cz (Postfix) with ESMTP id E698F12E92; Mon, 23 Oct 2000 13:34:43 +0200 (CEST) Content-Length: 4155 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <39F40E77.354CAF94@sentry.granch.ru> Date: Mon, 23 Oct 2000 13:34:43 +0200 (MET DST) Reply-To: mm@i.cz From: Martin Machacek To: achilov@granch.ru Subject: Re: probably stupid question (mounting BSD/OS filesystem) Cc: questions@FreeBSD.ORG Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Oct-00 Rashid N. Achilov wrote: > Isn't BSD/OS 3.1 partition not FFS? Yes, BSD/OS 3.1 uses FFS as default filesystem but that's not the problem. The problem is that FreeBSD refuses mount any BSD/OS created partition (that actually contains FFS filesystem. Example might help. I have FreeBSD 4.1.1 installed on IDE disk and BSD/OS 3.1 on SCSI disk. BSD/OS was installed on the disk specifying that no "real" FDISK table should be used. Let's try to print it from FreeBSD anyway: martin@mm0:~# fdisk da0 ******* Working on device /dev/da0 ******* parameters extracted from in-core disklabel are: cylinders=1222 heads=64 sectors/track=32 (2048 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=1222 heads=64 sectors/track=32 (2048 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 255,(BBT (Bad Blocks Table)) start 4278243231, size 255 (0 Meg), flag 0 beg: cyl 255/ sector 0/ head 0; end: cyl 0/ sector 0/ head 0 The data for partition 2 is: sysid 255,(BBT (Bad Blocks Table)) start 520097695, size 8239360 (4023 Meg), flag 93 beg: cyl 255/ sector 0/ head 207; end: cyl 0/ sector 0/ head 0 The data for partition 3 is: sysid 114,(unknown) start 1935810671, size 1634476132 (798084 Meg), flag 0 beg: cyl 357/ sector 36/ head 114; end: cyl 110/ sector 0/ head 114 The data for partition 4 is: sysid 0,(unused) start 0, size 0 (0 Meg), flag 62 beg: cyl 256/ sector 44/ head 101; end: cyl 0/ sector 0/ head 0 martin@mm0:~# ..and following messages appear on the console: da0s1: slice starts beyond end of the disk: rejecting it da0s2: slice starts beyond end of the disk: rejecting it da0s3: slice starts beyond end of the disk: rejecting it OK, there is actually no FDISK table, so I get garbage. But there should be some disklabel because from the BSD/OS view the disk has 3 partitions (using BSD/OS naming) sd0a (root partition), sd0b (swap), sd0c (whole disk) and sd0h (/usr). Let's try to read it from FreeBSD: martin@mm0:~# disklabel -r /dev/rda0 # /dev/rda0: type: SCSI disk: QUANTUM FIREBALL label: flags: bytes/sector: 512 sectors/track: 2048 tracks/cylinder: 1 sectors/cylinder: 2048 cylinders: 1223 sectors/unit: 2503872 rpm: 4500 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 131072 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 63) b: 524288 131072 swap # (Cyl. 64 - 319) c: 2503872 0 unused 0 0 # (Cyl. 0 - 1222*) h: 1847296 655360 4.2BSD 1024 8192 16 # (Cyl. 320 - 1221) martin@mm0:~# (again "da0s{1,2,3}: slice starts beyond end of the disk: rejecting it" on the console) It looks good, doesn't it? Exactly what I've expected (except for the "slice starts beyond end of the disk" messages). Let's try to mount the 'a' partition (first readonly): martin@mm0:~# mount -o ro /dev/da0a /mnt mount: /dev/da0a on /mnt: incorrect super block martin@mm0:~# (again "da0s{1,2,3}: slice starts beyond end of the disk: rejecting it" on the console) No luck. Hmm, maybe it should be da0s1a: martin@mm0:~# mount -o ro /dev/da0s1a /mnt mount: /dev/da0s1a on /mnt: incorrect super block martin@mm0:~# (again "da0s{1,2,3}: slice starts beyond end of the disk: rejecting it" on the console) No luck. Whatabout to tell the filesystem type explicitly: martin@mm0:~# mount -t ufs -o ro /dev/da0s1a /mnt mount: /dev/da0s1a on /mnt: incorrect super block martin@mm0:~# (again "da0s{1,2,3}: slice starts beyond end of the disk: rejecting it" on the console) It apears to me that FreeBSD disagrees with BSD/OS on how the superblock should look like because BSD/OS happily boots and runs from the disk. Or am I missing something? Thanks for trying to help, Martin --- [PGP KeyID F3F409C4] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message