Hi Chris,
can you post the vdsm logs (spm host) somewhere?
Thanks.
--
Federico
----- Original Message -----
From: "Chris SULLIVAN (WGK)"
<Chris.Sullivan(a)woodgroupkenny.com>
To: users(a)ovirt.org
Sent: Monday, September 23, 2013 9:08:26 PM
Subject: [Users] oVirt 3.3.0-4/F19 - Extending VM disk gives correct size but appears to
wipe the drive contents
Hi,
I had a number of Windows VMs running in oVirt 3.3 that required their
preallocated OS disks to be extended. Each OS disk had a single partition
taking up the entire drive. As per
http://www.ovirt.org/Features/Online_Virtual_Drive_Resize I shut down all
the VMs, extended each OS disk by 10GB (total 25GB) via the web interface,
then clicked OK. The tasks appeared to complete successfully and each of the
OS disks had the expected real size on the Gluster storage volume.
On startup however none of the VMs would recognize their OS disk as being a
bootable device. Checking one of the OS disks via TestDisk (both quick and
deep scans) revealed no partitions and the error ‘Partition sector doesn’t
have the endmark 0xAA55’. It appears that each OS disk was wiped as part of
the extension process although I’m really hoping that this isn’t the case!
Are there any other approaches I could use to attempt to recover the OS disk
data or at least verify whether the original disk partitions are
recoverable?