klepp0906

i may or may not have been editing the non-override portion the first time i gave it a go. this time i had more time to go through the covecube doc and was made aware of the override section. convenient and preferred for sure, the setting also held after a restart. Unfortunately changing it to false had no effect on my drives sleeping. changed it to false, changed my scanner to have 60min throttle and only check during work window "12am > 12pm" and 24 hours later 0 spindowns on any of my disks. disable the drivepool service in services.msc. down they go as intended.

gotcha. thanks anyways. one of my larger gripes with drivepool. ive tested on a brand new fresh windows 11 install. added drivepool and sleep immediately stopped. throttled smart scanning through timer and work window, disabled bitlocker detection in the json and still no sleep on any of my drives 24 hours later. disabled the drivepool service specifically and they immediately started sleeping. should be a higher priority for the dev id think. summer months are coming and people using drivepool tend to be using lots of drives in small spaces in a non enterprise environment. it gets ~75f in my upstairs office and with 24 7200rpm disks in a chassis i'd prefer them to be spun down if nobody is plex'ing etc.

I have 2 pools and 1 re-measures without fail every time i restart the PC. I've reset permissions for the entire pool, i've also changed CoveFs_WaitForKnownPoolPartsOnMountMs and CoveFs_WaitForVolumesOnMountMs from 10000 to 60000 in an attempt to make it stop. Ive set drivepool service to delayed start. Without fail it continues. i'm out of ideas. If i manually measure the pool it takes about 4 seconds. literally. for ~30TB data on a 75TB pool made up of 11 disks. Does this seem right? Or like its not even measuring the pool? Lord knows my other pool with just as much data takes a lot longer.

pretty much universally no lol. intel system and i'm connected via HBA. It seems to be in high stress situations though, have not seen it happen during general use that I can recall but its pretty frequent when accessing everything at once or under really heavy io

I'll be the first to admit, this is relatively new ground for me. That being said, its evident SMART is a standard and so you'd think most things would be uniform regardless of medium/platform. if i use snapraid and/or smartctl to run my smart data it comes up with one of my drives at 100% chance of failure within the next year. It has 43 unrecoverable errors. The SMART wiki itself indicates unrecoverable errors as being one of the several "critical" attributes. A quick google and the consensus is "id replace a disk with errors ASAP" i decided to check scanner as i'd received no warnings or anything of the nature. Meanwhile scanner sees the 43 errors but apparently determines that as being just fine. which is right?

Does this generally indicate failing disks? Ive noticed on two occasions now ive had 2 separate drives drop from the pool. A restart didnt bring them back. Only a shutdown and restart of my jbod/chassis that keeps the disks powered on 24/7 otherwise. They tend to drop during heavy use (during a snapraid scrub in this case) just trying to figure out if thats likely the issue before i go dropping the exorbitant cost on a few hard drives that may not fix the issue. I assume thats its likely but with no warnings from scanner smart or otherwise I'd love some reinforcement or otherwise

mkay, i was suckered in. mostly to support covecube (totally need to change company name to stablebit, confusing) but id be lying if i didnt say it was also in part to keep remote notifications on my phone etc, just in case. now since i feel like im on the board, where's my dark mode. speak up fellow shareholders!~

anyone able to bring me up to date on this? I have two pools, 11 disks each. Every time i restart the computer one of them re-measures. the other one does not. EDIT: so ive removed a few older drives and upgraded them to 12tb exos which did not solve the issue. ive also reset the permissions on the entire pool with no luck. gonna try that settings.json edit even though i cant understand why i'd need it on one pool and not the other. the irony is the pool that SHOULD be slower (millions of small files) is the one that does not have this issue while the pool with all large media files does.

I did not. I got side tracked and just disabled it for now. I’ll post back when I get back around to revisiting it should I get it sorted though.

ill try editing it and restarting without restarting the service. perhaps something is cached thats rewriting it or being synced from scanner or something. youre right, waiting for spin-up can be annoying. you have to pick your battle i guess. a lot of disks (27 in my case) is a lot of heat, power etc. some drives have data that i use once every few days or even less so i think you move beyond the tipping point as far as wear n tear from perpetual spinning vs spinning down. if nothing else i like things to function as they should and know that i have the option to go back and forth in the future. of course the other angle is what disabling the setting actually does. apparently has something to do with detecting encrypted drives which I dont use, but if i did - what would be the result. error? crash?

