MichaelG

Hi I just had to restore my flash usb with an old backup, using a new usb stick When I boot up, it says I have to replace the key for this new drive but when I try, it always fails. Attached is the screen shot. Could something have happened to my key? m

Ok, So a bit of progress. I found a very old usb flash backup and tried to flash the usb from that. At least this did not cause any rebooting. But I got into the GUI and it says the key is tied to another usb, When I try to replace the key it just keeps saying "key replacement failed" I am starting to think there is something wrong with the key itself and not the file. Is this a thing?

So I Tried your instructions. just copying over the files/folders you suggested. It had the same problems So I started eliminating items one by one. Re flashing the usb each time. All kept failing. I just tried the bare minimum as I don't think anything else will work to recover. I updated only the lines of the ident that were in the stock ident. And I just added the key files. And it goes to the same problem. So I think I may have a corrupt Key file. how would I fix this?

Hi I had some issues a few months ago, the rebooting issue was minor, it only rebooted randomly every couple of weeks, not great but handleable. Now, every time I boot into Unraid, as soon as it gets to the end of the boot where it says the ip address and login prompt, the server restarts I tried a completely fresh install on another flash drive, everything works fine and it stays on and running. I tried moving my original flash drive's config folder over to the new one, and I get the exact same reboot behavior as before. I have tried booting into safe mode and same issues. I have run through memtest and no errors I can't actually get into the server to retrieve any diagnostics or logs. Please help

Well, a friend had a spare cpu I could try. replaced the CPU, put the original usb drive back in Everything booted fine straight in, no issues So It is definitely a CPU issue. I just dont know what the issue is

I had already tried that. I guess I'm gonna have to buy a new CPU to test :( That's the only thing I didn't have a spare of lying around Had a spare and tried motherboard/ram/ssd's/coolers and fans

Ok I think I may have found a workaround for this From another computer (if WebGUI is inaccessible): Shutdown your Unraid server. Remove the USB flash drive that contains the Unraid OS. Insert the USB flash drive into another computer. Open the USB flash drive and navigate to the /syslinux directory. Open the syslinux.cfg file in a text editor. Edit the syslinux.cfg file: Locate the line that starts with append. Add clk_ignore_unused as a boot parameter to this line. For example, if the line is currently append initrd=/bzroot, you would change it to append clk_ignore_unused initrd=/bzroot. Save the changes and reboot: Save the modified syslinux.cfg file. Safely remove the USB flash drive from the computer. Insert the USB flash drive back into your Unraid server. Boot your Unraid server. On my first try, it got straight past the disabling clocks line. Now its stalled on a different line "rc.udev: triggering udev events" Can you try this and see if it works for you?

Any idea what the hardware issue could be? Like I said, the only thing I haven't swapped out is the CPU

Just did it. Still have the same problem This is very strange. What could it be?

@JorgeB what will happen to my setup. Will I lose everything (data, settings, etc)?

Hi, I have a new issue with booting unraid. Every time I try to boot, everything runs fine until the script starts and it just stops. The last line always being "clk: Disabling unused clocks" I have attached a screenshot of the boot I have tried everything. running in safe mode Replacing bz files Enabling/disabling Fast boot Enabling/disabling XMP Enabling/disabling amount of cores used (from 1 to 14) Enabling/disabling VM support Tried a boot drive of Ubuntu, It works fine Swapped out the memory Swapped out the Motherboard Didn't have a spare cpu on hand, so couldn't test that. Gone through all troubleshooting for both sets of Memory & Motherboard I also just tried a brand new USB from a usb flash backup I had after updating to 7.0 Exactly the same thing. Really running out of things this could be Please help

I have the same thing happening to me right now, did you ever find a reason/fix for this?

So we had a power outage, and my UPS failed (or had already been failing and I never knew because we hadn't had a power outage in a while) So I couldn't access the GUI or SSH I plugged in a monitor and everything seemed to be fine except it now said "tower login" as opposed to the usual "servername login". Strange I checked the config and everything had been reset to default values So I got an earlier version I had saved to get back my server details into the config file. Still nothing I have tried a bunch of fixes from this forum and nothing seems to work, so I am assuming its something specific with whatever happened to my flash drive. Attached is the latest diagnostics zip (which also is showing the wrong date and time even though the right date and time comes up in the info before the login prompt appears) I'm at a loss. I don't want to use the backup flash as its from quite a while ago, but I can if I have to tower-diagnostics-20211231-2242.zip