gfjardim

There have been loads of commits into the webgui GitHub repo. New functionality I saw there is CPU Pinning for Docker containers.

It's smtp.mailgun.com or Mail server: smtp.mailgun.org ?

@rxnelson, there was a small bug preventing the toggle between scripts, fixed in version 2018.08.23. Thanks for reporting.

@Squid, could you confirm those weirdness with Tooltipster and Preclear you mentioned are gone?

@bonienl, are you sure it was a preclear plugin error?

Not for now, @Frank1940. Everything appears to be running ok now. Thanks for the help.

As I said before, those failed drives are defective, apparently. Take a look at their SMART parameters and dispose those with bad status. Thank you for posting your logs.

@snowmirage, I only saw 3 errors, is that right?

Nope, drive is certified bad: === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: FAILED! Drive failure expected in less than 24 hours. SAVE ALL DATA. See vendor-specific Attribute list for failed Attributes. ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate PO-R-- 097 097 016 - 7 5 Reallocated_Sector_Ct PO--CK 100 100 005 - 156 196 Reallocated_Event_Count -O--CK 100 100 000 - 156 197 Current_Pending_Sector -O---K 100 100 000 - 7360

Please try the new 2018.08.21b version I just uploaded.

Nothing on your preclear_disk_log.txt file, very strange.

Yes, it is. When I get a little time I try to keep this updated.

Take a look into the OP and send me both diagnostics file and preclear log.

ST2000DM001-1CH164_XXXXXHL8 have medium errors, please look at the disk S.M.A.R.T. to see if it's dying. Aug 21 06:59:00 phoenix kernel: sd 17:0:0:0: [sdb] tag#30 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Aug 21 06:59:00 phoenix kernel: sd 17:0:0:0: [sdb] tag#30 Sense Key : 0x3 [current] Aug 21 06:59:00 phoenix kernel: sd 17:0:0:0: [sdb] tag#30 ASC=0x11 ASCQ=0x0 Aug 21 06:59:00 phoenix kernel: sd 17:0:0:0: [sdb] tag#30 CDB: opcode=0x28 28 00 22 dc 1b 38 00 00 08 00 Aug 21 06:59:00 phoenix kernel: print_req_error: critical medium error, dev sdb, sector 584850232 Aug 21 06:59:00 phoenix kernel: Buffer I/O error on dev sdb, logical block 73106279, async page read KingDian S280-24 4B too have problems: Aug 20 16:46:28 phoenix kernel: ata6.00: exception Emask 0x0 SAct 0x8000000 SErr 0x0 action 0x0 Aug 20 16:46:28 phoenix kernel: ata6.00: irq_stat 0x40000008 Aug 20 16:46:28 phoenix kernel: ata6.00: failed command: READ FPDMA QUEUED Aug 20 16:46:28 phoenix kernel: ata6.00: cmd 60/40:d8:00:c4:79/05:00:01:00:00/40 tag 27 ncq dma 688128 in Aug 20 16:46:28 phoenix kernel: res 41/40:40:00:c4:79/00:05:01:00:00/40 Emask 0x409 (media error) <F> Aug 20 16:46:28 phoenix kernel: ata6.00: status: { DRDY ERR } Aug 20 16:46:28 phoenix kernel: ata6.00: error: { UNC } Aug 20 16:46:28 phoenix kernel: ata6.00: configured for UDMA/133 Aug 20 16:46:28 phoenix kernel: sd 6:0:0:0: [sdj] tag#27 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Aug 20 16:46:28 phoenix kernel: sd 6:0:0:0: [sdj] tag#27 Sense Key : 0x3 [current] Aug 20 16:46:28 phoenix kernel: sd 6:0:0:0: [sdj] tag#27 ASC=0x11 ASCQ=0x4 Aug 20 16:46:28 phoenix kernel: sd 6:0:0:0: [sdj] tag#27 CDB: opcode=0x28 28 00 01 79 c4 00 00 05 40 00 Aug 20 16:46:28 phoenix kernel: print_req_error: I/O error, dev sdj, sector 24757248 Aug 20 16:46:28 phoenix kernel: ata6: EH complete Same for WDC WD20EADS-00S: Aug 20 20:31:24 phoenix kernel: mpt2sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000) Aug 20 20:31:24 phoenix kernel: mpt2sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000) Aug 20 20:31:24 phoenix kernel: mpt2sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000) Aug 20 20:31:24 phoenix kernel: mpt2sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000) Aug 20 20:31:24 phoenix kernel: mpt2sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000) Aug 20 20:31:24 phoenix kernel: sd 17:0:13:0: [sdt] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Aug 20 20:31:24 phoenix kernel: sd 17:0:13:0: [sdt] tag#2 Sense Key : 0x3 [current] Aug 20 20:31:24 phoenix kernel: sd 17:0:13:0: [sdt] tag#2 ASC=0x11 ASCQ=0x0 Aug 20 20:31:24 phoenix kernel: sd 17:0:13:0: [sdt] tag#2 CDB: opcode=0x28 28 00 92 d3 de 18 00 00 08 00 Aug 20 20:31:24 phoenix kernel: print_req_error: critical medium error, dev sdt, sector 2463358488 Aug 20 20:31:24 phoenix kernel: Buffer I/O error on dev sdt, logical block 307919811, async page read

You have probably 3 drives with read errors: WD-XXXXXXX79570, ST2000DM001-1CH164_XXXXXHL8 and KingDian_S280-240GB_XXXXXXXXX0135. Send me your diagnostics file to be sure.

@snowmirage, any news?

Those will be addressed in the next release, guys. Thanks for pointing them out.

@snowmirage, please update your plugin and start new sessions for those drives it had failed. Let's see what's happening.

Hi @snowmirage, thanks for reporting this. Your log is gold and it will take some time to analise it all, but saw some weird things with the script. I'll make some changes to it so I can get more information, ok? Will let you know when to update it so we can debug this.

Not always because LT doesn't update it's build machine environment every time, I think.

Just updated it to circumvent this error.

Just read the post, and the problem is that @1812 is compiling the kernel against GCC version 8.1.1 instead of compiling it agains GCC version 7.3.0, the default version for unRAID 6.5.3. Will take a look to see if this can be fixed without broke all systems that use official releases.

Very strange, since unRAID 6.5.3 gcc version is 7.3.0. Are you using any custom builds, like @CHBMB DVB?

If you call "headache-free" an easier setup, then you're about right, there's will be a handful of solutions out there to satisfy you. IMHO, "headache-free" NAS OS is something that will never exist; or you have some workload in the beginning with a more complicated setup, or you will buy a pre-customized product that will be easier to setup, but may lead to catastrophic loss with the usage of non-friendly SOHO storage system, because RAID5/6/Z are enterprise-focused on data availability and integrity, not on data resilience. Windows, by far, is not suited to the task, I'm afraid. Maybe LT could make things easier by creating some "wizard" setup that asks where the user want to store it's downloads, it's movies and it's documents, and the docker system request the predefined value instead of letting the user choose every path. But this didn't take the merits of the product itself.

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