JorgeB

Rebuilt disk will be corrupt, but if the disks are really failing there will always be some data loss, you can also use ddrescue on all the failing disks, this way at least you can know which files are corrupt.

Both disks appear to be failing, you can run an extended SMART test on both to confirm.

Syslog starts over after every reboot.

If you're not using ECC RAM start by running memtest.

The diags you posted don't show any parity sync, but even if they did it's not possible to know where the errors come from.

Sep 14 01:00:01 tower1 kernel: shfs[25263]: segfault at 0 ip 00000000004043b8 sp 0000146026a3d780 error 4 in shfs[402000+b000] shfs segfaulted, rebooting should bring your shares back, but if it continues to happen it might indicate an underlying issue.

First we need to know if this was a one time thing or if you keep getting sync errors after they were fixed, so if that was a correcting check run another one, also you're overclocking your RAM and that is known to corrupt data with some Ryzen servers, see here for max officially supported speed for your config.

Looks like a controller problem: Sep 14 04:40:04 dump kernel: aacraid: Host bus reset request. SCSI hang ? Sep 14 04:40:04 dump kernel: aacraid 0000:17:00.0: Adapter health - -3 Sep 14 04:40:04 dump kernel: aacraid 0000:17:00.0: outstanding cmd: midlevel-0 Sep 14 04:40:04 dump kernel: aacraid 0000:17:00.0: outstanding cmd: lowlevel-0 Sep 14 04:40:04 dump kernel: aacraid 0000:17:00.0: outstanding cmd: error handler-0 Sep 14 04:40:04 dump kernel: aacraid 0000:17:00.0: outstanding cmd: firmware-19 Sep 14 04:40:04 dump kernel: aacraid 0000:17:00.0: outstanding cmd: kernel-0 Sep 14 04:40:04 dump kernel: aacraid 0000:17:00.0: Controller reset type is 3 Sep 14 04:40:04 dump kernel: aacraid 0000:17:00.0: Issuing IOP reset Make sure it's well seated or try a different PCIe slot if available, if issues persist I would try a different controller, LSI recommended.

Disks can be connected for flashing, just make sure array is stopped.

Please use the existing docker support thread:

Yes, in this section: https://forums.unraid.net/forum/53-feature-requests/

Looks like a connection/power problem, see if the disks that failed share something, like a miniSAS cable or power splitter, could also be the PSU.

Only if the actual disks are OK, any emulated disks will be gone after a new config.

Tools -> New config Assign remaining disks and start array to begin a parity sync.

Sorry, missed your first reply due to an old forum bug, filesystem is crashing immediately after mounting, there are some recovery options here that you can try.

I forgot the device is USB, so not so easy to check if a driver is being loaded as if it was PCI, but that's likely the problem, you can make a feature request for the driver, LT are usually good at adding them quickly, if one is available.

Try booting in safe mode.

Attach the complete zip.

Likely there's no driver, diagnostics will confirm.

During the rebuild of disk1 there were read errors on disk5, do disk1 can't be correctly rebuilt, check/replace cables on disk5 and post new diags after array start. Posted diags don't show what happened to disk6 so can't comment on that.

They can cause sync and other issues like dropped disks and are not recommended, but they do work for some, so if you already have it might as well see how it goes.

Google rsync, but basically: rsync -av /path/to/source/ /path/to/dest/

That won't work, it will clone the disk but it won't be usable in Unraid, you can use rsync instead for example.

Replace/swap both cables on disk9 and post new diags.

Tools -> New config Then just re-assign the remaining drives, parity will need to be synced.