March 27, 201610 yr In moving stuff around in the server closet, I accidentally shut off the server. Once I re-started the server and the parity check was completed, I tried to restart W10 VM. Now W10 seems to want to start Recovery mode. I have rebooted the server several times hoping it would remedy itself but, it has not. The initial error screen seems to indicate a NTFS_FILE_SYSTEM error. Is it not seeing one of the images (.img or .iso)? In looking at my vdisk1.img, it looks like it was moved from the SSD cache (btrfs format) to my user share (xfs format). Could that be the issue?
March 27, 201610 yr In moving stuff around in the server closet, I accidentally shut off the server. Once I re-started the server and the parity check was completed, I tried to restart W10 VM. Now W10 seems to want to start Recovery mode. I have rebooted the server several times hoping it would remedy itself but, it has not. The initial error screen seems to indicate a NTFS_FILE_SYSTEM error. Is it not seeing one of the images (.img or .iso)? Don't run a w10 vm, but don't you usually have an option prior to it going into recovery mode to boot using Last Good Settings? (In my experience, recovery mode never works on windows) If the option for last good settings exists, and you successfully boot, run a chkdsk against drive C
March 27, 201610 yr Author In looking at my vdisk1.img, it looks like it was moved from the SSD cache (btrfs format) to my user share (xfs format). Could that be the issue?
March 27, 201610 yr Author Okay, so it seems that I have corrupted my original vdisk1.img. I was able to create another vdisk1.img but, obviously, W10 now wants to go through the install process again. Is there anyway to recover the original vdisk1.img? It appears that the NTFS file structure has been corrupted.
Archived
This topic is now archived and is closed to further replies.