JorgeB

If there's one best bet is to use the existing docker support thread:

Syslog starts over after every reboot, enable syslog mirror to flash then post hat log after a crash.

Issue is following the drive, could be a disk issue or it doesn't like the controller, also note that those controllers use a Marvell chipset and have known issues with Unraid, you can try connecting that disk to an onboard SATA port, that will confirm where the problem is.

Like mentioned rsync will create all the folders before start copying, but that only affects split level, i.e. it must be set to any, minimum free space will still be respected, so something else is going on, possibly 1GB for cache floor is too low, especially if there's anything else using it.

Possibly, but certainly a hardware problem.

There are multiple disk errors immediately at array start: Jun 26 22:37:34 Nostromo kernel: md: disk14 read error, sector=12885172896 Jun 26 22:37:34 Nostromo kernel: md: disk14 read error, sector=12885172904 Jun 26 22:37:34 Nostromo kernel: md: disk16 read error, sector=12885172656 Jun 26 22:37:34 Nostromo kernel: md: disk16 read error, sector=12885172664 And some disks are dropping offline and reconnecting with a different identifiers, this is usually a cable or power problem.

Should be, together with the email address, contact LT support.

At last array start.

I already did, it won't work correctly with Unraid.

At boot time there were 13 devices: May 11 13:32:11 Unraid emhttpd: Device inventory: May 11 13:32:11 Unraid emhttpd: ST8000DM004-2CX188_WCT0N0TG (sdm) 512 15628053168 May 11 13:32:11 Unraid emhttpd: ST10000DM0004-1ZC101_ZKG00HJ0 (sdj) 512 19532873728 May 11 13:32:11 Unraid emhttpd: ST8000AS0002-1NA17Z_Z8408PW9 (sdk) 512 15628053168 May 11 13:32:11 Unraid emhttpd: WDC_WD120EMFZ-11A6JA0_9RJMZWKL (sdh) 512 23437770752 May 11 13:32:11 Unraid emhttpd: WDC_WD120EMFZ-11A6JA0_X1G919GL (sdg) 512 23437770752 May 11 13:32:11 Unraid emhttpd: ST10000VN0004-1ZD101_ZA23N3Z6 (sdd) 512 19532873728 May 11 13:32:11 Unraid emhttpd: WDC_WD8002FRYZ-01FF2B0_VKHT9BEX (sde) 512 15628053168 May 11 13:32:11 Unraid emhttpd: ST2000LM007-1R8174_WDZSCX74 (sdb) 512 3907029167 May 11 13:32:11 Unraid emhttpd: HGST_HUH721010ALE604_7PG54N1R (sdf) 512 19532873728 May 11 13:32:11 Unraid emhttpd: ST8000DM004-2CX188_WCT3K4LQ (sdc) 512 15628053168 May 11 13:32:11 Unraid emhttpd: Samsung_SSD_970_EVO_1TB_S467NX0KB32140R (nvme0n1) 512 1953525168 May 11 13:32:11 Unraid emhttpd: ST8000DM004-2CX188_ZCT0EZQR (sdl) 512 15628053168 May 11 13:32:11 Unraid emhttpd: ST8000AS0002-1NA17Z_Z840P162 (sdi) 512 15628053168 If you reboot with the current connected devices you'll be able to buy a plus licence, or maybe just need to stop array.

It would be the UD plugin support thread.

Parity dropped offline, you're using a controller with SATA port multipliers that is known to drop disks, if you need an ad-don controller see here, but since you have so few disks why are you not using the Intel onboard ports (except for the SSD)? Jun 25 01:50:24 Jarvis kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jun 25 01:50:24 Jarvis kernel: ata1: SATA link down (SStatus 0 SControl 300) Jun 25 01:50:24 Jarvis kernel: ata4: SATA link down (SStatus 4 SControl 300) Jun 25 01:50:24 Jarvis kernel: ata2: SATA link down (SStatus 4 SControl 300) Jun 25 01:50:24 Jarvis kernel: ata3: SATA link down (SStatus 0 SControl 300) Jun 25 01:50:24 Jarvis kernel: ata6: SATA link down (SStatus 4 SControl 300)

That's the Unraid driver crashing, there's a different SMB related crash in the log, still looks like hardware related issue to me.

Not seeing anything out of the ordinary in those logs other than the already mentioned disk issues.

You need to run xfs_repair without -n (no modify flag) or nothing will be done. No, disks have to be formatted.

Yep.

Not a reason for crashing but there are errors like these for multiple disks: Jun 22 04:59:59 Lobot kernel: sd 1:0:3:0: attempting task abort!scmd(0x00000000cf5c076f), outstanding for 30333 ms & timeout 30000 ms Jun 22 04:59:59 Lobot kernel: sd 1:0:3:0: [sde] tag#1724 CDB: opcode=0x12 12 00 00 00 24 00 Jun 22 04:59:59 Lobot kernel: scsi target1:0:3: handle(0x000b), sas_address(0x4433221102000000), phy(2) Jun 22 04:59:59 Lobot kernel: scsi target1:0:3: enclosure logical id(0x500605b00544d590), slot(1) Jun 22 04:59:59 Lobot kernel: sd 1:0:3:0: task abort: SUCCESS scmd(0x00000000cf5c076f) Jun 22 04:59:59 Lobot kernel: sd 1:0:3:0: Power-on or device reset occurred Start by updating the LSI firmware, it's using a very old version, could also be a connection/power problem. As for the crashing, enable syslog mirror to flash then post that log after a crash.

Filesystem Size Used Avail Use% Mounted on /dev/nvme0n1p1 932G 931G 64K 100% /mnt/cache

You didn't before, that's how you stop that happening, don't let the cache fill up.

Diags are just after booting, but there are already ATA errors in multiple disks: Jun 25 07:19:58 RetroShare-Plex kernel: ata6: link is slow to respond, please be patient (ready=0) Jun 25 07:19:58 RetroShare-Plex kernel: ata1: link is slow to respond, please be patient (ready=0) ... Jun 25 07:22:27 RetroShare-Plex kernel: ata3: link is slow to respond, please be patient (ready=0) You should replace cables on these disks, could also be a power issue.

Free up some space on cache.

That's not normal, please post the diagnostics: Tools -> Diagnostics

If it keeps crashing enable syslog mirror to flash then post that log after a crash.

I would also recommend replacing/swapping cables with another disk before rebuilding to rule that out if it happens again to the same disk.

https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself It's always been the same, just make sure the emulated disk is mounting and contents look correct before doing it.