VapechiK

I just wanted to say that @Christopher (Drashna)has been very helpful each time I've created a topic. I have found him and the others I've worked with to be thoughtful and professional in their responses.
Thanks for all the work you all do.
Now we can all stop seeing that other thread previewed every time we look at the forum home.

Thanks @VapechiK for the info. I actually was able to recover the information from records I have. However, that doesn't recover the most recent scan information which also reset. Something has happened that is preventing that information from persisting for some reason. I'd like to get to the bottom of that.
As to UPS, I am on all (relatively affordable) consumer hardware so I'm not really worried about equipment failures due to power outage. I've got everything plugged into surge strips and worst case if a component fails I'll just replace it. Too many stories over the years of home UPSes catching fire. To me they're an unacceptable home fire risk.  However, that power outage alarm you shared is pretty neat. Never seen one of those.
We definitely use large enterprise grade UPS and generators in our datacenters at work though  

hello.  in Scanner go to settings with the wrench icon > advanced settings and troubleshooting and on the first tab is where to bu/restore its settings.  you may have to enable the avanced settings from the 'general' tab under 'Scanner settings...' first.  it will create a zip file containing many json files and want to put it in 'documents' by default so just back it up elsewhere.  after renaming drives in Scanner i stop the StableBit Scanner service, twiddle my thumbs for a sec or three, restart the service and GUI and and the custom names and locations are all saved (for me anyway).  only then do i actually create the Scanner backup zip file.  i haven't had to actually restore Scanner using this zip file yet but it seems like it will work (knock on wood).  and i don't see how recent scan history would be saved using this method.  saved from when the zip file was created maybe but anything truly recent is likely gone.
it's probably a good idea to create a spreadsheet or text file etc. with your custom info ALONG WITH the serial number for each of your drives so if it happens again you can easily copy/paste directly into Scanner.  i set up my C:\_Mount folder with SNs as well so i always know which drive is which should i need to access them directly.
i have 2 UPSs as well.  1 for the computer, network equipment, and the RAID enclosure where qBittorent lives.  the other runs my remaining USB enclosures where my BU drives and Drivepool live.  even that is not fool-proof; if no one's home when the power dies, the one with all the enclosures will just run till the battery dies, as it's not controlled by any software like the one with the computer and modem etc, which is set to shut down Windows automatically/gracefully after 3 minutes.  at least it will be disconnected from Windows before the battery dies and the settings will have a greater chance of being saved.  if you have a UPS and it failed during your recent storm, all i can say is WOW bad luck.
one of these or something similar is great for power outages:
https://www.amazon.com/dp/B00PUQILCS/?coliid=I1XKMGSRN3M77P&colid=2TBI57ZR3HAW7&psc=1&ref_=list_c_wl_lv_ov_lig_dp_it
saved my stuff once already.  keep it plugged in an outlet near where you sleep and it will wake you up.
hope this helps  and perhaps others may benefit from some of this info as well.
cheers

hello.  in Scanner go to settings with the wrench icon > advanced settings and troubleshooting and on the first tab is where to bu/restore its settings.  you may have to enable the avanced settings from the 'general' tab under 'Scanner settings...' first.  it will create a zip file containing many json files and want to put it in 'documents' by default so just back it up elsewhere.  after renaming drives in Scanner i stop the StableBit Scanner service, twiddle my thumbs for a sec or three, restart the service and GUI and and the custom names and locations are all saved (for me anyway).  only then do i actually create the Scanner backup zip file.  i haven't had to actually restore Scanner using this zip file yet but it seems like it will work (knock on wood).  and i don't see how recent scan history would be saved using this method.  saved from when the zip file was created maybe but anything truly recent is likely gone.
it's probably a good idea to create a spreadsheet or text file etc. with your custom info ALONG WITH the serial number for each of your drives so if it happens again you can easily copy/paste directly into Scanner.  i set up my C:\_Mount folder with SNs as well so i always know which drive is which should i need to access them directly.
i have 2 UPSs as well.  1 for the computer, network equipment, and the RAID enclosure where qBittorent lives.  the other runs my remaining USB enclosures where my BU drives and Drivepool live.  even that is not fool-proof; if no one's home when the power dies, the one with all the enclosures will just run till the battery dies, as it's not controlled by any software like the one with the computer and modem etc, which is set to shut down Windows automatically/gracefully after 3 minutes.  at least it will be disconnected from Windows before the battery dies and the settings will have a greater chance of being saved.  if you have a UPS and it failed during your recent storm, all i can say is WOW bad luck.
one of these or something similar is great for power outages:
https://www.amazon.com/dp/B00PUQILCS/?coliid=I1XKMGSRN3M77P&colid=2TBI57ZR3HAW7&psc=1&ref_=list_c_wl_lv_ov_lig_dp_it
saved my stuff once already.  keep it plugged in an outlet near where you sleep and it will wake you up.
hope this helps  and perhaps others may benefit from some of this info as well.
cheers

