On Sat, Nov 27, 2010 at 6:59 AM, Mick <michaelkintz...@gmail.com> wrote: > I haven't had much luck with the 2.6.35 version of kernels - they have > cause panics on two different x86 boxen. > > Now that 2.6.35 has gone stable so I tried it again and I'm getting a > kernel panic complaining about VFS unable to mount root fs: > ================================== > VFS: Cannot open root device "sda3" or unknown-block(0,0) > Please append a correct "root=" boot option; here are the available > partitions: > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) > Pid: 1, comm: swapper Not tainted 2.6.35-gentoo-r12 #2 > Call Trace: > [<c14b3530>] ? panic+0x5f/0xc6 > [<c1693c68>] ? mount_block_root+0x1c2/0x245 > [<c1002930>] ? do_signal+0x766/0x7f2 > [<c1693d31>] ? mount_root+0x46/0x5a > [<c1693e8b>] ? prepare_namespace+0x146/0x182 > [<c1093203>] ? sys_access+0x1f/0x23 > [<c16933f1>] ? kernel_init+0x1a9/0x1b7 > [<c1693248>] ? kernel_init+0x0/0x1b7 > [<c10030b6>] ? kernel_thread_helper+0x6/0x10 > panic occurred, switching back to text console > ================================== <SNIP> > > Am I missing something obvious to make the 2.6.35 series work with my boxen? > > Please ask if you need more info. > -- > Regards, > Mick > >
Hi Mick, OK, there's so many possibilities for what causes this. Basic confusion ensues... 1) When booting, if you look carefully, is the initial kernel seeing _any_ disks? Sometimes they fly bye and are hard to catch. If it is then is it showing sda3? 2) What sort of file system did you put on sda3? I assume this is built into the kernel if this is an upgrade? 3) Post the appropriate part of grub.conf to show how you are booting. 4) Post fstab - Mark
