Running SLES11sp2 and running Datasync as a XEN virtual machine.
I upgraded the Novell Datasync application on the VM and this went thru fine
and the system update and is working correctly.
but …
on a reboot of the virtual machine generates the following error:
waiting for device /dev/xvda to appear: ok
invalid root filesystem
exiting to /bin/sh
$
I then type “exit” and then everything works 100%
The “mount” command returns “/dev/xvda1 /boot” and “/dev/xvda3 /” which all
looks correct.
I’ve sometimes seen that the VM’s kernel somehow didn’t catch the root file system name correctly. You might want to try to set "root=/dev/xvda3"as an EXTRA parameter in your DomU’s configuration file and see if that helps.
I upgraded the Novell Datasync application on the VM and this went
thru fine and the system update and is working correctly.
but …
on a reboot of the virtual machine generates the following error:
waiting for device /dev/xvda to appear: ok
invalid root filesystem
exiting to /bin/sh
$[/color]
Hi John,
You may have encountered Bug 755924. Under certain conditions during an
upgrade or when applying patches, initrd may be built incorrectly.
The solution is quite simple: run mkinitrd to correctly rebuild initrd.
Let me know if this resolves your issue.
–
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…
Running “mkinitrd” fiddled in the OS and fixed the issue.
Many thanks
Regards
John
[color=blue][color=green][color=darkred]
On 27 February 2013 at 19:30, in message[/color][/color][/color] ForXs.4501$vO3.750@kovat.provo.novell.com,
KBOYLEKBOYLE@no-mx.forums.suse.com wrote:[color=blue]
John Gill wrote:
[color=green]
I upgraded the Novell Datasync application on the VM and this went
thru fine and the system update and is working correctly.
but …
on a reboot of the virtual machine generates the following error:
waiting for device /dev/xvda to appear: ok
invalid root filesystem
exiting to /bin/sh
$[/color]
Hi John,
You may have encountered Bug 755924. Under certain conditions during an
upgrade or when applying patches, initrd may be built incorrectly.
The solution is quite simple: run mkinitrd to correctly rebuild initrd.
I’ve sometimes seen that the VM’s kernel somehow didn’t catch the root
file system name correctly. You might want to try to set
"root=/dev/xvda3"as an EXTRA parameter in your DomU’s configuration file
and see if that helps.
on a reboot of the virtual machine generates the following error:
waiting for device /dev/xvda to appear: ok
invalid root filesystem
exiting to /bin/sh
$[/color]
From time to time I see posts in various forums from others who have
encountered this issue.
I had a bug opened for this almost a year ago. While patches have
reduced the chances of this happening they have not yet completely
resolved the issue. I have asked that it be documented in a TID.
–
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…