You are experiencing timeouts between your host(s) and your backup target. these issues stem from one or more of
Source disk bandwidth
network transport
Destination disk bandwidth.
for item 1- you mentioned your host storage is ceph. what is the...
Troubleshooting order:
1. Did you map your luns to your PVE HBA WWN?
2. does your HBA see the LUN during boot?
3. Whats the make and model of your HBA? are you using the default drivers that shipped with debian, or did you install a outside driver?
I have a few deployments using dot hill controllers (the same as in the MSA2060 or Dell ME5024.) They work fine, just understand the caveats when using shared block in pve, namely that you're limited to LVM thick for logical arrangement.
Not addressing the specific complaint (others are already) but two items to consider:
1. https://blogs.damiendye.uk/en/proxmox/q35-not-i440fx/ according to this its possible and even likely i440fx will be deprecated in the future.
2. note your...
late to the party, but:
lets start at the beginning.
There is an issue with your root file system. BECAUSE you're using lvm, the disk itself is accessible to you directly, without a container. start with this:
fsck -fy...
you can save a step by shutting off the vsphere machine, manually map the vmdk to your pve vmid, start, and then storage migrate on PVE. but in all honesty the backup/restore method is still the best/most predictable if you dont have meaningful...
AFACIT this is a generic Highpoint card. see https://www.highpoint-tech.com/linux-community, https://www.highpoint-tech.com/post/bootable-raid-drive-support-via-lacs-binary-driver-solutions
@bbgeek17 no disagreement. I was simply pointing out that the premise that a full node fence is required isnt necessarily true for the proposed solution to work. I'm not suggesting its easy, not fraught with gaping holes, probably too slow to be...
I agree with this sentiment entirely- but it doesnt necessarily mean the conclusion. fencing in this context is just the vg activation on the "source", not full node fence.
Any while I agree that this SHOULDNT be a function of the storage...
Fairly easy to test, since you have access to the storage both at the "linux" level on pve OR passed as an iscsi target directly to a vm instead of as a virtio device.
sounds like you got most of those covered; however, its imperative that you...
You may want to take a second and reconsider what that means.
While using mirroring or parity/ec creates disk level fault tolerance in a storage solution, REDUNDANCY is a function of system level fault tolerance; if redundancy is a mission...
testdisk doesnt make distinction between lvm or raw blocks. it looks for file system signatures, and assembled directories/files from available metadata. if that behavior is desirable, run testdisk on the vg/lv instead of the disk but its a very...
Fair point. Reflink with sparse raw files gets you thin provisioning and snapshots without qcow2... so qcow2 metadata is out of the picture.
What's left is the stuff underneath. o2cb has its own heartbeat and fencing that doesn't know corosync...
pay closer attention to what the error is telling you.
Youre trying to create a virtual machine using /mnt/pve/iso as the DESTINATION STORAGE.
there are two things you should do- first, go to datacenter-storage, select iso, and UNCHECK disk...
that changes nothing. When you operate your own environment you weigh the tradeoffs and make decisions accordingly. there is nothing in a "home environment" that stops you from partitioning; if you cant be bothered thats your decision. best...
you dont have write access to /mnt/pve/ISO. check owners/permissions on the remote filesystem and/or nfs export. I also dont think you meant to use that location as your vdisk destination.