skyhawk Posted February 18, 2015 Share Posted February 18, 2015 Seem to have a hardware issue that coincidentally coincides with my update. weird, but ive had tech issues in the past that happen at the same time. might have a bad mobo or CPU and cant get into the bios. I realized after posting this that I was in the General support for v6. My bad, but technically I guess its not too far off as Id be happy just upgrading to v6 and fixing my settings. Im currently running 5.0-rc12a. (but happy to just update to v6 beta now) I honestly didnt even realize i wasnt on the official 5.0 version of unraid. Its been working without issues.. other than the user. I attempted to install a new cache drive over the weekend (friday, 13th). I installed the drive months ago, but I dont have a Pro license, so I couldnt mount it (over the drive limit). I left it in there as a warm spare. Not sure if I cleared it or not. My current cache is 40 gigs and too small. I copied the files over to Disk 5, stopped the array, changed the cache drive selection, hit start and .... nothing. I sent a Restart command to the server after some time (telnet). I gave up for the day, the next day I could see the Flash on the network, but I couldnt access the GUI (but I could access unmenu). Did some searching, uninstalled Dynamix (per a helpful forum post), restarted and less than nothing (cant get unmenu or see the flash anymore). Cant ping server. My thoughts -- attempt to fix, which Im sure you all can help with (log below). OR can I just update to v6 beta. Im comfortable being on the v6 beta, or the stable v5. Can I just reinstall unraid (v6) on my flash and get everything back up and running and just reconfigure my apps and settings (without losing data on my drives) Or is there a simple fix (and then I will update). THANK YOU Feb 14 04:40:01 Tower syslogd 1.4.1: restart. Feb 15 10:59:52 Tower kernel: r8169: eth0: link down Feb 15 11:00:29 Tower kernel: r8169: eth0: link up Feb 15 16:08:54 Tower in.telnetd[26637]: connect from 192.168.1.77 (192.168.1.77) Feb 15 16:08:57 Tower login[26638]: ROOT LOGIN on '/dev/pts/0' from '192.168.1.77' Feb 15 16:11:19 Tower kernel: NTFS driver 2.1.30 [Flags: R/W MODULE]. Feb 15 16:13:48 Tower unmenu[6098]: which: no bwm-ng in (/bin:/usr/bin:/sbin:/usr/sbin) Feb 15 16:13:50 Tower unmenu[6098]: which: no bwm-ng in (/bin:/usr/bin:/sbin:/usr/sbin) Feb 15 16:19:45 Tower shutdown[28652]: shutting down for system reboot Feb 15 16:19:46 Tower init: Switching to runlevel: 6 Feb 15 16:19:49 Tower rc.unRAID[28671][28672]: Powerdown V2.06 Feb 15 16:19:49 Tower rc.unRAID[28671][28673]: Stopping Plugins. Feb 15 16:19:49 Tower rc.unRAID[28671][28681]: Running: "/etc/rc.d/rc.cachedirs stop" Feb 15 16:19:49 Tower rc.unRAID[28671][28684]: cache_dirs not running! Feb 15 16:19:49 Tower rc.unRAID[28671][28686]: Running: "/etc/rc.d/rc.couchpotato_v2 stop" Feb 15 16:19:49 Tower rc.unRAID[28671][28699]: Running: "/etc/rc.d/rc.dropbox stop" Feb 15 16:19:49 Tower rc.unRAID[28671][28703]: Running: "/etc/rc.d/rc.emailnotify stop" Feb 15 16:19:49 Tower rc.unRAID[28671][28706]: unraid_notify not running! Feb 15 16:19:49 Tower rc.unRAID[28671][28708]: Running: "/etc/rc.d/rc.headphones stop" Feb 15 16:19:49 Tower rc.unRAID[28671][28712]: Running: "/etc/rc.d/rc.openvpn stop" Feb 15 16:19:49 Tower rc.unRAID[28671][28716]: Running: "/etc/rc.d/rc.plexmediaserver stop" Feb 15 16:19:49 Tower pms: Stopping Plex... Feb 15 16:19:52 Tower rc.unRAID[28671][28727]: Running: "/etc/rc.d/rc.sabnzbd stop" Feb 15 16:19:52 Tower rc.unRAID[28671][28737]: Running: "/etc/rc.d/rc.sickbeard stop" Feb 15 16:19:52 Tower rc.unRAID[28671][28741]: Running: "/etc/rc.d/rc.sysstat stop" Feb 15 16:19:52 Tower rc.unRAID[28671][28745]: Stopping unRAID. Feb 15 16:19:53 Tower rc.unRAID[28671][28769]: Killing active pids on the array drives Feb 15 16:19:53 Tower rc.unRAID[28671][28773]: Sync filesystems Feb 15 16:19:53 Tower rc.unRAID[28671][28776]: Umounting the drives Feb 15 16:19:54 Tower rc.unRAID[28671][28780]: /dev/md1 umounted Feb 15 16:19:54 Tower rc.unRAID[28671][28780]: /dev/md2 umounted Feb 15 16:19:55 Tower rc.unRAID[28671][28780]: /dev/md3 umounted Feb 15 16:19:55 Tower rc.unRAID[28671][28780]: /dev/md4 umounted Feb 15 16:19:55 Tower rc.unRAID[28671][28780]: /dev/md5 umounted Feb 15 16:19:55 Tower rc.unRAID[28671][28788]: Stopping the Array Feb 15 16:19:55 Tower kernel: mdcmd (23): stop Feb 15 16:19:55 Tower kernel: md1: stopping Feb 15 16:19:55 Tower kernel: md2: stopping Feb 15 16:19:55 Tower kernel: md3: stopping Feb 15 16:19:55 Tower kernel: md4: stopping Feb 15 16:19:55 Tower kernel: md5: stopping Feb 15 16:20:00 Tower mdstatusdiff[28809]: --- /tmp/mdcmd.28671.1^I2015-02-15 16:19:55.452533137 -0500 Feb 15 16:20:00 Tower mdstatusdiff[28809]: +++ /tmp/mdcmd.28671.2^I2015-02-15 16:20:00.482602779 -0500 Feb 15 16:20:00 Tower mdstatusdiff[28809]: @@ -1,14 +1,14 @@ Feb 15 16:20:00 Tower mdstatusdiff[28809]: sbName=/boot/config/super.dat Feb 15 16:20:00 Tower mdstatusdiff[28809]: sbVersion=2.1.4 Feb 15 16:20:00 Tower mdstatusdiff[28809]: sbCreated=1312575816 Feb 15 16:20:00 Tower mdstatusdiff[28809]: -sbUpdated=1423862104 Feb 15 16:20:00 Tower mdstatusdiff[28809]: -sbEvents=298 Feb 15 16:20:00 Tower mdstatusdiff[28809]: -sbState=0 Feb 15 16:20:00 Tower mdstatusdiff[28809]: +sbUpdated=1424035195 Feb 15 16:20:00 Tower mdstatusdiff[28809]: +sbEvents=299 Feb 15 16:20:00 Tower mdstatusdiff[28809]: +sbState=1 Feb 15 16:20:00 Tower mdstatusdiff[28809]: sbNumDisks=6 Feb 15 16:20:00 Tower mdstatusdiff[28809]: sbSynced=1422799295 Feb 15 16:20:00 Tower mdstatusdiff[28809]: sbSyncErrs=0 Feb 15 16:20:00 Tower mdstatusdiff[28809]: mdVersion=2.1.6 Feb 15 16:20:00 Tower mdstatusdiff[28809]: -mdState=STARTED Feb 15 16:20:00 Tower mdstatusdiff[28809]: +mdState=STOPPED Feb 15 16:20:00 Tower mdstatusdiff[28809]: mdNumProtected=6 Feb 15 16:20:00 Tower mdstatusdiff[28809]: mdNumDisabled=0 Feb 15 16:20:00 Tower mdstatusdiff[28809]: mdDisabledDisk=0 Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.