JorgeB

Yep. No problem restoring that but those are just old preclear reports.

This is likely a general support issue, please start a thread in the general support forum and don't forget to include the diagnostics: Tools -> Diagnostics

Backup current flash, re-do it manually or using the USB utility and then restore the config folder from the backup.

You can enable this and post the syslog after a crash, but if it's a hardware problem most likely there won't be anything logged before crashing.

Best bet is to user the dedicated docker support thread:

GUI SMART tests/results don't currently work for SAS devices, you can still run the tests manually and check the SMART report for the result, i.e.: SMART Self-test log Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ] Description number (hours) # 1 Background short Completed - 23297 - [- - -] This was completed successfully without errors, though for a full drive test you want to run the long test (or do a parity check which basically accomplishes the same for all drives at the same time).

This suggests a flash drive problem, try re-doing it or using a different one.

Disk5 looks healthy, since disk1 suffered some corruption during the rebuild when disk5 dropped offline, easiest way forward would be: -Re-connect old disk1 (you can disconnect the new one if needed) -I would recommend replacing cables on disk5 just to rule them out if there are any more issues with it. -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) including old disk1, so that you have the array as it was before the disk upgrade. -Start array to begin parity sync -All disks should mount correctly, if they don't post new diags (never format) When the sync is done you can try the upgrade again.

If a different cable/port doesn't help it's likely a disk issue.

You should run memtest.

You might have a rogue docker or other process, start by running in safe mode with all dockers/VMs disabled, then if stable start enabling one thing at a time.

IIRC it should work with v6.8.2, but the long test still needs to be run manually because it's a SAS device.

loop2 is usually the docker image, was that created new?

Should be fixed now.

That one shows the server running out of memory.

https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

You still need to:

Disk wasn't offline during the boot, it dropped offline during the rebuild, and again, since single parity can't emulate 2 disks both disks currently have invalid data, now either disk5 died making recovery more difficult, or more likely it's just a connection problem, but we need the SMART to have a better idea, nothing you can do before rebooting/power cycling to see what's what.

Changed Status to Closed Changed Priority to Other

This is a general support issue, first thing to do is to update the LSI firmware since it's on a very old release: Jun 23 06:41:02 fileserver kernel: mpt2sas_cm0: LSISAS2008: FWVersion(07.15.08.00), ChipRevision(0x03), BiosVersion(07.39.00.00) Current one is 20.00.07.00, if after that you still need help please start a thread on the general support forum.

It will work with an older Unraid version, and possibly with the new beta, so you can run a long test and check the result.

Since the filesystem is corrupt it affects both devices, redundancy can only help when a device fail, look for the CA appdata backup/restore plugin.

Best bet is to use the docker dedicated support thread, you can find it by clicking on the docker:

Is current cache xfs or btrfs?

Problem with the Asmedia SATA controller that ended up dropping both cache devices: Jun 23 02:54:05 UnRAIDSVR kernel: DMAR: [DMA Read] Request device [0a:00.0] fault addr 7fffff00000 [fault reason 06] PTE Read access is not set Jun 23 02:54:35 UnRAIDSVR kernel: ata1.00: exception Emask 0x0 SAct 0x3c0007e SErr 0x0 action 0x6 frozen ... Jun 23 02:55:31 UnRAIDSVR kernel: ata2: softreset failed (1st FIS failed) Jun 23 02:55:31 UnRAIDSVR kernel: ata2: limiting SATA link speed to 3.0 Gbps Jun 23 02:55:31 UnRAIDSVR kernel: ata2: hard resetting link Jun 23 02:55:35 UnRAIDSVR kernel: ata1: softreset failed (1st FIS failed) Jun 23 02:55:35 UnRAIDSVR kernel: ata1: reset failed, giving up Jun 23 02:55:35 UnRAIDSVR kernel: ata1.00: disabled ... Jun 23 02:55:36 UnRAIDSVR kernel: ata2: softreset failed (1st FIS failed) Jun 23 02:55:36 UnRAIDSVR kernel: ata2: reset failed, giving up Jun 23 02:55:36 UnRAIDSVR kernel: ata2.00: disabled Jun 23 02:55:36 UnRAIDSVR kernel: ata2: EH complete Try using the Intel ports instead.