--November 20th

The last 2 nights unraid has crashed during the night.  This morning it was down and after powering down and back again, its coming up as Tower again, cant possibly be 2 bad MB and 2 bad USB drives in a row?!?

 

I have really enjoyed using unraid, but this is making me crazy.

 

--- November 9th

I had a motherboard(Gigabyte AX370 K7) up and die on me yesterday, I bought a replacement today(MSI b350 tomahawk), and CPU/Memory (Ryzen 7 1800X/4x16gb Corsair Vengence LPX 3000) are fine.  

 

Unraid boots, but at the gui I try to enter the web UI and it tells me it cant find localhost.   I know i need to reconfigure my Ethernet ports ( the K7 had 2(previously bond0), the Tomahawk has 1 )  and probably need to tell it what drives are what, but im not sure how to do that at this point.  Do I need to reinstall unraid?  

 

Thanks,

Bill

 

 

Edited November 20, 20187 yr by Ebein

So does a MB replacement require a re-installation?   Suppose I will need a replacement key also?

Unraid is largely hardware agnostic as it loads up (I.e. installs) itself). into RAM every time you boot.   Normally you can change the hardware and simply boot UnRAID up on the new hardware and it continues working.

 

Not sure exactly what your problem is, but you might want to try deleting (or renaming) the network.cfg file in the config folder on the flash drive to revert to default settings for the network.

Thanks ill give that a try!

 

I took some pictures as unraid booted, I renamed network.cfg, to old_network.cfg, saw it was still looking for "bond0" and renamed it again to network.cfg.old, same message.  not sure if the below messages help at all.

 

random: 7 urandom warning(s) missed due to ratelimiting

usb 1-10: reset high-speed USB device number 4 using xhci_hcd

usb 1-10: device descriptor read/64, error -110

usb 1-10: device descriptor read/64, error -71

usb 1-10: Device not responding to setup address.

modprobe: FATAL: Module bonding not found in directory /lib/modules/4.18....

Cannot find device "bond0"

how do i go about doing a reinstall and what am i going to loose doing that?

Is the console booting up to Login prompt?  If it is, login.

 

Then type     diagnostics    at the command line prompt.   That will write the diagnostics file to the  logs  folder/directory on the flash drive.  You can then shut the server down--- a quick push of the power button should do that.  (I believe that  poweroff  is the CLI command.) 

 

Upload the diagnostics with your next post.

great thanks!

 

is the logs folder hidden?

says /boot/logs/tower-diagnostics-20181111-0109.zip created  but i cant find the path or file

 

there is an EFI-\boot but no log folder there

 

Are you saying there is no ‘logs’ folder on the flash drive (/boot is where the flash drive is mounted).   If it is not there then it suggests the flash drive dropped offline so that /boot was pointing to a location in RAM.

Make sure that your Flash Drive is plugged into a USB2 port (black plastic insert) and not a USB3 port (blue insert).  (Some MB/BIOS have issue passing off a USB3 port to the Unraid OS as it loads. )

Edited November 11, 20187 yr by Frank1940

ok, so how do i copy this file from memory to the flash drive, the folders are blue and black on green and blue on green  is there any significance there?

 

If a   ls -al /boot  command gives an error, the flash drive is not mounted.  That condition must be fixed first before any other issue can be solved!!!

that command gives me a listing

 

Now do an   ls -al /boot/logs   and see if there is a file with diagnostics as part of the file name .  It should have today's date on it.  If there is you have a copy there.  If not, try the    diagnostics     command again.  (FYI, the up-and-down arrow keys will allow a replay of the recent commands on the command line.  You can also edit those commands with the left-and-right arrow keys, backspace key and delete key.) 

 

the file is there

 

 

And Thanks!

so now what?

 

is it normal for the USB to be constantly blinking?  sitting at a prompt and it hasn't stopped.

2 minutes ago, Ebein said:

so now what?

 

shutdown the server, pull the stick and post the file

 

Pulled drive checked it on Windows Machine, no logs directory in boot folder

Picture below, logged into Tower, double checked for log folder, ran diagnostics again, and logs folder shows up.

shut down machine, and no log dir.  

 

What am i screwing up?

3 hours ago, itimpi said:

the flash drive dropped offline so that /boot was pointing to a location in RAM.

Its this

 

Try a different port.  Ideally USB2

Is this why the drive constantly blinks, its trying to reconnect?  or is that just an unraid thing?

 

Im on a USB 2.0 port trying another, is there a way to tell ive lost the drive and its writing to ram without shutting the machine down?

If you use the ‘df’ command it will show you what devices are currently mounted.    If /boot is not on the list then the USB drive has dropped offline.

this is what I'm seeing, I tried the 4 front panel USB's ( 2 2.0, 2 3.0 ) and the 4 rear ones and each time the file is not on the thumbdrive when i move it back to the windows PC to open the zip and post it here.  can i just stick in another USB drive and cp the file there?

 

Thanks for everyones help, I am a linux/unraid novice(obviously).