mmm. a per device is rough. for minimal devices id prefer xxx a month up to 2 or 3 devices, then 1/m per additional device. will have to look into it and mull it over more. while i like the idea of supporting stablebit a bit more, nowadays im "subscriptioned" to death. literally its insane. A dollar a month i can submit to, but im not going to simply cover one device lol. thanks for the link

i cannot figure this out. I get notifications and they pile up. always one pool having been measured/complete over and over. 4 of them last i checked. 0 of them for my other pool. is this done as a maintenance sort of thing on a schedule or only when files are added? I can only assume it has to be the latter right? Thats all that would make sense in my scenario as they share the same exact settings through and through, all that is different is the latter has had some media added, the former has been static for now.

Ugh.. talk about triggering. I have 2 pools. one has very little other data relative to the media present. maybe 3gb against 40TB of actual data. I have another pool that also has about 40TB and after a full on disk equalizer balance pass it removed it all. showed 0 other data which was great, as i didnt expect there to be any outside of necessary metadata made by drivepool. I ended up doing a re-measure and now its showing 23.5gb..... from zero after balancing to 23.5gb. should i assume the latter number is correct and the first time it didnt calculate it for some reason? and is 23.5gb an unreasonable amount for metadata against this volume of data? Since both pools have the same amount of disks, the same amount of total storage, the same size of disks... the only thing i can come up with is the metadata is generated in blocks and on the pool that has barely any "other" data the files are way way way fewer in number because theyre big whereas the pool that shows ~24gb of "other" data theres a few million files i believe. lots of small stuff. confirmation thats the culprit or do i have something else going on?

Ever resolve this? I just came to the same conclusion. Reformatted to a fresh windows 11 and had sleep fine. Installed the stablebit trio and lost it. 6 services in total. Disabled them one by one until I got to the last one, drivepool itself. disabled that, sleep returned.

okay, did one final test here for posterity. i did a balancing pass (decided to give up on ordered file placement) and after it was finished a day or two later i disabled automatic balancing. i disabled ALL plugins. there was nothing left but drivepool itself running. still, pinging and keeping my drives awake every 5-6 seconds (my one, one-thousand, two one-thousand, may not be the most accurate) but on queue i can watch it blip the light on the drive closest to me. this speaks to something underlying that drivepool is doing. i even thought it might be controller based but a drive on a different controller and not in the pool altogether is still being kept awake. as a new user im not sure if this is something to manifest itself as of late as i've heard people speak about sleep/spindown in the context of drivepool during my research so assumed it worked. aka should a ticket be put in or the dev be made aware?

I found a drawback to using the non native windows frames! (i just upgraded to 11) man the window snapping by mousing over the maximize button is a game changer. not often i say this but w2g microsoft. unfortunately it comes at the expense of being able to move the taskbar, at least for now. ugh. anyhow, not possible with drivepool and cloud drive. something to consider. unless you can tap it into the up arrow. even then i'd go for cohesion though personally im anal and ocd AF though.

thank you very much for the detailed reply. youve been very helpful and i appreciate the time it took. sounds like outside of a bit of clarification on ~3 i have a much better understanding. seems like the defaults are defaults for a reason. ive recently decided to nix the whole ordered file placement idea anyhow. while it has merits I believe it runs converse to an idea of pooling to begin with. i can not only wash my hands of being concerned what is where and the micromanagement it will involve, but I also dramatically decrease the load on snapraid by not having my honking 10TB+ disks filled to the brim first (which is how it is atm, largest > smallest) all I lose is a bit of sanity (ocd) and a better idea of what would be missing if something died. I have to surrender to scanner/snapraid/local backups/databases doing their job. Anything thats "truly" unrecoverable is backed up anyhow. In the end it would just be time and/or willpower to pick up the pieces lol. I'm actually doing a first balancing pass atm. I reset everything to default, enabled disk space equalizer by percentage (it was the option that got my large disks to the lowest data volume relative to the smaller disks to have them closer in actual data since snapraid operates on file not block its important for efficiency). based on its current progress it looks like 3-4 days lol. im sure my first snapraid sync will take the same. ooof. after that i'll disable equalizer and automatic balancing and let it fly. (maybe all other balancers too except scanner). Since we dont want things moving after that and from what i understand drivepool will just always place on new drives with the largest amount of free space.

