May 2, 201115 yr Hey all, Having some strange issues going on with my unRAID server after trying to a Parity check. I am still able to log into the shell via telnet and I was able to grab this... What's going on? This is a brand new array with 21 drives. syslog.txt
May 2, 201115 yr Author Check out this wiki page. http://lime-technology.com/wiki/index.php?title=Troubleshooting
May 2, 201115 yr Author I also rebooted from inside the Telnet session and now the webgui asked for my login information, but won't load the gui....
May 2, 201115 yr Author Here is the systemlog after reboot. Note that I killed unMENU before rebooting... syslog-2008-04-10.txt
May 2, 201115 yr Author I just got into the WebGUI, though it was quite delayed. Finally asked me for my login and password and I'm in and launched unMENU. Note: Parity updated 156864 times to address sync errors. WOAH!!
May 2, 201115 yr It looks like a drive problem or a cabling problem. Try checking all the drive cables. You could also pull a SMART report from each drive and see if anything odd appears. Peter
May 2, 201115 yr Author It looks like a drive problem or a cabling problem. Try checking all the drive cables. You could also pull a SMART report from each drive and see if anything odd appears. Peter Checked all the cables and everything looks good. I also reseated them all. I am running Parity check and tailing the log to see if anything comes up.
May 2, 201115 yr Author Well here it happened live during the Parity check.... see attached log. updated-log.txt
May 3, 201115 yr I don't really know what to suggest. It appears multiple drives are dropping off the controller card. Do you have a good power supply in that server? Peter
May 3, 201115 yr Author I don't really know what to suggest. It appears multiple drives are dropping off the controller card. Do you have a good power supply in that server? Peter Peter, Thank you for checking in. I have this 650w P/S http://www.newegg.com/Product/Product.aspx?Item=N82E16817139005 I have a few 7200 drives in there.... but I was able to rebuild parity when I originally combined two smaller unraid servers into this large one....
May 4, 201115 yr Like Peter said, really weird. Drives dropping off like that. Are these plugged into the mobo port or a controller card? Shawn
May 4, 201115 yr That power supply should be fine. It's having trouble reading every drive on that card, which make me think it's a card or PCIe port power issue or something odd like that. Like Peter said, really weird. Drives dropping off like that. Are these plugged into the mobo port or a controller card? Shawn I'd bet money they're on a Supermicro AOC-SASLP-MV8. I could be wrong but it sure looks like that card from the syslog. Peter
May 4, 201115 yr Author That power supply should be fine. It's having trouble reading every drive on that card, which make me think it's a card or PCIe port power issue or something odd like that. Like Peter said, really weird. Drives dropping off like that. Are these plugged into the mobo port or a controller card? Shawn I'd bet money they're on a Supermicro AOC-SASLP-MV8. I could be wrong but it sure looks like that card from the syslog. Peter You are correct... Supermicro AOC-SASLP-MV8 cards. 2 of them...
May 4, 201115 yr Seems most likely then bad controller or maybe a bad slot on the mobo. Time to start ripping out parts and testing. You have another motherbpard you can move this all over to, to test? Shawn
May 4, 201115 yr Author Seems most likely then bad controller or maybe a bad slot on the mobo. Time to start ripping out parts and testing. You have another motherbpard you can move this all over to, to test? Shawn I do not... I think I'm going to try and pull a 750w power supply and put it in there. Ugh... I'm really not looking forward to this test!
May 4, 201115 yr Try first by connecting two Molex connectors to the backplanes (and not a single as per Norco). I do not have this case but I remember seeing some posts that fixed some HD problems. But anyway I believe you have configuration issue.
May 12, 201115 yr Author Update: 5/11 I have switched out the original 650w power supply with a 750w (Single rail Corsair as well). It's rebuilding parity at this time, but when I look at unMenu I am still seeing some of those errors. I am now starting to lean into a card/cable issue. I'm trying to understand which drives are being impacted by this to help determine the cable/card to test, but from the log I'm uncertain which drives I should be checking. Any advice?
May 12, 201115 yr Couple of things... when you rebooted from Telnet - did you stop the array? That would acocunt for a lot of the errors - dirty shutdown. You could try running NOCORRECT parity checks. Run 2 or 3. If you see all the errors in the same spot, that can actually be a good thing, no new ones. They just need to be rebuilt. Only then try running a CORRECT parity check. Also, you could run SMART reports on all your drives, see if any of them are looking off. Finally - are you running a Norco case? Like bcbgboy13 said, plug in both Molex. Although they are redundant, you never know. And maybe you actually have a back backplane? Some food for thought... Shawn
May 12, 201115 yr Author Couple of things... when you rebooted from Telnet - did you stop the array? That would acocunt for a lot of the errors - dirty shutdown. You could try running NOCORRECT parity checks. Run 2 or 3. If you see all the errors in the same spot, that can actually be a good thing, no new ones. They just need to be rebuilt. Only then try running a CORRECT parity check. Also, you could run SMART reports on all your drives, see if any of them are looking off. Finally - are you running a Norco case? Like bcbgboy13 said, plug in both Molex. Although they are redundant, you never know. And maybe you actually have a back backplane? Some food for thought... Shawn Thanks Shawn I will try adding 2x Molex into the backplanes. I do have a huge problem though... It looks like Disk10 has come up with a RED DOT and my Parity is Orange/invalid! What do I do?!?!?!
May 12, 201115 yr Author I just ran a SMART on Disk10 through unMenu: SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 100 100 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0007 063 063 011 Pre-fail Always - 11830 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 466 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 100 051 Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - 10630 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 7538 10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 127 13 Read_Soft_Error_Rate 0x000e 100 100 000 Old_age Always - 0 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0033 100 100 000 Pre-fail Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 076 068 000 Old_age Always - 24 (Min/Max 20/24) 194 Temperature_Celsius 0x0022 074 068 000 Old_age Always - 26 (Min/Max 20/26) 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 1494 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 100 100 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0 201 Soft_Read_Error_Rate 0x000a 253 253 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 7536 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.
May 12, 201115 yr What do I do?!?!?! Post a syslog. I don't see any error on that smart report. Could just be a sata cable ?
May 12, 201115 yr Author Here is the most recent log. Too big t post here even after cutting down. http://www.sendspace.com/file/xowrjl
Archived
This topic is now archived and is closed to further replies.