December 3, 2012 5:51:26 PM
> Subject: Re: [Users] VM has paused due to unknown storage error
>
>
> Hi everyone,
>
> Thank you for your responses.
>
> Yeela:
> >When oVirt started the vm it mounted the corrupt disk image that
> >seemed fine, but it couldn'
Hi everyone,
Thank you for your responses.
Yeela:
/>When oVirt started the vm it mounted the corrupt disk image that
seemed fine, but it couldn't find the OS because of the corrupted fs,
and the error caused it to pause the guest./
To clear things up it was the /var mount that had the corrup
David Wilson:
Hi everyone,
Some feedbackon this error, and a question I hope that someone could
possibly assist with.
I managed to get the guest running again byusing dd and qemu-img to
export the filesystem image and base image, convert to raw format and
run a fsck on the looped partition.
I
On Mon, Dec 03, 2012 at 04:37:01AM -0500, Yeela Kaplan wrote:
> Glad to hear it worked out.
>
> When oVirt started the vm it mounted the corrupt disk image that seemed fine,
>
> but it couldn't find the OS because of the corrupted fs,
> and the error caused it to pause the guest.
I think we sh
On Mon, Dec 3, 2012 at 10:37 AM, Yeela Kaplan wrote:
> Glad to hear it worked out.
>
> When oVirt started the vm it mounted the corrupt disk image that seemed fine,
> but it couldn't find the OS because of the corrupted fs,
> and the error caused it to pause the guest.
But if this is the case, I t
Thanks for your reply Yeela. I appreciate your feedback.
Please see my feedback to the list earlier. weird that I was able to
repair the disk using another physical system.Butwhen attached to the
guestoVirt kept pausing the guest which prevented fsck from completing.
Get important Lin
sers@ovirt.org
> Sent: Monday, December 3, 2012 10:55:37 AM
> Subject: Re: [Users] VM has paused due to unknown storage error
>
>
>
> H i everyone,
>
> Some feedback on this error , and a question I hope that someone
> could possibly assist with.
> I managed to get t
Hi everyone,
Some feedbackon this error, and a question I hope that someone could
possibly assist with.
I managed to get the guest running again byusing dd and qemu-img to
export the filesystem image and base image, convert to raw format and
run a fsck on the looped partition.
When mounted as
It seems that your guest file system is corrupted.
The dd approach won't help cause this is a virtual disk,
you need to fix the virtual disk inside the lv, that's why any operations on
the lv won't help.
You can try shutting down the vm (not paused, but literally down) and add the
guest vm disk
9 matches
Mail list logo