Yup.  If you mark the bad blocks as unchecked, it will attempt to scan those blocks at the next available time (typically immediately).  If the rest of the disk is marked as healthy, it will only scan these blocks (as it only scans sections of the disk that are not checked or haven't been checked in the normal scan window (30 days).
 

@Shane and @VapechiK - Thank you both for the fantastic, detailed information! As it seemed like the easiest thing to start with, I followed VapechiK's instructions from paragraph 4 of their reply to simply remove the link for DP (Y:) under DP (E:) and it worked instantly, and without issue! 

Again, I thanks for taking the time to provide solutions, it really is appreciated!

Thanks much!

hhmmm yes, seems a hierarchal pool was inadvertently/unintentionally created.  i have no idea of your skill level so if you're not comfortable with any of the below... you should go to https://stablebit.com/Contact and open a ticket.  in any event removing drives/pools from DrivePool in the DrivePool GUI should NEVER delete your files/data on the underlying physical drives, as any 'pooled drive' is just a virtual placeholder anyway. 
if you haven't already, enable 'show hidden files and folders.'  then (not knowing what your balancing/duplication settings are), under 'Manage Pool ^  > Balancing...'  ensure 'Do not balance automatically' IS checked, and 'Allow balancing plug-ins to force etc. etc...' IS NOT checked for BOTH pools. SAVE.  we don't want DP to try to run a balance pass while resolving this. maybe take a SS of the settings on DrivePool (Y:) before changing them.
so DrivePool (E:) is showing all data to be 'Other' and DrivePool (Y:) appears to be duplicated (x2).  i say this based on the shade of blue; the 2nd SS is cut off before it shows a green 'x2' thingy (if it's even there), and drives Q & R are showing unconventional total space available numbers.  the important thing here is that DP (E:) is showing all data as 'Other.'
under the DrivePool (E:) GUI it's just as simple as clicking the -Remove link for DP (Y:) and then Remove on the confirmation box.  the 3 checkable options can be ignored because DrivePool (E:) has no actual 'pooled' data in the pool and those are mostly evacuation options for StableBit Scanner anyway.  once that's done DrivePool (E:) should just poof disappear as Y: was the only 'disk' in it, and the GUI should automatically switch back to DrivePool (Y:).
at this point, i would STOP the StableBit DrivePool service using Run > services.msc (the DP GUI will disappear), then check the underlying drives in DrivePool (Y:) (drives P, Q, & R in File Explorer) for maybe an additional PoolPart.XXXXXXXX folder that is EMPTY and delete it (careful don't delete the full hidden PoolPart folders that contain data on the Y: pool).  then restart the DP service and go to 'Manage Pool^ > Balancing...' and reset any changed settings back the way you had/like them. SAVE.  if a remeasure doesn't start immediately do Manage Pool^ > Re-measure > Re-measure.
i run a pool of 6 spinners with no duplication.  this is OK for me because i am OCD about having backups.  i have many USB enclosures and have played around some with duplication and hierarchal pools with spare/old hdds and ssds in the past and your issue seems an easy quick fix.  i can't remember whether DP will automatically delete old PoolPart folders from removed hierarchal pools or just make them 'unhidden.'  perhaps @Shane or @Christopher (Drashna) will add more.
Cheers  

hhmmm yes, seems a hierarchal pool was inadvertently/unintentionally created.  i have no idea of your skill level so if you're not comfortable with any of the below... you should go to https://stablebit.com/Contact and open a ticket.  in any event removing drives/pools from DrivePool in the DrivePool GUI should NEVER delete your files/data on the underlying physical drives, as any 'pooled drive' is just a virtual placeholder anyway. 
if you haven't already, enable 'show hidden files and folders.'  then (not knowing what your balancing/duplication settings are), under 'Manage Pool ^  > Balancing...'  ensure 'Do not balance automatically' IS checked, and 'Allow balancing plug-ins to force etc. etc...' IS NOT checked for BOTH pools. SAVE.  we don't want DP to try to run a balance pass while resolving this. maybe take a SS of the settings on DrivePool (Y:) before changing them.
so DrivePool (E:) is showing all data to be 'Other' and DrivePool (Y:) appears to be duplicated (x2).  i say this based on the shade of blue; the 2nd SS is cut off before it shows a green 'x2' thingy (if it's even there), and drives Q & R are showing unconventional total space available numbers.  the important thing here is that DP (E:) is showing all data as 'Other.'
under the DrivePool (E:) GUI it's just as simple as clicking the -Remove link for DP (Y:) and then Remove on the confirmation box.  the 3 checkable options can be ignored because DrivePool (E:) has no actual 'pooled' data in the pool and those are mostly evacuation options for StableBit Scanner anyway.  once that's done DrivePool (E:) should just poof disappear as Y: was the only 'disk' in it, and the GUI should automatically switch back to DrivePool (Y:).
at this point, i would STOP the StableBit DrivePool service using Run > services.msc (the DP GUI will disappear), then check the underlying drives in DrivePool (Y:) (drives P, Q, & R in File Explorer) for maybe an additional PoolPart.XXXXXXXX folder that is EMPTY and delete it (careful don't delete the full hidden PoolPart folders that contain data on the Y: pool).  then restart the DP service and go to 'Manage Pool^ > Balancing...' and reset any changed settings back the way you had/like them. SAVE.  if a remeasure doesn't start immediately do Manage Pool^ > Re-measure > Re-measure.
i run a pool of 6 spinners with no duplication.  this is OK for me because i am OCD about having backups.  i have many USB enclosures and have played around some with duplication and hierarchal pools with spare/old hdds and ssds in the past and your issue seems an easy quick fix.  i can't remember whether DP will automatically delete old PoolPart folders from removed hierarchal pools or just make them 'unhidden.'  perhaps @Shane or @Christopher (Drashna) will add more.
Cheers  

Yes, to completely prevent any chance of data loss from 2 drives suddenly failing at the same time you'd need 3 times duplication. Note that scanner doesn't protect against sudden failures; that's why they're called "sudden". Scanner protects against the type of failures that'll take longer to kill your drive than you/drivepool will take to rescue any data you want off it.
Basically there are what I'd consider to be four types of drive failure:
Sudden - bang, it's dead. This is what things like Duplication and RAID are meant to protect against. Imminent - you get some warning it's coming. Duplication and RAID also protect against this type, and Scanner tries to give you enough time for pre-emptive action. Eventual - no drive lasts forever. Scanner helps with this too by notifying you of a drive's age, duty cycle, etc, so you can budget ahead of time for new ones. Subtle - the worst but thankfully rarest kind, instead of the drive dying it starts corrupting your data. Scanner can sometimes give clues, otherwise you need some method of being able to detect/repair it (e.g. some RAID types, SnapRAID, PAR2, etc) or at least having intact backups elsewhere. DrivePool might help here, depending on whether you notice the corruption before it gets to the other duplicate(s). If it helps any, I suggest following the old 3-2-1 rule of backup best practice, which means having at least three copies (production and two backups), at least two different types (back then it was disk and tape, today might be local and cloud) and at least one of those backups being kept offsite, or some variant of that rule suitable for your situation.
For example, my setup:
DrivePool with 2x duplication (3x for the most important folders) to protect against sudden mechanical drive failure on the home server. Pool is network-shared; a dedicated backup PC on the LAN takes regular snapshots to protect against ransomware and for quick restores. Pool is also backed up to a cloud provider to protect against environmental failures (e.g. fire, flood, earthquake, theft).

Especially if this is not an NVMe drive, SSDs use all sorts of different values for SMART.   What is valid and okay for one drive may be out of spec on another drive. And that's not asuming that the OEM isn't using some sort of encryption/obsfuscation for the numbers.   Which is super common.  
NVMe has an actual, published standard, and is generally better about this (though, we've seen a few instances of issues with this). 

hi.  in windows/file explorer enable 'show hidden files and folders.'  then go to:
https://wiki.covecube.com/Main_Page  
and bookmark for future reference.  from this page on the left side click StableBit DrivePool > 2.x Advanced Settings. 
https://wiki.covecube.com/StableBit_DrivePool_2.x_Advanced_Settings
if you are using BitLocker to encrypt your drives you will NOT want to do this, and will just have to live with the drive LEDs flashing and disc pings i assume. i don't use it so i don't know much about it.
the given example on this page just happens to be the exact .json setting you need to change to stop DP from pinging your discs every ~5secs.
set "BitLocker_PoolPartUnlockDetect" override value from null to false as shown.
if StableBit CloudDrive is also installed you will need to change the same setting for it also. opening either of these json files, it just happens to be the very top entry on the file.
you may need to give your user account 'full control' on the 'security' tab (right click the json > properties > security) in order to save the changes.
this worked immediately for me, no reboot necessary. YMMV...  good luck

hi.  in windows/file explorer enable 'show hidden files and folders.'  then go to:
https://wiki.covecube.com/Main_Page  
and bookmark for future reference.  from this page on the left side click StableBit DrivePool > 2.x Advanced Settings. 
https://wiki.covecube.com/StableBit_DrivePool_2.x_Advanced_Settings
if you are using BitLocker to encrypt your drives you will NOT want to do this, and will just have to live with the drive LEDs flashing and disc pings i assume. i don't use it so i don't know much about it.
the given example on this page just happens to be the exact .json setting you need to change to stop DP from pinging your discs every ~5secs.
set "BitLocker_PoolPartUnlockDetect" override value from null to false as shown.
if StableBit CloudDrive is also installed you will need to change the same setting for it also. opening either of these json files, it just happens to be the very top entry on the file.
you may need to give your user account 'full control' on the 'security' tab (right click the json > properties > security) in order to save the changes.
this worked immediately for me, no reboot necessary. YMMV...  good luck

Thanks Shane for confirming DrivePool was the source and thanks VapechiK for the solution. I set the "BitLocker_PoolPartUnlockDetect" override value to False and after a reboot all the pings were gone.
For what it's worth the only reason I noticed this is that I wasn't seeing the external (backup) drive going into standby power mode so I started to look for reasons. Power mode is still active but I think Hard Disk Sentinel's SMART poll may be keeping that drive alive. Not a big deal now that the pings are gone.

Thanks for your insight and review, @VapechiK
I'll definitely keep it out of a mission critical role.  Right now it just has duplicated data from my drivepool, that is backed up elsewhere, and Steam game installs, so nothing I'm afraid of losing.  It's the first offbrand SSD I've bought so I wanted to give it a shot and tried to grow my drivepool cheaply.
I have an Intel 1TB nVME boot drive and a Samsung 1TB EVO and 2TB QVO and a Crucial 1TB besides the SP drive in the same machine. 
I had 2 Samsung 128GB Pro boot drives that stopped being useful after 10 years of power on time.  They would randomly corrupt system files until it wouldn't boot. I'd say they were a success. I bought a Kingston 480GB drive to replace the last one of those and it seems to be doing well.  I had an OCZ that would hangup at boot time and not be detected after only a year or so, that one really sucked.  Never any weird Scanner reporting with any of these drives.
I think I'll hold out a little longer to see what happens further to the price of the name brand 2TB SSDs.

and 104F = 40C, so it is likely the same crappy firmware on yours that was on the 2 that i returned.
i guess they can get away with it as 'most' users will just buy it, install it, and not really monitor it. so these errors and notifications are never seen by joe average user who runs games from it and is suprised when it fails suddenly (check out all the 1 star reviews on the amazon page lol).
i have 4 SSDs. all are WD. 1x Red SN700 500GB NVME boot drive. 2x Red 1TB 2.5" and 1x Blue 2TB M.2. they all show up fine SMARTwise in Scanner and HDSentinel. i guess this makes me a WD 'fangirl,' but really that's just how it worked out. before i tried the Silicon Power drives, i tried both the LEVEN JS600 SSD 2TB and the 
fanxiang S101 2TB SSD. all 3 were underwhelming performance-wise compared to the WDs. gotta love amazon's 30 day return policy
iceman1337 is correct and he's echoing christopher (drashna). SMART on SSDs is all over the place as manufacturers just make it up as they go.
your SP might last for years ignoring whatever errors it shows. but i wouldn't trust it for mission critical data. just my .02 cents...

I'm certainly not reading it backwards, as Scanner has a clear 100% life used warning in red, that I ignored for this SSD and the SSD Life Remaining field saying 0%.
Also has way too many power cycles because my PC was sleeping and waking almost immediately, I finally tracked that down to being Scanner's wake to scan feature, which made no sense, because because it didn't scan after it woke up the PC.

welcome to the world of cheap SSDs. a few months ago i bought 2x2TB Silicon Power 2.5" SSDs from amazon. hooked them both up to system SATA bus. one drive reported 1863GB and the other 1907GB. diskpart was ineffectual. both were locked at SMART temp 40C (idle or high I/O). writing to them from my WD Red NVMe was ~300MB/s so much less than advertised. there is a downloadable SP monitoring tool similar to the WD dashboard. i did not notice an option to upgrade firmware when i ran it. so after a few days of this i returned them to amazon easy peasy.
aside from a much needed firmware update from SP, i doubt scanner can do much other than report whatever the drive is feeding it. the drive itself may be perfectly fine and ignoring the warning is probably safe for now. i myself cannot abide that type of discrepancy staring me in the face. YMMV, but if it were me i'd return it and get a WD, which is what i actually did. 
 

You also opened a ticket for this. 
But to repeat what I said there, and echo what vapechiK said, 
This is perfectly normal, and expected.  In all cases, here. 
the pool drive itself is fully virtual, but doesn't have any blocks/data on the drive. All of the data is "reverse proxied" to the underlying disks, and handled invisible.  So CHKDSK won't work on the drive, and it does not appear in StableBit Scanner.   And the size is normal, as Windows needs a size before that can be properly read, so the 2TB size is a placeholder. 

Thanks to you both for the prompt and detailed response.

I think I'm gonna call the tray icon from now on the "Gold Shield of Worry" (GSoW).  Kinda goes along with Blue Screen of Death and Red Ring of Death, only with less Death.
Thanks, Christopher, for the likely answer.  Still hasn't occurred again (thank God).  I've already lost a bunch of drives over 2022 and didn't need this on the very first damn week of 2023.
VapechiK, it's good to share misery, even if it is, y'know, misery.  I'm actually on the verge of swapping-out my entire system, as I suspect my creaky Norco has been slow-roasting my drives for the better part of five years.  Then again, I did modify it to support an AIO and probably blocked some critical airflow in the process.
Never let me borrow a dremel.

Hi everyone,
After dreading that i would have to add an additional drive to my server to be able to mount my clouddrives (which would cost me a lot, as it is not local to me), I tried a lot of possible workarounds.
While i understand the reasoning for not allowing certain drives to be pooled, and I do not recommend doing this unless you understand the risks, I am happy to report it definitely works, with no issues in my testing.
So a as a TL;DR;
You can create a VHD(X) file on a dynamic volume, mount that, then create a storage space with this mounted VHD(X) file, which can then be pooled and/or used as clouddrive cache.
The performance decrease is quite minor, as you can see from some quick testing on a old 840 evo drive;

[LEFT: local disk mounted directly, RIGHT: mounted VHDX -> Storage Space -> Drivepool]
Step-By-Step:
Doing this is easy, and it only takes a few steps;
Create the VHD(X) file Mount the VHD(X) file as a drive Create a storage space with the mounted VHD(X) drive(s) Use the storage space as clouddrive cache or add it to a drivepool pool 1. First we make the VHD(X) file if you do not have one yet, which we can simply do from disk manager; Action -> Create VHD
you are then presented with the following prompt, in which you can choose the size and location of the VHD(X)

For optimal performance it is recommended to choose 'VHDX' and 'Fixed size'
2. Next we need to mount the VHD file if it hasn't done so already, which we can also do from disk manager; Action -> Mount VHD
We don't need to initialize or format the drive, it will undo this in the next step anyway.
3. Almost done! We now need to create a storage space, as the mounted VHD(X) still cannot be used by clouddrive/drivepool
To do this, we open the storage spaces configuration screen (search 'storage spaces'), and choose 'create a new pool and storage space'
in the following screen select the mounted VHD drive ("Attached via VHD"), which should show up under "Unformatted drives" be careful to not select a different drive, this will wipe all data!
In the wizard we can now select the size, parity settings, and format settings, in this example we are using 'simple', but you can choose other settings if you're using multiple VHDs.

4. If everything went well, we should now be able to detect the new storage space drive in both clouddrive and drivepool, ready to be used!
And we are done!
For some reason because we created a storage space, we no longer need to manually mount the VHD drives on reboot, so the system keeps working.