LinuxQuestions.org - Acronis Image -> VM Conversion -> boot issues

- Linux - Server (https://www.linuxquestions.org/questions/linux-server-73/)

- - Acronis Image -> VM Conversion -> boot issues (https://www.linuxquestions.org/questions/linux-server-73/acronis-image-vm-conversion-boot-issues-743413/)

Acronis Image -> VM Conversion -> boot issues

Ok, Here is the run down.:

Using the Acronis True Image Echo Agent, I created an image of one of our linux boxes. I then used the VMware converter 4 to comvert this image into a VM. Upon booting the newly created VM, I got an "Unable to load operating system (or something along those lines) error so I installed grub using a floppy image.

Now when I select the kernel to boot, I end up with the following output at failure:

Code:

Creating block devices

VFS: Cannot open root device "LABEL=/" or 00:00

Please append a correct "root=" boot option

Kernel panic: VFS: Unable to mount root fs on 00:00

So, I edit the kernel arguements and remove the root statement and it fails at this point:

Code:

Loading jbd.o module

Journalled Block Device driver loaded

Loading ext3.o module

Creating block devices

EXT2-fs: unable to read superblock

isofs_read_super: bread failed, dev=09:01, iso_blknum=16, block=32

EXT3-fs: unable to read superblock

Kernel panic: VFS: Unable to mount root fs on 09:01

What is going wrong?

If you boot the VMware guest from CDROM or ISO (HELIX, KNOPPIX, whatever you fancy) with the vmdk available and run 'sfdisk -l /dev/devicename' and 'disktype /dev/devicename', what do they return?

Moved: This thread has been moved at the OPs request.

d/ling KNOPPIX image now. I'll be back.

Quote:

Originally Posted by unSpawn (Post 3624263)

If you boot the VMware guest from CDROM or ISO (HELIX, KNOPPIX, whatever you fancy) with the vmdk available and run 'sfdisk -l /dev/devicename' and 'disktype /dev/devicename', what do they return?

sfdisk results:
http://i15.photobucket.com/albums/a3...ann/sfdisk.jpg

says disktype: command not found

OK, so disktype exists on HELIX only... In any case your sfdisk output shows the partitions inside the VMDK are recognised. Running 'echo /dev/sda[0-9]* | xargs -iX e2label 'X' 2>/dev/null' should show which partition has what label so you can append the right "root=" at the GRUB commandline.

Quote:

Originally Posted by unSpawn (Post 3625613)

after running

Code:

echo /dev/sda[0-9]* | xargs -iX e2label 'X' 2>/dev/null

I get no output. Am I missing something?

Are you running the command with the same conditions as in post #2?

The first command i ran was

sfdisk -l /dev/sda

does this mean i should imput the second command as

echo /dev/sda[0-9]* | xargs -iX e2label 'sda' 2>/dev/null

No, I mean the command should be run with the VMware guest booted from CDROM or ISO and with the vmdk available. FDS don't give e2label arguments like that or you'll write things to it and writing to your VMDK is th last thing you want to do right now, just recon.