Activity log for bug #1326199

Date Who What changed Old value New value Message
2014-06-04 03:10:47 Anton Blanchard bug added bug
2014-06-04 03:12:08 Anton Blanchard tags ppc64el
2014-06-04 03:13:26 Adam Conrad affects initramfs-tools initramfs-tools (Ubuntu)
2014-06-04 03:13:26 Adam Conrad initramfs-tools (Ubuntu): assignee Adam Conrad (adconrad)
2014-06-04 03:13:49 Adam Conrad nominated for series Ubuntu Trusty
2014-06-04 03:13:49 Adam Conrad bug task added initramfs-tools (Ubuntu Trusty)
2014-06-04 03:14:01 Adam Conrad initramfs-tools (Ubuntu Trusty): assignee Adam Conrad (adconrad)
2014-06-04 04:03:47 Adam Conrad initramfs-tools (Ubuntu): status New In Progress
2014-06-04 04:03:50 Adam Conrad initramfs-tools (Ubuntu Trusty): status New In Progress
2014-06-04 04:23:45 Adam Conrad description After installing Trusty on a ppc64el box, each boot drops into a shell because we aren't waiting long enough for the root device: Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/disk/by-uuid/d55ef64e-2d0c-4a51-9c6f-20999ee0276e does not exist. Dropping to a shell! The dmesg shows the device appeared at 49 seconds: [ 49.367749] sdb: sdb1 sdb2 sdb3 I could fix this by overriding ROOTDELAY on the command line: rootdelay=180 Could we get ROOTDELAY in initramfs-tools bumped for ppc64el? [Impact] See original description. [Test Case] Install updated packages on an affected ppc machine, update-initramfs -u, reboot without any special rootdelay set on the cmdline, watch it not fail to boot. [Regression Potential] This is already tested locally by Anton, so barring me having made a typo in the uploaded version, the potential for new bugs is pretty much nil. Bumping the rootdelay to 180 (from 30) could be seen as a regression in itself, as people who are legitimately failing to find a root device will have to wait that much longer to get dropped to a shell to investigate, which is why I limited the fix to PPC only for now. [Other Info] A better long-term fix would be to make scripts/local (or wait-for-root) a bit smarter and learn about specific driver quirks and multipath devices, etc, as IPR controllers can't be the only place we see this bug, and it would be nice to have backoff in cases where we expect delays, but quicker failure modes in cases when we don't. [Original Description] After installing Trusty on a ppc64el box, each boot drops into a shell because we aren't waiting long enough for the root device: Gave up waiting for root device. Common problems:  - Boot args (cat /proc/cmdline)    - Check rootdelay= (did the system wait long enough?)    - Check root= (did the system wait for the right device?)  - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/disk/by-uuid/d55ef64e-2d0c-4a51-9c6f-20999ee0276e does not exist. Dropping to a shell! The dmesg shows the device appeared at 49 seconds: [ 49.367749] sdb: sdb1 sdb2 sdb3 I could fix this by overriding ROOTDELAY on the command line: rootdelay=180 Could we get ROOTDELAY in initramfs-tools bumped for ppc64el?
2014-06-04 05:56:11 Launchpad Janitor initramfs-tools (Ubuntu): status In Progress Fix Released
2014-06-04 14:00:04 Stéphane Graber initramfs-tools (Ubuntu Trusty): status In Progress Fix Committed
2014-06-04 14:00:06 Stéphane Graber bug added subscriber Ubuntu Stable Release Updates Team
2014-06-04 14:00:11 Stéphane Graber bug added subscriber SRU Verification
2014-06-04 14:00:13 Stéphane Graber tags ppc64el ppc64el verification-needed
2014-06-06 02:59:18 Anton Blanchard tags ppc64el verification-needed ppc64el verification-done
2014-06-09 21:13:36 Breno Leitão initramfs-tools (Ubuntu Trusty): status Fix Committed Fix Released
2014-06-11 16:08:14 Scott Kitterman removed subscriber Ubuntu Stable Release Updates Team
2015-08-16 12:32:23 Launchpad Janitor branch linked lp:ubuntu/initramfs-tools