Urgent - VM deleted but config still here

Elmani335

New Member
Jun 22, 2023
12
0
1
Hey every ! so here is my issue,

I was doing some networking and had to shutdown my servers, but when I pluged back everything on (like always I have autorestart 1 day per week)

But then.. my windows server wasn't booting up.. this is what I get :
1687481303089.png

I think the VM image got deleted but I don't know how, and I tryed some recover stuff but no service run with this VM-Id or anything else

I builded this vm in the next way :

1687481355066.png

(HD means = Hard Disk)
the HD(ide 0) is the boot drive
the HD(ide 1) is where is my stored data (the one that I need to recover ! )

And this is a shell output gives me a little hope :
1687481491804.png

I created another Windows server, completely blank VM, Is there any way to attach the HD ide1 (15 000G) to the new windows and try recover data ?


Or this here any other way of recovering the .qcow2 to restore the VM ?

I don't have any proxmox backups for it, I really need to recover the data it is really important.

Hope someone have a solution for this issue

=====[EDIT 1]=====
Succesfully recovered all the REALLY importand data ! (Attached the big disk to another windows server VM worked)

But know if there is any way to recover the data of the .qcow2 (ide0 100G) I would apreciate ! [it contains my website + other certfiles :).. ]

If not possible, I can still reconfigure all but will literally take me an entire week
================
 
Last edited:
what kind of storage is RAID_DATA? could you post the output of "pvesm status" and "pvesm list RAID_DATA", as well as the contents of /etc/pve/storage.cfg ?
 
what kind of storage is RAID_DATA? could you post the output of "pvesm status" and "pvesm list RAID_DATA", as well as the contents of /etc/pve/storage.cfg ?
hey ! thx for the reply, my RAID_DATA is a raid array of 6 SAS hard drives powered by a H710 RAID card, here are the screen of the different outputs :

PVE version : 7.3-3

the actual disk on my PVE :
1687507065552.png
pvesm status
1687506964256.png

pvesm list RAID_DATA
1687506986550.png

storage.cfg
1687506998337.png


Hope this can help to debug the issue.
 
looks like the volume was (accidentally?) deleted at some point since the last successful start of the VM.. note that it could have happened while the VM was running - the file will only actually be gone once the last process that has it open exits..

doesn't hurt to also double check that it's not just in an unexpected location, e.g. by doing

find /mnt/pve/RAID_DATA -type f -iname ".*320.*"

but I am afraid you will have to recover the contents from memory (and I'd highly recommend setting up backups to avoid this situation in the future!)
 
looks like the volume was (accidentally?) deleted at some point since the last successful start of the VM.. note that it could have happened while the VM was running - the file will only actually be gone once the last process that has it open exits..

doesn't hurt to also double check that it's not just in an unexpected location, e.g. by doing

find /mnt/pve/RAID_DATA -type f -iname ".*320.*"

but I am afraid you will have to recover the contents from memory (and I'd highly recommend setting up backups to avoid this situation in the future!)
Yup, I configured monthly entire backuops for all the important VMs,

here is the find command output (nothing) :
[IMAGE 1]
1687510831744.png

also, before all of that I had this issue, I booted server, and none of the servers were starting :
[IMAGE 2]
1687510904725.png

The error was a XFS corruption (cannot fit the whole output of the coruption in the image) :
[IMAGE 3]
1687510924053.png

And to fix it, it was saying me to do "xfs_repair /dev/sda1" (we can see it on the red lines)
wich I did (/dev/sda1 is the RAID_DATA)

And here the final output after "succesful" reparation :
[IMAGE 4] <<< important
1687511118628.png


And what actually happened, is that the RAID_DATA disk identifier changed after the reboot ??
before identifier :
[IMAGE 5]
1687511188654.png

after identifier :
[IMAGE 6]
1687511200226.png

Actaully the first one isn't existing anymore, or at least I can't find it.

You will probably tell me that there is no chance to recover it, but the "320.conf" file is still there :
[IMAGE 7]
1687511276206.png


I didn't restart the server between the xfs_repair and now.

And I know that XFS is a block file system, so I hope some data recover possibility maybe ?

And here an important line present on IMAGE 4
1687511458241.png

(sorry for the long text, I give all the info I have in my hands to figure out a way to possibly recover all of that)
 

Attachments

  • 1687510659516.png
    1687510659516.png
    14.2 KB · Views: 0
  • 1687511487565.png
    1687511487565.png
    8.3 KB · Views: 0
yeah, that sounds like xfs_repair detected corruption surrounding your missing image file and removed it.. I am not a data recovery expert, but the usual approach in such a situation would be to do a bit-wise copy of the disks before attempting such a repair/recovery, in order to try multiple possible destructive techniques with as much of the data around as possible. if the data is important to you, I would suggest not doing any more changes and contacting a company specializing in such recovery.
 
yeah, that sounds like xfs_repair detected corruption surrounding your missing image file and removed it.. I am not a data recovery expert, but the usual approach in such a situation would be to do a bit-wise copy of the disks before attempting such a repair/recovery, in order to try multiple possible destructive techniques with as much of the data around as possible. if the data is important to you, I would suggest not doing any more changes and contacting a company specializing in such recovery.
Yup, thx ! I will try to do tests because it's in a RAID array, I should probably have some more info on my RAID controler dashboard, will try some XFS recovering tool

Also I can't figure out how to install and use the xfs_undelete tool wich is on github, there isn't any real instructions on how to ? and since I haven't turned off the server still, there should be some data laying arround on the drive/ram/temp junk file
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!