VFS: Cannot open root device
"disk/by-id/scsi-SATA_WDC_WD1600BEVS-WD-WXEZ07100576-part 7" or
unknown block(0,0)
Please append a correct "root = " boot option; here are the available
partitions.
Pid:1,comm:swapper Not tainted
2.6.26-rt1-default#[email protected]
[< ffff ffff 8046 c149 >] rt_mutex_lock+0x22/0x50
[< ffff ffff 8046 cae6 >] _mutex_unlock+0xe/0x10
[< ffff ffff 8020 cb00 >] exit_intr+0x10/0x1e
[< ffff ffff 8028 633d >] trace_hardirqs_on_caller+0x1e/0x133
[< ffff ffff 8020 d608 >] child_rip+0xa/0x12
[< ffff ffff 8020 cb69 >] restore_args+0x0/0x30
[< ffff ffff 8020 d5fe >] child_rip+0x0/0x12
preempt count 00000001
1-level deep critical section nesting
[< ffff ffff 8047 43e2 >] .... panic +0x43/0x167
[< ffff ffff 8073 6338 >] (<= mount_block_root+0x258/0x26f
On Sat, Aug 2, 2008 at 2:16 PM, John Kacur <[email protected]> wrote:
> VFS: Cannot open root device
> "disk/by-id/scsi-SATA_WDC_WD1600BEVS-WD-WXEZ07100576-part 7" or
> unknown block(0,0)
> Please append a correct "root = " boot option; here are the available
> partitions.
> Pid:1,comm:swapper Not tainted
> 2.6.26-rt1-default#[email protected]
> [< ffff ffff 8046 c149 >] rt_mutex_lock+0x22/0x50
> [< ffff ffff 8046 cae6 >] _mutex_unlock+0xe/0x10
> [< ffff ffff 8020 cb00 >] exit_intr+0x10/0x1e
> [< ffff ffff 8028 633d >] trace_hardirqs_on_caller+0x1e/0x133
> [< ffff ffff 8020 d608 >] child_rip+0xa/0x12
> [< ffff ffff 8020 cb69 >] restore_args+0x0/0x30
> [< ffff ffff 8020 d5fe >] child_rip+0x0/0x12
>
> preempt count 00000001
> 1-level deep critical section nesting
> [< ffff ffff 8047 43e2 >] .... panic +0x43/0x167
> [< ffff ffff 8073 6338 >] (<= mount_block_root+0x258/0x26f
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Hello; I was receiving this last week,
wasn't receving this:
Pid:1,comm:swapper Not tainted
> 2.6.26-rt1-default#[email protected]
> [< ffff ffff 8046 c149 >] rt_mutex_lock+0x22/0x50
> [< ffff ffff 8046 cae6 >] _mutex_unlock+0xe/0x10
> [< ffff ffff 8020 cb00 >] exit_intr+0x10/0x1e
> [< ffff ffff 8028 633d >] trace_hardirqs_on_caller+0x1e/0x133
> [< ffff ffff 8020 d608 >] child_rip+0xa/0x12
> [< ffff ffff 8020 cb69 >] restore_args+0x0/0x30
> [< ffff ffff 8020 d5fe >] child_rip+0x0/0x12
but was having this:
VFS: Cannot open root device
what was causing this is grub from dapper,feisty,etc..
if you compile you're kernel with initrd.img then will work,
but if you: make you're kernel statically(make, make install)
it will produce unable to mount vfs.
downgrade grub or use grub2.
if you've already did that, then I don't know.
regards;
--
Justin P. Mattock
On Sat, 2 Aug 2008, John Kacur wrote:
> VFS: Cannot open root device
Do you use an initrd boot disk? If so make sure the initrd is correct.
Sometimes it is best to first get a 2.6.26 kernel booting without initrd
and then use that same config on the -rt kernel.
-- Steve
> "disk/by-id/scsi-SATA_WDC_WD1600BEVS-WD-WXEZ07100576-part 7" or
> unknown block(0,0)
> Please append a correct "root = " boot option; here are the available
> partitions.
> Pid:1,comm:swapper Not tainted
> 2.6.26-rt1-default#[email protected]
> [< ffff ffff 8046 c149 >] rt_mutex_lock+0x22/0x50
> [< ffff ffff 8046 cae6 >] _mutex_unlock+0xe/0x10
> [< ffff ffff 8020 cb00 >] exit_intr+0x10/0x1e
> [< ffff ffff 8028 633d >] trace_hardirqs_on_caller+0x1e/0x133
> [< ffff ffff 8020 d608 >] child_rip+0xa/0x12
> [< ffff ffff 8020 cb69 >] restore_args+0x0/0x30
> [< ffff ffff 8020 d5fe >] child_rip+0x0/0x12
>
> preempt count 00000001
> 1-level deep critical section nesting
> [< ffff ffff 8047 43e2 >] .... panic +0x43/0x167
> [< ffff ffff 8073 6338 >] (<= mount_block_root+0x258/0x26f
>
On Sat, Aug 2, 2008 at 11:31 PM, Steven Rostedt <[email protected]> wrote:
>
> On Sat, 2 Aug 2008, John Kacur wrote:
>
>> VFS: Cannot open root device
>
> Do you use an initrd boot disk? If so make sure the initrd is correct.
> Sometimes it is best to first get a 2.6.26 kernel booting without initrd
> and then use that same config on the -rt kernel.
>
> -- Steve
Thanks Justin and Steve for the hints - it turned out to be simple,
somehow the make install scripts were mangling the location of the
initrd, a quick edit to grub and everything is working again.
John
>
>> "disk/by-id/scsi-SATA_WDC_WD1600BEVS-WD-WXEZ07100576-part 7" or
>> unknown block(0,0)
>> Please append a correct "root = " boot option; here are the available
>> partitions.
>> Pid:1,comm:swapper Not tainted
>> 2.6.26-rt1-default#[email protected]
>> [< ffff ffff 8046 c149 >] rt_mutex_lock+0x22/0x50
>> [< ffff ffff 8046 cae6 >] _mutex_unlock+0xe/0x10
>> [< ffff ffff 8020 cb00 >] exit_intr+0x10/0x1e
>> [< ffff ffff 8028 633d >] trace_hardirqs_on_caller+0x1e/0x133
>> [< ffff ffff 8020 d608 >] child_rip+0xa/0x12
>> [< ffff ffff 8020 cb69 >] restore_args+0x0/0x30
>> [< ffff ffff 8020 d5fe >] child_rip+0x0/0x12
>>
>> preempt count 00000001
>> 1-level deep critical section nesting
>> [< ffff ffff 8047 43e2 >] .... panic +0x43/0x167
>> [< ffff ffff 8073 6338 >] (<= mount_block_root+0x258/0x26f
>>
>
>
On Sat, Aug 2, 2008 at 3:24 PM, John Kacur <[email protected]> wrote:
> On Sat, Aug 2, 2008 at 11:31 PM, Steven Rostedt <[email protected]> wrote:
>>
>> On Sat, 2 Aug 2008, John Kacur wrote:
>>
>>> VFS: Cannot open root device
>>
>> Do you use an initrd boot disk? If so make sure the initrd is correct.
>> Sometimes it is best to first get a 2.6.26 kernel booting without initrd
>> and then use that same config on the -rt kernel.
>>
>> -- Steve
>
> Thanks Justin and Steve for the hints - it turned out to be simple,
> somehow the make install scripts were mangling the location of the
> initrd, a quick edit to grub and everything is working again.
> John
>
>>
>>> "disk/by-id/scsi-SATA_WDC_WD1600BEVS-WD-WXEZ07100576-part 7" or
>>> unknown block(0,0)
>>> Please append a correct "root = " boot option; here are the available
>>> partitions.
>>> Pid:1,comm:swapper Not tainted
>>> 2.6.26-rt1-default#[email protected]
>>> [< ffff ffff 8046 c149 >] rt_mutex_lock+0x22/0x50
>>> [< ffff ffff 8046 cae6 >] _mutex_unlock+0xe/0x10
>>> [< ffff ffff 8020 cb00 >] exit_intr+0x10/0x1e
>>> [< ffff ffff 8028 633d >] trace_hardirqs_on_caller+0x1e/0x133
>>> [< ffff ffff 8020 d608 >] child_rip+0xa/0x12
>>> [< ffff ffff 8020 cb69 >] restore_args+0x0/0x30
>>> [< ffff ffff 8020 d5fe >] child_rip+0x0/0x12
>>>
>>> preempt count 00000001
>>> 1-level deep critical section nesting
>>> [< ffff ffff 8047 43e2 >] .... panic +0x43/0x167
>>> [< ffff ffff 8073 6338 >] (<= mount_block_root+0x258/0x26f
>>>
>>
>>
>
Cool;
yeah last week this happened as well
to me, something so simple. causing me
to run around freaking out.
regards;
--
Justin P. Mattock