Hoopster

This would me my guess as well. When power supplies start to fail, it is first noticed when the PC is under load. I have had a couple of power supplies fail (never on an Unraid server, fortunately) and, in both cases, heavy graphics load would cause the PC to reboot. I suspect this is what is causing your problem.

Well, I talked him into getting Unraid in the first place back in 2017, so, I felt somewhat responsible. He has moved to a new house four times since that initial setup and never really knew what he was doing with Unraid and IT type stuff in general. If there was not a friend or relative at every stop who knew what he was doing, his Unraid server just sat in a corner unused for years. No one had a clue what this server even was, let alone anything about Unraid. He recently moved back within a reasonable distance from my home and asked me to come help him "get all the data off that blue box." He had no idea what to do with it. I asked him to let me take it back to my house (the "IT hospiltal" is what he called it) so I could see what I could do to resurrect it for its original use in an environment I could control. He had no idea where his router was or how to access its admin page so I could see if his server was even getting an IP address. It's a headless box and he had no monitor or keyboard I could use for on-site diagnosis. Turns out it had a static IP address set from long ago that was not on the same private subnet as his current setup (done by his son in law). It's setup for DHCP from the Unraid side now and if I can get him to figure out how to get into his router admin page, I'll setup a DHCP reservation there when I return the patient to him. I'll set it up for Wireguard access so I can get to it remotely when I need to in case he breaks something or forgets how things work. Primarily, he wants it as a Plex media server and a place to store photos. We're both in our mid 60s but "tehcnology" to him is creating a basic Excel spreadsheet. I am doing what I can to "idiot proof" his Unraid server so he does not have to do anything with it and I don't have to be long-term IT support.

File system on all array data disks is XFS v5, so, no changes needed. That is sufficient for his uses of this server.

Yeah, he was just a few versions behind. His last update was in 2018. 6.5.3 --> 6.9.2 6.9.2 --> 7.0.1 7.0.1 --> 7.3.1 It all went very smoothly with plugin and docker container updates at each step. Of course, I needed to reinstall community apps and some updated versions of some plugins but all seems well now. Plex was a mess, but, that has also been sorted. A little reconfiguration still needs to be done, but, at least he is up to date on everything.

@UNPAID Yes. I forgot Tailscale. I have used that as well and it does not require port forwarding like some of the others.

There are several ways to do this. Reverse proxy, Wireguard or other VPN, PiKVM (lets you turn Unraid server on/off remotely) with a VPN. In my homes, I have a Ubiquiti UniFi network infrastructure so it is even easier via teleport and SD-WAN, although, I also use all the remote access methods I mentioned. There are many safe Unraid remote access methods and several youtube videos on the subject.

Updated three servers from 7.2.6 to 7.3.0. No issues on any of the three have been discovered. I am still using USB boot on all three servers. It isn't broken and I don't yet see a need to "fix" it. Nice to have the option in the future if needed, but, happy to stand pat for now. I skipped the onboarding process on all three upgrades and left everything "as-is"

Parity check on my system with 8TB parity and 5 x 8TB data drives takes slightly over 16 hours. Assuming your parity drive is also 8TB, it should be similar.

I still have the same build as my main server. It still does everything I need and more. With the prices of RAM, SSDs and HDDs these days, I may be milking it a few more years. I did also build a backup server with a Mini-ITX variant of the MB, the E3C246D2I (details in my signature). That is getting long in the tooth now as well, but it is mainly just for storing disk-to-disk backups of my main server data and as a fallback should the main server have problems. I started looking to upgrade around the time of the Intel 14th generation core processor release; however, the 13th/14th generation Intel processor problems put me off that idea. By the time I was considering it again last year, component prices started their upward climb and there is still no relief in sight.

I had the same problem many have reported recently; web GUI would not open. I tried some of the "fixes" mentioned above and none worked. I have PIA and had configured DelugeVPN for Wireguard. The only thing that resolved the problem for me was deleting DelugeVPN and the image, clearing out its appdata folder and reinstalling. I did not use Previous Apps to reinstall. I installed and configured DelugeVPN as if it were the first time I had used it. Success! The web GUI now opens as it should.

