Ok. Ready.

Joe L:

Your my only hope on Disk 8.  Hopefully, you can figure it out and help me through.  Things are working good, but; I know I lost a bunch of stuff if I don't get Disk 8 back up.

Roger

Joe L:

Your my only hope on Disk 8.  Hopefully, you can figure it out and help me through.  Things are working good, but; I know I lost a bunch of stuff if I don't get Disk 8 back up.

Roger

Well... I'm back home now.    I'll do a little bit of searching on badblocks using google.

Hanks

Any luck

Any luck

step 1.  Get a fresh smart report on what was disk8. 

step 2. let's get a  fresh list of the badblocks by running it once more on the disk.  This time, run it on /dev/sdX1  (with the "1" suffix)

 

attach them to the next post.  zip them if needed.

 

I just tried running badblocks on a disk I have here.  When I then tried the subsequent command for reiserfsck it stated:

Badblocks can be specified with --fix-fixable or --rebuild-tree only.

 

The correct sequence should therefore be:

badblocks -v -o /boot/badblocks_disk8 -b 4096 /dev/sdX1

(where sdX1 =  the four character device name of the disk8 reiserfs partition. )

 

Then

reiserfsck --fix-fixable --badblocks /boot/badblocks_disk8 /dev/sdX1

(again, /dev/sdX1 = the first partition, where the file-system resides)

 

followed by:

reiserfsck --rebuild-tree -S /dev/sdX1

 

 

Joe L:

Thanks for the new command stream. I will try tonight.  I see the commands are a bit different so maybe they will work.  I did see some discussion online that was very complicated addressing how to write over each individual badblock, but; way over my head.

 

Roger

Joe L,

Badblocks are identical as to the last check.  19 in total.  See attached

Also, when I run your 2nd command, I get the following message: Failed to open the given badblock file '/boot/badblocks_8'

badblocks_disk8.zip

Joe L,

Badblocks are identical as to the last check.  19 in total.  See attached

Also, when I run your 2nd command, I get the following message: Failed to open the given badblock file '/boot/badblocks_8'

probably because you named it /boot/badblocks_disk8 and not /boot/badblocks_8.

 

badblocks_8 probably does not exist, exactly as the command is telling you.

 

Joe L.

Joe L, well I guess I am still as lame as it comes.  O.K., re typed the command and now it's running.  Command just failed.  It says Bad root block 0.  (--rebuild-tree did not complete).

I suppose I'm missing something, we did try this before with the rebuild command and the badblocks and it failes like a typical rebuild -S

Joe L, well I guess I am still as lame as it comes.  O.K., re typed the command and now it's running.  Command just failed.  It says Bad root block 0.  (--rebuild-tree did not complete).

what SPECIFIC command did you type?  (Please be EXACT)

 

Take 20 minutes to learn how to use "telnet" to access your server as well as the system console.  Then you can cut/paste/scroll backwards...

 

Install "putty" on your PC, it is a far better "telnet" client than the one supplied with most Microsoft products.

 

Joe L, sorry I was unclear. You were correct. I mistyped file name. Redid. It took it. Was running when I left for work.

Joe L, just got home.  Same bad result we got before.  CAnnot read the block (52051000): (input/output error). Aborted.  Happened at exactly the same spot, with 192133767 left to read of the hard drive.  There must be a way to write to the drive to teach it that these 19 blocks should be ignored.  19 out of millions.

 

Puty, way cool.  Great way to access my Tower, thanks.  Never new such a thing existed.

 

ROger

Joe L, just got home.  Same bad result we got before.  CAnnot read the block (52051000): (input/output error). Aborted.  Happened at exactly the same spot, with 192133767 left to read of the hard drive.  There must be a way to write to the drive to teach it that these 19 blocks should be ignored.  19 out of millions.

 

ROger

You can try this... but be absolutely sure you get the commands correct.

 

badblocks -b 4096 -p 100 -s -v -n /dev/sdX1  52051000 52051000

Since "-n" uses a non-destructive read/write mode, it might force the re-allocation of the bad block.

Do this for each of the block addresses marked as bad.

 

You can test if it is subsequently readable by typing:

debugreiserfs -1 52051000 /dev/sdX1

 

If it is, great.  If not we can force write zeros to that block and hopefully force the SMART firmware to re-allocate it for you.

dd if=/dev/zero bs=4096 count=1 seek=52051000  of=/dev/sdX1

