June 5, 20179 yr I've got a server using a Cruzer 16GB drive, been working fine for over 2 years. Just did an upgrade for Plex and when the server rebooted, I'm at a Tower login vs the normal login. I can ping the server and can login to the server from the console (but NOT telnet). I thought the problem was a failed USB drive, but I can read the drive with no issues. I edited the network.cfg file and changed the ip address and was able to ping the new address. But cannot see the flash drive from the console. At the root, an LS produces a directory listing, but all the normal directories are empty (log, mnt, etc). I can't find a way to save the syslog since unraid is not seeing the USB drive. How could an upgrade to Plex mess up the flash drive? Not seen behavior like this before. Suggestion?
June 5, 20179 yr Community Expert 1 hour ago, jeffreywhunter said: did an upgrade for Plex and when the server rebooted Shouldn't require a reboot. How are you running plex? 1 hour ago, jeffreywhunter said: How could an upgrade to Plex mess up the flash drive? Probably a coincidence. Any reboot might have had the same result. Shutdown, put the flash in your PC and let it checkdisk. If it looks OK, try a different USB port.
June 6, 20179 yr Author Running plex as a docker. Upgrade applied through docker. Sorry, I should have said I did try different USB ports (one 3.0 and one 2.0). Also did a checkdsk on the drive and it passed with no errors. However, I did see a Found.000 file on the stick with a number of files in it - dated may 2015, so pretty old. This was my son's plex server and unfortunately, we didn't backup his Cruzer yet (forgot about it actually...duh). So if we have to rebuild the USB drive, are there instructions somewhere on how to rebuild a server w/o losing the array?
June 6, 20179 yr Community Expert 11 hours ago, jeffreywhunter said: are there instructions somewhere on how to rebuild a server w/o losing the array The main thing about starting from scratch is to know which drive is supposed to be parity. As long as you don't assign a data disk to the parity slot the rest can be worked out. If you can read the flash drive in Windows, backup the config folder. It has everything in it about your current configuration. Then you can do a new install on that flash or another and just restore the config.
June 6, 20179 yr Author Perfect, thanks trurl. I can access all the files on the USB and have backed up the files. Is there a way to get the syslog from the server? I've been able to cat it to the screen, I see a bunch of errors. Would there be a few specific things to grep to see if there is a root to the problem? At first I thought it was not seeing the USB, but it has to be reading it because the server has an IP, I can ping it on the network. Odd one...
June 6, 20179 yr Community Expert 41 minutes ago, jeffreywhunter said: Perfect, thanks trurl. I can access all the files on the USB and have backed up the files. Is there a way to get the syslog from the server? I've been able to cat it to the screen, I see a bunch of errors. Would there be a few specific things to grep to see if there is a root to the problem? At first I thought it was not seeing the USB, but it has to be reading it because the server has an IP, I can ping it on the network. Odd one... It is not unheard of for the flash drive to get dropped after everything else is working, and everything will continue to work except for things that need to access flash, such as saving changes in the webUI, since the OS is actually loaded into RAM already. A dropped flash is usually a problem with the port. This often shows up in the log as "bread" errors. If you cannot see the flash drive from the console then it isn't mounted. So you can't really save log to flash since it isn't there. You might be able to save it to cache or array and get it later after you reboot. I don't think there is anything you can do to recover from unmounted flash except reboot. Even if you can manually mount it unRAID won't see it as the drive that it should be looking at for the OS flash drive. You can't even do a "clean" shutdown since it won't be able to write the "clean" status to flash. Just because it will boot from a flash drive or from a USB port doesn't mean there isn't an intermittent hardware problem with either the flash or the port.
June 7, 20179 yr Author Perhaps this can help. I did a cat syslog|more and then made a short movie paging through the syslog. Perhaps there's something hidden in that which can help. Here's a link to the video: https://www.dropbox.com/s/segop77y2biih48/unRaidSyslog20170607.mp4?dl=0 Interestingly, many utilities are available. I was able to load MC and display the syslog. Searched for "bread" but not found. USB Loads around :42 seconds. At 45 seconds the Cruzer loads (plugged into one of the USB MOBO black usb Ports (2.0?)). At :50 secs theres a strange "random: udevd: unitialized urandom read (16 bytes)" that repeats many times. At 1:09 I'm seeing device descriptors error reported - device descriptor read/64, error -110 And several others -71, -62, then finally at 1:10 you'll see a usb4-port3: unable to enumerate USB device Hope this helps. I'm kinda stuck at this point... Thanks in advance!
Archived
This topic is now archived and is closed to further replies.