On Mon, 2011-09-12 at 09:58 +0200, Cyril Hrubis wrote: > > > * The second problem is that yaboot fails to boot after this change > > > > What do you mean by "yaboot fails to boot"? At which point the boot > > procedure failed? What did you see on the screen? Did you get the yaboot > > prompt at all? If you did, what happened after that? Did you get a shell > > prompt? > > Sorry the description would better be that the kernel failed to find rootfs so > the booting stops in the initramfs (again).
Doesn't that imply that only initramfs-tools is at fault? So long as yaboot loads the kernel and initramfs (if present) at the right places and passes the right information to the kernel, then it has done its job. [...] > > If you do, what 'cat /proc/cmdline' shows? What 'ls -l > > /dev/disk/by-uuid' shows? > > All seems to be in place now. The /proc/cmdline shows root="UUID=58..." ro and > ls /dev/disk/by-uuid shows to UUID and one of them match the root kernel > parameter. > > > What happens if you type "old" at the yaboot prompt after the upgrade? > > Before changing yaboot back to root = "UUID=58..." the boot failed as the > kernel was unable to mount rootfs. After root was set back to the UUID both > old > (2.6.39-2) and the current (3.0.0-1) boots fine (tried several times). So this > must have been some temporal glitch. But if you boot Linux 2.6.39, does the root filesystem show up in /dev/disk/by-uuid? I have a suspicion that it won't. Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity.
signature.asc
Description: This is a digitally signed message part
