> > 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.
Actually that has happend after the initramfs contained the the right modules and the disk was initalized and ready in /dev/. However somehow the kernel was unable to mount the rootfs and I've ended up in the initramfs shell again. Writing yaboot with 'ybin -v' seems to fixed that problem. Which is strange and unexpected, I first thought that the root parameter was wrong, but it works the original config now. Maybe it just needed one more reboot to start working properly. > > 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. It's there, at least after I botted into the 'old' kernel and did 'ls /dev/disk/by-uuid/' I see no difference between 2.6.39 and 3.0.0. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
