Christopher (Drashna)
-
Posts
11573 -
Joined
-
Last visited
-
Days Won
366
Posts posted by Christopher (Drashna)
-
-
On 9/16/2021 at 1:42 AM, Umfriend said:
Whether there is a benefit I am not sure about but if you want to disable it, select the disk -> disk settings -> never scan automatically.
Yup, that's exactly how to disable it.
As for if there is benefit, I'd say there is. The surface scan is a sector by sector read. For an SSD, this doesn't read the platters, but it does read from the NAND flash. If that is having issues, it will show up, all the same. Also, because they're SSDs, the scan should happen a lot faster, and IIRC, there is no real downside to scanning, as it's read only. It's writes that are an issue with SSDs.
-
There are two settings that may effect this.
The "Smart" "NoWmi" option, and the "DirectIO" "Unsafe" option.
https://wiki.covecube.com/StableBit_Scanner_Advanced_Settings#Advanced_Settings
-
in this case, try navigating to the pooled drives, rather than the pool itself. See if any of the disks also exhibit this issue.
-
Try doing the same on the underlying drives.
Also, if you have antivirus software installed, it may be worth disabling/uninstalling that temporarily, as that can cause issues.
-
That's definitely not typical.
Is StableBit Cloud connected?
And could you open a ticket at https://stablebit.com/contact ?
-
Tinkering with the I/O performance settings may help here, namely the download threads.
And the enumeration is dependant on the pinning and connection speed.
-
Is this over Remote Desktop, by chance?
If so, make sure you're on the latest versions.
-
Are you using MSI Afterburner, by chance?
If so, that can cause this to happen.
Otherwise, there is a "C:\Program Files\StableBit\DrivePool\DrivePool.UI.exe.default.confg" file, copy this and remove the ".default" from the file name. Edit the file (I recommend Notepad++ for this), and there should be a "Wpf_SoftwareOnlyRendering" setting. Set this to "True" and it should fix the issue.
-
On 8/30/2021 at 8:53 PM, Gurrman said:
REFS is a dead filesystem at this time as its no where near ready for primetime usage. Always stick with NTFS.
I wouldn't say dead. It's far from mature enough to be used with anything other than Storage Spaces, and a mirrored or parity array.
-
It's an automount issue. We have a guide on how to fix this, actually:
https://wiki.covecube.com/StableBit_DrivePool_F3540This will let you remove the drive letters and still keep the drives mounted properly.
-
Remeasuring the pool is a good idea.
Also, running a CHKDSK pass on the disk in question may help (and remeasuring).
-
Try stopping the StableBit Scanner service, and see if that helps?
-
DrivePool does read and enumerate the directory listing directly from the underlying disks. If one of them is taking forever, it can adversely effect the pool.
-
Yes, it should be able to identify those drives, as long as the Orico enclosure wasn't modifying the partitining/file system.
-
More than likely, it's a section of the disk that hasn't been scanned. StableBit Scanner uses a sector map to keep track of which parts of the disk have been scanned, and when. So you may see it finish one day, and then scanning "again" the next.
Also, by default, StableBit Scanner only scans one disk per controller, at a time. This is to prevent saturating the controller's bus.
-
My guess is that there are locked files on the disk in question, and it's stuck on that.
Alternatively, antivirus or disk tools could be causing this.
either way, could you open a ticket at https://stablebit.com/Contact
-
"Arm64"?
that should be x64, not ARM. If that's the problem you're having here.
-
if it's stored, it's stored internally for the drive.
-
No, not itself.
A number of drives do actually store historical temperature data within their firmware, and StableBit Scanner will display that information, if it's present.
StableBit Cloud will track that sort of information but only for as long as it's been installed and enabled.
-
It's run with the normal priorities. And the order of the balancers in the settings dictates which balancers have priority.
-
It's on the do-do/evaluate list.
-
Yeah, it's to make sure that the system doesn't create hot spots while scanning.
And no, I don't think there is a way to exclude a specific drive from this.
-
First, I'm sorry to hear about your drive failures, as that is never a pleasant experience!
For the settings, I personally like having the StableBit Scanner balancer move out unduplicated data for SMART warnings too.
I also have the rescan option to 14 days instead of 30.
Otherwise, that ll looks good.
-
Could you open a ticket about this at https://stablebit.com/Contact
StableBit Scanner not showing SMART Data when there is a SCSI to ATA Translation layer between the drives and the OS
in General
Posted
You posted on another thread too.
But You may need to enable the "Unsafe" "Direct IO" option to get the SMART data off of these drives, due to the controller.
https://wiki.covecube.com/StableBit_Scanner_Advanced_Settings#Advanced_Settings
if that doesn't work, enable the "NoWmi" option for "Smart", as well.