repeat with each of the blocks listed in the badblocks file.  Then

reiserfsck --check /dev/sdX1

 

followed by whatever it suggests next.

probably

reiserfsck --fix-fixable /dev/sdX1

or

reiserfsck --rebuild-tree -S /dev/sdX1

 

Joe L, so on my list first bad block is 52050944, so can I start with that?  I'm assuming your block number is an example

The first two I tried, when done, came back with the following message when checked with the debugreiserfs command:

 

5250944 is free in ondisk bitmap, Looks like unformatted.  For what it's worth, I tried the debugreiserfs command on the next badblock in line before I did the badblocks command, and it came back as free in ondisk bitmap as well.

some took longer to clear then others, however.Zoomed through the first few and is taking some considerable time on block 52050993.  All the passes so far are coming back completed, 0 bad blocks found testing from 52050993 to 52050994, but at the bottom it hanging on 5250993/ 5250993, which of course is the instruction that was put in.

 

Is this good?

 

Roger

Been stuck on 52050997 for awhile.  Happens athe end after is runs a bunc of tests and comes ack with 0 bad blocks.  Wondering if I need to run a 52051000, because I got that error message or will that location just get picked up automatically when I run the command on 520501001.  Seems to run the test one block before and after, then focus on the block.

 

Does it mean it's rellocating when it hangs on the last function?  Is that why it sometimes takes so long to process?  Been over an hour so far on this particular block.

 

Roger

Joe L, so on my list first bad block is 52050944, so can I start with that?  I'm assuming your block number is an example

No, it was the actual block reported by YOUR previous post where you posted : CAnnot read the block (52051000): (input/output error). Aborted.

If you want to not zero it, then fine, ignore my advice, but do not be surprised when the reiserfsck fails on that same block.

The first two I tried, when done, came back with the following message when checked with the debugreiserfs command:

 

5250944 is free in ondisk bitmap, Looks like unformatted.  For what it's worth, I tried the debugreiserfs command on the next badblock in line before I did the badblocks command, and it came back as free in ondisk bitmap as well.

some took longer to clear then others, however.Zoomed through the first few and is taking some considerable time on block 52050993.  All the passes so far are coming back completed, 0 bad blocks found testing from 52050993 to 52050994, but at the bottom it hanging on 5250993/ 5250993, which of course is the instruction that was put in.

 

Is this good?

I have absolutely no idea.   I've never used these commands... you are the first person I know on this forum who has.

Joe L, O.K. ran them all including 52051000.  Interestingly, took 30 seconds to do 9 of them this morning, whereas it took hours to complete a few of them last night.

 

ROger

Joe L, O.K. ran them all including 52051000.  Interestingly, took 30 seconds to do 9 of them this morning, whereas it took hours to complete a few of them last night.

 

ROger

proceed with the

--check

and then proceed as it instructs.

When fixed (if fixed) you should be able to run

--rebuild-tree -S

 

Joe L, now I get a new response whne I run check,  Bad root block 0.  (--rebuild-tree did not complete).  Now this is after I run the earlie command on all the 19 bad blocks and they all come back O.K. after checking them as well.

 

Roger

Joe L, now I get a new response whne I run check,  Bad root block 0.  (--rebuild-tree did not complete).  Now this is after I run the earlie command on all the 19 bad blocks and they all come back O.K. after checking them as well.

 

Roger

Are you sure you typed the device name correctly?  (With the "1" suffix)

 

If so, try running the --rebuild-tree once more.

 

And PLEASE.  Learn how to cut and paste from a telnet session.  I'm tiring of having to guess at what commands you actually typed.

 

Joe L.

 

Joe L, did not type the command, I am now using cut and paste, using putty. Putty is very cool.  Taking the text from your post and dropping it in.

 

Roger

Joe L, unfortunately, at the same location in rebuild Tree, I get CAnnot read the block 52050987.  When I rerun your fist command, I get 0 bad blocks, so I'm going to try the second command you suggested, if you think that's a good idea, which is

 

dd if=/dev/zero bs=4096 count=1 seek=52051000  of=/dev/sdX1

 

Joe L, seems like we are getting close, but; still hung up on this one issue.  What's odd is the last series of commands either report no bad block, or have no problem writing 0 to the bad block.  Your the expert, and I am very thankful for your help.  Suff I'm, reading says the bad block 0 respone the the fix-fixable simply means you need to run rebuild-tree.  Which I'm doing, but; then it fails.  Trying again