Fresh install, booted up earlier today and everything was fine, verified that I could see all the disks, etc and then shut down the box.

Powered up tonight to start doing real config, grabbed my laptop and tried to connect (I could only connect via IP during the original uptime) so my servername.local and got nowhere (so that is a different issue that I need to figure out) so I assume it is the hostname issue and try to access directly via IP and get nothing. I ping the box to make sure it is up and sure enough, all the packets come back indicating that its listening.

Walk to my office, fire up the connected monitor and log in to the GUI and Firefox pops up and states Unable to Connect.

So, it cannot connect to itself via localhost. I even tried 127.0.0.1 for kicks and nothing there either.

Not sure I trust this thing to work being that its the second boot and I already can't connect. With 0 config changes.

 

Let me know if there is any other info you would need to help. I have rebooted several times over the course of a couple hours

Attach diagnostics to your NEXT post in this thread.

Adding diagnostic from USB
Note I did add the disks to the array earlier today but didn't do anything with them so no data is going to be lost if I just need to start over. The only other thing I did was set the password as the guide states, and added a secondary user account. I saw telnet and disabled that.

unraid-diagnostics-20220215-2143.zip

Edit config/ident.cfg on flash drive and change your server name to something without special characters.

Oh look, user error. Thanks for the help! That was it. As you can tell I'm probably in for quite a ride lol. Next step - identifying which spinny disk is which. See you shortly (just kidding, I hope)

5 minutes ago, seecs2011 said:

identifying which spinny disk is which

Unraid keeps track of disk assignments by serial number.