JorgeB

Look for a BIOS update to see if it helps with that log spam, then enable the syslog server and post that after a crash.

Controller is not being detected, also that's an old SAS1 LSI, it will be limited to 2TB disks.

You could upgrade the two parity disks at the same time then upgrade the two data disks also together, just two rebuilds total, of course there's also more risk than doing one at a time, recommendation will depend on the backup situation, etc.

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

There's some activity going on on disk7, make sure nothing is reading/writing it and see if speed improves.

So you must set your BIOS to boot UEFI. Just a quick note, EFI folder allows UEFI boot, but it doesn't require it, i.e., if the folder is named EFI you can boot Unraid legacy or UEFI, if the folder is named EFI- you can only boot Unraid in legacy/BIOS mode.

Disk is not being detected, assuming it's also connected to the LSI check its BIOS, if it's not detected there it also won't be in Unraid.

There were some changes in how devices are detected with some controllers, but you just need to do a new config, re-assign all devices to their original slots, check "parity is already valid" and start the array, this should be a one time thing.

All older models, if the problem is the newer kernel like you mention not much LT can do, they cannot go back to an older one.

That's what I suspect, the problem is with older models, can you list the other models that are having the same issue?

This might be related to being and older GPU/driver, just this week I tested with GT1030/GTX1060/GTX1080/RTX2060S, all installed the driver correctly with v6.10.

OK, than it can't be the iommu mode change, that was only done in v6.10.3

You didn't answer my question:

Do the recovery password procedure anyway, it should ask you to create one after that: https://wiki.unraid.net/Manual/Troubleshooting#Lost_root_Password

There is, and you're right, it was correct, do you remember if it was manually started or scheduled? They were logged differently, though it's been some time since I checked, could have changed. Jun 13 13:12:29 Tower kernel: mdcmd (52): check Jun 13 13:12:29 Tower kernel: md: recovery thread: check P Q ... ... Jun 14 05:33:26 Tower kernel: md: sync done. time=58857sec Jun 14 05:33:26 Tower kernel: md: recovery thread: exit status: 0 Start, duration and end (exit status 0 means it completed successfully, independent of finding sync errors or not) are always logged.

Sorry, missed that you were saying that setterm -blank wasn't working, there was a change, colors are back, and probably why -blank no longer works. Not a common issue, enable the syslog server and post that after a crash.

I believe it's not very likely that the change @dlandonmentions will help, but it's easy to try, before doing it just let us know if you ran any previous v6.10 release or did you update from v6.9.2 directly to v6.10.3?

From what I could find it's apparently related to the Intel microcode, if that's the case it should go away with a future release that includes an updated microcode.

Yes.

Some good info about permission issues after updating to v6.10 here: https://forums.unraid.net/topic/123901-plex-issues-upon-upgrade-to-6101/?do=findComment&comment=1138715

It's a hardware error, but cannot tell from where based on that.

If Docker/VM services are using the cache pool disable them, unassign all cache devices, start array to make Unraid "forget" current cache config, stop array, reassign all cache devices (there can't be an "All existing data on this device will be OVERWRITTEN when array is Started" warning for any cache device), re-enable Docker/VMs if needed, start array.

Yeah, if nothing else try updating again when the new release includes a newer kernel.

Usually you just need to move all the devices and the flash drive to the new hardware, exception to that is when RAID controllers and/or some USB enclosures are being used.

Jun 15 15:17:32 Cygnus kernel: ahci 0000:00:17.0: Found 1 remapped NVMe devices. Jun 15 15:17:32 Cygnus kernel: ahci 0000:00:17.0: Switch your BIOS from RAID to AHCI mode to use them.