TQ Posted March 24, 2015 Share Posted March 24, 2015 Starting last night, my unRAID server just powered off. I powered it back on and it was online for about 45 mins then shutdown again. Prior to this, it had been running fine for some time. Today I powered it up and didnt start the array but starting tailing the syslog. I still cannot figure out what it going on but its still happening. I just keep seeing this over, and over, and over.... Mar 23 18:45:01 unRAID kernel: md: unRAID driver removed Mar 23 18:45:01 unRAID kernel: md: unRAID driver 2.2.0 installed Mar 23 18:45:01 unRAID emhttp: Device inventory: Mar 23 18:45:01 unRAID emhttp: OCZ-VERTEX_7B36ED6572C5W05PX8BD (sdb) 3126 Mar 23 18:45:01 unRAID emhttp: ST2000VN000-1H3164_W1H39E52 (sdc) 19535145 Mar 23 18:45:01 unRAID emhttp: ST2000DL003-9VT166_5YD5L8LF (sdd) 19535145 Mar 23 18:45:01 unRAID emhttp: ST2000DL003-9VT166_6YD162D8 (sde) 19535145 Mar 23 18:45:01 unRAID emhttp: ST2000DL003-9VT166_5YD2SB3K (sdf) 19535145 Mar 23 18:45:01 unRAID emhttp: ST2000DL003-9VT166_5YD2WYC6 (sdg) 19535145 Mar 23 18:45:01 unRAID emhttp: ST2000DL003-9VT166_5YD2WYD4 (sdh) 19535145 Mar 23 18:45:01 unRAID emhttp: WDC_WD30EZRX-00MMMB0_WD-WCAWZ2706097 (sdi) Mar 23 18:45:01 unRAID emhttp: shcmd (9464): /usr/local/sbin/emhttp_event Mar 23 18:45:01 unRAID emhttp_event: driver_loaded Mar 23 18:45:01 unRAID kernel: mdcmd (1): import 0 8,128 2930266532 WDC_W Mar 23 18:45:01 unRAID kernel: md: import disk0: [8,128] (sdi) WDC_WD30EZ Mar 23 18:45:01 unRAID kernel: mdcmd (2): import 1 8,80 1953514552 ST2000 Mar 23 18:45:01 unRAID kernel: md: import disk1: [8,80] (sdf) ST2000DL003 Mar 23 18:45:01 unRAID kernel: mdcmd (3): import 2 8,96 1953514552 ST2000 Mar 23 18:45:01 unRAID kernel: md: import disk2: [8,96] (sdg) ST2000DL003 Mar 23 18:45:01 unRAID kernel: mdcmd (4): import 3 8,112 1953514552 ST200 Mar 23 18:45:01 unRAID kernel: md: import disk3: [8,112] (sdh) ST2000DL00 Mar 23 18:45:01 unRAID kernel: mdcmd (5): import 4 8,64 1953514552 ST2000 Mar 23 18:45:01 unRAID kernel: md: import disk4: [8,64] (sde) ST2000DL003 Mar 23 18:45:01 unRAID kernel: mdcmd (6): import 5 8,48 1953514552 ST2000 Mar 23 18:45:01 unRAID kernel: md: import disk5: [8,48] (sdd) ST2000DL003 Mar 23 18:45:01 unRAID kernel: mdcmd (7): import 6 8,32 1953514552 ST2000 Mar 23 18:45:01 unRAID kernel: md: import disk6: [8,32] (sdc) ST2000VN000 Mar 23 18:45:01 unRAID kernel: mdcmd (: import 7 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (9): import 8 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (10): import 9 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (11): import 10 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (12): import 11 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (13): import 12 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (14): import 13 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (15): import 14 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (16): import 15 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (17): import 16 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (18): import 17 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (19): import 18 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (20): import 19 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (21): import 20 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (22): import 21 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (23): import 22 0,0 Mar 23 18:45:01 unRAID kernel: mdcmd (24): import 23 0,0 Mar 23 18:45:02 unRAID emhttp: shcmd (9465): rmmod md-mod |& logger Mar 23 18:45:02 unRAID emhttp: shcmd (9466): modprobe md-mod super=/boot/ Mar 23 18:45:02 unRAID emhttp: shcmd (9467): udevadm settle unRAID-syslog.txt.gz Link to comment
JonathanM Posted March 24, 2015 Share Posted March 24, 2015 The snippet you quoted will show up every time the main web gui is accessed or refreshed. Link to comment
itimpi Posted March 24, 2015 Share Posted March 24, 2015 Unexpected power off is almost certainly hardware related. I would carefully check all fans as something like you describe could happen if the processor is overheating. Link to comment
pcgirl Posted March 24, 2015 Share Posted March 24, 2015 I agree about the hardware related. Also, what UPS are you using? I had my server on a UPS that was not strong enough for the server. Every hiccup in the power and the the UPS app would think that it was on battery backup and it would shut down because it didn't have enough battery power to keep it up. I updated to a 1300 UPS with AVR and all is well now. Link to comment
TQ Posted March 25, 2015 Author Share Posted March 25, 2015 My thought was hardware related too, but I just wanted to cover all my bases by attaching a syslog in hopes that the community might notice something that I didn't. Seems like the thoughts on hardware were correct; tonight I noticed a small, un-obvious cable lodged into my CPU fan causing it not to spin. That explains why after so many minutes, the server would just shut itself off. Re-routed those cables tonight and powered unRAID back on. Currently running Parity check and has been up for several hours. I guess that was it. Thanks to the few of you for responses, the unRAID community is such a wonderful community and I'm happy to belong to this group. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.