Kernel Bug Tracker – Bug 37692
Linux 2.6.39.x fails to boot - unable to mount root fs
Last modified: 2011-07-23 15:52:55 UTC
Created attachment 62342 [details]
When I start 2.6.39 or 18.104.22.168 it fails to boot with SATA messages clearly showing that partitions were detected, and "unable to mount root fs"
This does not happen on 2.6.38.x
Can you post a diff of your 2.6.38.x config and the failing config? Also what fs do you have on your root partition and what is your kernel commandline, and what is your disk setup?
Can't honestly get back to the 2.6.38.x config - but I'll keep trying. It's gone. I'm unable to do make oldconfig back to it right now, compiling it stops half way through....
root=UUID=8613a5bc-0ddc-4a8d-b6bd-780faeee25e7 ro vt.handoff=7
I keep getting a "arch/x86/kernel/entry_64.S:1544: Error: .size expression for do_hypervisor_callback does not evaluate to a constant" when I try oldconfig'ing the 2.6.39 one...
Don't know about that. Sorry.
Maybe a copy still lingers in /boot/ ?
Or if you boot on the 2.6.38.x kernel, maybe you have it in /proc/config.gz available (If CONFIG_IKCONFIG_PROC was set at compiletime)
What filesystem do you have on your root-partition? (sorry, I'm still trying to figure out if you set up everything correctly)
The same thing happened on 3.0.
The solution was to set the root=/dev/sdb7 to /dev/sda7 in the grub config. I don't know why it decided on the wrong one. It also doesn't work with UUID like: