Jeff in Indy

Thanks for that. It does show a GUID. However, at the top of the screen it says that the flash drive is corrupt or offline. Is that due to the drive not having a valid key, or could that be part of the problem with using it as a replacement?

I copied Pro.key to the config folder and restarted. I went through the replace key procedure and it failed. Since I've never replaced the USB before, I assume it's a GUID issue. Is there a way to tell if a USB has a GUID? Also, should I copy over the other items in the config folder? I hadn't made any changes to my system in months.

Yes, I’m so sorry. That was rather vague. But I’ve been many different places trying to figure it out, so I wasn’t sure where to begin. I was able to get UNRAID to boot as a new trial version. I scroll down from the main screen and click on the link to register. It offers me the chance to buy it or recover my key, but not to replace a key so I’m not sure where I need to go to register this new key. It offers me the chance to buy it or recover my key, but not to replace a key so I’m not sure where I need to go to register this new key. I’m away from home, but can show you a screenshot you might need when I get back.

Yesterday I started to get crashes every half hour or so. A lot of "SQUASHFS error" messages, so I guess I need to create a new USB drive for my server. So I found an old thumb drive, ran it through the installation process, and booted it up on my server. Now, for the life of me, I can't figure out how to get it up and running with my system. I've got my login for my online Unraid account, but I have no idea how to get the system back up and running. Searches turn up methods that no longer work, I'm just at a loss. Any help would be appreciated.

I set up a VM, installed Debian, Casa OS, Crafty, and set up a Minecraft server. It's worked flawlessly for about a month. Until a couple of days ago. Now it's crashing once or twice a day. It just says "reason-crashed". But hours before the crash it says something about being tainted: 2025-07-29 20:01:40.701+0000: Domain id=5 is tainted: high-privileges char device redirected to /dev/pts/0 (label charserial0) 2025-07-30 06:27:37.974+0000: shutting down, reason=crashed I don't know what that means, but it SOUNDS bad... ;-) Any ideas why this is happening? The VM log doesn't have a ton, is there any other logs I should be looking at?

As the title states, over the last few weeks my server's been crashing every 2-3 days. Any help would be greatly appreciated. syslog.log

My server's been crashing every few days, and I want to post the logs here. I THOUGHT the proper procedure was to go into Settings, Syslog Server, and set Local syslog server to Enabled, and set the Local Syslog folder to a share on the system (I set up one called "Log" and set it to Cache Only). When it crashes, there is nothing there. I'm missing something obvious...

That worked, though I figured it out before I read your post. I created a clean install USB, copied all the files from the zip file to it, and it worked like a charm.

So I replaced my MB/CPU/RAM for my server. I wasn't sure how to restore my config, so I ran the UnRaid tool and created a bootable drive for the version I was using. I didn't realize there was an option to use the backup zip file as the source, so I ended up installing a new version of UnRaid on the thumb drive. I tried running the tool again, and this time I noticed that at the very bottom you can point it to your zip backup file. But when I did this, the thumb drive was not bootable, so I couldn't load the OS. How do I get a bootable OS AND have it contain my backed up files?

To button up this thread, it was already connected to MOLEX, so I knew that wasn't it. But itimpi made me wonder if that port was bad. I found a MOLEX splitter and split another port in the PS, and connected it there. It rebuilt and is running great! Thanks for the idea!

My current load is 153W, according to UnRAID's UPS tool. Maybe something with that branch of the power supply? Would that be possible? I'm not sure if I have any Molex ports available. I'll try to shut down the server tonight and see.

I'm using UnRAID primarily for Plex, that's the workhorse. I also have a couple of VMs - Home Assistant, a few basic desktops. I've got about $500 to spend. Would it be better to buy a video card, or replace the MB/CPU/RAM? Here's what I've got: CPU - Intel Core i3-8100 CPU @ 3.60GHxz MB - ASRock B365M Pro4 Mem - 32GB DDR4 No Graphics card - uses the Intel for GPU I could get something like: AMD Ryzen 9 9900X, MSI X670E MAG Tomahawk WiFi, G.Skill Flare X5 Series 32GB DDR5 for $500 or I could get something like a NVIDIA RTX 4060 8GB or an AMD Radeon RX 7700XT or an 7800XT. Any advice would be appreciated.

Bought a 14TB Exos a while back to shuck and use in my array. I always pre-clear prior to shucking the drive. Pre-clear went great. When I put it in the array (running 6.12.14, if it matters), while rebuilding the array, it would make an awful whistle/grinding noise every 5 seconds or so. But it did rebuild. It worked for a few days, then fell out of sync for some unknown reason. I plugged the USB panel back in and tested in Windows using SeaTools. 100% fine, no problems. Re-read the above paragraph 2 more times. 3 attempts to rebuild, it works, then falls out of sync. I have tried everything. I don't think I can RMA it, because Seagate would test it and it would come back fine. Anyone else have problems like this with Seagate? I'd buy another drive and use this in my personal drive, but I'm afraid it will happen again.

My UPS load is at 127W. This drive replaced a 4TB that had no problems at all, so unless this hard drive has more power consumption than the last one, it didn't change. I wasn't seeing any errors about losing connection to the drive, but I'm not sure. I DO know that my #6 drive has connection issues, it fell out of sync again. When my new one finishes rebuilding, I'm going to swap cables. The server has been up for 26 hours, and the rebuild is at 22%. So it is getting better, and I'm not hearing the chirping as often. So maybe it will resolve itself.

If you're getting that from the log, that log was obtained while it was plugged into my Windows machine.