ericbr

I needed to remove the entire pool (since there was only one device in the pool) and was then able to set up internal boot. Thanks!

After running Unraid Flash Creator with a default image and then copying the files from the zip, Unraid boots successfully. I opened a bug report on Unraid Flash Creator.

I have a small (256 GB) SSD on my Unraid server that is currently being used for a cache drive. I'd like to set it up to be used for internal boot, but I can't seem to remove it once the array is stopped. Any pointers?

Well. Reflashed the drive, and the same thing happened. Unraid Flash Creator just.... didn't copy those files. Will try again after manually copying the files from the zip.

So I tried to run the make_bootable.bat command on my new flash drive, and it failed because it couldn't find K:\syslinux\syslinux.exe, which, in fact, is not there. I reran the Unraid Flash Creator on a separate drive, and there's a lot of stuff (/EFI/boot, /syslinux, /config) missing from my original drive. I checked the contents of the flash backup zip file, and those files are present in the zip file. I'm recreating the flash drive using Unraid Flash Creator, and will double check the contents before booting again.

I'm pretty sure it's UEFI boot, since the other flash drive booted.

I've been having some problems with my Unraid boot volume, and so I thought I'd restore a flash backup. So I downloaded the backup from unraid.net, flashed it to a new 16 GB Verbatim thumb drive using the Unraid Flash Creator, and rebooted the machine. But with the Verbatim drive installed, the machine just enters the BIOS and doesn't even try to boot. Booting from the original flash drive at least boots, but has problems. Is there some extra step I need to do after running the Unraid Flash Creator?

I edited down the logs until just before the failure. It looks like something goes wrong with the USB connection to the flash drive, at which point everything goes to hell. kernel.zip

I had remote system logging set up, so I was able to find the remote logs. I didn't attach all of them, but these were the ones that had been most recently updated. Clearly, at least part of the problem is that /var/log had filled up with ssh logs, but it's weird that the file system filling up would cause problems with the boot flash drive. This seems like rclone with the sftp backend is, in fact, not the backup solution I was looking for, and maybe I should try rsync, since I'm already using rsync to back up my synology NAS. Alternatively, is there a way to greatly reduce the amount of ssh logging generated by rclone/sftp? I still have this suspicion that the problem really triggers when some large amount of data is sent, though. zimacube.zip

Interestingly enough, I was able to cause the problem again w/o using a VM. I was using rclone to back up another server, and after backing up ~320 GB, the web UI crashed, and, after logging in on the console, /usr/local/sbin has exactly1 file: lwrxrwxrwx 1 root root 17 Jun 22 09:35 unraid-api -> ../bin/unraid-api*df shows that /var/log is at 100%, and the array at 65%. (Sorry, can't copy & paste from the console.) Any ideas what might be triggering this? A bad spot on the disk array?

Updating to Unraid 7.3.1 (and making sure the Unraid API was running) seems to have fixed the issue.

I installed the Connect plugin, and can see the updated icon. When I click on 'register server', I get redirected to unraid.net (good), where I click 'Register Server' again, which then sends me back to my server page & brings up a 'Performing Actions' dialog showing 'signing in <username>' for a minute or two, and then fails with 'Something went wrong. Sign in failed.' Which is weird, because I can sign into unraid.net just fine.

Actually, I think it might be because of some problems with the USB boot drive. On the most recent "crash", Unraid couldn't even start the web UI; the logs were showing read failures on sda1 (the boot drive); I moved it to Windows and repaired the disk, and it seems to have fixed the initial issue. I turned off the VM as well, and maybe that will resolve the issue.

I want to set up automated flash backup for my Unraid server. The (docs)[Automated flash backup | Unraid Docs] say it's at Settings → Management Access → Unraid API. But when I go to Settings -> Management Access, the tabs are: Management Access Unraid API Status Unraid API Settings API Keys And nowhere in any of the Unraid API tabs does it mention flash backup. So - where did it go?

So when the Unraid GUI is unresponsive, the entire /usr/local directory is "missing". /usr/local/sbin doesn't exist, so (obviously) I can't run diagnostics. The reboot command "works", but doesn't shut down any VMs/docker containers, nor does it actually reboot anything. Based on some other threads, I have decided to run memtest86+, and so far (21 hours in) the 10 test passes have all passed. I also set up remote syslogging, but nothing has shown up in the logs. The only thing that seems to have changed is that I set up a VM to run Proxmox Backup Server around the time that the crashes started to happen. Before setting up the VM, RAM usage was in the low GBs (~2); with the VM, RAM usage is around 8 GB. The system has 16 GB, so that seems like plenty of headroom.

So - when the Unraid GUI is running, diagnostics works (and I've attached the output). I did note down the path, and when the GUI stops working again, I'll follow up with the results. zimacube-diagnostics-20260511-1604.zip

I've been having consistent problems with the UnRaid GUI crashing. When this happens, I can't ssh in, either; I can only log in directly on the local console. The only way I've been able to recover is to power cycle the machine, which I'm not a big fan of. Many places in the forums say to run the diagnostics from the console, but typing diagnostics from the local console results in diagnostics not found