I just did a reboot on a perfectly fine Unraid server and not it will not go online. I am using the internal boot drive. Only thing I did last night was add a script to the boot drive that after 30 minutes, it should turn off an attached usb drive. That part also was working fine.

I have backup's, I just don't know where to start. Attached is the screen of the Server.

Running the latest version of Unraid. Lifetime membership with 6 drives. Can provide more information, just need to know the process of getting it back online.

Your screen shows the server is not stuck on the array disks. Those are all detected. It is stuck waiting for one device, sda, which is not responding:

sd 10:0:0:0: [sda] tag#0 timing out command, waited 180s

Each of these messages means one command failed after 3 minutes of trying, so boot can stall for a very long time. From its position after the SATA ports, sda is most likely a USB storage device. Since the only change was the script that turns off your USB drive, that drive is my first suspect. A normal reboot may not reset a USB drive, so it can stay unresponsive and block the boot.

Please try this:

1. Turn the server off completely. If it does not respond to the keyboard, hold the power button. The array has not started at this point, so this is safe.

2. Unplug the USB drive from the server, and also unplug its power cable if it has one.

3. Turn the server on and see if it comes online.

If it still stops on the same message, turn it off again, unplug any other USB storage, including a USB flash drive if you have one for the license, and try again. If you still see sda timing out with no USB storage attached, the problem is an internal device. In that case, please post a new photo of the screen.

If it boots, please don't reconnect the USB drive yet. Post the script, tell us how you start it (go file, User Scripts plugin, or something else), and attach the diagnostics from Tools > Diagnostics. Then we can check how it turns the drive off.

You don't need your backups for now. Nothing here points to a problem with your boot drive or data.

The GPT messages on the screen for sdg and sdh are a separate thing and are not stopping the boot. Please don't try to fix them with Parted as the message suggests.

Smart advice. I determined not to do anything in haste, walked away to work on replacing my cracked toilet, just came back to read your message, and the server is up!

I remember now why I wanted to reboot in the first place, the USB drive "Mount" was grayed out. I read in those cases to reboot the server. That's where I ended up hanged up with it not booting for so long.

Just unplugged the drive and it's gone now as well as the grayed out Mount.

Array is now booted up. Going to delete that script. It worked when the array was up, but rebooting looks like it causes issues. The script polled the usb drive and if it was idle for 30 minutes it would un-mount it and stop the spinning disk.

Thank you for your help!