April 21, 201214 yr I got a replacement key and as soon as I finished configuring, parity check complete this error is contimuous in the syslog. How does one make this stop and fix the problem? Apr 21 09:13:57 Tower kernel: REISERFS error (device md7): vs-5150 search_by_key: invalid format found in block 25020364. Fsck? Apr 21 09:13:57 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 759 does not match to the expected one 3 Apr 21 09:13:57 Tower kernel: REISERFS error (device md7): vs-5150 search_by_key: invalid format found in block 25020364. Fsck? Apr 21 09:13:57 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 759 does not match to the expected one 3 Apr 21 09:13:57 Tower kernel: REISERFS error (device md7): vs-5150 search_by_key: invalid format found in block 25020364. Fsck?
April 22, 201214 yr Author I did this and the utility suggested to rebuild-sb after rebuild-tree. What settings do I use? Version 3.6 and block size. Are there any additional options to select? If this doesn't fix the drive is there anything additional I should try?
April 22, 201214 yr Use the settings given in the link for the Check file systems page: http://lime-technology.com/forum/index.php?topic=1483.0
April 23, 201214 yr Author I'm stuck with this reply from the utility. The problem has occurred looks like a hardware problem. If you have bad blocks, we advise you to get a new hard drive, because once you get one bad block that the disk drive internals cannot hide from your sight,the chances of getting more are generally said to become much higher (precise statistics are unknown to us), and this disk drive is probably not expensive enough for you to you to risk your time and data on it. If you don't want to follow that follow that advice then if you have just a few bad blocks, try writing to the bad blocks and see if the drive remaps the bad blocks (that means it takes a block it has in reserve and allocates it for use for of that block number). If it cannot remap the block, use badblock option (-B) with reiserfs utils to handle this block correctly. bread: Cannot read the block (2): (Input/output error). RMA Time?
April 23, 201214 yr I'm stuck with this reply from the utility. The problem has occurred looks like a hardware problem. If you have bad blocks, we advise you to get a new hard drive, because once you get one bad block that the disk drive internals cannot hide from your sight,the chances of getting more are generally said to become much higher (precise statistics are unknown to us), and this disk drive is probably not expensive enough for you to you to risk your time and data on it. If you don't want to follow that follow that advice then if you have just a few bad blocks, try writing to the bad blocks and see if the drive remaps the bad blocks (that means it takes a block it has in reserve and allocates it for use for of that block number). If it cannot remap the block, use badblock option (-B) with reiserfs utils to handle this block correctly. bread: Cannot read the block (2): (Input/output error). RMA Time? Possibly, but the inability to read block 2 could just as easily be because either the power or data cable is loose. Have you powered down and re-seated them? Joe L.
Archived
This topic is now archived and is closed to further replies.