REFS - Storage Spaces - Dual Boot W10/S2K16
I have setup Storage Spaces with 4 disks, Two way Mirror, formatted REFS, worked fine in both O/S's Updated S2K16, now it says Storage Space drive needs formatting.. Drive is perfectly readable in Windows 10 1703. All I can do is move the files off of SS drive in W10
SS 4 x WD 4TB Drives
Such a pain to have to keep moving 8TB
SS 4 x WD 4TB Drives
Such a pain to have to keep moving 8TB
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for stopping by.. didn't know they were different versions
FYI:
Win10 v1703 offers REFS 3.2 (not v1!)
Win2016 v1607 offers REFS 3.1
(verified using fsutil fsinfo refsinfo x:)
Also a note on Cliff's "2016 is moving to the same release cycle as win10" - not quite, only Nano server will be CBB. Please see https://blogs.technet.microsoft.com/windowsserver/2016/07/12/windows-server-2016-new-current-branch-for-business-servicing-option/ for details.
Win10 v1703 offers REFS 3.2 (not v1!)
Win2016 v1607 offers REFS 3.1
(verified using fsutil fsinfo refsinfo x:)
Also a note on Cliff's "2016 is moving to the same release cycle as win10" - not quite, only Nano server will be CBB. Please see https://blogs.technet.microsoft.com/windowsserver/2016/07/12/windows-server-2016-new-current-branch-for-business-servicing-option/ for details.
Microsoft has shifted the focus and purposes nano. That post is from mid 2016. Here is a more recent post talking about server (not nano) and Windows and office aligning to a semi-annual release.
http://m.winsupersite.com/windows-10/windows-10-feature-updates-aiming-semi-annual-release-cycle
http://m.winsupersite.com/windows-10/windows-10-feature-updates-aiming-semi-annual-release-cycle
Ha, I knew something wasn't right about the table in my link, since I knew, hyper-v core server would be Semi-annual Channel!
But still, the server that many, many will use, "desktop experience installation" will not be aligned with win10 but LTSB instead. That's why we will not see REFS 3.2 in those servers for a while.
Anyway, switching the drive to and fro would only become a problem, if the formatting was changed, which should not even be the case here.
But still, the server that many, many will use, "desktop experience installation" will not be aligned with win10 but LTSB instead. That's why we will not see REFS 3.2 in those servers for a while.
Anyway, switching the drive to and fro would only become a problem, if the formatting was changed, which should not even be the case here.
Thanks for the correction. I've not seen anything in my regular channels on Windows Client getting an update.
ASKER
what was driving me nuts was.
I created the storage space in Server 2016, formatted it to REFS, moved a bunch of files over (VHD's), rebooted into Windows 10, had to put the drive online. Was prompted to upgrade the storage space to gain additional options.. I declined. Continued the move of the .vhd's, went back into Windows Server and the drive said format to access the drive! Boot back into Windows 10 and the drive was readable.
As an aside, Windows Image backup is going away.
I created the storage space in Server 2016, formatted it to REFS, moved a bunch of files over (VHD's), rebooted into Windows 10, had to put the drive online. Was prompted to upgrade the storage space to gain additional options.. I declined. Continued the move of the .vhd's, went back into Windows Server and the drive said format to access the drive! Boot back into Windows 10 and the drive was readable.
As an aside, Windows Image backup is going away.
Features that are removed or deprecated in Windows 10 Fall Creators Update
System Image Backup (SIB) Solution. We recommend that users use full-disk backup solutions from other vendors.
Don't confuse system image backup in the client with Windows Server Backup on the server. They've always been two different technologies. One being deprecated doesn't have a lot of bearing on the future of the other.
"Was prompted to upgrade the storage space to gain additional options.. I declined." - I bet the expected behavior would be that it is interchangeable to and fro if you decline at that spot (what you did), but somehow, MS managed to have win10 modify the disk anyway. You should see whether it's reproducible and then inform Microsoft.
Please verify the version of the REFS volume before and after connecting to v1703 using
fsutil fsinfo refsinfo x:
Please verify the version of the REFS volume before and after connecting to v1703 using
fsutil fsinfo refsinfo x:
Now that 2016 is moving to the same release cycle as win10, that will be lessened a bit. But since server revisions will be tied to SA, those on long-term releases can still but that issue.
I woulnt recommend dual booting with SS. It just wasn't built with that use case in mind.