SOS SOS SOS

[Skyway]

Hello i'm using , Virtual box 4.3.8
Real Os :Windows
Virtual OS: Debian Wheezy

This morning when i restarted my computer i wasn't able to launch my virtual server , after when i starting searching for the problem i found out that my virtual hard disk Fresh Debian Wheezy-disk1.vmdk is 0 bytes totaly empty
inside i had my website project that i have been working on past 5 month please tell me that there is some way to restore the data

i found 2014-03-23T04-20-25-392879100Z.sav file in my snapshot folder. can i restore data from this file ?

[loukingjr]

The simplest way is if you do regular backups of your Windows (version?) host or if you have System Restore points.

[Skyway]

The simplest way is if you do regular backups of your Windows (version?) host or if you have System Restore points.

i have none of those

what about 2014-03-23T04-20-25-392879100Z.sav can i restore data from there ?

[loukingjr]

The simplest way is if you do regular backups of your Windows (version?) host or if you have System Restore points.

i have none of those

what about 2014-03-23T04-20-25-392879100Z.sav can i restore data from there ?

I don't know what that is.

[loukingjr]

nevermind, I looked it up. no you can't.

[loukingjr]

are you sure you have no restore points? did you disable system restore? and what version of Windows do you have?

[Skyway]

are you sure you have no restore points? did you disable system restore? and what version of Windows do you have?

unfortionatly yes windows 7

system restore:

No restore points have be created on your computer's system drive

[loukingjr]

with no backups and no restore points I don't see how you can recover. maybe someone else knows.

[yolf]

This may be the most trivial suggestion, but if you select that file or the containing folder, right click, select Properties, there should (may) be a tab labeled Previous Versions. It just might have what you are hoping for. I do not know if this relies on restore points or not.

[loukingjr]

This may be the most trivial suggestion, but if you select that file or the containing folder, right click, select Properties, there should (may) be a tab labeled Previous Versions. It just might have what you are hoping for. I do not know if this relies on restore points or not.

Previous Versions come from either a restore point or a Windows backup.

[mpack]

Moved to "Windows Hosts".

The ".sav" file is a hibernation file. It contains nothing you can use.

Please show the complete contents of the VM folder, including the "Snapshots" subfolder. Also post a VM log file - see Minimum information needed for assistance.

Don't get your hopes up. So far, this sounds terminal - exactly the sort of scenario that backups are needed for.

[Skyway]

/Logs ( http://skyway.ge/Logs.rar )
/Snapshots/2014-03-23T04-20-25-392879100Z.sav 729,427kb
Fresh Debian Wheezy-disk1.vmdk 0kb
Skyway 1TB.vbox 0kb
Skyway 1TB.vbox-prev 9kb

[mpack]

The vbox file is 0b as well?

"xxx-disk1" is an odd name for a disk when it's the only disk in the set, but I'll have to take your word that this VM was previously working.

Tell me, did you make a habit of suspending the VM instead of shutting it down? I.e. did you make a habit of closing the VM without forcing it to flush changes to disk? Mind you, even if you made the classic mistake of never installing Debian, always running from RAMdisk until the suspend feature broke... then even then I'd expect the stub VMDK to be larger than 0b.


Also, the fact that the vbox file is 0b as well implies some sort of catastrophic host glitch. And if that's a complete directory listing you have me then I don't see any way to get the data back, sorry.

[socratis]

From your logs:

00:00:17.488432 AHCI: LUN#0: disk, PCHS=16383/16/63, total number of sectors 4294965248
00:00:17.594755 Guest Log: BIOS: AHCI 0-P#0: PCHS=16383/16/63 LCHS=1024/255/63 -2048 sectors

That translates to (almost) 2 TB (=4.294.967.296) of virtual HD. Something doesn't seem right from the get go. Even your "BIOS" is confused and passes a negative number (-2048) as the number of sectors. Compare it with a similar machine of mine where the virtual HD is 8 GB.

00:00:01.045542 AHCI: LUN#0: disk, PCHS=16383/16/63, total number of sectors 16777216
00:00:01.122694 Guest Log: BIOS: AHCI 0-P#0: PCHS=16383/16/63 LCHS=1024/255/63 16777216 sectors

Then at 161 hours of operation (!?!) something hit the fan.

161:01:13.591423 AHCI#0P0: Write at offset 2004770357248 (524288 bytes left) returned rc=VERR_DISK_FULL
161:01:13.635712 AHCI: Host disk full
161:01:13.663514 VM: Raising runtime error 'DevAHCI_DISKFULL' (fFlags=0x6)
161:01:13.703831 I/O cache: Error while writing entry at offset 2004763541504 (524288 bytes) to medium "ahci-0-0" (rc=VERR_DISK_FULL)
161:46:22.503532 SSM: Failed to save the VM state to 'C:\Users\Skyway\VirtualBox VMs\Skyway 1TB\Snapshots\2014-04-07T21-15-51-382839900Z.sav' (file deleted): VERR_DISK_FULL

I don't know if you hit a limit in VBox or your hard drive, but it was definitely a recipe begging for disaster.