GEOM problems when installing 5.0-RELEASE
Hi all, please point me to the right list if this isn't the right one, but I'm running into what appears to be GEOM trouble when installing 5.0-RELEASE. [btw, the below uses MSDOS terminology for partitions, sorry] The setup is a fairly straight athlon 700 with IDE 2 harddisks, a primary master of 13 G and primary slave of 6 G. BIOS detects both fine, I have Windows XP installed in the first primary partion of ad0, and an extra FAT logical partition in the extended partion on the same drive, resulting in ad0s1, ad0s2 and ad0s5. This disk is fine. The other however, is not. I first tried to install FreeBSD when I still had a primary FAT partition with Win98 on it. Booting from floppy doing an FTP install went fine, but on reboot, the kernel couldn't mount the root partition. Even worse, after rebooting in XP, it turned out that my Win98 partition was unrecognizable (fortunately nothing was lost). I thought it might be due to my 'unusual' (for me) setup of having 2 primary partitions, 1 win98 and 1 BSD, so I tried again, this time allocating the whole 6 G disk to BSD. Retried the install, once again went fine until the reboot, when the kernel still couldn't find the root partition. Handtyping ad1s1 didn't work, ad1 wasn't listed in the boot devices list, no go. I booted from floppy once again and tried the fixit floppy. And I think I found out where the problem was (forgive any typos, this is transcribed as I don't have a serial console): Fixit# ls -l /dev/ad* crw-r- 1 root operator4, 4 Mar 3 20:07 /dev/ad0 crw-r- 1 root operator4, 5 Mar 3 20:07 /dev/ad0s1 crw-r- 1 root operator4, 6 Mar 3 20:07 /dev/ad0s2 crw-r- 1 root operator4, 8 Mar 3 20:07 /dev/ad0s5 crw-r- 1 root operator4, 7 Mar 3 20:07 /dev/ad1 There is no ad1s1 device! No wonder the kernel can't find it's root if it doesn't detect the correct partition. Am I doing something wrong here? Unfortunately I'm not able to get at sysctl output so I can't find GEOM debugging output there. Is there any way I can provide more information on this? Has anyone else run into this? --Stijn -- Fairy tales do not tell children that dragons exist. Children already know dragons exist. Fairy tales tell children the dragons can be killed. -- G.K. Chesterton pgp0.pgp Description: PGP signature
Re: GEOM problems?
In message [EMAIL PROTECTED], Brian F. Feldman writes: All the partitions do mount and seem to work OK, so I'm not sure how much of this is expected behavior. Are you using dangerously-dedicated disks? That is, no fdisk-style partition table? If so, disklabel on ad0 or ad2 itself would be valid. No, GEOM is a strictly stacking system, so in that case the disklabel would be on ad0c and ad2c -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GEOM problems?
Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], walt writes: #disklabel ad0 disklabel: ioctl DIOCGDINFO: Operation not supported by device ad0 does not have a disklabel. Okay, next problem(?). Disklabel with and without the -r flag: #disklabel -r ad2s2 #size offsetfstype [fsize bsize bps/cpg] a: 17207240 77738354.2BSD0 0 0 # (Cyl. 483*- 1554*) b: 40 7373835 swap # (Cyl. 459 - 483*) c: 17607240 7373835unused0 0# (Cyl. 459 - 1554) Warning, partition c doesn't start at 0! Warning, partition c doesn't cover the whole unit! Warning, An incorrect partition c may cause problems for standard system utilities Warning, partition d: size 0, but offset 7373835 Warning, partition e: size 0, but offset 7373835 Warning, partition f: size 0, but offset 7373835 Warning, partition g: size 0, but offset 7373835 Warning, partition h: size 0, but offset 7373835 #disklabel ad2s2 #size offsetfstype [fsize bsize bps/cpg] a: 17207240 404.2BSD0 0 0 # (Cyl. 24*- 1095*) b: 400 swap # (Cyl.0 - 24*) c: 176072400unused0 0# (Cyl.0 - 1095) Warning, partition c doesn't cover the whole unit! This behavior is new with GEOM, as is the warning about c not covering the whole unit. The kernel without GEOM offers no complaints about the same label. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GEOM problems?
In message [EMAIL PROTECTED], walt writes: #disklabel -r ad2s2 #size offsetfstype [fsize bsize bps/cpg] a: 17207240 77738354.2BSD0 0 0 # (Cyl. 483*- 1554*) #disklabel ad2s2 #size offsetfstype [fsize bsize bps/cpg] a: 17207240 404.2BSD0 0 0 # (Cyl. 24*- 1095*) This behavior is new with GEOM, as is the warning about c not covering the whole unit. The kernel without GEOM offers no complaints about the same label. This is because the old code would lie to you if you tried to read the disklabel directly off the media instead of using the ioctl() calls. I feel it is fundamentally wrong to modify data in-band this way without telling the user. Therefore I have not implemented it in GEOM. For reasons I have never fully accepted, the BSD disklabel is written to represent the entire physical disk so the ondisk information does not actually list partition 'c' as starting on sector zero, rather it lists the physical sector number (which corresponds to the start sector of that slice). The way GEOM deals with BSD labels, it will try to identify such a magic offset and correctly DTRT, but it will also accept un-offset ondisk disklabels, which I hope we can migrate to now. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GEOM problems?
On 06.10-06:43, walt wrote: Okay, next problem(?). Disklabel with and without the -r flag: don't know if it is a problem or not but i found that doing a null edit on the disk to make GEOM rewrite it's information to the disk eliminated the messages. -- t t z msg44110/pgp0.pgp Description: PGP signature
GEOM problems?
Just finished making world and kernel at about 01:00 GMT Oct 6. dmesg includes this printout: Initializing GEOMetry subsystem ad0: 76319MB ST380021A [155061/16/63] at ata0-master UDMA100 ad2: 42934MB WDC WD450AA-00BAA0 [87233/16/63] at ata1-master UDMA66 acd0: CD-RW R/RW 4x4x24 at ata1-slave PIO4 Mounting root from ufs:/dev/ad2s2a 00 01 c1 ff 83 fe ff ff 3f 00 00 00 06 5b 5f 00 |?[_.| [0] f:00 typ:131 s(CHS):255/1/193 e(CHS):255/254/255 s:63 l:6249222 00 00 c1 ff 05 fe ff ff 45 5b 5f 00 b3 f1 5a 00 |E[_...Z.| [1] f:00 typ:5 s(CHS):255/0/193 e(CHS):255/254/255 s:6249285 l:5960115 00 01 c1 ff 07 fe ff ff 3f 00 00 00 74 f1 5a 00 |?...t.Z.| [0] f:00 typ:7 s(CHS):255/1/193 e(CHS):255/254/255 s:63 l:5960052 00 00 c1 ff 05 fe ff ff f8 4c ba 00 e2 05 18 00 |.L..| [1] f:00 typ:5 s(CHS):255/0/193 e(CHS):255/254/255 s:12209400 l:1574370 many more lines snipped Is this normal output now? And there's this: #disklabel ad0 disklabel: ioctl DIOCGDINFO: Operation not supported by device #disklabel -r ad0 disklabel: bad pack magic number (label is damaged, or pack is unlabeled) Same errors with ad2. All the partitions do mount and seem to work OK, so I'm not sure how much of this is expected behavior. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GEOM problems?
walt [EMAIL PROTECTED] wrote:
Just finished making world and kernel at about 01:00 GMT Oct 6.
dmesg includes this printout:
Initializing GEOMetry subsystem
ad0: 76319MB ST380021A [155061/16/63] at ata0-master UDMA100
ad2: 42934MB WDC WD450AA-00BAA0 [87233/16/63] at ata1-master UDMA66
acd0: CD-RW R/RW 4x4x24 at ata1-slave PIO4
Mounting root from ufs:/dev/ad2s2a
00 01 c1 ff 83 fe ff ff 3f 00 00 00 06 5b 5f 00 |?[_.|
[0] f:00 typ:131 s(CHS):255/1/193 e(CHS):255/254/255 s:63 l:6249222
00 00 c1 ff 05 fe ff ff 45 5b 5f 00 b3 f1 5a 00 |E[_...Z.|
[1] f:00 typ:5 s(CHS):255/0/193 e(CHS):255/254/255 s:6249285 l:5960115
00 01 c1 ff 07 fe ff ff 3f 00 00 00 74 f1 5a 00 |?...t.Z.|
[0] f:00 typ:7 s(CHS):255/1/193 e(CHS):255/254/255 s:63 l:5960052
00 00 c1 ff 05 fe ff ff f8 4c ba 00 e2 05 18 00 |.L..|
[1] f:00 typ:5 s(CHS):255/0/193 e(CHS):255/254/255 s:12209400 l:1574370
many more lines snipped
Is this normal output now?
Sounds like debugging prints that should probably not be enabled by
default...
And there's this:
#disklabel ad0
disklabel: ioctl DIOCGDINFO: Operation not supported by device
#disklabel -r ad0
disklabel: bad pack magic number (label is damaged, or pack is unlabeled)
Same errors with ad2.
All the partitions do mount and seem to work OK, so I'm not sure how
much of this is expected behavior.
Are you using dangerously-dedicated disks? That is, no fdisk-style
partition table? If so, disklabel on ad0 or ad2 itself would be valid. It
doesn't appear you are, in which case a disklabel operation should be
performed on the slice, e.g. disklabel ad2s2.
--
Brian Fundakowski Feldman \'[ FreeBSD ]''\
[EMAIL PROTECTED] [EMAIL PROTECTED] \ The Power to Serve! \
Opinions expressed are my own. \,,\
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: GEOM problems?
In message [EMAIL PROTECTED], walt writes: Just finished making world and kernel at about 01:00 GMT Oct 6. dmesg includes this printout: Initializing GEOMetry subsystem ad0: 76319MB ST380021A [155061/16/63] at ata0-master UDMA100 ad2: 42934MB WDC WD450AA-00BAA0 [87233/16/63] at ata1-master UDMA66 acd0: CD-RW R/RW 4x4x24 at ata1-slave PIO4 Mounting root from ufs:/dev/ad2s2a 00 01 c1 ff 83 fe ff ff 3f 00 00 00 06 5b 5f 00 |?[_.| [0] f:00 typ:131 s(CHS):255/1/193 e(CHS):255/254/255 s:63 l:6249222 00 00 c1 ff 05 fe ff ff 45 5b 5f 00 b3 f1 5a 00 |E[_...Z.| [1] f:00 typ:5 s(CHS):255/0/193 e(CHS):255/254/255 s:6249285 l:5960115 00 01 c1 ff 07 fe ff ff 3f 00 00 00 74 f1 5a 00 |?...t.Z.| [0] f:00 typ:7 s(CHS):255/1/193 e(CHS):255/254/255 s:63 l:5960052 00 00 c1 ff 05 fe ff ff f8 4c ba 00 e2 05 18 00 |.L..| [1] f:00 typ:5 s(CHS):255/0/193 e(CHS):255/254/255 s:12209400 l:1574370 many more lines snipped Is this normal output now? Yes, but not for long, its a debug printf that has slipped through. And there's this: #disklabel ad0 disklabel: ioctl DIOCGDINFO: Operation not supported by device ad0 does not have a disklabel. Same errors with ad2. Same diagnosis. Typically you will find that devices with disklabels are named ad%ds%d All the partitions do mount and seem to work OK, so I'm not sure how much of this is expected behavior. All of it :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
