Constant file system errors with newest update

[Austin]

Version is 2.6.9.4059

For years the scanner has been working well, every now and then it finds a problem with a drive. I evac the drive and run tests on it:

SMART, chkdsk /f, chkdsk /r etc to determine if the drive is fixable and replace when it isnt (only needed to do this once). However since this version it has been a non stop occurrence! Old drives, new drives, small (4tb) and large (16tb) are constantly getting marked as file system damaged. In the last couple weeks it has been 9 drives! The problem is it takes an extremely long time to evac the drive just to do all the tests and nothing be wrong. Ive done this 3 times now (and not a single scan returns an issue) and yet today i got 3 more drives that are "damaged".

The repair built into the scanner never works so it is a long process over and over of transferring tb's of data just to do scans and have no problems.

Is there an actual drive report that states what cased the drive to be marked as damaged that can be reviewed as this is getting to be madness.

 

Edit: And since i posted this, 2 more have now been marked as "Damaged". There is no way every drive is all of a sudden damaged in the span of 2 weeks.

[backup]

On 10/18/2024 at 3:24 PM, Austin said:

Version is 2.6.9.4059

For years the scanner has been working well, every now and then it finds a problem with a drive. I evac the drive and run tests on it:

SMART, chkdsk /f, chkdsk /r etc to determine if the drive is fixable and replace when it isnt (only needed to do this once). However since this version it has been a non stop occurrence! Old drives, new drives, small (4tb) and large (16tb) are constantly getting marked as file system damaged. In the last couple weeks it has been 9 drives! The problem is it takes an extremely long time to evac the drive just to do all the tests and nothing be wrong. Ive done this 3 times now (and not a single scan returns an issue) and yet today i got 3 more drives that are "damaged".

The repair built into the scanner never works so it is a long process over and over of transferring tb's of data just to do scans and have no problems.

Is there an actual drive report that states what cased the drive to be marked as damaged that can be reviewed as this is getting to be madness.

 

Edit: And since i posted this, 2 more have now been marked as "Damaged". There is no way every drive is all of a sudden damaged in the span of 2 weeks.

Well, now you have me concerned after just installing scanner for eval You would think after 40 years *Someone* would have released an accurate test for disks - WITH the option to move marginal blocks to the $badclustr file? Cuz we all know that drive manufacturers don't want returns - so they skew their SMART Systems to prevent it.

My situation is mostly similar to yours. I'm getting notices of file corruption from our Kopia repository. Kopia stores Blake 2 hashes for every file. At first I feared the problem was with the Drivepool software (used as RAID 0 here). Chkdsk * /r found no problems....but then I dusted off an old friend (https://panthema.net/2013/disk-filltest/).   Sure enough, it quickly failed the drive (perhaps absolving DrivePool's software).

Now trying "Scanner" to determine if it sees something amiss on this drive. Sure hope it isn't foo-foo dust like the others.

 

[Shane]

Hi Austin, I would either revert to the previous release (2.6.8.4044) or update to the newer releases (2.6.10.4074 or 2.6.11.4077) of Scanner and see if the problem remains or goes away (link to releases).

Scanner's logs are written to "C:\ProgramData\StableBit Scanner\Service\Logs".

[Austin]

2 hours ago, Shane said:

Hi Austin, I would either revert to the previous release (2.6.8.4044) or update to the newer releases (2.6.10.4074 or 2.6.11.4077) of Scanner and see if the problem remains or goes away (link to releases).

Scanner's logs are written to "C:\ProgramData\StableBit Scanner\Service\Logs".

Settings -> General "Always check for newer version" is enabled so if there are multiple new versions i am curious why i am not being prompted to update? That being said i do not see a check now or update now button in that area either. EDIT: i found the manual check for DrivePool and ran it, about 10m later it updated both so it is now on 2.6.11.4077 (but still odd there where multiple releases and this did not pick up any of that with auto update on)

 

So i looked at emails, i had 5 drives marked as "damaged" on the 18th, opened the log for the 18th and searched:

error: 0 results

damage: 0 results

Not really helpful logs. The "errors" folder has logs but are encrypted so that isnt useful at all. Next place to look?

[Austin]

7 hours ago, backup said:

Well, now you have me concerned after just installing scanner for eval You would think after 40 years *Someone* would have released an accurate test for disks - WITH the option to move marginal blocks to the $badclustr file? Cuz we all know that drive manufacturers don't want returns - so they skew their SMART Systems to prevent it.

My situation is mostly similar to yours. I'm getting notices of file corruption from our Kopia repository. Kopia stores Blake 2 hashes for every file. At first I feared the problem was with the Drivepool software (used as RAID 0 here). Chkdsk * /r found no problems....but then I dusted off an old friend (https://panthema.net/2013/disk-filltest/).   Sure enough, it quickly failed the drive (perhaps absolving DrivePool's software).

Now trying "Scanner" to determine if it sees something amiss on this drive. Sure hope it isn't foo-foo dust like the others.

 

Im not going to say their software is 100% wrong but throwing nearly a dozen drives into a damaged state in a 10 day span kinda leads me to believe there might be more than just a bad drive at play. I dont mind to evac and test them but i still want to see whatever log/test it ran and the result that now marked all these drives as damaged.

[Christopher (Drashna)]

If you're seeing a lot of drives coming up with errors, and suddenly, there is the "burst test" option.  It may be worth running this on one or more of the drives.  This reads a very small block of data, but reads it over and over and over.  This way, it should not be reading it from the disk, but from the drives cache.    BUt this should saturate the bus/communication.  If you see errors coming back from this burst test, then there is some sort of communication error with the drive.

If there is a connection error, it could be with the drive's pcb, the cables themselves, the connectors for the cables (eg, loose fit), the SATA controller, drivers, etc.  

If that's not the case, then could you open a ticket at https://stablebit.com/Contact

[Austin]

2 hours ago, Christopher (Drashna) said:

If you're seeing a lot of drives coming up with errors, and suddenly, there is the "burst test" option.  It may be worth running this on one or more of the drives.  This reads a very small block of data, but reads it over and over and over.  This way, it should not be reading it from the disk, but from the drives cache.    BUt this should saturate the bus/communication.  If you see errors coming back from this burst test, then there is some sort of communication error with the drive.

If there is a connection error, it could be with the drive's pcb, the cables themselves, the connectors for the cables (eg, loose fit), the SATA controller, drivers, etc.  

If that's not the case, then could you open a ticket at https://stablebit.com/Contact

Ran it for an hour an doesnt seem to have any complaints. Guess i'll open a ticket

[muaddib]

On 10/21/2024 at 5:13 PM, Austin said:

Ran it for an hour an doesnt seem to have any complaints. Guess i'll open a ticket

Did you get your issue resolved? I am having similar issues with multiple dropped drives.

[Austin]

My issue was not dropping drives, that seems more of a sata/usb/power/hub/etc problem. My issue was drives being marked as damaged when they where fine.

This got better after an update or two but my question of being able to review the logs has never been satisfied. I guess they do not want to allow users to see the logs/errors that trigger the scanner to mark things as damaged as the only response i got pointed to an encrypted file instead of just giving useful information on where the actual readable logs are. Well that or they simply are not readable logs and you're just supposed to fully trust this software (which i do not as i have proven time and time again their "damaged" is very broken and unreliable to no response from anyone who seems to care or be knowledgeable to assist with that)