July 28, 20169 yr All I did was add another drive and now my parity drive has an X next to it. I'm even willing to re-do a parity check but when I scroll all the way down there is no option to even perform a parity drive. I have checked the slot with another drive, works good, and I can't tell the future but I would imagine this parity drive is good. Has low hours, high end consumer model. How can I perform a parity check on a drive that can't be found?
July 28, 20169 yr Community Expert Post diagnostics. What do I do if I get a red X next to a hard disk?
July 28, 20169 yr Author Post diagnostics. What do I do if I get a red X next to a hard disk? Sorry for not posting the diags. Been here a while and should know the rules. Anyway, I'm %100000 sure my parity drive wasn't written to since I started. I basically had the problem finding that command, "NEW CONFIG" option. Soon as I hit that and started my array my shares came up and I started a parity check just to be %100000000000 sure. Thank you.
July 28, 20169 yr If you hit new config its not a parity check that is started.. its a parity sync.. actually creating the parity information..
July 28, 20169 yr Author If you hit new config its not a parity check that is started.. its a parity sync.. actually creating the parity information.. I ended up performing a "Trust my Array". Reassigned all my drives to the correct slot according to all my information I save and print out and then selected NEW CONFIG. Brought the array online all green...so I started a new parity check to be on the safe side.
July 28, 20169 yr In case of a read error during the parity check, unRaid would have attempted to re-write the sector. Diagnostics would be really helpful, but to recreate the drive, you've got to stop the array, set parity to be not installed, start, stop, set it back to the drive and then start.
July 28, 20169 yr If you hit new config its not a parity check that is started.. its a parity sync.. actually creating the parity information.. I ended up performing a "Trust my Array". Reassigned all my drives to the correct slot according to all my information I save and print out and then selected NEW CONFIG. Brought the array online all green...so I started a new parity check to be on the safe side. If you ADDED a drive, then parity would NOT be correct, so the "Parity is already valid" box should NOT have been checked (i.e. the "Trust my Array" procedure). => unless, of course, the new drive was pre-cleared. In any event, as long as you're doing a correcting parity check, when it's done parity will be valid then -- you may just have a LOT of "corrections" if the new drive wasn't all zeroes.
July 28, 20169 yr Author If you hit new config its not a parity check that is started.. its a parity sync.. actually creating the parity information.. I ended up performing a "Trust my Array". Reassigned all my drives to the correct slot according to all my information I save and print out and then selected NEW CONFIG. Brought the array online all green...so I started a new parity check to be on the safe side. If you ADDED a drive, then parity would NOT be correct, so the "Parity is already valid" box should NOT have been checked (i.e. the "Trust my Array" procedure). => unless, of course, the new drive was pre-cleared. In any event, as long as you're doing a correcting parity check, when it's done parity will be valid then -- you may just have a LOT of "corrections" if the new drive wasn't all zeroes. I'm having trouble and need some help. I kicked off a parity check about 2PM EST and it is now 7PM EST and it's only at 30% complete. I think I may need an expert to check my diags. I looked them over myself but kept seeing that, "Did not receive identification string from 192.168.1.104". Whatever that is. I always keep a printout if I ever make a change to the array like add a drive or move one, etc. Everything is where it is supposed to be. If the forum level can't throw some solution out, maybe I'll try the LT remote help system. I've been a long time user of unraid, but when messing around with 30GB+ of content I'm taking this one carefully. Thanks, Michael sun-diagnostics-20160728-1920.zip
July 29, 20169 yr Is this a correcting check? ... and how many errors does it show? [As I noted above, it's likely it will show a lot; and every error will slow down the check a bit as it "corrects" it.] Perhaps post a screen shot of the Web GUI in its current state.
July 29, 20169 yr Author Is this a correcting check? ... and how many errors does it show? [As I noted above, it's likely it will show a lot; and every error will slow down the check a bit as it "corrects" it.] Perhaps post a screen shot of the Web GUI in its current state. This is all started with a red X standing next to my parity drive. So I tried doing a parity and it stuck at %44 and only 1 drive was lighting up. Kind of had no choice but to restart clean and re-start. Probably not the best thing in the world to do, but after having a few beers ( on vacation ) things just happened. So I started the parity check again and it seems to be doing good, but I haven't reached %44 yet. Snapshot here.
July 29, 20169 yr Community Expert Well, presumably it had already corrected everything up to that point before, so no sync errors yet since the restart. After it gets past that point if it starts finding errors to correct then it will slow down again.
July 29, 20169 yr As trurl noted, the 0 errors at this point doesn't say anything about what it might have already corrected. But in any event, it's looking fine; so I'd just let it run to completion. If any errors are corrected in the process, it'd be a good idea to repeat the check to confirm everything's now okay.
July 29, 20169 yr Author As trurl noted, the 0 errors at this point doesn't say anything about what it might have already corrected. But in any event, it's looking fine; so I'd just let it run to completion. If any errors are corrected in the process, it'd be a good idea to repeat the check to confirm everything's now okay. A sigh of NO relief this morning. Parity finished, with lots of errors. Last checked on Fri 29 Jul 2016 05:44:02 AM EDT (today), finding 886688 errors. Duration: 13 hours, 29 minutes, 54 seconds. Average speed: 82.3 MB/s The following is just a snip of the end of my syslog, BEFORE rebooting anything. I've ran my box for years with no issues, wonder what my bad luck is. Jul 29 00:24:57 SUN kernel: md: correcting parity, sector=5860528560 Jul 29 00:24:57 SUN kernel: md: correcting parity, sector=5860528568 Jul 29 00:24:57 SUN kernel: md: correcting parity, sector=5860528576 Jul 29 00:24:57 SUN kernel: md: correcting parity, sector=5860528584 Jul 29 00:24:57 SUN kernel: md: correcting parity, sector=5860528592 Jul 29 00:24:57 SUN kernel: md: correcting parity, sector=5860528600 Jul 29 00:24:57 SUN kernel: md: correcting parity, sector=5860528608 Jul 29 00:24:57 SUN kernel: md: correcting parity, sector=5860528616 Jul 29 00:24:57 SUN kernel: md: correcting parity, sector=5860528624 Jul 29 00:24:57 SUN kernel: md: correcting parity, sector=5860528632 Jul 29 00:24:57 SUN kernel: md: correcting parity, sector=5860528640 Jul 29 00:24:57 SUN kernel: md: correcting parity, sector=5860528648 Jul 29 00:24:57 SUN kernel: md: correcting parity, sector=5860528656 Jul 29 00:24:57 SUN kernel: md: correcting parity, sector=5860528664 Jul 29 00:24:57 SUN kernel: md: correcting parity, stopped logging Jul 29 00:27:54 SUN sshd[28109]: Did not receive identification string from 192.168.1.104 Jul 29 00:43:01 SUN sshd[30092]: Did not receive identification string from 192.168.1.104 Jul 29 00:58:10 SUN sshd[32090]: Did not receive identification string from 192.168.1.104 Jul 29 01:13:17 SUN sshd[1681]: Did not receive identification string from 192.168.1.104 Jul 29 01:28:25 SUN sshd[3689]: Did not receive identification string from 192.168.1.104 Jul 29 01:43:33 SUN sshd[5667]: Did not receive identification string from 192.168.1.104 Jul 29 01:58:41 SUN sshd[7662]: Did not receive identification string from 192.168.1.104 Jul 29 02:13:52 SUN sshd[9651]: Did not receive identification string from 192.168.1.104 Jul 29 02:29:11 SUN sshd[11682]: Did not receive identification string from 192.168.1.104 Jul 29 02:44:26 SUN sshd[13673]: Did not receive identification string from 192.168.1.104 Jul 29 02:59:41 SUN sshd[15684]: Did not receive identification string from 192.168.1.104 Jul 29 03:14:56 SUN sshd[17679]: Did not receive identification string from 192.168.1.104 Jul 29 03:30:11 SUN sshd[19697]: Did not receive identification string from 192.168.1.104 Jul 29 03:45:26 SUN sshd[21690]: Did not receive identification string from 192.168.1.104 Jul 29 04:00:41 SUN sshd[23701]: Did not receive identification string from 192.168.1.104 Jul 29 04:15:56 SUN sshd[25795]: Did not receive identification string from 192.168.1.104 Jul 29 04:31:10 SUN sshd[27847]: Did not receive identification string from 192.168.1.104 Jul 29 04:40:01 SUN logger: Community Applications Auto Update Running Jul 29 04:46:25 SUN sshd[29929]: Did not receive identification string from 192.168.1.104 Jul 29 05:01:40 SUN sshd[31923]: Did not receive identification string from 192.168.1.104 Jul 29 05:16:55 SUN sshd[1544]: Did not receive identification string from 192.168.1.104 Jul 29 05:32:10 SUN sshd[3566]: Did not receive identification string from 192.168.1.104 Jul 29 05:44:02 SUN kernel: md: sync done. time=48594sec Jul 29 05:44:02 SUN kernel: md: recovery thread sync completion status: 0 Jul 29 05:47:25 SUN sshd[5576]: Did not receive identification string from 192.168.1.104 Jul 29 06:02:40 SUN sshd[7568]: Did not receive identification string from 192.168.1.104 Jul 29 06:17:55 SUN sshd[9578]: Did not receive identification string from 192.168.1.104 Jul 29 06:33:10 SUN sshd[11585]: Did not receive identification string from 192.168.1.104 Jul 29 06:48:25 SUN sshd[13594]: Did not receive identification string from 192.168.1.104 Jul 29 07:03:40 SUN sshd[15587]: Did not receive identification string from 192.168.1.104 Jul 29 07:18:55 SUN sshd[17596]: Did not receive identification string from 192.168.1.104 Jul 29 07:34:10 SUN sshd[19596]: Did not receive identification string from 192.168.1.104 Jul 29 07:49:25 SUN sshd[21607]: Did not receive identification string from 192.168.1.104 Jul 29 08:04:40 SUN sshd[23597]: Did not receive identification string from 192.168.1.104 Jul 29 08:19:54 SUN sshd[25658]: Did not receive identification string from 192.168.1.104 Jul 29 08:35:09 SUN sshd[27743]: Did not receive identification string from 192.168.1.104 Jul 29 08:50:24 SUN sshd[29751]: Did not receive identification string from 192.168.1.104 Jul 29 09:05:39 SUN sshd[31744]: Did not receive identification string from 192.168.1.104 Jul 29 09:20:54 SUN sshd[1358]: Did not receive identification string from 192.168.1.104 Jul 29 09:36:09 SUN sshd[3384]: Did not receive identification string from 192.168.1.104 Jul 29 09:51:24 SUN sshd[5394]: Did not receive identification string from 192.168.1.104 Jul 29 10:06:39 SUN sshd[7386]: Did not receive identification string from 192.168.1.104 Jul 29 10:21:54 SUN sshd[9396]: Did not receive identification string from 192.168.1.104 Jul 29 10:34:08 SUN emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Jul 29 10:37:11 SUN sshd[12147]: Did not receive identification string from 192.168.1.104 192.168.1.104 is the computer I use in my living room. I wonder if there's something on here trying to get into my unraid box? Maybe I'll change the IP to see. sun-diagnostics-20160729-1034.zip
July 29, 20169 yr As I noted earlier, you said that you (a) added a drive; and (b) checked the "parity is already valid" box -- which is NOT correct since you added a drive. So effectively the parity "check" simply did the equivalent of a parity sync, except slower, since was checking first, then "correcting". Do another parity check -- all should be fine now.
July 29, 20169 yr Author As I noted earlier, you said that you (a) added a drive; and (b) checked the "parity is already valid" box -- which is NOT correct since you added a drive. So effectively the parity "check" simply did the equivalent of a parity sync, except slower, since was checking first, then "correcting". Do another parity check -- all should be fine now. Thanks. I was just going to kick one off to make sure I'm all trued up. Speaking of parity checks, my electric just went out and it started a parity check on it's own. I do have a small UPS on it the server and should have gotten 15 minutes out of it and the outage was more like a flicker because it's so damn hot. I have have to Check that Cyber1500 model if it's good enough. I'm done with APC.
Archived
This topic is now archived and is closed to further replies.