is this still an issue with recent releases?
** Summary changed:
- Problem booting raid 1 since upgrading to intrepid (uuid missing)
+ /dev/disk/by-uuid not set up reliably
** Description changed:
+ ( since upgrading to intrepid )
+
When booting, the system cannot find the /dev/disk-by-uuid for the root
fs, and drops me to busybox. On checking
/dev/disk-by-uuid is missing the UUID symlink for my raid 1 root,
however the raid is up and running and available on /dev/md0
This has happened during a few reboots recently, and I have had to pull
the machine from the cupboard to see why it wasnt booting. Normally a
few resets and eventually it will work. I have a longer than needed
rootdelay too, but this does not seem the factor since if i set my grub
to boot from /dev/md0 everything is fine. just when it is set to the
raid 1 fs uuid I get the problem
Current the raid is in degraded mode, but this has happened recently the
raid was not degraded also.
** Summary changed:
- /dev/disk/by-uuid not set up reliably
+ /dev/disk/by-uuid not set up reliably (sometimes boot is failing)
** Changed in: mdadm (Ubuntu)
Status: New => Incomplete
--
/dev/disk/by-uuid not set up reliably (sometimes boot is failing)
https://bugs.launchpad.net/bugs/298481
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
