Ken Bolingbroke
2006-Jan-29 20:57 UTC
Have the device names for hard discs been changed? (fwd)
On Sun, 29 Jan 2006, Christian Baer wrote:> ... > After that I started sysinstall and created a new slice and a new > partition which sysinstall called /dev/ad6s1d - which I expected. But > after creating the partition, the mount failed, because "no such file or > directory". And sure enough, ad6s1d did not exist in /dev/: > > jon# ls -l /dev/ad6* > crw-r----- 1 root operator 0, 76 Jan 22 15:23 /dev/ad6 > crw-r----- 1 root operator 0, 93 Jan 22 15:00 /dev/ad6c > crw-r----- 1 root operator 0, 96 Jan 22 15:00 /dev/ad6cs1 > crw-r----- 1 root operator 0, 92 Jan 22 15:00 /dev/ad6s1 > crw-r----- 1 root operator 0, 94 Jan 22 15:00 /dev/ad6s1cAll the other responses on this thread are confusing the 'c' in here with the normal bsdlabel slice 'c' that covers the whole partition. This is something entirely different, a bug in sysinstall... You start out with a disk, /dev/ad6, and you "dangerously dedicate" it, then you _should_ have 's1' appended to /dev/ad6 to make /dev/ad6s1. But for some reason, it's appending it to /dev/ad6c instead to make /dev/ad6cs1, and then sysinstall tries to label the disk with /dev/ad6cs1c, etc, and fails. (Note the _two_ 'c' characters in that device name) My work around so far is after using fdisk in sysinstall to "dangerously dedicate" my disk, I exit, then "rm /dev/ad6cs1", then go back to sysinstall and label the disk, and then it will correctly use /dev/ad6s1. If I find some time, I might see how to submit a bug report on this... Ken
Daniel O'Connor
2006-Jan-29 22:21 UTC
Have the device names for hard discs been changed? (fwd)
On Monday 30 January 2006 15:27, Ken Bolingbroke wrote:> You start out with a disk, /dev/ad6, and you "dangerously dedicate" it, > then you _should_ have 's1' appended to /dev/ad6 to make /dev/ad6s1. But > for some reason, it's appending it to /dev/ad6c instead to make > /dev/ad6cs1, and then sysinstall tries to label the disk with /dev/ad6cs1c, > etc, and fails. (Note the _two_ 'c' characters in that device name) > > My work around so far is after using fdisk in sysinstall to "dangerously > dedicate" my disk, I exit, then "rm /dev/ad6cs1", then go back to > sysinstall and label the disk, and then it will correctly use /dev/ad6s1.If you're using 5.x or 6.x which have devfs, it would point to a bug in geom (or somewhere in the kernel anyway) as the device names are generated inside the kernel. Personally I'd just stick to not using dangerously dedicated. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20060130/28db3f8a/attachment.bin