M
MadisonAster
Hi,
I previously had a windows storage spaces drive with 9 spinning disks. After updating to 2004 my storage spaces got ruined due to this bug. So I destroyed that, and then further discovered that windows storage spaces is not functional at all due to no longer being able to create disk pools
So I figured fine, I have hardware raid controllers, I'll just go back to using those because it doesn't seem like a good idea to trust windows to do any striping. So created 2 raid 0's with 4 disks each in my bios. Windows recognizes those just fine. And then I used disk manager to mirror the 2 volumes as a software raid 1. That seemed to be working great, and after about 4 days of restoring from my backup system I have all my data back.
The problem now is that after about 24 hours of uptime, windows explorer completely locks up and requires a hard reboot of the machine when I try to access the software volume. This exact configuration with this exact same hardware worked fine a couple years ago.
So to recap:
* Storage space parity is broken
* Creating storage spaces pools is broken
* disk manager raid 1 causes the machine to completely freeze after 24 hours
* I haven't tried disk manager raid 0 yet
Is there anything I'm missing? Are software raids completely unsupported now?
At this point I honestly don't want to invest the time in trying to set up a software raid 0 and restoring all my backups again just to run into one more failure. I'm probably just going to fall back to using 2 separate hardware raid 0's and running a nightly synchronization script to turn them into a pseudo raid 1 instead of using disk manager.
I sincerely appreciate all the work that has gone into WSL2. Finally having Docker is amazing. And if I had to guess all of these issues probably stem from having linux metadata now embedded in the ntfs volumes, and the windows volume manager not being updated to account for it. But that's just my suspicion.
This whole situation sucks, please help :-(
Continue reading...
I previously had a windows storage spaces drive with 9 spinning disks. After updating to 2004 my storage spaces got ruined due to this bug. So I destroyed that, and then further discovered that windows storage spaces is not functional at all due to no longer being able to create disk pools
So I figured fine, I have hardware raid controllers, I'll just go back to using those because it doesn't seem like a good idea to trust windows to do any striping. So created 2 raid 0's with 4 disks each in my bios. Windows recognizes those just fine. And then I used disk manager to mirror the 2 volumes as a software raid 1. That seemed to be working great, and after about 4 days of restoring from my backup system I have all my data back.
The problem now is that after about 24 hours of uptime, windows explorer completely locks up and requires a hard reboot of the machine when I try to access the software volume. This exact configuration with this exact same hardware worked fine a couple years ago.
So to recap:
* Storage space parity is broken
* Creating storage spaces pools is broken
* disk manager raid 1 causes the machine to completely freeze after 24 hours
* I haven't tried disk manager raid 0 yet
Is there anything I'm missing? Are software raids completely unsupported now?
At this point I honestly don't want to invest the time in trying to set up a software raid 0 and restoring all my backups again just to run into one more failure. I'm probably just going to fall back to using 2 separate hardware raid 0's and running a nightly synchronization script to turn them into a pseudo raid 1 instead of using disk manager.
I sincerely appreciate all the work that has gone into WSL2. Finally having Docker is amazing. And if I had to guess all of these issues probably stem from having linux metadata now embedded in the ntfs volumes, and the windows volume manager not being updated to account for it. But that's just my suspicion.
This whole situation sucks, please help :-(
Continue reading...