If the count gets high enough or grows frequently, it can cause a drive to be disabled. This has happened on two of my HDDs in the past. In both cases, the UDMA CRC error count was over 1100 and growing frequently before they became disabled. This usually happened when backing up PCs to the Unraid array. I ended up rebuilding both drives onto themselves as there was nothing inherently wrong with the drive. These errors are usually the result of a bad or loose SATA/SAS cable or MB/HBA port. The drives were fine after rebuild when I swapped cables or attached them to a different HBA port.

The two Unifi Cloud Gateways (Network Controller built in) are one each in my two homes 260 miles apart. They are on separate subnets but thanks to the magic of Ubiquiti SD-WAN/Teleport, devices on both subnets are accessible as if they were on the same LAN. It sure makes scripted backup of one Unraid server to another in the other location easy. I have this Unifi Reborn network docker as a backup should a UCG fail and I quickly need to put my old USG back into service temporarily. Before getting the UCG, I used this docker with great success.

ITEM: HP v150W USB2.0 STORE: Office Depot WHEN: 2023.03 PRICE WHEN PURCHASED: $5, current price $9 (drive I purchased was labelled as a 16GB flash drive, but, as seen below, it is almost 32GB NOTES: Works great with Unraid Controller: Phison PS2319 Possible Memory Chip(s): Not available Flash ID: 983E9803 76E4 Chip F/W: 10.01.5D Firmware Date: 2022-07-19 VID: 03F0 PID: 2D40 Manufacturer: HP Product: v150w Query Vendor ID: hp Query Product ID: v150w Query Product Revision: PMAP Physical Disk Capacity: 31042043904 Bytes Windows Disk Capacity: 31021137920 Bytes Internal Tags: 2N2P-SX5L File System: FAT32 Relative Offset: 4032 KB USB Version: 2.00 Declared Power: 300 mA

Check out the recycle bin plugin in Apps tab.

The older HP v150w USB 2.0 flash drives that are available at Office Depot supposedly had either SLC or MLC NAND. Newer ones, just have "standard flash NAND" whatever that means; probably TLC. I bought one about three years ago for use with Unraid and it has been great. I think they are actually made by PNY for HP. I have no idea if this is "old stock" but I doubt they are still manufacturing a lot of USB 2.0 flash drives. They are fairly inexpensive at $9 for a 16GB flash drive. Every once in a while they go on sale. I got mine for $5.

Both of my Unifi gateway devices (runs Network on the device) have been on 10.0.162 for a few weeks now with no issues. If there are things that still need to be fixed in Network 10.0.160+ that have not been affecting me. Finger crossed that does not change.

As ConnerVT said, the libusb_init error message can be ignored. The message appears in the logs every time Plex starts (unless you have a usb TV tuner). Note the line in red in my Plex logs. Plex tells you to ignore it.

Another option is to enable Turbo Write. This spins up all array disks, but it also significantly speeds up write operations in a parity-protected array. There is also an Auto Turbo Write plugin which manages disk spin up to facilitate Turbo Write and does not require that all array disks always be spun up. Details on Turbo Write:

The link referenced here seems to work to download firmware.

For the most part, this is true. Unraid runs on just about any hardware. It does not support ARM processors, but it runs without issue on most Intel or AMD based hardware. The Unraid license is tied to the GUID of the USB flash device which also holds the OS files (loaded into RAM on each boot) and the Unraid server configuration. This makes Unraid "portable" if you make hardware changes. I have personally changed motherboard, CPU, RAM, etc. five times on my main server while still using the same USB flash drive to boot Unraid.

By the way, there is a very useful plugin called parity check tuning that allows a parity check (like @ConnerVT , I do mine quarterly) to be broken up into several increments over a period of days. A parity check on my main server takes approximately 24 hours with a 12TB parity drive and 8TB array drives. I have it set to run in 9-hour increments from midnight to 9am on the second Thursday of Jan, Apr, Jul and Oct. It finishes before the third increment is scheduled to end. Of course, with larger parity drive(s), it could take more increments but you decide how long each increment will last and a parity check will run in those increments until finished. Another useful tip is to enable signatures in your forum profile if you do not see them. A lot of forum users put the hardware details of their servers in their signature. This gives you a good idea of the variety of hardware configurations that can be used with Unraid. There is no "recommended" hardware as Unraid runs on just about anything (other than ARM).

No need for the cache as you determined I have an rsync script that runs unattended from User Scripts once a week (could be as often as you like) to backup from main Unraid server to the backup server. It does the following: 1 - power on backup server (this is possible because it has IPMI). Before I had a board with IPMI, it was just asleep and the script woke it up via etherwake commands. Possible also to use a smart power switch I suppose 2 - waits until backup server is up and array started 3 - copies new or modified files from disk to disk. Backup server has the same number of HDDs of the same size as source server. Before it was like this, the script copied from share to share. 4 - emails me the results of the backup with a disk to disk summary of backup (files, overall amount of data copied, time to completion, etc.) 5 - powers down backup server until next backup is needed Script has been running unattended for about 4 years now. Every once in a while, I run a modified version of the script that deletes files from the backup server that no longer exist on the source server. I don't do this with backup script so I can recover "accidentally" deleted files on the source server since there is a good chance they are still on the backup server. Had to do this once when my wife accidentally deleted a full folder of photos and was in panic mode :)

What hardware you use for server is irrelevant. License is tied to GUID of USB boot flash drive. It is "portable." I have changed MB, CPU, RAM, etc. five times over the 14 years I have used Unraid and continue to use the same license as I keep the same array/pool drives. Of course, changes and additions can be made but then those are in the config for the next hardware change. I have 12TB parity drive (single parity) and 8TB array drives and a parity check takes about 24 hours. Unraid can reference file locations directly via diskX (/mnt/diskX) or user share (/mnt/user/sharename. Might as well learn this now that you are new to Unraid; NEVER, EVER mix disks and shares when dealing with files in Unraid. This can result in data loss. Details of why this is the case are all over in these forums. Always deal disk to disk or share to share. Copying files via CLI to /mnt/diskX does not bypass parity if it is present. If your goal is to populate the array disks with data at a faster speed (bypass the parity "penalty"), do not have parity disks assigned during the initial large data transfer. Parity can then be enabled and built after the initial data is transferred to the array. Using cache disk/mover is usually not an effective strategy during initial data transfer as the cache will fill up fast and can't be moved to array fast enough to be available for more data caching. Copying directly to disk will avoid the FUSE system (shares) overhead and will be slightly faster but it does not bypass parity. Yes, of course

Thanks for the answers @JorgeB I will likely keep booting from the USB flash drive on my main server, but, I have a couple of other servers on which I can experiment more with internal boot. My current USB boot flash has been going strong for over 10 years. Maybe it is bound to fail soon. Having more boot options is great, but, in my case, I don't yet see a compelling reason to use internal boot but the potential redundancy of boot device is nice.

Lots of things to consider 1 - my smallest SSD is 500 GB, making an 8GB boot partition would not be a problem, but, if I use the rest of the storage for something else, when will the wear and tear cause the SSD to fail? I've had two fail in my Unraid server after six years of use. 2 - Using two current SSDs in a redundant pool with 8GB flash partitions is certainly something to consider. Can the remaining storage space (492 GB in my case) still be used independently in separate pools? 3 - as mentioned by @tjb_altf4 , I really like the idea of my current USB flash drive as a redundant backup boot device in case of SSD problems and being able to boot from either device. 4 - does moving to an internal boot device mean the license is now tied to some GUID associated with that device? If I change motherboard, CPU, RAM, etc. but use the same internal SSD, I assume that would boot Unraid on the new hardware just like it currently does if using the same USB flash drive? Of course, I assume that moving to internal boot would make the current USB boot flash a non-licensed device?