JorgeB

Could have been the port, but make sure you have a current backup; if it happens again on a different port, it's best to replace the flash drive.

Jul 9 11:21:41 F4-424 emhttpd: cmdStart: already starting This is typically a plugin issue; see if it happens in safe mode.

Those should be harmless; a BIOS update may help, the only thing that could be a problem is this: Jul 6 18:18:05 Babel kernel: ata4.00: HPA detected: current 976771055, native 976773168 Mostly if it is later created on array disks, on the SSD it should not be an issue

Enable the syslog server and post that after the next crash.

You are blacklisting the Realtek NIC driver, and that board has one, so the driver is not loaded. Delete /config/modprobe.d/r8169.conf from the flash drive and reboot. You can delete it from the CLI with rm /boot/config/modprobe.d/r8169.conf

You can use this to help with the assignments if you don't have a backup: https://docs.unraid.net/unraid-os/system-administration/maintain-and-update/changing-the-flash-device/#recovering-from-a-failed-boot-device-without-a-backup

If you mean the onboarding wizard, you can just close it.

This looks to me more like a kernel regression, and if that is the case, not much LT can do, but take a look at the bug reports. I believe there's already one about that or a similar issue; if there isn't, feel free to create one https://product.unraid.net/b/unraid-os-bugs

I would start by recreating the Docker image in case there is one or more stale networks present https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#re-creating-the-docker-image-file Then: https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#reinstalling-docker-applications Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#restoring-docker-custom-networks

Possibly, at least I don't see anything else logged, and the server appears to have shut down correctly, meaning it wasn't completely crashed.

It's logged as a disk problem, but there's no SMART report for parity, reboot and post new diags.

If you don't see anything on the screen, i.e., the server is not posting, it's not an Unraid problem.

Possibly, try recreating it or using a different one.

Don't see any crash logged at that time; see a shutdown: Jul 8 21:26:49 Media-Server shutdown[4118851]: shutting down for system halt Was that started by you?

Pretty sure the NFS warnings will be unrelated to any crashing.

You need to replace X with the correct devices you want to offline, e.g., echo 1 > /sys/block/sdb/device/delete echo 1 > /sys/block/nvme0n1/device/device/remove

You would need to use -L, for now, it just looks like a filesystem issue.

In that case you should be able to recover the pool the same as before, then recommend setting up the syslog server to have the syslog if it happens again.

Yep, or if you prefer to avoid messing with cables, you can use echo 1 > /sys/block/sdX/device/delete echo 1 > /sys/block/nvmeXn1/device/device/remove The bottom one is for NVMe devices; that will drop them offline, the array should be stopped, a reboot will bring them back.

According to diags it exists; it's just not mounting: Jul 8 10:14:36 Tower emhttpd: shcmd (141): mount -t xfs -o noatime,nodiscard,nouuid /dev/mapper/md7p1 /mnt/disk7 With the array started, post the output from xfs_repair -v /dev/mapper/md7p1

Copy/paste is better when it's for a key transfer, but it will have the needed info as well.

The UUID is the same one from the pool. Temporarily disconnect all other devices, and with just the sda connected, post the output from btrfs fi show

Please post the output from xfs_repair on the emulated disk.

The pool device is already missing in both diags posted, do you have the diags from when the device dropped? Those could help see what's happening.

It could be, if support is receiving an email from a different sender that doesn't match the registered one, they may not be able to validate it's you, if you have an Unraid license registered to that account, you can send a screenshot from Tools - Registration; that should help prove you are the owner