Re: where did my ata drives go?
On Fri, Sep 10, 2010 at 13:13:50 -0400, Stephen Powell wrote:
> On Fri, 10 Sep 2010 12:47:33 -0400 (EDT), Rick Pasotto wrote:
> > On Fri, Sep 10, 2010 at 12:18:07PM -0400, Stephen Powell wrote:
> >> What happens if, after the system has booted,
> >> you issue a manual mount command as root, using the new device
> >> name?
> >>
> >> mount -t ext3 /dev/sdc1 /hd0
> >
> > That works perfectly.
[...]
> >> then try
> >>
> >> umount /hd0
> >> mount -t ext3 UUID=03c23684-dea8-458d-b04b-0ae8a056cb0d /hd0
> >
> > mount: special device UUID=03c23684-dea8-458d-b04b-0ae8a056cb0d does not exist
> >>
> >> then try
> >>
> >> umount /hd0
> >> mount -t ext3 LABEL=hdb1 /hd0
> >
> > mount: special device LABEL=hdb1 does not exist
[...]
> OK, this looks like a udev problem of some sort. The udev aliases
> are not being created. I'm not sure why yet.
My guess would be that blkid does not read the UUID and label of the
partition correctly. AFAIK, udev relies on blkid to obtain the
information that is necessary to populate the /dev/disk/by-label/ and
/dev/disk/by-uuid/ directories. Here is an example of how it should
work:
$ /sbin/blkid /dev/sda5
/dev/sda5: LABEL="root" UUID="d0100d2c-69e9-4a37-bf17-9af5ff151032" TYPE="ext3"
Rick, if "/sbin/blkid /dev/sdc1" fails report anything on your system
then show us the output of:
BLKID_DEBUG=0xffff /sbin/blkid /dev/sdc1
--
Regards, |
Florian |
Reply to: