JorgeB

Reboot, before starting the array unassign disk4, start array, post new diags.

@dlandon

Is that an old screenshot then? I guess so because disk7 is still set to auto.

Now stop the array, click on disk7, change the filesystem from auto to xfs, and without doing anything else start the array in normal mode, all disks should now mount but there will likely be some files in a lost+found folder for one or both disks. Note that before rebuilding disk4 you must update to v6.11.3 since there's a bug with that release that won't correctly partition the new disk.

Still in maintenance mode type: xfs_repair -vL /dev/md7 and post output

If like I think that is the problem it's a bug, it works correctly with a registered key, it only happens with a trial key, I've already reported the bug to LT so I would expect it to be fixed soon.

That's not how you check filesystem on an array disk, link above has the instructions. That's more concerning, reboot to clear the log, run that command again after starting the array in maintenance mode and post new diags right after.

Stop the array, start again but in maintenance mode, then in the console type: xfs_repair -v /dev/md4 and then xfs_repair -v /dev/md7 post output for both

That's not expected, and don't format anything, please post the diagnostics.

See here for a list of recommended controllers:

I can tell more after the diags are posted, but looks like you are using a SATA port multiplier, that can cause ATA errors, the sync errors might just be the result of an unclean shutdown.

Hmm, this might be the issue: Nov 10 09:09:56 Biohazard-UR emhttpd: cmdStart: no registration key Nov 10 09:09:57 Biohazard-UR emhttpd: Trial key detected, GUID: 1..7 FILE: /boot/config/Trial.key Looks like the key is being detected only after the start attempt. @zeus83 please post you diags also.

Delete and re-create the docker image

You can see the instructions here: https://wiki.unraid.net/Manual/Release_Notes/Unraid_OS_6.10.0#Linux_Kernel

Nothing relevant logged, if you are not using it try blacklist the iGPU driver from loading, it has been known to cause issues for some.

Disk were already disabled at boot time, so we can't see what happened, most likely they got disabled before or during the previous shutdown, and have nothing to do with the OS upgrade, SMART looks fine and the emulated disk5 is mounting so you can rebuild on top.

Could be the flash drive failing.

Syslog is just after rebooting, enable the syslog server and post that together with the complete diagnostics zip after it happens again.

https://www.ghacks.net/2022/05/13/how-to-bypass-the-microsoft-account-requirement-during-windows-setup/ https://forums.unraid.net/topic/129806-windows-11-vm-unable-to-boot/?do=findComment&comment=1182249

Flash drive problems: Nov 10 10:25:55 Tower kernel: FAT-fs (sda1): Directory bread(block 37377) failed Nov 10 10:25:55 Tower kernel: FAT-fs (sda1): Directory bread(block 37378) failed Nov 10 10:25:55 Tower kernel: FAT-fs (sda1): Directory bread(block 37379) failed Nov 10 10:25:55 Tower kernel: FAT-fs (sda1): Directory bread(block 37380) failed It dropped offline, might have been a one-time thing, but make sure you are using a USB 2.0 port.

Not a good sign cloned disk not mounting with UD, but before trying to fix that lets see if you can emulate disk4: -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) if needed, including the new disk4 and the cloned disk7, replacement disk4 should be same size or larger than the old one -IMPORTANT - Check both "parity is already valid" and "maintenance mode" and start the array (note that the GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the checkbox, but it won't be as long as it's checked) -Stop array -Unassign disk4 -Start array (in normal mode now), post new diags.

SMART looks OK and since the emulated disk is mounting and assuming contents look correct you can rebuild on top.

Using user shares it will only show the 1st copy of any duplicate files.

The USB tool should make the flash drive bootable, but if you're booting UEFI not sure it enables that by default, I believe last releases do, but confirm.

User shares will always have a performance penalty, usually less noticeable with a CPU with good single thread performance, multi thread not important for this.