gfjardim

Send me your Dignostics file.

If you have hotswap bays, you can add more drives after the array is started. Enviado de meu SM-N970F usando o Tapatalk

You can clear any number of drives you want. Just go to Tools > Preclear Disk and click the icon Start Multiple Sessions. If you hit any hardware limit, you can limit the number of concurrent sessions using the queue: Enviado de meu SM-N970F usando o Tapatalk

It wasn't really an error, just a bogus message. Thanks for reporting. Enviado de meu SM-N970F usando o Tapatalk

The install script will check if there isn't a newer version of a package installed, avoiding the installation of an older version. Enviado de meu SM-N970F usando o Tapatalk

New feature explained on the OP: Q) I lost communication with the webgui, can I manage preclear sessions from the terminal? A) Yes, you can. If you lost communication with the webgui or want to use the command line interface to manage your preclear sessions, you just need to type preclear on your terminal to start/stop or observe a preclear session.

Try this: https://docs.google.com/spreadsheets/d/1upEmvZZgV0JiHjUX-JNUFYPHMarC0-sLLNoLS3Gbr_g Enviado de meu SM-N970F usando o Tapatalk

I see no reason why this would not work, but some users had problems with USB hard drives before. You can easily try it yourself, the odds are that it will work for you.

You have a pending sector at 135121. Update the plugin and try to run another full Clear on it. Enviado de meu SM-G973F usando o Tapatalk

Please send me your diagnostics file again.

You're welcome, thanks for reporting.

It's preclearing now?

Preclear Plugin usually tries to update your CSRF token if it's invalid. I've added a new version right now that changes this behavior, showing an alert instead. Please update it to 2020.03.14a and see if it helps.

That resolved your problem?

That what the syslog is telling us.

Your login session is no longer valid, just close your web browser and login again into the webgui.

In Tools > Diagnostics

Please send me your diagnostics file.

Yes it will.

Unraid itself writes very little into the flash drive. You will see writes mainly during settings change, SO update and plugins update. Plugins are a whole different matter. Many plugins use flash drive to store their own installation files and their configuration only, but some will store some status too like Preclear Plugin that stores reports and resume status. Resume status is written every minute, they are less than 1KB size, so every instance of preclear will write at most 1.44MB each 24 hours, which isn't much. It writes two 4KB reports too at the end, again, not much. Not only NAND wearing kills flash drives. Some controllers too have low MTBF and will render your flash drive useless even if your memory isn't wore out. I do recommend Sandisk flash drives since them all have wear leveling, but it's good to make a flash backup now and then.

I've looked the code and I see no obvious way this is happening. It filters the report from /boot/preclear_reports using disk short serial number, and that value you see in the link it's the file base name without the extension. I've tried and couldn't replicate it too....

@wepee, please close all your browser windows and tabs and try it again. Let's try to replicate it.

If you still have this problem, you can try to change the SHUTDOWNCMD argument in upsmon.conf to "/sbin/init 0".

Glad it helped both ways! Pre-read will abort if there is any read errors, including those generated by pending sectors. The problem here is documentation IMO, because the pending sector will show in the log but the user don't have any indication of what to do. Maybe more Q/A entries on the OP should help Thanks for pointing out.

There are no incompatibilities between the script and your hard drives; or the data stream became corrupted before it was written, or it became corrupted after it was read, or your system produces zero filled data streams that aren't composed only by zeros. Many things can corrupt data, like bad memories, bad PSU, bad cables, bad HBA. The script relies on applications widely used around the world, like dd for read and cmp for comparison. And no incompatibility can lead to hard drives being dropped by the HBA, only a driver or a hardware problem can drop drives like that. I'm not defending the script by itself, I'm alerting you that your system may have more serious issues than it appear to have.