Recent content by aconnor

oh god, I just spent all day wrestling with getting my stuff setup on DHCP. Tried to migrate a VM, got this error and now I need a drink. I didn't come here to whine, despite appearances, I'll see if I can add anything useful to the conversation.

now that link is gone too...

ah, that makes sense, thanks again @fabian I did spend a lot of time on this but the tutorials I saw did not mention that requirement Cheers!

I've been getting help from @fabian in this thread- https://forum.proxmox.com/threads/zfs-mirror-rebuild.109411/#post-470449 But this is a new error, thus a new thread. I've been able to get the VMs to local storage, but nothing I do will import them Closest I can get is qm importdisk 300...

Thanks so much for the extra level of detail @fabian This helps a lot. It's been 3 weeks of hell, just getting the last bits sorted. Thank you!

Thanks @fabian Sorry for sounding dumb, but my 'read-only' rpool is as pictured, what would I do to copy them off the rpool and into the new disk? Guessing I can use /var/lib/vz/images/ for this.

Thanks @fabian This is partly a learning exercise- no one will die if the data is unrecoverable, but I am learning so much about what does and doesn't work. I have been able to mount the zfs mirror as 'read only' by forcing it- now I'm trying to figure out how to move the VMs off the mirror...

Hi, I've had some interesting issues this last week, things now mostly ok but I want to ask advice on this- Proxmox installed on a ZFS mirror Had RAM issues and Proxmox now will not boot Can't scrub the zpool because it was created on another system. I've installed Proxmox on another drive...

ok thank you. Just to close this off for future readers- the node would not boot with only one disk in it- I tried both individually. If one disk was damaged we'd expect the good one to boot- I hope!

Hi @mira yes- over the weekend I was able to repair the boot partition of vm 103, and it was working Monday. Attempting to transfer the vm to a new node on Monday night and the node crashed. I rebooted node by using a remote power switch- I guess that's probably what killed it, because it never...

thanks @mira - the node did have significant bios firmware updates to do- from v34 to v69 or something. I didn't think about the storage. Is there any way to figure out the boot issue / and or any way to poke around the filesystem to find out what happened? I no longer care about the data...

Hi @mira the drives are Vendor= Intel Model= 665p I am attaching pics of the drives, and also where the boot process stopped - please let me know if this error is familiar- or fixable

thanks @Dunuin - couldn't get it to boot at all. I got the VM running on different hardware (and software) and I brought the non booting node back to the office to see if I can find out what killed it. Thanks for your help

Hi, I've been struggling with a node for some time where I couldn't backup, copy or migrate the VMs. Tonight it seems to have gone down for the last time, so I'll go onsite tomorrow to see what I can do to fix it. The Proxmox OS and datastore is all on a pair of ZFS mirrored NVMe drives. Can...

thanks for the reply @mira zpool status shows some errors root@pve01:~# zpool status -v pool: rpool state: DEGRADED status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible...