Trying to rebuild parity after upgrading my parity disk (from a 3tb to a 4tb).  The array keeps locking up.. what I mean by locking up is that its totally unresponsive, and doesnt appear on my network (so I cant putty into it).  I would wake up and give it another shot (2 times) I wouldnt notice anything strange in the syslogs, but today I started noticing these errors.  Ive ensured I have good airflow and temps have been 35-41

 

Jul 21 12:12:57 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 31407 does not match to the expected one 1 (Minor Issues)

Jul 21 12:12:57 Tower kernel: REISERFS error (device md3): vs-5150 search_by_key: invalid format found in block 629753083. Fsck? (Errors)

Jul 21 12:12:57 Tower kernel: REISERFS error (device md3): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [87419 87263 0x0 SD] (Errors)

Jul 21 12:12:58 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 31407 does not match to the expected one 1 (Minor Issues)

Jul 21 12:12:58 Tower kernel: REISERFS error (device md3): vs-5150 search_by_key: invalid format found in block 629753083. Fsck? (Errors)

Jul 21 12:12:58 Tower kernel: REISERFS error (device md3): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [87419 87263 0x0 SD] (Errors)

Jul 21 12:12:58 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 31407 does not match to the expected one 1 (Minor Issues)

Jul 21 12:12:58 Tower kernel: REISERFS error (device md3): vs-5150 search_by_key: invalid format found in block 629753083. Fsck? (Errors)

Jul 21 12:12:58 Tower kernel: REISERFS error (device md3): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [87419 87263 0x0 SD] (Errors)

Jul 21 12:12:58 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 31407 does not match to the expected one 1 (Minor Issues)

Jul 21 12:12:58 Tower kernel: REISERFS error (device md3): vs-5150 search_by_key: invalid format found in block 629753083. Fsck? (Errors)

Jul 21 12:12:58 Tower kernel: REISERFS error (device md3): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [87419

 

Im wondering now if im having a hardware problem that is keeping my parity from re-building.

 

I ran a parity check before I removed my working parity drive (3tb) and very little, if nothing, has been written to the array since.

 

heres the steps I used

ran parity check

shutdown array

removed power from old parity (3tb)

hooked up new precleared parity drive (4tb)

turned on and started parity sync.

Its locked up 2 times since..

 

running unraid 5 rc3  (6 drives+cache drive)

on AMD A6-3500with a gigabyte a75 board, 4 gigs of ram

the only plugin Im running is unMenu

 

attached is latest syslog (I had to crop the first part to get under the filesize limit)

 

any advice is appreciated

 

syslog_part_two.txt

See Check Disk Filesystems in my sig. This should not effect parity build unless the disk is being accessed during the rebuild. It needs to fixed in any case.

Parity sync is 120 mins away from completion, so Im going to wait it out and see if it completes this time.  But ill need to do as explained on Check Disk Filesystems to my drive 3?

 

Thanks!

Yes.

Is it locking up ... or is emhttp simply not responding?    Are all of the disk activity lights still active?  If so, it may very well be working fine, but the Web GUI (emhttp) has simply stopped responding.

 

I've seen this a few times during parity syncs or checks.  Sometimes just closing the browser and reloading it will get a response;  sometimes rebooting the PC you're using will work (or using a different PC); and sometimes emhttp has actually stopped working.    But the parity sync/check MAY still be working just fine -- and if that's the case the system will likely respond when it's finished.    If your disk activity lights are still active, I'd just wait it out (recognizing for for a 4TB drive that could be a LONG time 

Parity sync finally finished.. Now off to fix my drive 3 (I hope). 

Thanks guys!