On Tue, 2011-05-17 at 16:48 +0100, Bei Guan wrote:
>
>
> 2011/5/17 Ian Campbell <
Ian.Campbell@xxxxxxxxxx>
>
> On Tue, 2011-05-17 at 16:27 +0100, Bei Guan wrote:
> >
> >
> > 2011/5/17 Konrad Rzeszutek Wilk <
konrad.wilk@xxxxxxxxxx>
> > > menuentry "Ubuntu_Xen 4.2 (2.6.32.28)" {
> > > recordfail
> > > insmod ext2
> > > set root='(hd0,9)'
> > > search --no-floppy --fs-uuid --set
> > 59c64afa-47a8-4a5f-a4cf-dbe3be20cc15
> > > multiboot /boot/xen.gz dom0_mem=1024M
> loglvl=all
> > guest_loglvl=all
> > > sync_console console_to_ring com1=115200,8n1
> console=com1
> > lapic=debug
> > > apic_verbosity=debug apic=debug iommu=off
> > > module /boot/vmlinuz-2.6.32.28 nopat
> > > root=UUID=59c64afa-47a8-4a5f-a4cf-dbe3be20cc15 ro
> > console=tty0
> > > console=ttyS0,115200n8 console=hvc0
> earlyprintk=xen
> > nomodeset initcall_debug
> > > debug loglevel=10
> > > module /boot/initrd.img-2.6.32.28
> > > }
> > >
> > > In the debug, there is message like this:
> > >
> > > Loading, please wait...
> > > mount: mounting none on /dev failed: No such
> device
> >
> >
> >
> > So your /dev/sda is being seen. Not sure why the
> UUID hasn't
> > been read, but
> > you could do 'root=/dev/sdaX' where X is the correct
> root
> > partition.
> >
> > This would replace the 'UUID=59...'.
> >
> > I just tried this. Because the /dev/sda9 is the root fs, so
> I used
> > 'root=/dev/sda9' to replace the original one. But it also
> the same
> > error as the following. Detailed is also attached.
> >
> >
> > Loading, please wait...
> > mount: mounting none on /dev failed: No such device
>
>
> This is trying to mount something on /dev, presumably a TMPFS
> or
> DEVTMPFS or similar, this fails which apparently cascades into
> not
> finding the disk.
>
> I suggest you have a dig into your initramfs and try and
> figure out what
> specifically it is trying to do and what requirements your
> distro has
> put on the kernel configuration.
>
> You appear to be getting dumped into a debug shell within the
> initramfs
> so you can quite easily have a poke around and see what's
> going on I
> think.
>
>
> Sorry, can you give me more detail about how to do this? What command
> or what others? Many thanks.