So updated my server with the Windows anniversary update...
before I start
- yes I know I should have done it X way or Y way or should be running Linux, that I should not of used storage spaces or should have a proper back up etc etc
- I use my server PC as a central 'headless PC' for use of storing all my media files centrally, for downloading stuff in the background and for working on some computing tasks in the background
- its a Lenovo TS140 with an external 'DAS' eight bay tower connected via USB3 with 4x6 Tb WD Reds and 4x4 Tb WD Reds. The DAS unit is used for media storage with the drives configured through storage spaces into two 'mirrored' drives with the 6Tb drives forming one mirror and the 4tb the other. These drives are formatted with the ReFS file system . I don't have any 'proper' backup for most of the files on the DAS as they are ultimately not THAT important and are mostly replaceable albeit it would be a pain in the ***. I have the data mirrored on the DAS and consider any extra redundancy too expensive given the type and size of the data at hand for my uses...
- Internally the server boots from my old 480 Gb OCZ Revodrive and has 4x3Tb Seagate Barracuda's in RAID as a scratch space
Well up until installing the update I have found this works quite well and have not had any problems with this setup.
Unfortunately I rushed into installing the Windows anniversary update early without checking what problems it was caused and after installing it on my server found that the disc in my DAS were no longer accessible with Windows seeing the drives in disk management and storage spaces (which showed that they were X% full still as well!) but with the drives showing as unformatted!!!
No it appears that the update has not physically deleted the actual data on the drives and has just instead hosed the GPT table for the drives so that windows can no longer access the drives!
Testing with some recover programs shows that the data all still appears to be there.
From checking online this issue does not appear to be limited to drives using any combination of ReFS or Storage Spaces. With people reporting all sorts of internal and external drives being rendered unreadable directly through windows post the Windows anniversary update.
and before anyone mentions it this was NOT caused by inadvertently downloading malware/ransomware from a certain download site! This was definitely the work of the Windows anniversary update!
Take care in installing the Windows anniversary update and I would advise disconnecting all secondary/ external drives leaving just the OS drive attached when updating!
I'm currently running a very longwinded process with some 3rd party software to recover the data from my DAS unit to some spare drives!
before I start
- yes I know I should have done it X way or Y way or should be running Linux, that I should not of used storage spaces or should have a proper back up etc etc
- I use my server PC as a central 'headless PC' for use of storing all my media files centrally, for downloading stuff in the background and for working on some computing tasks in the background
- its a Lenovo TS140 with an external 'DAS' eight bay tower connected via USB3 with 4x6 Tb WD Reds and 4x4 Tb WD Reds. The DAS unit is used for media storage with the drives configured through storage spaces into two 'mirrored' drives with the 6Tb drives forming one mirror and the 4tb the other. These drives are formatted with the ReFS file system . I don't have any 'proper' backup for most of the files on the DAS as they are ultimately not THAT important and are mostly replaceable albeit it would be a pain in the ***. I have the data mirrored on the DAS and consider any extra redundancy too expensive given the type and size of the data at hand for my uses...
- Internally the server boots from my old 480 Gb OCZ Revodrive and has 4x3Tb Seagate Barracuda's in RAID as a scratch space
Well up until installing the update I have found this works quite well and have not had any problems with this setup.
Unfortunately I rushed into installing the Windows anniversary update early without checking what problems it was caused and after installing it on my server found that the disc in my DAS were no longer accessible with Windows seeing the drives in disk management and storage spaces (which showed that they were X% full still as well!) but with the drives showing as unformatted!!!
No it appears that the update has not physically deleted the actual data on the drives and has just instead hosed the GPT table for the drives so that windows can no longer access the drives!
Testing with some recover programs shows that the data all still appears to be there.
From checking online this issue does not appear to be limited to drives using any combination of ReFS or Storage Spaces. With people reporting all sorts of internal and external drives being rendered unreadable directly through windows post the Windows anniversary update.
and before anyone mentions it this was NOT caused by inadvertently downloading malware/ransomware from a certain download site! This was definitely the work of the Windows anniversary update!
Take care in installing the Windows anniversary update and I would advise disconnecting all secondary/ external drives leaving just the OS drive attached when updating!
I'm currently running a very longwinded process with some 3rd party software to recover the data from my DAS unit to some spare drives!
Last edited:
