Unable to mount root fs on unknown-block(202,3)
Luciano Rocha
strange at nsk.no-ip.org
Fri Oct 12 05:02:33 PDT 2007
On Fri, Oct 12, 2007 at 11:53:20AM +0530, Rajeev Bansal wrote:
> Hello All,
>
> I am trying to build a custom initrd using the busybox. In my initrd I
> have modified the /sbin/init to a init script which I am mentioning below,
Initramfs uses /init, not /sbin/init (that's old-style initrd, where it
is a filesystem image).
<snip>
> checking if image is initramfs...<6>Switched to high resolution mode on
> CPU 0
> it is
</snip>
Well, the kernel believes it is an initramfs archive, but you didn't put
a /init there.
<snip>
> VFS: Cannot open root device "<NULL>" or unknown-block(202,3)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(202,3)
</snip>
It ended up trying to mount the block-major 202, which belongs to Xen
(xvda3).
--
lfr
0/0
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://busybox.net/lists/busybox/attachments/20071012/4be13008/attachment.pgp
More information about the busybox
mailing list