JorgeB

This.

If the 1st two options in the FAQ didn't help not much more I can add, filesystem is corrupt, you can try asking for help on IRC or btrfs fsck. Also it won't help assigning just one device, they are both corrupt, since it's the same filesystem.

You can but unlikely to be the disks crashing the server.

Since the disks look healthy probably better to do a new config and re-sync parity, if there are still disk issues it could be bad controller, cables. power, etc.

That suggest the source is heavily damaged, probably doesn't matter if you then clone to an ISO.

Yes.

Nope.

Sorry, never tried that, you can always clone to another device.

Yes, you can see his thread, he just re-assigned the devices and the pool came back, no data was lost.

Same thing.

No similar at all, yours were just unassigned, not wiped, that's very different thing.

Cache shouldn't be unassigned after updating, but you're not the first to report this, note that it's normal to be unassigned if you downgrade back to v6.8.

You need to unmount from UD first if they are mounted with the array stopped, just need to unmount one of them.

Yes, they are in a pool, with the array stopped reassigned them both to cache, there can't be any "data on this device will be deleted" warning after the devices, then start array.

Post the output of: btrfs fi usage -T /mnt/disks/name_of_the_UD_mountpoint you can see the name by clicking on the + sign

Yes sorry, sometimes I get the threads mixed up, just clear the errors and keep monitoring.

More likely the result of the reboot, upgrade doesn't touch any filesystem.

Unrelated. Format then restore data from backups.

They appear to be the same filesystem, did you have a pool?

If you want to use the add on NIC as the main one you need to change it to eth0 (Settings -> Network Settings -> Interface Rules), if not it's need to have an IP address set (dhcp or static) to not show port down.

Krusader is known to be slower in some cases, hence why I suggested rsync.

Yep, of the 3 possible file systems Unraid uses there's no valid one on that device: Mar 3 10:30:30 Buddha emhttpd: shcmd (68610): mkdir -p /mnt/cache Mar 3 10:30:30 Buddha emhttpd: shcmd (68611): blkid -t TYPE='xfs' /dev/sdd1 &> /dev/null Mar 3 10:30:30 Buddha emhttpd: shcmd (68611): exit status: 2 Mar 3 10:30:30 Buddha emhttpd: shcmd (68612): blkid -t TYPE='btrfs' /dev/sdd1 &> /dev/null Mar 3 10:30:30 Buddha emhttpd: shcmd (68612): exit status: 2 Mar 3 10:30:30 Buddha emhttpd: shcmd (68613): blkid -t TYPE='reiserfs' /dev/sdd1 &> /dev/null Mar 3 10:30:30 Buddha emhttpd: shcmd (68613): exit status: 2 Mar 3 10:30:30 Buddha emhttpd: /mnt/cache mount error: No file system You need to restore from backups.

Don't see anything crash related in that log, this usually suggests a hardware problem, one 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.

https://forums.unraid.net/topic/86337-are-my-smart-reports-bad/?do=findComment&comment=800888

If you're not sure, with the array stopped, click on cache and set fs to auto, then start array and post new diags.