Christopher (Drashna)
-
Posts
11573 -
Joined
-
Last visited
-
Days Won
366
Posts posted by Christopher (Drashna)
-
-
Not really, unfortunately. It's all done through normal APIs, so "it's a windows thing/issue".
-
-
Try resetting the settings
https://wiki.covecube.com/StableBit_DrivePool_Q2299585B
If that doesn't help, open a ticket at https://stablebit.com/contact
-
No, it's not. Files are written to the "SSD", and then later balanced off.
-
-
You can set a work window for StableBit Scanner to run it's scans, yes.
Also, over time, it should get better about when to scan the drives.
And to clarify, it isn't an "all or nothing" for the scan. It keeps track of the areas on the disk that have been scanned, and when. So even if a scan gets interupted, it will pick up where it left off.
-
On 2/28/2022 at 6:07 PM, klepp0906 said:
ive been a longtime user of voidtools everything. one of my must-haves. the problem is, if i try to search a directory and its part of my pool, i get nothing. I have to go find the mount point and as you can imagine, trying to find which one contains a particular file isnt the ideal way. (i believe in my limited reading on the matter, the actual fix for that is on you guys end atleast as per an old post by the dev).
If VoidTools Everything is using the USN Journal to search for things, that would be why. It is not supported on the pool, and you need to fall back to a different method.
On 2/28/2022 at 6:07 PM, klepp0906 said:having a context menu item to open the items path would give a little bit slower and little bit less convenient way to search a directory or drive with everything but it would be an improvement on what it is now. I had to choose between no drivepool or breaking everything and i chose drivepool but man im trying to make it as little pain as possible
Do you mean like a context menu in explorer that would jump to the underlying disks for the path in the pool?
-
Mostly, this.
You can use utilities like WinDirStat to view the drives. But it's very possible/likely that you won't find anything specifically. Most likely, the difference is due to the size vs size on disk differences (slack space), as well as the System Volume Information folder on each disk.
-
Real-time placement limiters are different. They're mostly used by the Stable Scanner, Ordered File Placement and SSD Optimizer balancers to ensure that no files are placed on these drives. They're the "red arrows" you may see on the drives.
-
The SSD Optimizer balancer plugin causes new files to be written to the "SSD" drives (which you can pick), and then later balanced off of those drives.
So sudden power loss or reboots should not impact the data, at all.
-
I just use column and row for my server chasis, but "bay #" for internal drives.
-
On 2/26/2022 at 2:29 AM, Cabel said:
I read about it, but in case I wonder why it poped up after many month out of nowhere.
I even reseted my pool and the 50GB were shown on another drive then.
So what else can i try to delete the 50GB "Others"?
The main two reasons that this can happen. File system errors and chkdsk, which may lead to a "found.###" folder. the other reason is VSS snapshots, especially if the data on that drive changed a lot (such as balancing data off of it).
On 2/26/2022 at 2:29 AM, Cabel said:In diskmanagement the size of the pool is 2TB instead of 50,9TB. Does this matter in my case?
That's normal. It's an artifact of how Windows manages drives. It has to have a size before we can properly calculate the size. So it's a placeholder. But if you notice, everywhere else, it reports the correct size.
On 2/26/2022 at 2:29 AM, Cabel said:BTW: Where are the wss troubleshoot tools in V2? I cant find them.
Nope. But I think it should still work for v2
-
Yeah, I believe that it should.
-
Thanks for letting us know.
I can confirm this behavior, as well, and have flagged it.
-
There aren't any plans on doing so, ATM. That may change in the future.
-
Nice!
-
No, it's not, currently. And there are some issues with doing so, for a number of providers (eg, app folders, etc)
-
Internally, there has, yeah.
But one of our goals for the pricing is to to keep it reasonable, so that it's attractive to everyone.
-
On 2/26/2022 at 5:30 AM, klepp0906 said:
1) What happens if i were to swap drives in my chassis though? not replace one but simply change location from say Bay 5 to Bay 7. I assume i'll need to manually update this in scanner or will scanner somehow track this for me?
You will need to manually update the location information.
On 2/26/2022 at 5:30 AM, klepp0906 said:2) I'm trying to find the best balance between reliability and allowing my drives to spin down. 24 in a chassis is a lot of juice and a lot of heat. Stablebit stuff is keeping them from sleeping period, ever. I want to dial in on which one of the trio is the culprit but first i'm trying to get my settings right. Under SMART the throttle queries option is self explanatory. How about only query during the work window or if scanning though? I dont have a work window set so I assume that part is null? So only if scanning applies. Does this mean when it does a scan of a disk thats the only time it will query SMART? Will it do it for the entirety of the time its scanning or just at the start of the scan? Will it query smart on just the disk its scanning, or on all disks?
In StableBit DrivePool, disable the bitlocker detection. That helps from that end.
https://wiki.covecube.com/StableBit_DrivePool_2.x_Advanced_SettingsFor StableBit Scanner, throttle the SMART queries, as that usually helps.
https://stablebit.com/Support/Scanner/2.X/Manual?Section=SMARTAs for the work window, that's defined in the "general" tab. So if you don't have a window set, then this setting doesn't do you much good.
On 2/26/2022 at 5:30 AM, klepp0906 said:3) Does scanner only notify if the disk EXCEEDS (not reaches) the maximum temperature?
Meets or exceeds it. Also, there is a threshold setting to. It will warn you as it approaches that maximum. (default is for a 15C window)
On 2/26/2022 at 5:30 AM, klepp0906 said:4) what is the logic as far as scan time goes when set to automatically scan with no work window defined? I have scanner open right now and nothing is scanning even though I have a dozen disks that have yet to been scanned. I also have some saying (waiting to scan disk access) which is odd considering its an unpooled unmapped disk with nothing on it. Also another of the same (unmapped and empty) that says Waiting to scan (bus saturated) meanwhile looking in task manager all my disks are idle for all intents and purposes...
It's one disk per controller. So if you have multiple controllers, such as onboard, and a controller card, it can scan multiple disks.
It checks the disks, and see if there are any disks with sections that haven't been scanned in "x" days, with x being the settings for how frequently to scan.
There are some other factors, such as disk activity, etc.
On 2/26/2022 at 5:30 AM, klepp0906 said:5) scan using background i/o priority. is this a disk by disk basis? or does it mean if theres any disk activity on that controller it'll cede scanning? seems redundant with the "do not interfere with disk access" setting
It means that the scanning is done in such a way that any normal activity takes priority over the scans, and may stop the scanning from occurring. This way, it minimizes the performance impact for the drives, ideally.
-
Awesome, thank!
-
You are very weclome!
On 2/25/2022 at 2:08 PM, klepp0906 said:I assume by deleting the device from stablebit cloud you mean removing the pc that shows with the hostname? I imagine that will leave me re-activating all my stablebit softwares?
Correct. At least for that system. Reconnecting it should automatically re-activate, though.
-
lol. Well if it helps, IIRC, you can have multiple parity drives with SnapRAID, which I'd definitely recommend.
-
Yeah, the notification will remain until it's resolved.
If you really, really must kill the notifcations, you an disable the notification.exe process. I don't recommend it, because you may (will) miss important notifications.
-
StableBit Cloud will sync the scan data, actually. So reconnecting it will get it back.
You will want to delete the device in the cloud, IIRC.
7 hours ago, klepp0906 said:scanning seems to be taking a lifetime with 200tb worth of drives and with it defaulting to every 7 days I think,it won’t even make it through them before the cycle resets so it’ll just be scanning in perpetuity.
Correct, but that's not exactly how the scan works.
StableBit Scanner keeps a sector map of the scanning progress. Different regions are tracked independently, and it's those regions that have to be older than "x days" (7 days in your example), when they're rescanned.
Over time, this should cause the drives to be scanned when there is less activity, and should spread out the scanning over the week.
Does scanner read files in any way?
in Nuts & Bolts
Posted
Nope.
The surface scan is a sector by sector scan.
The file system scan is an api call for CHKDSK.
So unless you're using the file recovery option, it should not be reading files.