July 23, 201312 yr As per the WIKI, I am here to seek advice MD1 = 1 corruptions can be fixed only when running with --rebuild-tree. 1 - what is the next step? 2 - a couple years back this same drive required a - reiserfsck --fix-fixable /dev/md1 3 - MANY parity runs with corrections have been run Additional info: Despite a UPS, after a mid-parity check power out, my production servers parity has not normalized. http://lime-technology.com/forum/index.php?topic=28598.0 Steps Taken: 1 - Multiple Parity correction runs in different hardware configurations (all SMART and SYSLOGS look clean and good) 2 - Update from 4.6 to latest 5rc and redo 1 above 3 - Overnight memtest with no errors 4 - reiserfsck on 4 data disks MD2, MD3, and MD4: No Corruptions Found MD1 = 1 corruptions can be fixed only when running with --rebuild-tree.
July 23, 201312 yr It looks like a RAM issue. Have you run memtest overnight? How many RAM modules in the system? It could be a disk. The drive can be isolated with repeated use of the New Config Utility.
July 23, 201312 yr Author 1 ram module - I ran memtest from 3pm to 9am with zero issues Do you happen to have a link to 'new config utility' ?
July 23, 201312 yr Under the Utils tab on the unRAID webGUI. Repeatedly set a new config using a subset of the disks. Each iteration will require that parity is built and then checked. It should take at most 3 trials to isolate a bad data disk. If it's the parity drive it may take an additional iteration.
July 23, 201312 yr Author Goggling 'unraid New Config Utility' returns very different results than 'unraid New Config' - I promise I was not being purposefully daft on this point. Just to confirm my understanding - this will kill the parity drive then rebuild the parity information when I start the array to the parity drive (with hopefully no data loss). Repeat these steps 3 or 4 times. What should I look for at the conclusion of each run? http://lime-technology.com/wiki/index.php/FAQ ******** OR do you mean that I should say forget about saving the data and: run1 = parity + md2 + md3 +md4 ...if an issue, likely the parity drive problem ...if not an issue run 2: run2 = md1 (as parity) + md2 + md3 +md4 ...if an issue, likely the md1 drive problem what would runs 3 and 4 be? ******** OR something else entirely? Thanks again!
July 23, 201312 yr Parity is already corrupt. The data on 3 data disks is good. One of the data disks may be corrupt. Or the parity disk may be bad. Once the bad disk is determined if it's a data disk the contents of the drive will have to be copied to a new disk. A windows recovery tool may help. Always assign the parity drive as parity or you will lose data. Set a New Config (see image attached) Assign parity, disk1 and disk2. Start the array and build parity. Check parity. If there a are zero errors then the issue is with disk 3 or 4. Set a New Config. This run will have parity and either disk1 or disk3 assigned depending on the previous result. If all trials result in errors then try with a new parity disk
July 24, 201312 yr Author First Run Results: Assign parity, disk1 and disk2 STARTED, 3 disks in array. Parity is Valid:. Last parity check 15911 days ago with no sync errors. HOWEVER - Disk 1 has gone from over 90% full to 1% ..... Onto the 2nd test Stopped array new config assigned Parity + disk 3 (as 1) + disk 4 (as 2) Start
July 25, 201312 yr First Run Results:Parity is Valid:. Last parity check 15911 days ago with no sync errors. Onto the 2nd test Were you able to successfully complete a parity check with no errors? I seem to remember the root symptom you were trying to track down was the different parity errors every time a check was run. If you didn't run a pair of back to back parity checks with zero errors, I don't think your first test was a valid indicator of a healthy system.
July 25, 201312 yr Yes. A parity check is required to complete the test. It should say, "Last parity check 0 days ago..."
July 25, 201312 yr Author oh dang, despite your clear instructions dgaschk, in my excitement i moved onto test 2 pre-parity check. I am checking the parity on disk 3+4 now. These disk's used % did NOT change post New Config Array start ---Thanks again Crew
July 25, 201312 yr Author Stop Array Utilities/New Config Assign, start, parity Check Parity + Disk 3 + Disk 4 = ZERO errors post Parity Check (So Parity, 3, and 4 are all likely good) Stop Array Utilities/New Config Assign, start, parity Check Parity + Disk 1 + Disk 2 = ~1,800 errors and growing during Parity Check - at this point I stopped the parity check Stop Array Utilities/New Config Assign, start, parity Check Parity + Disk1 => Now Rebuilding Parity - Sync. Will run a parity check tomorrow am. Again - you have my many thanks!
July 26, 201312 yr Author Just an update Test Parity Check Results 1 (P) + 3 + 4...Good 2 (P) + 1 + 2...Errors 3 (P) + 1.......Errors 4 (P) + 3.......Good 5 (2TB)+1.......In Progress (expecting Errors) If my expectations are met, Disk 1 will be trashed. It's location on the motherboard will be delegated to preclear tasks ONLY.
July 29, 201312 yr Author Test Parity Check Results 1 (P) + 3 + 4...Good 2 (P) + 1 + 2...Errors 3 (P) + 1.......Errors 4 (P) + 3.......Good 5 (2TB)+1.......Errors Found. Disk 1 (or its location on the Motherboard, or its cable, or its location in the ICYDOCK is BAD). Rather than instantly delegating the spot as bad - time for 1 more test where I place the parity drive into the DISK 1 bay. 4 (P) + 3.......Good - I hope Thanks for all the help everyone!
Archived
This topic is now archived and is closed to further replies.