JorgeB

Try without it to see if it's a Connect/API issue; I'm not using it:

Try recreating the flash drive or using a different one, and make sure it's selected as the boot device in the BIOS.

There appears to be a container continually restarting, spamming the log, and it is difficult to look for any other issues. Go to the Docker page and look at the container's uptimes; if you have one with just a few seconds, that is the problem, after resolving that (or sibsaling it), reboot and post new diags after trying to assign the disk.

Should be fine, create a full flash drive backup before updating, and good to read the release notes for the minor releases in between, like 6.4.0, 6.50, etc

Cannot reproduce; is this with or without Connect?

There are multiple issues spamming the log, frst one you should look at is the apparent power/connection issues with the parity disk. Check/replace cables and post new diags after arrays start (and please create a new thread in the general support forum)

Up to you, but can't really help without them.

Please post the diagnostics

All devices are missing, also any reason why you are still on beta.2? Update to stable; it should give a more relevant error, and then post new diags.

Aug 2 17:18:51 NakUnraid kernel: SQUASHFS error: Unable to read fragment cache entry [22a4edb0] Aug 2 17:18:51 NakUnraid kernel: SQUASHFS error: Unable to read page, block 22a4edb0, size 7314 Aug 2 17:18:51 NakUnraid kernel: SQUASHFS error: Unable to read fragment cache entry [22a4edb0] Aug 2 17:18:51 NakUnraid kernel: SQUASHFS error: Unable to read page, block 22a4edb0, size 7314 Aug 2 17:18:51 NakUnraid root: sh: line 1: /usr/local/sbin/update_cron: Input/output error Aug 2 17:18:51 NakUnraid emhttpd: shcmd (1088119): exit status: 126 Aug 2 17:18:51 NakUnraid emhttpd: Retry unmounting user share(s)... Aug 2 17:18:52 NakUnraid kernel: fat__get_entry: 118 callbacks suppressed Aug 2 17:18:52 NakUnraid kernel: FAT-fs (sdq1): Directory bread(block 61440) failed Aug 2 17:18:52 NakUnraid kernel: FAT-fs (sdq1): Directory bread(block 61441) failed Flash drive issues, you can try to first recreate it, if the issues persist, replace it.

The utility should create the flash drive correctly, but if it was previously used with some specific layouts, it may not work; in those cases, using Rufus should resolve the issue: Get the Unraid zip from https://docs.unraid.net/unraid-os/download_list/ - Open Rufus and change "Boot selection" to "Freedos" - Set the "Volume label" to UNRAID - set filesystem to FAT32 - click START - once done, unpack the Unraid ZIP to the flash drive If you are booting UEFI nothing else you need to do, if you are booting legacy/CSM, run the make_bootable.bat as administrator first.

That confirms the disk has failed, and it needs to be replaced.

That SMART report looks very bad; it may be worth replacing/swapping power cables (also removing any power splitters if in use), and if they still click, you cannot recover the whole array with 3 failed drives; you can do a new config with the remaining good ones.

Try recreating the flash drive, first backup the current one, then recreate it using the USB tool, confirm the flash drive boots with the stock install, and if yes, restore only the /config folder from the backup overwriting any existing files.

That disk is not even giving a valid SMART report, that's typically a bad disk, but you can swap cables/slots with another disk to confirm.