[SOLVED] Help accessing files on ssd from dead machine

uh oh, I had a feeling Proxmox starts the VMs prior to taking backups... and it does...
this won't work as the VM had iGPU passthrough that is not there anymore (I mean the iGPU is different in this one, still AMD tho)... so it won't boot... any way to take the backup offline ? or is it even advised to take the backup knowing it won't boot even on a new install ?
 
Oh boy, I managed to fix my networking you were right it was as simple as the number in the interface name changed (still planning to reinstall clean once my files are safe :) )
 
And I more or less managed to bring the VM back to life. It doesn’t have a video output so I guess the gpu is not correctly passed but good enough to boot and be able to ssh into it… should be enough to get my files out of there !

Thank you again for all your help !
 
You're welcome! Please give a thumbs up and mark the topic as Solved if you don't mind. :)
Last question on this subject, I promise :p
I have been copying since 12+ hours now, and I realise my speed is extremely slow.
I am copying from the VM to my NAS, a basic cp -r nothing fancy and I estimate the speed to be about 15 Mbs which is nowhere the normal speed I have usually....
I even wondered if my NAS has issues (I just added a new drive to it - not in RAID so it should not have any impact)
Just to make sure nothing is wrong I did a quick test of copying a 1,5 GB file from my macOS to the NAS to the same disk that is used to copy by the VM (the cp is still running so my macOS test is slower then it should be) and it was done in about 2 - 2,5 minutes... that is almost 5 times the speed the VM is experiencing....

Any idea why is that ? I presume cause the Proxmox install and the VM creation was done on different hardware so some things are probably still off... not sure...

macOS is on WiFi and Proxmox machine is on ethernet, so that should be in Proxmox VMs advantage....
 
That I don't know. I haven't had that problem myself, but I have seen other threads about it.

Purely guessing, I wonder if it has to do with the virtualization capabilities of the NIC, or the type of virtualization being used (e.g. VirtIO-net vs e1000).

For that I'd suggest searching through past threads and perhaps opening new thread so that someone else more experienced with those types of issues might be able to help.

I'd also suggest rubber ducking with an LLM (e.g. Grok, GPT, DeepSeek, Qwen) about the problem so that you can learn some things to try and more of the terminology associated with virtualized NICs - and on the off chance that it comes up with a valid solution.
 
No worries, I have time to finish copying and will see if the issue persists once I reinstall everything from scratch, no need to chase an issue that might be due to a boinked install... I asked in case you had an idea of the top of your head.

Is there a "best AI for tech stuff" or do all perform more or less the same ?