I’ve been battling this for a solid week now. It’s not scanner it’s drivepool itself. At least in my case. I was coincidentally in a position with a brand new windows install and my drives zzzz. I installed the stablebit trio. Sleep went bye. Disabled the services for each one by one. Scanner disabled. No sleep. Cloud drive disabled. No sleep. Drivepool disabled, started sleeping again. the hilarious part is the drive I was monitoring at the time for sleep isn’t even on the same controller or part of the pool. that being said, the lsi registry edit is necessary, as I tested it on my old windows install. The hba connected disks wouldn’t sleep without it. Wouldn’t sleep with drivepool service going either way. still I wanted a clean environment to be 100% and so that was the first thing I checked post format.

I'll paypal over the cost of another license right now if you get this in. please please please allow to choose sorting method. its using lexicographical and not numeric. doesnt jive with explorer among other things and makes me insane. I dont want to have to prepend zeroes on everything just to get it to sort in order. dont have to swap to the other sorting method entirely (even though i believe that'd be the lesser evil) just make it an option so people can choose. i beg of you data gods.

so just did some more testing. stablebit installs 5 services. I disabled them all one by one and watched. the final one to disable was DrivePoolService. Voila, perpetual pinging disappeared. Here the entire time i figured it was scanner, its drivepool itself. so why is that hammering my drives in perpetuity and how do i fix it? I have auto balancing off, I have every single plugin disabled except for ordered file placement. is it some kind of unintended bug or? Summer is coming and a 10x room with 24 of these 7200rpm badboys spinning next to me is no bueno.

Man if i dont feel like a familiar face around these parts at this point. I just dont want any surprises so i want to get this right he first time, for the long haul. My intentions are to use ordered file placement to keep what i have together, and fill drives sequentially to make life easy with snapraid. so far ive done no balancing and disabled automatic balancing. under balancers ive left the hierarchy at default (in case i want to use others later i'll have a lay of the land) and disabled all of them except ordered file placement. Ive used that to set my drive order and gave it a 90% limit. assuming I want the aforementioned behavior, how do i want the following settings, checked or unchecked? 1 - Allow balancing plug-ins to force immediate balancing (regardless of the automatic balancing setting). 2 - File placement rules respect real-time file placement limits set by the balancing plug-ins. 3 - Balancing plug-ins respect file placement rules. 4 - Unless the drive is being emptied. Now the only other use-case I can foresee in the near future is potentially enabling the scanner plug-in for evacuation. If i were to do so, would i leave it where it is, or move it below Ordered file placement and how would those 4 settings change? Ugh, i feel like after this I can finally be free of spamming these forums in perpetuity

Brand new windows install. drives are sleeping as expected, as they should. I install stablebit suite and poof, no more sleep once again. I can literally watch the light on my single external disk in a dock flicker every 5-6 seconds. what are these guys doing in that timeframe on repeat? I have a work window set on scanner. all my drives are already checked/healthy/not due. I have SMART set to only query during the work window or scanning of which it is neither. I dont know what else to do. on my old windows 10 install i entertained the fact it could have been a combination of any number of things i had running in tandem/under the hood (even though it was unlikely) but now with a fresh install of windows and watching it happen the second i installed these guys...... anyone able to offer some suggestions/guidance? I'd already throttled the queries out to 12 hours and it didnt help or change anything. leads me to believe its not the smart, but something else under the hood. is it even scanner, could it be drivepool itself or clouddrive?

the answer i expected. so the abridged version is "apple things" naturally.

i just ended up taking this opportunity of learning all the stablebit softwares and setting up snapraid etc to rip the bandaid and after 5 or so years running and a proclamation to never do so, reformat my pc and upgrade to 11. to be fair, i was pushed over the edge by permissions issues with adobe that i simply could not resolve. still bugs me, and scares me it could crop up again but i digress. back to the point, Ive kept 2FA disabled so i'm going to reconnect on 11, and let it sit for awhile. If it all checks out i'll re enable 2FA and repeat. should it crop back up i'll post a ticket instead of posting here. 2FA should pose no issue for it then? on any of the providers for that matter?

no, the cache was/is on a spinner and the image is of the system drive (C) @johnibhoni as for the type of i/o errors, unsure I was just going off of the notifications I was getting from clouddrive not windows i/o errors.