November 16, 201510 yr My luck of late seems to stink, my server was running smoothly for the last 4 years. However these last 2 weeks everything seems to want to break. I had just copied about 100gb of data over to my cache and was watching something that hadn't been moved over to the array yet when i heard a beeping coming from my box, i shut it down to investiage. Upon restarting i noticed my cache is showing as unmountable and unraid is asking me to format it. Not sure if they drive is totally dead or what. i have attached a SMART extended self test result which is showing some read failures. anyway to salvage what is on the disk? VB0250EAVER_9VMXPV81-20151116-2247.txt
November 16, 201510 yr try a different SATA cable. Mine didn't beep when it went offline but diff cable brought it back. PS. makes no sense that its been fine on the bad cable for over a year but what do I know lol
November 16, 201510 yr Author just deactivated my parity and used the cable from that for my cache, disk is still unmountable
November 17, 201510 yr Disk has pending sectors so it should be replaced or at a minimum run through preclear a few times and check if pending sectors goes to 0, runing preclear will erase the disk. If you have data that you want to recover and need more help post the complete zip from tools > diagnostics, but usually an unmountable disk means problems with the file system, so depending on the file system in use see here.
November 17, 201510 yr Author Ok so i followed that link and worked through it, reiserfsck --fix-fixable was a no go and it is recommending a rebuild. the wiki page talks about the answers needing to be perfect so i guess i need help from someone with more experience, not sure what options need to be selected.
November 17, 201510 yr I’ll let someone with more reiserfsck experience help you but you may want to post here the output you get when running the command.
November 17, 201510 yr Ok so i followed that link and worked through it, reiserfsck --fix-fixable was a no go and it is recommending a rebuild. the wiki page talks about the answers needing to be perfect so i guess i need help from someone with more experience, not sure what options need to be selected. Can you please post the exact command you used when running the reiserfsck (and the result). A common mistake is to forget to specify the partition number as part of the device name and this leads to an error message about not being able to find the superblock. In such a case you must NOT try and recover the superblock as this will definitely lead to data loss.
November 17, 201510 yr Author your right, once i ran it with partition number reiserfsck --check /dev/sdf1 i got the following output 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 (1344): (Input/output error).
November 17, 201510 yr your right, once i ran it with partition number reiserfsck --check /dev/sdf1 i got the following output 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 (1344): (Input/output error). hmm - that suggests that the drive really could have a problem. It could also be caused by something like a loose cable, but I assume that you have checked for that?
November 17, 201510 yr Author well i tried swapping the drive location to use the cable from my parity drive but it is still Unmountable. haven't tried running a reiserfsck with it connected differently.
Archived
This topic is now archived and is closed to further replies.