Just tried Linux Kernel 3.18.0-031800rc2_3.18.0-031800rc2.201410262035 from the PPA which simply fails to properly boot and falls to a busybox console because for some reason it fails to find the root drive. Considering its an rc2 release it was not unexpected to run into some unrelated issues. FYI the failed boot output was:
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system waut long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/disk/by-uuid/MYROOT-DRIVE-UUID does not exist. Dropping to a shell!
I'm now running 3.17.1-031701_3.17.1-031701.201410150735_all instead. If I don't get the issue I will report back end of next week as it takes a while for it to get triggered.
Just tried Linux Kernel 3.18.0- 031800rc2_ 3.18.0- 031800rc2. 201410262035 from the PPA which simply fails to properly boot and falls to a busybox console because for some reason it fails to find the root drive. Considering its an rc2 release it was not unexpected to run into some unrelated issues. FYI the failed boot output was:
Gave up waiting for root device. Common problems: by-uuid/ MYROOT- DRIVE-UUID does not exist. Dropping to a shell!
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system waut long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/disk/
BusyBox v1.22.1 (Ubuntu 1:1.22.0-8ubuntu1) built-in shell (ash)
I'm now running 3.17.1- 031701_ 3.17.1- 031701. 201410150735_ all instead. If I don't get the issue I will report back end of next week as it takes a while for it to get triggered.