February 9, 201313 yr Unraid 4.7 Most connected via AOC-SASLP-MV8 to the backplanes on a Norco RPC-4224 Mainly WD green 2TB drives. So about a week ago there was a big storm and the power got knocked out, unfortunately I was away so I wasn't able to safely power down my Unraid beforehand. When we finally got power back my syslog was full of errors Jan 29 18:57:07 Loveserver kernel: md: disk6 write error Jan 29 18:57:07 Loveserver kernel: handle_stripe write error: 1353712/6, count: 1 I figured there was an issue with the disk, so I stopped the array before it caused any more problems, precleared some spare drives and then replaced the drive that was giving me problems and set it to rebuild the array. Unfortunately when I came back to check it later it said that my disk4 had ~4,000,000 parity errors and they had all been fixed. I safely powered down and then came back a few days later to have a better look. Powered on and I was getting these errors Feb 7 18:47:20 Loveserver kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 47197 does not match to the expected one 2 Feb 7 18:47:20 Loveserver kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 148815358. Fsck? Feb 7 18:47:20 Loveserver kernel: REISERFS error (device md4): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [25 2768 0x0 SD] Using the unmenu file browser on disk4 it looked as though the first word from every folder had managed to replace the date modified section. So browsing the forums it told me that the errors message required me to run "reiserfsck --check /dev/md4" which I did, and that informed that I needed to "run reiserfsck --rebuild-tree /dev/md4" which I did. However this didn't solve the problem, I've got a huge lost+found folder with basically nonsense files in it. On top of that, I'm now getting the same error message, but on disk6, the one I originally had a problem with. Feb 8 09:09:39 Loveserver kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 2 Feb 8 09:09:39 Loveserver kernel: REISERFS error (device md6): vs-5150 search_by_key: invalid format found in block 156130897. Fsck? Feb 8 09:09:39 Loveserver kernel: REISERFS error (device md6): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [513 2888 0x0 SD] Now these drives are both on the same backplane, and therefore the same disk controller and SAS cable. Do these issues point to a hardware problem, or is it just a coincidence? What's my next step from here? Do I run the reiserfsck on disk6 or do I cut my losses, format both drives and go about reacquiring all the data that I lost? Luckily there's nothing important on there, but getting back ~3.5TB worth of stuff is going to take a while. I've attached my last 3 logs. logs.zip
Archived
This topic is now archived and is closed to further replies.