JorgeB

Does it crash for disk2 only? Post the diags after it does.

It won't freak out.

Drive is failing to initialize: Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08 Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] Sense Key : 0x2 [current] [descriptor] Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] ASC=0x4 ASCQ=0x0 Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08 Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] Sense Key : 0x2 [current] [descriptor] Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] ASC=0x4 ASCQ=0x0 Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] 0 512-byte logical blocks: (0 B/0 B) Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] 0-byte physical blocks Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] Test WP failed, assume Write Enabled Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] Asking for cache data failed Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] Assuming drive cache: write through Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] Spinning up disk... Post a manual SMART report for that drive since the one in the diags is incomplete.

Please post the diagnostics: Tools -> Diagnostics

Check file system in all the array drives, without -n (assuming they are xfs).

Boot and see how it goes, difficult to say for sure one way or the other, also not absolutely certain RAM is the problem, but it's the most common reason so it should be the first thing to try.

That's unusual, does it start in maintenance mode?

Start the array, then grab the diags on the console by typing "diagnostics", it might log the problem.

You should really avoid using the server until the data corruption issue is fixed, or will likely just corrupt more data, possibly an entire filesystem.

It's normal for new xfs formatted drives. As for the other issue, try uninstalling the s3 sleep plugin, it has known issues with v6.9.

Check that shares are correctly configured, only shares set to cache=yes will be moved from cache to the array.

Probably a good place to start.

I see ATA1 link going down and getting disable: Mar 16 08:38:17 unraid kernel: ata1: SATA link down (SStatus 0 SControl 300) ### [PREVIOUS LINE REPEATED 2 TIMES] ### Mar 16 08:38:28 unraid kernel: ata1.00: disabled If that it's happening when you hot unplug a drive it's likely a problem with the backplane, or that slot in the backplane, or it doesn't really support hot-swap, best to avoid it.

Since v6.8 some tunables changed and are no longer used, in practice Unraid should auto tune for best performance and the remaining tunables don't do a lot (if any) difference, but it's known to be slower in some cases, especially for larger arrays.

Issue appears related, since it happen after a spin up, you can try connecting those disks to the onboard SATA controller or disabling spin down.

You can ask in the existing plugin support thread:

This script is only for v6.7.x or older, it's not needed for newer releases.

It's logged as a disk problem, you should run an extended SMART test.

First one having issues after the fix, are you sure it was done correctly?

Nope, scrub on the array can only detect corruption, not fix it since there's no redundancy, there will be a list of corrupt files in the syslog, delete or replace them from backups.

New kernel can find previously undetected corruption, if the cache mounts with v6.8.3 you can back it up then re-format.

Please post the diagnostics: Tools- diagnostics

Set the share's minimum free space to about twice the largest file you expect to copy there.

There are issues with the cache device: Mar 14 20:51:13 hafer kernel: sd 1:0:1:0: [sdc] tag#3509 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s Mar 14 20:51:13 hafer kernel: sd 1:0:1:0: [sdc] tag#3509 Sense Key : 0x3 [current] Mar 14 20:51:13 hafer kernel: sd 1:0:1:0: [sdc] tag#3509 ASC=0x11 ASCQ=0x0 Mar 14 20:51:13 hafer kernel: sd 1:0:1:0: [sdc] tag#3509 CDB: opcode=0x28 28 00 00 be a7 e0 00 00 20 00 Mar 14 20:51:13 hafer kernel: blk_update_request: critical medium error, dev sdc, sector 12494816 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 0 Mar 14 20:51:13 hafer kernel: BTRFS warning (device sdc1): direct IO failed ino 260 rw 0,0 sector 0xbea7e8 len 0 err no 10 Mar 14 20:51:13 hafer kernel: BTRFS warning (device sdc1): direct IO failed ino 260 rw 0,0 sector 0xbea7f0 len 0 err no 10 Mar 14 20:51:13 hafer kernel: BTRFS warning (device sdc1): direct IO failed ino 260 rw 0,0 sector 0xbea7f8 len 0 err no 10 Mar 14 20:51:13 hafer kernel: BTRFS warning (device sdc1): direct IO failed ino 260 rw 0,0 sector 0xbea800 len 0 err no 10 Mar 14 20:51:13 hafer kernel: blk_update_request: I/O error, dev loop2, sector 11925472 op 0x0:(READ) flags 0x1000 phys_seg 1 prio class 0 Mar 14 20:51:13 hafer kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 293, flush 0, corrupt 48, gen 0 Try connecting it to the onboard SATA ports instead, then run a scrub.

Constant ATA errors, replace cables on that disk and try again.