JorgeB

Please don't start multiple thread for the same thing, continue discussion on the other one.

Do you mean it now boots but you don't get an IP? If yes please post diagnostics after boot.

Sep 18 05:01:51 DL380G6 kernel: hpsa 0000:04:00.0: scsi 1:1:0:0: resetting logical Direct-Access HP LOGICAL VOLUME RAID-0 SSDSmartPathCap- En- Exp=1 Sep 18 05:02:45 DL380G6 emhttpd: error: get_device_size, 1544: No such device or address (6): open: /dev/sdb Sep 18 05:02:45 DL380G6 kernel: hpsa 0000:04:00.0: Controller lockup detected: 0xffff0000 after 30 Sep 18 05:02:45 DL380G6 kernel: hpsa 0000:04:00.0: Telling controller to do a CHKPT Sep 18 05:02:45 DL380G6 kernel: hpsa 0000:04:00.0: failed 3 commands in fail_all Sep 18 05:02:45 DL380G6 kernel: hpsa 0000:04:00.0: controller lockup detected: LUN:0000004000000000 CDB:01040000000000000000000000000000 Sep 18 05:02:45 DL380G6 kernel: hpsa 0000:04:00.0: Controller lockup detected during reset wait Sep 18 05:02:45 DL380G6 kernel: hpsa 0000:04:00.0: scsi 1:1:0:0: reset logical failed Direct-Access HP LOGICAL VOLUME RAID-0 SSDSmartPathCap- En- Exp=1 Sep 18 05:02:45 DL380G6 kernel: sd 1:1:0:0: Device offlined - not ready after error recovery Controller is failing to initialize the device, if you have one try with a HBA instead, ideally an LSI.

If you have issues with the mover you need to enable mover logging, run the mover, then post new diags.

Settings -> Docker Settings -> Docker custom network type -> ipvlan Advanced view must be enable (top right)

Yes.

Could be a backplane problem, or cable, or power, you can also update the LSI firmware.

Did you switch to ipvlan mode?

You are having issues with multiple disks: Sep 18 00:53:05 Tower kernel: sd 10:0:2:0: Power-on or device reset occurred Sep 18 00:53:05 Tower kernel: sd 10:0:8:0: Power-on or device reset occurred Sep 18 00:53:08 Tower kernel: sd 10:0:2:0: Power-on or device reset occurred Sep 18 00:53:08 Tower kernel: sd 10:0:8:0: Power-on or device reset occurred Sep 18 00:53:08 Tower kernel: sd 10:0:16:0: Power-on or device reset occurred This is usually a connection/power problem.

This and you can monitor/post the logs to look for any remaining disk issues.

That's pretty important, post current diagnostics, if a disk is clearly failing it should be visible on SMART.

That suggests a cable or device problem, though I guess it could also be a bad HBA, do you hear the disks spinning up?

There's a way, do you know all the disk assignments, single or dual parity?

This yes, and server crashing can cause issues with the cache filesystem, see how it goes for now, if cache keeps getting corrupt there could be other issues, like bad RAM.

yep.

These are usually a connection problem, 9 times out of 10 a bad SATA cable.

Boot in safe mode and disable all VM/dockers, if it doesn't do it start enabling VMs/dockers one by one, if still OK, reboot in normal mode then look at the plugins.

According to this it can be solved by updating the firmware: https://bugs.archlinux.org/task/63409 If it doesn't help you can also try v6.10-rc1 which probably includes a newer driver.

Try with a different one, without transferring the key for now, just to see if it boots.

Not without knowing the array status, that's why wee need the diags, or at least a screenshot of the array devices like mentioned.

It does, but without the diags can't say what the problem is, you can also post a screenshot of the array devices.

Unfortunately there's nothing relevant logged before the crash, there's a lot of what looks like unrelated USB log spam though: Sep 10 20:08:10 darkonnas kernel: usb usb4-port1: Cannot enable. Maybe the USB cable is bad? Sep 10 20:08:10 darkonnas kernel: usb usb4-port1: config error Sep 10 20:08:14 darkonnas kernel: usb usb4-port1: Cannot enable. Maybe the USB cable is bad? Sep 10 20:08:14 darkonnas kernel: usb usb4-port1: config error Sep 10 20:08:18 darkonnas kernel: usb usb4-port1: Cannot enable. Maybe the USB cable is bad? Sep 10 20:08:18 darkonnas kernel: usb usb4-port1: config error Sep 10 20:08:22 darkonnas kernel: usb usb4-port1: Cannot enable. Maybe the USB cable is bad? Sep 10 20:08:22 darkonnas kernel: usb usb4-port1: config error Sep 10 20:08:26 darkonnas kernel: usb usb4-port1: Cannot enable. Maybe the USB cable is bad? Sep 10 20:08:26 darkonnas kernel: usb usb4-port1: config error Sep 10 20:08:30 darkonnas kernel: usb usb4-port1: Cannot enable. Maybe the USB cable is bad? Sep 10 20:08:30 darkonnas kernel: usb usb4-port1: config error Sep 10 20:08:35 darkonnas kernel: usb usb4-port1: Cannot enable. Maybe the USB cable is bad? Sep 10 20:08:35 darkonnas kernel: usb usb4-port1: config error Sep 16 23:34:51 darkonnas kernel: microcode: microcode updated early to revision 0x21, date = 2019-06-13 When there's nothing logged it's usually a hardware issue, one more thing you can try it to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

Everything looks normal on the controller side, see if the drives show up in the LSI BIOS, if not they also won't show up in Unraid.

Make sure "Initial Memory" and "Max Memory" are set to the same value.

Syslog is unavailable for download, try attaching again.