itimpi

Have you tried the obvious thing of looking for a BIOS upgrade for your motherboard since the error message indicates a BIOS issue?

Larger capacity IS supported. The issue is that Windows will not as standard format files greater than 32GB as FAT32 which is why this is till the recommended maximum size, and that is more than enough for Unraid. As long as you use the USB Creator tool or a 3rd party tool such as Rufus (my personal preference) to get the drive formatted as FAT32 then drives larger than 32GB will work fine.

Which drives did you add? There should be no need to run a parity check but it would not do any harm.

For reference there is a description of the default Unraid write mode here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. The Unraid OS->Manual section in particular covers most features of the current Unraid release.

If you have hard links then the space will not be released until all such links are deleted so there are none remaining for any given file.

Try rewriting all the bz* type files as described here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. The Unraid OS->Manual section in particular covers most features of the current Unraid release.

Try running Tools->New Permissions against the share to see if that changes the results. If so the original issue was that files/folders were created without the correct permissions to allow them to be visible over the network.

If you have the Mirror to Flash option set for the syslog server then it does not need the network working to capture a log to the flash drive in the 'logs' folder.

The link provided will mean you do not lose any data any shares will be available with default settings. To keep everything then you need to be able to get the contents of the 'config' folder off the flash drive if you have no backups. Going forward you should make sure you DO have a backup of the flash drive. There are several standard ways of achieving this Manually by clicking on the Boot drive on the Main tab and selecting the backup option. Automated local copy on a schedule using the appdata backup plugin Automated web copy on Limetech servers using Unraid Connect.

You may need to force a shutdown via the power button. You definitely do not want to pull the flash drive out while Unraid is actually running as that is guaranteed to cause problems.

Something like this is likely to be possible in a future release when the current Unraid main array becomes just another pool type. Hopefully at that point you can specify any array type as primary or secondary storage which should achieve what you want I think. However we are going to have to wait and see if this is what eventually materializes and even if it does come I have no idea of any likely ETA.

If you get continual corruption at the BTRFS level I would think the most likely culprit I is RAM issues

Loop2 is the docker image file and the messages suggest it is corrupt. You should delete it, create a new empty one and reinstall your containers via Apos->Previous apps to get containers back with previous settings.

Disabling that script could have all sorts of unforeseen consequences as it is essential for keeping the GUI state information current.

APC are quite common and are well regarded, and many suppliers (e.g. the CyberPower UPS I use) are APC compatible at the software level. There is also the issue of which UPS drivers have been incorporated as standard into the Linux kernel so it is easy to include support for them.

I am a bit confused by exactly what has happened. You seem to imply that the drive is not part of the array and you want to copy data to the array, and then you talk about adding it to the array before doing any copying. You also mention formatting which would wipe any existing data but it is not clear exactly what was formatted.

That is one reason why it is best to go to the top level of the documentation via the links from the top/bottom of forum or GUI as they tend to be kept up-to-date. Links from individual forum posts are always liable to break after some time has passed. Suggestions on improving the actual documentation to help make it easier to find specific items are always welcomed. I have fed some of my personal ideas back to Limetech but other people’s viewpoints will be useful to see if they have the same idea.

Have you tried running a memory test? I saw the other day someone mentioning the “Ultimate Boot Disk” as a way of getting a number of useful diagnostic tools. Not tried them myself although it looked useful. Would not think a hard drive should cause a reboot but always worth trying a different one as something easy. you could also try booting a Linux Live distribution to see if the system stays running using that.

The monitor task that runs every minute is standard on all Unraid systems and has been for many years. Quite what can make it log an error exit code I have no idea. the read SMART messages will be logged when Unraid thinks a drive has just been automatically spun up due to an access occurring.

This looks like the events leading up to the reboot: Oct 8 17:11:14 Lab-Test rc.inet1: ip link del bond0 Oct 8 17:11:14 Lab-Test kernel: bond0 (unregistering): Released all slaves Oct 8 17:11:14 Lab-Test rc.inet1: ip link set lo down Oct 8 17:14:31 Lab-Test kernel: microcode: microcode updated early to revision 0x28, date = 2019-11-12 Oct 8 17:14:31 Lab-Test kernel: Linux version 6.1.49-Unraid (root@Develop-612) (gcc (GCC) 12.2.0, GNU ld version 2.40-slack151) #1 SMP PREEMPT_DYNAMIC Wed Aug 30 09:42:35 PDT 2023 Oct 8 17:14:31 Lab-Test kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot Oct Nothing there to give a clue as to why the system rebooted I am afraid. Not sure what else to suggest to check for at this point other than to say nothing being logged is normally what we see when there is a hardware error.

Your diagnostics show that flash drive really appears to have dropped offline: Oct 8 03:30:55 AKserver kernel: usb 1-5: device not accepting address 2, error -71 Oct 8 03:30:55 AKserver kernel: usb 1-5: USB disconnect, device number 2 Oct 8 03:30:55 AKserver kernel: device offline error, dev sda, sector 557311 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 Oct 8 03:30:55 AKserver kernel: write_file: /w..9/... Oct 8 03:30:55 AKserver kernel: md: could not write superblock file: //..t/... Oct 8 03:30:55 AKserver kernel: device offline error, dev sda, sector 375650 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 0 Oct 8 03:30:55 AKserver kernel: Buffer I/O error on dev sda1, logical block 375587, lost async page write Oct 8 03:30:55 AKserver emhttpd: Unregistered - missing key file (ENOKEYFILE2) Oct 8 03:30:55 AKserver kernel: FAT-fs (sda1): Directory bread(block 375584) failed Oct 8 03:30:55 AKserver kernel: FAT-fs (sda1): Directory bread(block 375585) failed Oc You should probably plug it into a PC/Mac and check it is readable.

A sudden shutdown normally points to a hardware issue, particularly as you mentioned it being accompanied by a beep. You might want to check that all fans and cooling are working as expected in case it was a thermal shutdown due to,CPU overheating. The PSU might be another suspect. the syslog included in the diagnostics is the RAM copy that starts fresh each time the system is booted. To get one that survives a reboot you can use the syslog server.

Try removing the Mover Tuning plugin. Been quite a few reports recently of it causing this sort of issue.

For security reasons a password is now mandatory even when logging in locally. You could always set your browser to remember it.

If you still have them then the diagnostics would probably tell me if you had encountered the problem that yesterdays release fixed.