headnail Posted November 12, 2018 Share Posted November 12, 2018 (edited) Hello, I have been using Unraid for a number of years now without any issues (even changed platform without any issues!), always keeping up-to-date with the latest stable release without any issues until I just updated to 6.6.5. It might be useful to note that while I consider myself reasonably tech literate, my Linux experience is somewhat limited. I have no clue what went wrong, followed the same procedure I always do (download stable update, stop array, reboot), however once rebooted I no longer had access to my server. I hooked up a monitor and observed the boot procedure, everything went smooth right up to "Starting Samba; /usr/sbin/nmbd -D /user/sbin/smbd -D /usr/sbin/winbindd -D" Following which I get the following error: "/var/tmp/go: line 1: $'\377\377\377 (a bunch more \377\)': command not found I do get an IP assigned but access the web interface. Tried the GUI boot mode but still no access to the web interface (cannot connect to localhost). Attempted to revert the update (copied contents from /previous), managed to downgrade to 6.6.4 but the problem still persists. I have attached my syslog file and the diagnostics file. Any help would be highly appreciated! Edited November 13, 2018 by headnail added diagnostics file Quote Link to comment
trurl Posted November 13, 2018 Share Posted November 13, 2018 For some reason your go script is hosed, so nothing will start. Replace it with a good copy. Quote Link to comment
headnail Posted November 13, 2018 Author Share Posted November 13, 2018 Thanks!! Made a new Unraid USB and grabbed the go script from there....everything appears to be working! Much appreciated! I did notice that there is a large number of FSCK**** files on my main Unraid flash drive, also Windows reported issues on the drive (when attempting to copy I could not access plugins_previous), is it possible that my USB stick is dying? Quote Link to comment
trurl Posted November 13, 2018 Share Posted November 13, 2018 Possible but not necessarily. Filesystem corruption often has other causes like unclean shutdown, disk or flash dropping offline for some reason, etc. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.