gfjardim

Nope, I'm using Tapatalk right now and didn't saw your PM. Sorry for that. Will take a close look soon.

Please take a look at the first post for "How can I download a copy of the plugin log" and send the file here.

Please send me the whole previews plugin log, please.

You have to rename it preclear_disk.sh too.

It's the only one in the dropdown list?

Yes, just take a look at the first post of this thread.

Update 2018.05.03 just released. In my tests it fixed the "not zeroed" error. Enviado de meu SM-G955F usando Tapatalk

Joe L. script reads the disk in chunks. It reads, in a loop, n bytes and sum them up to verify it's zeroed. The speed you guys see on the cli is the read speed; in the gui you can see the whole operation speed (read + sum + verify zero sum). Enviado de meu SM-G955F usando Tapatalk

Nope, still testing it and will release it later this week. Enviado de meu SM-G955F usando Tapatalk

Yep, that's the one. Enviado de meu SM-G955F usando Tapatalk

It was never reverse engineered, the md driver was always open source. Guys , let's be straight: adding new functionality is always an opportunity to inadvertently introduce some bugs into the code. Some fixes I made (e.g. fail dd in case of read errors) led to an odd behavior. I'd try to circumvent this, but it takes some time. Enviado de meu SM-G955F usando Tapatalk

Ok guys, there's an error in the 0.9.5 version of the script causing this anomaly. It should copy zeroes to the entire disk, but dd is skipping the last 10 (2097152 bytes sized) blocks of the disk, leaving it in an inconsistent state. I'm trying to fix it right now, but every change need 24 hours to be tested on my test disk, so it will take some time to debug it.

I have a theory about this problem but could not fix it without a Preclear log (please see the original post of this thread).

These are harmless, but I'll suppress them on the next version.

Y It's the drive in question, scsi target6:0:0 is disk sdg. Yep, maybe its a controller issue.

Your hard drive has tons of these errors on the syslog: Don't know what that error mean, but apparently those aborts are interfering with the preclear operation.

Sorry for the delay, guys. I'm very short on time so I had to decrease the level of support dedicated to this plugin. If someone could verify if the script is working fine with v6.5 I do appreciate that.

No, Clear is the default operation. Erase should be used when removing a disk from your array to be sold, e.g. Enviado de meu SM-G955F usando Tapatalk

Please update and tell me if it helps.

Please send the output of this command: cat /proc/version|grep -Po 'gcc version \K[\d.]*'

Please post the result of this command: cat /proc/version|grep -Po 'gcc version \K[\d.]*'

Erase will fill the entire disk with randomly generated data; Erase and Clear will do the erase operation, then fill it with zeroes and write the unRAID clear signature. Clear will fill the disk with zeroes then write the unRAID clear signature.

See the original post for instructions about getting the logs.

Yes. The correct command to test it is /etc/rc.d/rc.diskinfo --daemon Enviado de meu SM-G955F usando Tapatalk

Please reboot your server.