bturrie
February 14th, 2011, 01:39 PM
My system won't boot unless I have 2 sata drives. It doesn't matter what's on the second one. It even boots if the second "disk" is a powered sata to IDE adapter attached to an unpowered IDE drive.
If I don't have the second drive I get this when I try to boot:
Alert! /dev/disk/by-uuid/ ...<your UUID>.... does not exist
which as best I can tell from other posts, is a kernel problem. If it helps, the UUID in question is for sda5 and is present.
I don't see anything that seems odd to me in my /etc/fstab file.
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
/dev/sda1 / ext4 errors=remount-ro 0 1
# /home was on /dev/sda5 during installation---this is the uuid of sda5
UUID=e261d2a4-0d80-4746-9bf9-b74a9bc36ef8 /home ext4 defaults 0 2
# swap was on /dev/sda6 during installation--this is the uuid of sda6
UUID=92ce5628-9764-4425-a174-c7b2c6866665 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
/dev/sda3 /media/secondhome ext4 defaults 0 0
I've done the whole use a live disk, chroot into my system and reinstall the kernel to no avail.
uname -r gives -- 2.6.32-28-generic
Any suggestions other than leaving in the second drive and hoping the next kernel update fixes things?
And, um I haven't filed a bug report yet.
If I don't have the second drive I get this when I try to boot:
Alert! /dev/disk/by-uuid/ ...<your UUID>.... does not exist
which as best I can tell from other posts, is a kernel problem. If it helps, the UUID in question is for sda5 and is present.
I don't see anything that seems odd to me in my /etc/fstab file.
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
/dev/sda1 / ext4 errors=remount-ro 0 1
# /home was on /dev/sda5 during installation---this is the uuid of sda5
UUID=e261d2a4-0d80-4746-9bf9-b74a9bc36ef8 /home ext4 defaults 0 2
# swap was on /dev/sda6 during installation--this is the uuid of sda6
UUID=92ce5628-9764-4425-a174-c7b2c6866665 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
/dev/sda3 /media/secondhome ext4 defaults 0 0
I've done the whole use a live disk, chroot into my system and reinstall the kernel to no avail.
uname -r gives -- 2.6.32-28-generic
Any suggestions other than leaving in the second drive and hoping the next kernel update fixes things?
And, um I haven't filed a bug report yet.