kavo Posted January 6, 2015 Share Posted January 6, 2015 Hi, My box has been going unresponsive when doing a parity check and needing reboot. I deleted alot of the plugins to see if that was the issue and the webgui and a few of the plugins i left on have gone unresponsive but I can still access the shares etc which is new and an improvement. I wonder will the parity check finish and all will be ok? Is this being caused by a faulty disc? its been a hile since a parity check has been completed, that im aware of. if the system goes unresponsive does the parity check still run? Syslog: http://pastebin.com/q3qgUZPF Link to comment
trurl Posted January 7, 2015 Share Posted January 7, 2015 Have you tried booting in SAFE mode? If you are using PhAzE plugins on 6b12, have you done the workaround for 6b12 PhAzE added to the first post of his thread? Link to comment
kavo Posted January 7, 2015 Author Share Posted January 7, 2015 Have you tried booting in SAFE mode? If you are using PhAzE plugins on 6b12, have you done the workaround for 6b12 PhAzE added to the first post of his thread? the go file workaround to view the settings page? Yes I have Link to comment
kavo Posted January 8, 2015 Author Share Posted January 8, 2015 Boot in SAFE mode then Thanks I'll try this when I get back from work (away for a week). What will booting in safe mode do and how will it help me find he issue? Link to comment
trurl Posted January 8, 2015 Share Posted January 8, 2015 SAFE mode is without any addons. Link to comment
kavo Posted January 17, 2015 Author Share Posted January 17, 2015 Ok so I've booted in safe mode. Its currently at 12% parity check. Is there anything to check or do now its in safemode? Link to comment
kavo Posted January 17, 2015 Author Share Posted January 17, 2015 Ok so while i was sleeping it became unresponsive, the parity check could well have been finished but i cant say for sure. Can not access via telnet or anything. What can I do? Link to comment
Frank1940 Posted January 17, 2015 Share Posted January 17, 2015 You should probably read the first post in this thread: http://lime-technology.com/forum/index.php?topic=9880.0 Notice the tail command line. You will probably have to open a Telenet window and leave it open until the system locks. Or you could connect a monitor and keyboard to the server and take a photo of the screen after it becomes unresponsive. Link to comment
kavo Posted January 17, 2015 Author Share Posted January 17, 2015 here is the tail of the log Link to comment
Frank1940 Posted January 17, 2015 Share Posted January 17, 2015 I am not a true expert on Linux but from what I see, you have had a system crash. Since there have not been a lot of posts regarding this type of occurrence, I am assuming that you have an issue with your hardware. Two things to look at: (1) Open the case and make sure that all of the fans are spinning. Be sure you check to see that PSU fan is running! Clean out the dust and dirt from any heat sink cooling fins and the inside of the case. (You probably will want to do this outside of any living area!) (2) Run a memory test. As unRAID is booting, you will see an option to run a memory checking program. Let it run overnight. Link to comment
kavo Posted January 17, 2015 Author Share Posted January 17, 2015 (1) Open the case and make sure that all of the fans are spinning. Be sure you check to see that PSU fan is running! Clean out the dust and dirt from any heat sink cooling fins and the inside of the case. (You probably will want to do this outside of any living area!) (2) Run a memory test. As unRAID is booting, you will see an option to run a memory checking program. Let it run overnight. (1) found one fan not spinning and one with a few broken fins and and the filters all covered with dust. I've replaced the not spinning fan and will replace the other one when i can get a part. cleaned the PSU. (2) Will do a memtest once I have the other fan Link to comment
Frank1940 Posted January 17, 2015 Share Posted January 17, 2015 (1) Open the case and make sure that all of the fans are spinning. Be sure you check to see that PSU fan is running! Clean out the dust and dirt from any heat sink cooling fins and the inside of the case. (You probably will want to do this outside of any living area!) (2) Run a memory test. As unRAID is booting, you will see an option to run a memory checking program. Let it run overnight. (1) found one fan not spinning and one with a few broken fins and and the filters all covered with dust. I've replaced the not spinning fan and will replace the other one when i can get a part. cleaned the PSU. (2) Will do a memtest once I have the other fan Of one of the fans was the CPU fan, you most likely have found your problem. Be sure you clean those fins on the CPU heat sink. Most CPU's will crash if they overheat! However if the air flow through the case was restricted enough, almost any component could have problems due to overheating. (Parity are the worst case condition with unRAID for producing heat.) Link to comment
kavo Posted January 18, 2015 Author Share Posted January 18, 2015 (1) Open the case and make sure that all of the fans are spinning. Be sure you check to see that PSU fan is running! Clean out the dust and dirt from any heat sink cooling fins and the inside of the case. (You probably will want to do this outside of any living area!) (2) Run a memory test. As unRAID is booting, you will see an option to run a memory checking program. Let it run overnight. (1) found one fan not spinning and one with a few broken fins and and the filters all covered with dust. I've replaced the not spinning fan and will replace the other one when i can get a part. cleaned the PSU. (2) Will do a memtest once I have the other fan Of one of the fans was the CPU fan, you most likely have found your problem. Be sure you clean those fins on the CPU heat sink. Most CPU's will crash if they overheat! However if the air flow through the case was restricted enough, almost any component could have problems due to overheating. (Parity are the worst case condition with unRAID for producing heat.) The fan that wasn't spinning was a case fan directly above the cpu. The cpu fan is spinning however it is a small crappy one. This case is quite cramped so if the case fan wasn't spinning it wouldn't matter if the CPU one was as there was no airflow in the case. hopefully this is the problem, but I'll run the memtest and see what it says as well. Link to comment
kavo Posted January 23, 2015 Author Share Posted January 23, 2015 Would a disk read error cause the crash? Jan 23 22:11:42 Box kernel: md: disk2 read error, sector=465597408 Jan 23 22:11:42 Box kernel: md: disk2 read error, sector=465597416 Link to comment
trurl Posted January 23, 2015 Share Posted January 23, 2015 Would a disk read error cause the crash? Jan 23 22:11:42 Box kernel: md: disk2 read error, sector=465597408 Jan 23 22:11:42 Box kernel: md: disk2 read error, sector=465597416 Not likely, but it might be reason for concern anyway. Post a smart report of that drive. Also, did you ever do a memtest? Link to comment
kavo Posted January 23, 2015 Author Share Posted January 23, 2015 Not likely, but it might be reason for concern anyway. Post a smart report of that drive. Also, did you ever do a memtest? No memtest yet as fans havent arrived yet. I didn't want the box running but my sister was watching tv shows off it while I was away working (I work Fly In Fly Out) so I wont be able to do a mem test until next weekend smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.17.4-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green (AF, SATA 6Gb/s) Device Model: WDC WD20EARX-00PASB0 Serial Number: WD-WCAZAC263964 LU WWN Device Id: 5 0014ee 25bbb2b61 Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Sat Jan 24 06:32:03 2015 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 113) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (40200) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 387) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. 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 0x002f 198 198 051 Pre-fail Always - 142816 3 Spin_Up_Time 0x0027 162 160 021 Pre-fail Always - 6900 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1860 5 Reallocated_Sector_Ct 0x0033 144 144 140 Pre-fail Always - 1076 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 070 070 000 Old_age Always - 22329 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 584 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 478 193 Load_Cycle_Count 0x0032 060 060 000 Old_age Always - 420339 194 Temperature_Celsius 0x0022 118 092 000 Old_age Always - 32 196 Reallocated_Event_Count 0x0032 099 099 000 Old_age Always - 101 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 15 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 12 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 2 200 Multi_Zone_Error_Rate 0x0008 188 188 000 Old_age Offline - 3340 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: read failure 10% 22329 447328808 # 2 Short offline Completed without error 00% 2823 - 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. Link to comment
JonathanM Posted January 23, 2015 Share Posted January 23, 2015 That smart report looks pretty bad. If I were you, I'd plan to replace it ASAP. Be sure to pull smart reports on the rest of your drives to make sure you don't have multiple drives on the way out. Link to comment
Frank1940 Posted January 23, 2015 Share Posted January 23, 2015 I concur! I would go so far as to say that you should shut that server off until you get the fans and a new disk to replace that one. Right now, that disk will have to rebuilt from the parity information and the data on all the remaining disks in the array. IF you have a problem with another disk, you will lose all the information on this disk! At this point, you should get the new fans installed and the dust and dirt cleaned out of the case. While you are waiting on a new hard drive, run the memtst (located on the boot menu) for at least 24 hours. This is long enough to verify that you don't have a memory issue and to make sure that the rest of your computer's hardware (MB and CPU) is OK. Then, after the new disk gets there, do a preclear on the new disk before you attempt to rebuilt it. Link to comment
kavo Posted February 27, 2015 Author Share Posted February 27, 2015 So I've had a chance to replace the fans and the hard drive. The hard drive has now been rebuilt. It has since come up with this see attached Link to comment
loady Posted February 28, 2015 Share Posted February 28, 2015 Almost the same issue which has been plaguing me for nearly 2 months now . That screen shot you posted is almost identical to mine after crash, the variables possibly different..seems to happen more often that not during a parity check, I am currently adding another drive and moving my data whilst converting the drives to xfs one by one... not Co disentangle that this is the problem as the crashes are so very severe in that I can't access anything and even a console session becomes unresponsive not allowing me to make a sys.log dump... would be good if there was a way for unraid to be told to make incremental log dumps at regular intervals so at least I would stand a chance of getting one at the crucial point. If this xfs conversion doesn't resolve the problem then I have to lean toward hardware... not looking forward to that.. my cpu fan is a corsair sealed water cooled unit.... not really possible to easily tell if the pump is working properly....I'll be watching your thread for further info...good luck and I hope your problems get resolved. Link to comment
HellDiverUK Posted February 28, 2015 Share Posted February 28, 2015 On Intel, overheating CPU isn't really an issue, the CPU just throttles down until it cools enough, and if that doesn't work it'll pause. They don't really crash and burn like AMD. Link to comment
kavo Posted February 28, 2015 Author Share Posted February 28, 2015 Here is what I got when I woke up this morning Link to comment
Squid Posted February 28, 2015 Share Posted February 28, 2015 ... even a console session becomes unresponsive not allowing me to make a sys.log dump... would be good if there was a way for unraid to be told to make incremental log dumps at regular intervals... Enter this at the console and let it run tail -f /var/log/syslog >/boot/syslogtail.txt Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.