1:29 p.m.
I have a VM that's a little over 4TB in size that won't import for whatever
reason. I've tried changing the export from the streaming disk format to a flat
vmdk,thinking that might be it, but it didn't work. I've gone through the OVF and
don't see anything that stands out. Same for the logs, I see where it's having
issues importing the 4TB drive from the VM, but I can't decipher the error messages
well enough to know how to fix it. The drives had chkdsk run on them before they were
exported, and the VM was cleanly shut down, so I don't understand what the issue is.
Not even sure at this point how to run a filesystem repair on the vmdk, in case the export
corrupted something. And I can't export it directly from ESXi either, for some reason.
Each attempt fails with an unspecified error.
Below is a snip from the import log where it's reading the drives. It has one of the
first errors:
[ 2.492229] scsi host0: Virtio SCSI HBA
[ 2.501365] scsi 0:0:0:0: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI:
5
[ 2.504080] scsi 0:0:1:0: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI:
5
[ 2.506035] scsi 0:0:2:0: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI:
5
[ 2.540737] sd 0:0:0:0: Power-on or device reset occurred
[ 2.540790] sd 0:0:1:0: Power-on or device reset occurred
[ 2.540899] sd 0:0:2:0: Power-on or device reset occurred
[ 2.541130] sd 0:0:0:0: [sda] 8589934592 512-byte logical blocks: (4.40 TB/4.00 TiB)
[ 2.541168] sd 0:0:2:0: [sdc] 8388608 512-byte logical blocks: (4.29 GB/4.00 GiB)
[ 2.541319] sd 0:0:2:0: [sdc] Write Protect is off
[ 2.541391] sd 0:0:0:0: [sda] Write Protect is off
[ 2.541592] sd 0:0:2:0: [sdc] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
[ 2.542019] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
[ 2.544060] sd 0:0:2:0: [sdc] Attached SCSI disk
[ 2.545294] sd 0:0:1:0: [sdb] 251658240 512-byte logical blocks: (129 GB/120 GiB)
[ 2.545437] sd 0:0:1:0: [sdb] Write Protect is off
[ 2.545966] sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
[ 2.551250] sdb: sdb1 sdb2
[ 2.556698] sd 0:0:1:0qemu-nbd: Disconnect client, due to: Failed to send reply:
reading from file failed: Invalid argument
: [sdb] Attached SCSI disk
qemu-nbd: Disconnect client, due to: Failed to send reply: reading from file failed:
Invalid argument
qemu-nbd: Disconnect client, due to: Failed to send reply: reading from file failed:
Invalid argument
[ 2.618883] sd 0:0:0:0: [sda] tag#157 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_OK cmd_age=0s
[ 2.618890] sd 0:0:0:0: [sda] tag#157 Sense Key : Aborted Command [current]
[ 2.618892] sd 0:0:0:0: [sda] tag#157 Add. Sense: I/O process terminated
[ 2.618894] sd 0:0:0:0: [sda] tag#157 CDB: Read(16) 88 00 00 00 00 01 ff ff ff f8 00 00
00 08 00 00
[ 2.618897] I/O error, dev sda, sector 8589934584 op 0x0:(READ) flags 0x0 phys_seg 1
prio class 2
supermin: intern[ 2.618902] Buffer I/O error on dev sda, logical block 1073741823,
async page read
al insmod virtio[ 2.618927] Alternate GPT is invalid, using primary GPT.
The rest of the log is peppered with Buffer I/O error entries on /dev/sda (the 4TB vmdk).
Could someone please help? I think I've been looking at these logs and trying to fix
the drive for so long I've gone logic blind and can't see the answer right in
front of my eyes.
Here's a link to the logs pulled from the host:
https://www.dropbox.com/scl/fi/570t279s0k3pfgafuvv01/felicity-import-1.18...