As the slightly lengthy title describes, there's 2 notable issues which weren't there the last time that I needed to do something like this - on an unknown previous build.
Well, it's only spasmodically that I need to do something major with the pools that's better done by creating new ones from scratch.
So firstly, whilst removing other drives from a pool works fine, removing the final one *always* causes a BSOD - this occurring on 2 different machines & with the drives on Intel, Marvell & a LSI controller; as well as if the final drive's connected via USB... ...& irrespective of whether there's any user data on the last drive in the pool.
(it can be worked around by either booting into safe mode & deleting the partition in Computer Management / or connecting to a machine without DP installed - however these aren't exactly user friendly)
&, secondly, if any drive is missing from the pool, it's making all of the files/folders read only - again on both machines - which, given that there are finite SATA/SAS ports (& a USB dock), means that the new pool(s) cannot be made with all of the drives that 'should' be there; leading to time wasting with the new pool having to move data around again once it's possible to add the remaining drives.
(obviously the data can be 'recovered' from the RO drives, using something like R-Studio, however this really isn't a great solution - as 'if' instead the issue was a failed drive & someone couldn't afford to replace it instantly then this significantly limits the ability to use the data)
Okay, so having moved most of the data around - 5 new pools created / 4 of the new pools having all of the data on / & 4 of the 5 pools removed - then any solution probably won't be in time to help...
...so it's simply reporting that these issues have been a b nuisance & they really need sorting.
Oh, & (obviously) using v2.2.0.906 - the 64bit Windows version.
Question
PocketDemon
As the slightly lengthy title describes, there's 2 notable issues which weren't there the last time that I needed to do something like this - on an unknown previous build.
Well, it's only spasmodically that I need to do something major with the pools that's better done by creating new ones from scratch.
So firstly, whilst removing other drives from a pool works fine, removing the final one *always* causes a BSOD - this occurring on 2 different machines & with the drives on Intel, Marvell & a LSI controller; as well as if the final drive's connected via USB... ...& irrespective of whether there's any user data on the last drive in the pool.
(it can be worked around by either booting into safe mode & deleting the partition in Computer Management / or connecting to a machine without DP installed - however these aren't exactly user friendly)
&, secondly, if any drive is missing from the pool, it's making all of the files/folders read only - again on both machines - which, given that there are finite SATA/SAS ports (& a USB dock), means that the new pool(s) cannot be made with all of the drives that 'should' be there; leading to time wasting with the new pool having to move data around again once it's possible to add the remaining drives.
(obviously the data can be 'recovered' from the RO drives, using something like R-Studio, however this really isn't a great solution - as 'if' instead the issue was a failed drive & someone couldn't afford to replace it instantly then this significantly limits the ability to use the data)
Okay, so having moved most of the data around - 5 new pools created / 4 of the new pools having all of the data on / & 4 of the 5 pools removed - then any solution probably won't be in time to help...
...so it's simply reporting that these issues have been a b nuisance & they really need sorting.
Oh, & (obviously) using v2.2.0.906 - the 64bit Windows version.
Link to comment
Share on other sites
5 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.