September 1, 20187 yr Hi! I'm on unraid 6.5.3 and the system is/was usually stable. A week ago, I upgraded from 5.0-rc8a without any problems. But when I'm trying to preclear a drive or checking parity the system stops responding. I can't reach the webgui nor telnet into the server. The checking-Parity related issue was also present while using 5.0-rc8a. I thought it has something to do with my RFS-formatted drives becoming full (>90%), because if I redistributed my data throughout the drives parity check worked. I checked the Smart-Reports of all drives, nothing wrong. Right now I've disabled the parity drive and added a 8tb drive (xfs). I created a new share exclusive for this drive and copy the data of my other drives onto it (3tb+2tb+2tb). Any ideas what I should do instead? server-syslog-20180901-0754.zip Edited September 10, 20187 yr by Evin
September 1, 20187 yr If you could please attach your full system diagnostics, that would be very helpful (Tools > Diagnostics). In addition, the logs you posted look like from a fresh boot, prior to any errors occurring. Due to the nature of the issue, it would be more helpful if you opened an SSH session into the system before running a parity check, and then once the UI hangs, type the word "diagnostics" and press enter. This will save the diagnostics to the flash even though you can't access the UI. Then shut down the server and put the flash in your PC and you can obtain the diagnostics file for upload here which should show some more information as to what's happening at the time of the hang.
September 1, 20187 yr I'd be interested to know how hard your processor is working during those activities when the system becomes unresponsive. With a passmark of 653 it's near the lower end of the scale but it still ought to be adequate. There may be some tweaks that can be done to makes things more responsive. Parity checks work at block level and are independent of file systems.
September 1, 20187 yr Author 59 minutes ago, John_M said: I'd be interested to know how hard your processor is working during those activities when the system becomes unresponsive. With a passmark of 653 it's near the lower end of the scale but it still ought to be adequate. CPU-Usage is around 30%. Everything worked this time. Maybe preclear will work too...
September 9, 20187 yr Author Unfortunately it's happening again. I can't provide a diagnostics report since the connection is lost due to Timeout Error. Any ideas where I might begin to search for a solution?
September 9, 20187 yr Author Started in maintenance mode and doing a parity check. Speed dropped to 600kb/sec and all drives spun down while performing the check... server-syslog-20180909-0909.zip server-diagnostics-20180909-0912.zip
September 9, 20187 yr Author Was checking the smart logs, one drive seems failing: SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 197 195 051 - 6498 3 Spin_Up_Time POS--K 243 167 021 - 2833 4 Start_Stop_Count -O--CK 099 099 000 - 1940 5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0 7 Seek_Error_Rate -OSR-K 200 200 000 - 0 9 Power_On_Hours -O--CK 069 069 000 - 23140 10 Spin_Retry_Count -O--CK 100 100 000 - 0 11 Calibration_Retry_Count -O--CK 100 100 000 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 818 192 Power-Off_Retract_Count -O--CK 200 200 000 - 58 193 Load_Cycle_Count -O--CK 194 194 000 - 20787 194 Temperature_Celsius -O---K 111 094 000 - 39 196 Reallocated_Event_Count -O--CK 200 200 000 - 0 197 Current_Pending_Sector -O--CK 200 200 000 - 0 198 Offline_Uncorrectable ----CK 200 200 000 - 0 199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 1 200 Multi_Zone_Error_Rate ---R-- 193 173 000 - 1994 Could this be the source of all my troubles?
September 9, 20187 yr Community Expert Can't say it's the source of all your problems, but that disk does look very bad, at best it will be very slow, I would replace it.
September 9, 20187 yr Author So what are my options? Remove the drive, adding my new 8tb drive and let rebuild it? But afaik are there some parity-errors.
September 9, 20187 yr Author Have done a filesystemcheck: reiserfsck 3.6.27 Will read-only check consistency of the filesystem on /dev/md3 Will put log info to 'stdout' ########### reiserfsck --check started at Sun Sep 9 10:04:12 2018 ########### Replaying journal: Replaying journal: Done. Reiserfs journal '/dev/md3' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 414547 Internal nodes 2500 Directories 1321 Other files 6773 Data block pointers 418672868 (0 of them are zero) Safe links 0 ########### reiserfsck finished at Sun Sep 9 10:27:28 2018 ###########reiserfsck 3.6.27 Edited September 9, 20187 yr by Evin
September 9, 20187 yr Community Expert Replace it but keep the old disk intact, if rebuild is successful that was probably the problem, if you have doubts if parity was 100% valid, and after the rebuild is done, copy every file you can from the old disk replacing those on the rebuilt disk, all successfully copied files can be assumed OK.
September 9, 20187 yr It is also recommended to convert ReiserFS to XFS. The former is no longer maintained and only present for backward compatibility.
September 10, 20187 yr Author OH COME ON! Everything seemed fine. Total size: 8 TB Elapsed time: 1 day, 8 hours, 11 minutes Current position: 7.99 TB (99.8 %) Estimated speed: 79.7 MB/sec Estimated finish: 3 minutes And suddenly the system doesn't respond. No GUI, no Putty. I had an open connection through Putty the whole time.
September 11, 20187 yr Author Hi, it's me again. Ran a memtest, first pass completed without any errors. I will let it continue overnight and run a few passes. But it seems as another possible problem got eliminated. At this point I would happily accept a faulty RAM.
Archived
This topic is now archived and is closed to further replies.