JorgeB

You should replace that disk.

Sim.

Wait for the extended test to finish and than act accordingly.

Where did you see that? They are both supported.

If you want some informed advice next time post the diagnostics after a drive fails.

See if this applies to you: https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/

Parity drive is failing, you can continue the rebuild since there's no better option but there will be some data loss.

If the preclear read was successful it's OK by now.

Yes.

What were the SMART tests results?

Disks look OK, mot likely a power/connection problem.

Yes.

Yes, and post the output once it's done.

Enable this then post that log after a crash.

Next time please post the complete diagnostics but looks more like a power/connection problem.

Isso é o normal sem turbo write, devido à maneira que a atualização da paridade é feita. Essa é o pior para velocidade de escrita, visto que escritas para o disco de paridade vão ser feitas em simultâneo sempre que troca de disco, aconselho um dous outros dois, high water é o mais adequado para a maior parte das pessoas.

Yep.

Problem with RAID controller detecting the devices: May 7 20:02:12 Unraid kernel: sd 1:0:24:0: Device offlined - not ready after error recovery May 7 20:02:12 Unraid kernel: sd 1:0:24:0: rejecting I/O to offline device May 7 20:02:12 Unraid kernel: sd 1:0:24:0: [sdc] Read Capacity(16) failed: Result: hostbyte=0x01 driverbyte=0x00 May 7 20:02:12 Unraid kernel: sd 1:0:24:0: [sdc] Sense not available. May 7 20:02:12 Unraid kernel: sd 1:0:24:0: [sdc] Read Capacity(10) failed: Result: hostbyte=0x01 driverbyte=0x00 May 7 20:02:12 Unraid kernel: sd 1:0:24:0: [sdc] Sense not available. May 7 20:02:12 Unraid kernel: sd 1:0:24:0: [sdc] 0 512-byte logical blocks: (0 B/0 B) May 7 20:02:12 Unraid kernel: sd 1:0:24:0: [sdc] 0-byte physical blocks May 7 20:02:12 Unraid kernel: sd 1:0:24:0: [sdc] Write Protect is off May 7 20:02:12 Unraid kernel: sd 1:0:24:0: [sdc] Mode Sense: 00 00 00 00 May 7 20:02:12 Unraid kernel: sd 1:0:24:0: [sdc] Asking for cache data failed May 7 20:02:12 Unraid kernel: sd 1:0:24:0: [sdc] Assuming drive cache: write through May 7 20:02:12 Unraid kernel: sd 1:0:24:0: [sdc] Attached SCSI disk RAID controllers are not recommended anyway, use the onbaord SATA ports (or one of the recommend controllers).

Rede balanceada apenas pode ajudar para transferências simultâneas, cada ficheiro transferido apenas usa um NIC, qual é a velocidade atual? Unraid por defeito não atinge o limite de gigabit, é possível melhorar a velocidade bastante usando turbo write, com a desvantagem de todos os discos serem acordados para qualquer escrita.

Diags are after rebooting so we can't see what happened, but disk6 is showing pending sectors, run an extended SMART test. As for disk24: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

Please post the diagnostics: Tools -> Diagnostics

Did it finish successfully? Post the current reiserfsck --check output.

Once a disk is disable it needs to be rebuild, if you replaced the cable and since the emulated disk is mounting you can rebuild on top. P.S. there are now lots of ATA errors on the cache disk, replace those cables to see if they stop.

Syslog server log is saved to the chosen path, in this case appdata.

Please use the existing docker support thread: