[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: where did my ata drives go?



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.
>>
>> If that works, issue
>> 
>>    umount /hd0
>>    mount -t ext3 /dev/disk/by-uuid/03c23684-dea8-458d-b04b-0ae8a056cb0d /hd0
> 
> mount: special device /dev/disk/by-uuid/03c23684-dea8-458d-b04b-0ae8a056cb0d does not exist
>> 
>> and see if that works.  If that works, try
>> 
>>    umount /hd0
>>    mount -t ext3 /dev/disk/by-label/hdb1
> 
> (assuming you inadvertanly left off the /hd0 from the mount command)
>

Correct.  Sorry.
> 
> mount: special device /dev/disk/by-label/hdb1 does not exist
>>
>> 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

>> Which of the above work, and which do not?  What do you see when you issue
>> 
>>    cat /proc/partitions
> 
>    8        0  244198584 sda
>    8        1    1951866 sda1
>    8        2      64260 sda2
>    8        3    2931862 sda3
>    8        4  239248012 sda4
>    8       16  976762584 sdb
>    8       17  976760001 sdb1
>    8       32   39082680 sdc
>    8       33   19535008 sdc1
>    8       34          1 sdc2
>    8       37   19535008 sdc5
>    8       48  244198584 sdd
>    8       49  244196001 sdd1
>  254        0    1048576 dm-0
>  254        1   20971520 dm-1
>  254        2   41943040 dm-2
>  254        3  125829120 dm-3
>  254        4   20971520 dm-4
> 
> That's how I found out about /dev/sdc1 and /dev/sdc5.

OK, this looks like a udev problem of some sort.  The udev aliases
are not being created.  I'm not sure why yet.  The first thing I would
try would be to re-build the initial RAM file system:

update-initramfs -uk `uname -r`

Then shutdown and reboot.  If you're lucky, that will fix the problem.
Be sure to issue this command while you're running your new kernel,
not the old one.  By the way, what boot loader do you use?

> 
> Would I be correct in thinking that hard coding /dev/sdc1 and /dev/sdc5
> in /etc/fstab would not be reliable since those might point to different
> devices on subsequent boots?

That depends.  The device name assignment is not likely to change unless
you install or remove a hard drive, as long as you only run the new kernel.
But of course, if you boot your old kernel, which uses different device
names, this will fail.

-- 
  .''`.     Stephen Powell    
 : :'  :
 `. `'`
   `-


Reply to: