Ubuntu P2V won't boot (ureadahead main process terminated with status 5)

[testudo]

Hi,

I'm trying my first experiment with P2V, creating a VM on ESXi 4.1 of an Ubuntu 10.04.2 LTS machine.  The conversion runs fine (although I do have to resize my partitions to make them small enough for my datastore's block size), but the installed Ubuntu on the VM doesn't boot.  It just displays the error:

init: ureadahead main process (<pid#>) terminated with status 5

I've tried with Conveter versions 4 and 5 with the same result.  Is there a step I'm missing?  Maybe something I need to do to fix the fstab?

Thanks.

[aca_besak]

Hello

I've exactly the same problem with converter 5 and Vsphere 5....

Anybody have a idea ?

[alyster]

I'm having the exact same issue.

A little more information though, here's the file system layout:

/dev/sda1 on / ext3

/dev/sda2 is swap ext3

/dev/sdb1 on /usr type ext3

/dev/sdb2 on /var type ext3

/dev/sdb3 on /tmp type ext3

/dev/sdb4 on /home type ext3

The FS on the original VM (A mounted KVM VM that is being V2Vd to VMWare) is ext4, this has been converted to ext3 by VMWare converter.

I've tried modifying  the /etc/init/ureadahead.conf file to add the following:

start on starting mountall

start on mounted MOUNTPOINT=/etc

start on mounted MOUNTPOINT=/var

start on mounted MOUNTPOINT=/tmp

start on mounted MOUNTPOINT=/home

I've moved the 'start on starting mountall' line to the end and omitted altogether and have the same issue.

I've performed a fsck on all partitions other than root and there are no errors.  I can access the data on them if I boot into rescue mode and manually mount the partitions.

Modifying /etc/init/ureadahead.conf got rid of the ureadahead error on boot, now the VM simply hangs with 'Starting up...'

Any pointers would be appreciated

[aa_matze]

Hi,

I have the same issue.

I tried the following steps

- reconfigure the ureadahead package,

- modify /etc/fstab

- removed the ureadahead software

but the error remains or the system shows only a blank screen.

[azel]

Hi,

I've got the same issue here. Anyone having a solution ?