ReFS sucks big time - or reinstalling has lost me access to my files.

cyclone3d

[H]F Junkie
Joined
Aug 16, 2004
Messages
16,244
So, it is not the end of the world, but it would take me quite some time to re-get everything I had on one of the drives I had formatted as ReFS.

The other was my Steam drive, so other than having to re-download a bunch of stuff it isn't a big deal.

I ended up having to reinstall Windows 10 from scratch due to it repeatedly failing on updates and nothing I tried would fix it.

It kept trying to update, rebooting and then coming up to 2 of my screens being black with just a huge mouse cursor.

After installing Windows 10 from scratch and hooking my non-boot drives back up it is now saying that both the drives that were ReFS are not formatted.

Any way to get them back without having to run recovery software? If not, what is a good recovery software for ReFS?

And I am NEVER using ReFS again. Stupid piece of crappy crap that needs to DIAF.
 
Don't give up on it yet.

Did you install the right edition of Windows 10? Is it updated to the point of your previous installation yet?
 
It isn't updated yet. I tried to update after the clean install of 1703 and the dumb update just fails.

Going to put it on slow release setting when I get back home and see if it tries an earlier version.
 
Well, that didn't help. finally got it to update only after swapping out the boot SSD for another.

After updating to the latest, Windows will not even boot with those 2 drives hooked up. Just sits there and spins forever. Waited at least 20 minutes one time. And if I hook up one of the drives after Windows is booted, it can't access it at all. Disk management even freezes up.

Not sure what else to do but go back to 1703 and use recovery software.

I guess I could try going back to the slightly older build on the slow ring first.
 
Nope, 16288.1(rs3_release) is on the slow ring as well.

Just the stupid 2 screen with an enlarged cursor requiring a hard power off. Then when it starts back up it reverts back to 1703.

Done wasting time to get it working with the ReFS drives unless somebody else has a better idea.
 
Have you tried using Windows Server 2016 instead? This sounds like file system or drive corruption to me, but Windows 10 was not meant to have full ReFS support, and is being phased out of Windows 10 entirely.
 
Have you tried using Windows Server 2016 instead? This sounds like file system or drive corruption to me, but Windows 10 was not meant to have full ReFS support, and is being phased out of Windows 10 entirely.

I suppose I could set up a temp Server 2016 VM at work and hook the drives up via a USB dock.

Last ditch effort I guess before buying a copy of EaseUS Data Recovery Wizard.. which can see all the files just fine.

I don't see how it could be file system or drive corruption. I turned off my computer and unhooked the drives. Did a clean install of Windows, and then turned off the computer and hooked the drives back up and boom... RAW partitions.
 
Well that was a bust. Can't get VMWare to even recognize that there is anything plugged into the USB ports.. not even a keyboard or mouse. Checked the BIOS settings and there are no options for passthrough.
VMWare sees the USB ports and lets me add them for passthrough, but when I try to add a USB device to the VM it says there are no host USB devices available.

Done screwing with it. Data recovery software it is.
 
If it's not too late, you might want to try booting Win 2016 from a USB stick and press shift-f10 to see if you can access the drives from the Win 2016 command line.
 
If it's not too late, you might want to try booting Win 2016 from a USB stick and press shift-f10 to see if you can access the drives from the Win 2016 command line.

Got everything back with EaseUS Data Recovery Wizard. Just took forever to scan the drives and then copy everything off.

Then I used diskpart to clean the drives and then I made new partitions and did full NTFS formats on them.
 
The weird thing about Microsoft, is that they release their new tech, like ReFS for Enterprise customer use first. And when/if it works fine, MS finally release it to the broad masses; i.e the desktop users. I dont really get it.

Solaris tech is always released for beta users, i.e desktop users and when it works fine, they release it to the Enterprise customers last. For instance, ZFS was released that way in a beta Solaris version, and when ZFS had been hardened, Sun released ZFS into the ordinary Solaris upgrade path.

MS does the other way around. Why the heck does MS release new unstable tech to Enterprise customers first? Is it because Enterprise customers have more resources?
 
The weird thing about Microsoft, is that they release their new tech, like ReFS for Enterprise customer use first. And when/if it works fine, MS finally release it to the broad masses; i.e the desktop users. I dont really get it.

Solaris tech is always released for beta users, i.e desktop users and when it works fine, they release it to the Enterprise customers last. For instance, ZFS was released that way in a beta Solaris version, and when ZFS had been hardened, Sun released ZFS into the ordinary Solaris upgrade path.

MS does the other way around. Why the heck does MS release new unstable tech to Enterprise customers first? Is it because Enterprise customers have more resources?


Enterprise customers pay more...plus Enterprise/Corp IT guys moan if they don't get the sparkly new toys first.;)
 
in the MS world it is due to money. (enterprise pays support contracts so MS can get paid to fix their own bugs) in the Solaris world it is due to testing. (free testing and reporting from the 'users' who can help make it work)
 
Back
Top