JorgeB

Also try booting using the GUI mode with UEFI, for some reason it sometimes works if the other option doesn't.

You need a dedicated GPU for those boards, try if you have one available.

This error basically means the GUI is out of sync with the array, but it's not always clear the root cause, make sure no other browser windows are open on the GUI, reset cookies or try a different browser and also try booting in safe mode.

You can ignore all those SATA link down messages, it's typical with some Asmedia controllers, they are "phantom" ports, i.e., they don't exist.

Yes, WD60EFRX original RED drives - CMR WD60EFAX new RED drives - SMR Yes, as long as there's enough space.

It can be fine, depending on the use case, still they should not be dropping just because they are SMR, all your other drives are CMR, just both parity drives are SMR.

If you want 6TB you have for example: WD RED Plus - WD60EFZX Toshiba N300 - HDWG460UZSVA Seagate Ironwolf - ST6000VN001

Any brand/model, just not SMR, especially for parity.

Yes, now it's IT mode, but like mentioned if it also happened with the onboard SATA that would not be the problem. I would suggest trying different non SMR disks.

BTW, it's usually easy to reflash to IT mode.

Jun 30 01:55:04 Tower kernel: mpt2sas_cm0: LSISAS2008: FWVersion(20.00.06.00), ChipRevision(0x03), BiosVersion(07.39.02.00) Jun 30 01:55:04 Tower kernel: mpt2sas_cm0: Protocol=(Initiator), Capabilities=(Raid,TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ) Firmware should be 20.00.07.00, and IT mode looks like this: Jun 27 16:56:23 Tower7 kernel: mpt2sas_cm0: LSISAS2008: FWVersion(20.00.07.00), ChipRevision(0x03), BiosVersion(00.00.00.00) Jun 27 16:56:23 Tower7 kernel: mpt2sas_cm0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ) Jun 27 16:56:23 Tower7 kernel: scsi host11: Fusion MPT SAS Host Note Protocol=(Initiator,Target) and no RAID mentioned in the capabilities like above.

Strange, they are both SMR drives, still they should not drop out like that, also the LSI is in RAID mode and with a firmware with known issues, but if the same with the onboard ports I would suggest trying different disks, SMR are not recommended anyway, especially for parity.

You can assign it as a pool or use the UD plugin.

Unfortunately there's nothing, I assumed it happen between these lines: Jun 29 19:53:06 Tower autofan: Highest disk temp is 40C, adjusting fan speed from: 163 (63% @ 1548rpm) to: 140 (54% @ 1336rpm) Jun 29 20:50:13 Tower kernel: mdcmd (36): set md_write_method 1

To be honest and if this is true don't see the point of VM autostart not always working, IIRC and like mentioned above this was initially done on purpose so any user could fix a VM that was crashing Unraid, if VM autostart was on and it always autostarts after the array start it would make fixing it very difficult, since AFAIK there's no easy was to disable VM autostart by editing some config file, so the array autostarts, VMs autostart, Unraid crashes, user reboots, array autostarts, VMs autostart and Unraid crashes, and so on, the solution was disabling array autostart, and that can be done by editing a config file, the VMs would not start automatically allowing the user to edit the VM, if they still autostart at first array start it's not possible to do that, so if this is the current behavior might as well always auto-start the VMs.

That was expected like mentioned above, but usually xfs_repair can recover well from this, so if data looks correct and there's no lost+found folder you should be fine.

Unraid driver is crashing, assuming that previously was working with this release start by running memtest.

Looks more like a hardware specific issue, probably the board, we'd need another user with the same one to confirm or not.

In fact @dlandonIMHO you should remove that part from the summary, it will just confuse users, SMART assessment only fails if there's a "FAILING NOW" SMART attribute, and the GUI already warns about that.

Still worth trying a different flash drive, you don't need a key, just to see if the boots, you can also try booting UEFI if currently booting CMS or vice-versa.

Yeah, I assumed he meant a SMART test, SMART assessment is basically meaningless.

Long or short? Both are showing pending sectors, so likely a drive problem.

You could possibly use this instead: smartctl -i /dev/sdX And parse this line: SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)

Try a different slot.

Please use the Nvidia plugin support thread: