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

If a stock install works, backup the current one first and then recreate it using the USB tool and just restore the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder (\config\plugins\dockerMan\templates-user), if all works you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit.

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?

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?

If it's using the old key, you should be able to just copy the new one from the most recent backup, or get it from Unraid.net.

Hello,

I allow myself to up this post as my problem seems similar and no definitive solution seems to have been provided.
I hope it'll help me and others.

Problem description

After a fresh install of the Unraid OS using unraid-usb-creator-1.1.0.exe found here (made bootable via the given script), I notice that the OS boots up until the login prompt (with no noticeable error appearing) but it sometimes restarts immediately after without any error notice.

Any previous configuration if there was any gets overwritten and it occurs on around 2/3 of my startups.

Any configation that was set on the stick is overwritten. This can cause SSH to be disabled or the root account's password to become invalid or other similar problems.

To be precise, this even happens on fresh USB installs and I do not have any problem linking a licence to my USB stick.

I have ran my unraid trial with a different USB (3.2) stick. It behaved in a similar fashion. Unraid has always been run with only one USB stick pluggedin the server at a time.

USB stick

- Philips USB 2.0 Snow 32GB (current).
- Sandisk USB 3.2 Gen 1 Ultra Flair 32GB (used during my unraid trial).

System description

- MB: B850 GAMING PLUS WIFI6E (notice the motherboard provides no USB 2.0 ports so I use a 3.2 5G one).

- CPU: AMD Ryzen 9 7900X 12-core
- GPU: None (excluding the one internal to the MB).

- RAM: 2*16GB of DDR5 G.Skill Flare x5 (Memtest86+ passes)
- Storage: 1*1TB N.2 NVME SSD & 3*4TB Sata SSDs.
- PSU: A gold rated corsair gaming PSU (model undefined for the moment, Online Wattage calculators suggest a necessity of 500W or less).

Kernel settings fiddled with

- XHCI Hand-off: on/off.

- Legacy USB support: enabled

- BIOS UEFI/CSM mode: UEFI

- Secure Boot: disabled

- Fast boot: ??? not available

- Power Supply Idle Control: Typical Current Idle/Auto

- Global C-State control: auto/disabled

- No overcloaking settings at all.

I dispose of a backup of my configuration and all and ways to restore my NAS quickly.
Sadly, for now, I'm out of ideas and this situation is stressful.

Would someone have any ideas to make my setup stable ?

Thanks in advance for all help that could be provided.

If my post has insufficient details please tell me in a polite manner and I'll update it as soon as possible.
I do not know yet about the unraid forum's standards.

Best regards.

Edited March 20Mar 20 by Rishmor
Additionnal information (cf. later posts).

9 minutes ago, Rishmor said:

but it sometimes restarts immediately after without any error notice.

Server rebooting by itself is typically a hardware issue, start by running memtest, or because memtest is only definitive if it finds errors, if you have multiple sticks try using the server with just one, if the same try with a different one, that will basically rule out bad RAM.

1 hour ago, JorgeB said:

Server rebooting by itself is typically a hardware issue, start by running memtest, or because memtest is only definitive if it finds errors, if you have multiple sticks try using the server with just one, if the same try with a different one, that will basically rule out bad RAM.

Hello !
Thanks for your answer.

I'm reviewing my system's specs because as you said I also think it's probably a hardware failure.
The server is newly built (1 month old as of now).

I'll update my original post with all the additionnal information I'll be putting here below:
- I ran the provided Memtest86+ tool and it succeeded. I don't think the RAM is faulty.
- At all times I only have one USB stick plugged in the server on a USB-A 3.2 5G port.
- I have run the unraid trial on a kingston USB 3.0 32GB stick and I ran into the same problem. I don't think the USB stick is faulty.

As for the GPU, I only have the one internal to the MotherBoard.

As for the PSU, all the online calculators suggest a wattage off 500 or less.
I don't remember exacly what PSu I have but it's a gold rater gaming corsair PSU. It should be able to cover it. I don't think the PSU is faulty here.