O
Ondřej Mašita
Hello, I'm dealing with an odd issue I have with Storage Spaces. I have been using it for a while now on two machines without major issue, until today. The machine in question has:
Storage Pool:
Virtual Disk (notice the Unhealthy status):
And the drives themselves:
FASTPARITY1 is a disk with Bitlocker enabled and automount off. Whenever the PC is started and user wants to access data, they are prompted for Bitlocker password.
FASTPARITY2 is a disk without any encryption. It is formatted with NTFS and is available after logging into Windows.
What have I done that has caused this:
Due to some hardware upgrading today, I have done the following: I have unplugged all physical discs from PC1 (where everything worked and PC1 was properly shut down like always) and connected them to PC2. I knew from before that this works and Storage Spaces on PC2 should pick everything up automatically. I have noticed that virtual disk FASTPARITY2 was immediately recognized by PC2's Storage Spaces, while the FASTPARITY1 was not. I went into Storage Spaces UI and this popped up:
When I scroll down to physical drives section, there is no issue:
When I try to manually connect the detached virtual disk, I am greeted with strange error:
I thought to myself: "OK, there's something wrong here, let's plug them back to PC1 where it all worked 5 minutes ago." But situation at PC1 is identical, same errors, same issues. The Storage Space seems fine (reports healthy), but the bitlocker-encrypted virtual disk reports unhealthy status and cannot be accessed.
The data is mostly backed up elsewhere, but some would still be lost if I can't recover from this. Any help is greatly appreciated.
Continue reading...
Storage Pool:
Virtual Disk (notice the Unhealthy status):
And the drives themselves:
FASTPARITY1 is a disk with Bitlocker enabled and automount off. Whenever the PC is started and user wants to access data, they are prompted for Bitlocker password.
FASTPARITY2 is a disk without any encryption. It is formatted with NTFS and is available after logging into Windows.
What have I done that has caused this:
Due to some hardware upgrading today, I have done the following: I have unplugged all physical discs from PC1 (where everything worked and PC1 was properly shut down like always) and connected them to PC2. I knew from before that this works and Storage Spaces on PC2 should pick everything up automatically. I have noticed that virtual disk FASTPARITY2 was immediately recognized by PC2's Storage Spaces, while the FASTPARITY1 was not. I went into Storage Spaces UI and this popped up:
When I scroll down to physical drives section, there is no issue:
When I try to manually connect the detached virtual disk, I am greeted with strange error:
I thought to myself: "OK, there's something wrong here, let's plug them back to PC1 where it all worked 5 minutes ago." But situation at PC1 is identical, same errors, same issues. The Storage Space seems fine (reports healthy), but the bitlocker-encrypted virtual disk reports unhealthy status and cannot be accessed.
The data is mostly backed up elsewhere, but some would still be lost if I can't recover from this. Any help is greatly appreciated.
Continue reading...