From: HL <ste...@fr...> - 2009-09-16 14:12:47
|
Hi there Bruce or Douglas, i really need help to save my data. My problem is that i had simple sata timeout problems which led to my serious problem of having millions of badblocks on my harddisk. I used the samsung tool hutil to make a (as said by the tool) non-destructive test on my harddisk. It checked the smart data - ok. Write test - ok <- i guess this is where the shit happened. Ok to make a long story shorter: I can't mount my reiserfs partition and reiserfsck stopped with an error message. ******************************* Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes 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 (147958639): (Input/output error). Abgebrochen ************************************* Currently i have badblocks running on this partition writing all badblocks to a file. Badblocks ended with a file of roblem. 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 (147958639): (Input/output error). Abgebrochen ************************************* Currently i have badblocks running on this partition writing all badblocks to a file. Badblocks ended with a file of 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 (147958639): (Input/output error). Abgebrochen ************************************* Currently i have badblocks running on this partition writing all badblocks to a file. Badblocks ended with a file of roblem. 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 (147958639): (Input/output error). Abgebrochen ************************************* Currently i have badblocks running on this partition writing all badblocks to a file. Badblocks ended with a file of 122727898 badblocks $ (cat badblocksfile | wc -l) What can i do now? I think the test of hutil destroyed the filesystem and the badblocks are 'just in software'. Is there hope? What can i do to save my data? I ask you because of your very good bad blocks howto. Sincerely, Heiko Liebfried |