S
Saleen-Stangin
I see this question alot lately, but no firm answers.
I have a 60TB storage enclosure with 54TB of video. This was configured using Storage Spaces and named the pool "Example". All worked fine on this one specific machine with Windows 10 (1903). It worked so well that I had to buy another 60TB enclosure and do the exact same with it. Then I even put the exact same video files on this one using the old one. This one I named the pool "Example2".
Now a year has gone by and I need some of the video. I plug in pool "Example" to a Windows machine with Windows 10 (1909) on it and the pool sees the enclosure, all drives showing healthy and the pool named just as it should be... but WAIT... all of a sudden a "You need to format this drive" box pops up. ****?? No.. NO.. NOOO.. not good.
So I go into Disk Management and see this drive type is now RAM. ****... really?? Ok, well I have a secondary backup.. (named Example2). So I plug in this enclosure and the exact same thing with this one comes up.
Now understand.. both enclosures are the exact same type and size. Both built the same, just named differently. After reading, I see Microsoft has admitted to the 2004 package build being an issue, but my machines are only at 1909. I tried and older OS device with Windows 10 1803, with no help there either.
Has ANYONE come up with any idea as to why this is happening? Drivers for the Storage or Spaces controller maybe? Something we can roll back and get these drives working again.. at least so I can get the data off of it?
BTW.. using powershell to set the virtual disk to ReadOnly, does NOT work. Disk is still RAM and cannot access data.
Basically this step does not fix the issue:
get-virtualdisk | ? WriteCacheSize -gt 0 | get-disk | set-disk -IsReadOnly $true
Any thoughts or fixes is greatly appreciated.
Continue reading...
I have a 60TB storage enclosure with 54TB of video. This was configured using Storage Spaces and named the pool "Example". All worked fine on this one specific machine with Windows 10 (1903). It worked so well that I had to buy another 60TB enclosure and do the exact same with it. Then I even put the exact same video files on this one using the old one. This one I named the pool "Example2".
Now a year has gone by and I need some of the video. I plug in pool "Example" to a Windows machine with Windows 10 (1909) on it and the pool sees the enclosure, all drives showing healthy and the pool named just as it should be... but WAIT... all of a sudden a "You need to format this drive" box pops up. ****?? No.. NO.. NOOO.. not good.
So I go into Disk Management and see this drive type is now RAM. ****... really?? Ok, well I have a secondary backup.. (named Example2). So I plug in this enclosure and the exact same thing with this one comes up.
Now understand.. both enclosures are the exact same type and size. Both built the same, just named differently. After reading, I see Microsoft has admitted to the 2004 package build being an issue, but my machines are only at 1909. I tried and older OS device with Windows 10 1803, with no help there either.
Has ANYONE come up with any idea as to why this is happening? Drivers for the Storage or Spaces controller maybe? Something we can roll back and get these drives working again.. at least so I can get the data off of it?
BTW.. using powershell to set the virtual disk to ReadOnly, does NOT work. Disk is still RAM and cannot access data.
Basically this step does not fix the issue:
get-virtualdisk | ? WriteCacheSize -gt 0 | get-disk | set-disk -IsReadOnly $true
Any thoughts or fixes is greatly appreciated.
Continue reading...