You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Windows 11
For example, when I plugged in No.1 drive, it showed as F:\ and SpaceDrive indexed No.1 drive correctly.
I unplugged No.1 drive, and plugged in No.2 drive instead, Windows will show drive No.2 as the same F:\ (Normal behavior)
But now SpaceDrive will recognize No.2 drive as the same "F:" drive, and overwrites the previously created drive No.1's index.
I really hope developers could use the drive's hardware serial number to recognize different drives.
Steps to reproduce
Plug in a new drive No.1, it showed as F:\ by Windows. SpaceDrive indexed it automatically without issue.
Unplug drive No.1
Plug in drive No.2, Windows will show drive No.2 as F:\ (Normal behavior)
SpaceDrive will recognize drive F:\ (Drive No.2) as the previously indexed drive No.1
Indexes would get overwritten and the index of drive No.1 would get replaced by drive No.2's index
Platform and versions
OS: Windows 11
Spacedrive: Alpha 0.4.2
Development tool versions (optional)
Stack trace
Additional context
No response
Code of Conduct
I agree to follow the Code of Conduct.
The text was updated successfully, but these errors were encountered:
Check for other issues
Issue description
Windows 11
For example, when I plugged in No.1 drive, it showed as F:\ and SpaceDrive indexed No.1 drive correctly.
I unplugged No.1 drive, and plugged in No.2 drive instead, Windows will show drive No.2 as the same F:\ (Normal behavior)
But now SpaceDrive will recognize No.2 drive as the same "F:" drive, and overwrites the previously created drive No.1's index.
I really hope developers could use the drive's hardware serial number to recognize different drives.
Steps to reproduce
Platform and versions
Development tool versions (optional)
Stack trace
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: