[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Why I can not boot xen without initrd? Please help.


  • To: "kanour-xen" <xen@xxxxxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Nico Kadel-Garcia" <nkadel@xxxxxxxxx>
  • Date: Fri, 23 Feb 2007 00:23:01 -0000
  • Delivery-date: Thu, 22 Feb 2007 16:22:20 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:from:to:references:subject:date:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole; b=mTC+ZT+0P2fRsXXLYPuGPtMMBDfOlMD253mIpPG0wPbOccpy4GyPm7mCsLoXrPWh02ELJhDnl7HFjawx5u8cR0U7n5dH/oHsRv5wi1EBZyR+SGpvoPi1t5B3Zd7yZyUjszqHqCeKVI2lJM8wHUq+SF1Q0AuWaFnHqt60KMASwk8=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

kanour-xen wrote:
Hi.

I have SATA HDDs in software raid1 (mdadm). debian amd64
Why I cannot boot xen without initrd?
I get error:
VFS: Cannot open root device "md2" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)

Thank you for any help. I am getting crazy about this.

Well, let's see. Because the RAID, SATA, ext3, or other drivers were not hard-loaded into your kernel, but need to be present in an initrd to provide enough access to your file-system for you to boot?

The practice of preloading drivers versus module loading them, and usiing initrd to pre-loading modules, is an old well worth studying a bit about.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.