Re: 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/ad6s1c

All 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
_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Problem adding new slices
    ... I suspect I will not be the one to find anything, ... Ran sysinstall again. ... It was at this point that I tried to mount the partition, which failed with an incorrect super block error. ... Then it occurred to me that I never actually saw newfs run from sysinstall like it usually does during a fresh install or adding a new disk. ...
    (freebsd-stable)
  • releng_6 sysinstall creating labels
    ... While having a (SCSI) disk outage yesterday night, ... After labeling it by using sysinstall, ... After that I found that sysinstall created a partition which exceeded ... past the end of the slice, but my memories might be wrong. ...
    (freebsd-stable)
  • Re: input/output error on hd
    ... I tried deleting and recreating the one slice on that drive in sysinstall, ... BIOS sector numbering starts with sector 1 ... The data for partition 1 is: ...
    (freebsd-questions)
  • Re: diskLabelCommit fails within a sysinstall script?
    ... sysinstall, but I don't seem to be getting this right. ... diskPartitionEditor ... I don't know about all you ask, but the 'c' partition should always ... the size be the size of the slice. ...
    (freebsd-questions)
  • Re: Different sysinstall labelling behaviour when run post-install vs. during install?
    ... > Yesterday I was upgrading the disk in one of my workstations. ... > but ran into a problem: sysinstall doesn't allocate the partition letters, ... filesystems to go inside those partitions. ...
    (freebsd-questions)