Hi, I just installed ovirt version 0.95 and when I start the appliance it panics with the following message: RAMDISK: Couldn't find valid RAM disk image starting at 0. VFS: Cannot open root device "sda2" 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) Is this a known issue and how can I get the appliance to boot up properly? Regards, Dennis
Hi, I get the same problem with version 0.95. Thomas On 11.11.2008, at 19:31, Dennis J. wrote:> Hi, > I just installed ovirt version 0.95 and when I start the appliance > it panics with the following message: > > RAMDISK: Couldn't find valid RAM disk image starting at 0. > VFS: Cannot open root device "sda2" 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) > > Is this a known issue and how can I get the appliance to boot up > properly? > > Regards, > Dennis > > _______________________________________________ > Ovirt-devel mailing list > Ovirt-devel at redhat.com > https://www.redhat.com/mailman/listinfo/ovirt-devel
Hello,> On 11.11.2008, at 20:57, Alan Pevec wrote: > > Thomas von Steiger wrote: > > I get the same problem with version 0.95. > Thomas > On 11.11.2008, at 19:31, Dennis J. wrote: > > Hi, > > I just installed ovirt version 0.95 and when I start the appliance it panics with the following message: > > RAMDISK: Couldn't find valid RAM disk image starting at 0. > VFS: Cannot open root device "sda2" 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) > > Is this a known issue and how can I get the appliance to boot up properly? > > is this i386 or x86_64 ? > > > it's i386.We were also facing the same problem. We solved the problem by recreating the initrd file. Details, 1. mount the ovirt-appliance image # nohup qemu-nbd /var/lib/libvirt/images/ovirt-appliance.img & # modprobe nbd # nbd-client localhost 1024 /dev/nbd0 # kpartx -a /dev/nbd0 # mount /dev/mapper/nbd0p2 /mnt # mount /dev/mapper/nbd0p1 /mnt/boot 2. do a chroot, backup the initrd image and recreate it # chroot /mnt # mv /boot/initrd-2.6.26.6-79.fc9.i686 /root # mkinitrd /boot/initrd-2.6.26.6-79.fc9.i686 2.6.26.6-79.fc9.i686 # exit 3. unmount # umount /mnt # kpartx -d /dev/nbd0 # nbd-client -d /dev/nbd0 4. boot the machine # virsh start ovirt-appliance It solved our problem. ref: http://ovirt.org/page/TroubleShooting Vignesh
Hello,> On 11.11.2008, at 20:57, Alan Pevec wrote: > > Thomas von Steiger wrote: > > I get the same problem with version 0.95. > Thomas > On 11.11.2008, at 19:31, Dennis J. wrote: > > Hi, > > I just installed ovirt version 0.95 and when I start the appliance it panics with the following message: > > RAMDISK: Couldn't find valid RAM disk image starting at 0. > VFS: Cannot open root device "sda2" 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) > > Is this a known issue and how can I get the appliance to boot up properly? > > is this i386 or x86_64 ? > > > it's i386.We were also facing the same problem. We solved the problem by recreating the initrd file. Details, 1. mount the ovirt-appliance image # nohup qemu-nbd /var/lib/libvirt/images/ovirt-appliance.img & # modprobe nbd # nbd-client localhost 1024 /dev/nbd0 # kpartx -a /dev/nbd0 # mount /dev/mapper/nbd0p2 /mnt # mount /dev/mapper/nbd0p1 /mnt/boot 2. do a chroot, backup the initrd image and recreate it # chroot /mnt # mv /boot/initrd-2.6.26.6-79.fc9.i686 /root # mkinitrd /boot/initrd-2.6.26.6-79.fc9.i686 2.6.26.6-79.fc9.i686 # exit 3. unmount # umount /mnt # kpartx -d /dev/nbd0 # nbd-client -d /dev/nbd0 4. boot the machine # virsh start ovirt-appliance It solved our problem. ref: http://ovirt.org/page/TroubleShooting Vignesh
(forgot to reply all) On Fri, Nov 28, 2008 at 1:44 PM, Alan Pevec <apevec at gmail.com> wrote:> On Fri, Nov 28, 2008 at 1:23 PM, Vigneswaran R <vignesh at atc.tcs.com>wrote: > >> We were also facing the same problem. We solved the problem by >> recreating the initrd file. >> >> Details, >> >> 1. mount the ovirt-appliance image >> >> # nohup qemu-nbd /var/lib/libvirt/images/ovirt-appliance.img & >> # modprobe nbd >> # nbd-client localhost 1024 /dev/nbd0 >> # kpartx -a /dev/nbd0 >> # mount /dev/mapper/nbd0p2 /mnt >> # mount /dev/mapper/nbd0p1 /mnt/boot >> >> 2. do a chroot, backup the initrd image and recreate it >> >> # chroot /mnt >> # mv /boot/initrd-2.6.26.6-79.fc9.i686 /root >> # mkinitrd /boot/initrd-2.6.26.6-79.fc9.i686 2.6.26.6-79.fc9.i686 >> # exit >> >> 3. unmount >> >> # umount /mnt >> # kpartx -d /dev/nbd0 >> # nbd-client -d /dev/nbd0 >> >> 4. boot the machine >> >> # virsh start ovirt-appliance >> >> >> It solved our problem. >> >> ref: http://ovirt.org/page/TroubleShooting >> >> > Excellent, thanks for solving this! > It's strange that appliance-creator produced broken i386 initrd while > x86_64 is ok and there were no errors reported in the build log. I'll take > special care of i386 when doing the next build. > > Cheers, > Alan > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/ovirt-devel/attachments/20081128/7964548d/attachment.htm>