View previous topic :: View next topic |
Author |
Message |
Given M. Sur l33t
Joined: 03 Feb 2004 Posts: 648 Location: No such file or directory
|
Posted: Sun Jul 10, 2005 10:26 pm Post subject: Corrupted reiserfs - cannot fsck [SOLVED - hardware problem] |
|
|
I'm having some serious problems with a reiserfs partition. You can skip to "Current Problem" or continue reading this section to learn how it started: I tried to untar a file, and I got some errors saying I was out of disk space. I don't think that was right, but now I have to way to confirm it. So, I decided to just delete the files I had uncompressed, I got a "permission denied" error. So, I switched to root and tried again, and got a seg fault. So, being the dumbass that I am, I thought... hmmm... a seg fault, let's try that again and see if it happens again.
So, I tried again to delete the files, and rm froze -- it also seemed to have frozen the root user. Everything under my X session for my regular user was still working, but I could not su to root from any of my terminals, it would just freeze after typing the root password (although I could Ctrl-C it to stop the login attempt). After waiting a while to see if the problem would fix itself I finally decided to reboot my system. Trying to exit X in the normal way failed, so I had to Ctrl-Alt-Backspace. I then logged in as root without a problem and typed reboot. I got the "system is shutting down" message (or whatever it says at the beginning of a reboot), and then the system froze.
So, I waited a while, hoping it was just taking a while, but I ended up having to do a hard reset.
Current Problem
I cannot mount my /home directory now. I get an error that says fsck couldn't fix it, and that I need to fix it manually.
So, I try to reiserfsck /dev/hdb1 and I get the following error: Code: | 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 (1835008): (Input/output error).
Aborted | note: I also get the same error with "reiserfsck --check", and "reiserfsck --rebuild-tree"
So I figure I'll have to use the --badblocks option but I then get the following error: Code: | create_badblock_bitmap: block number (1835008) belongs to system reiserfs area. It cannot be relocated. |
So do I have any options left, or am I screwed? My data is not backed up (I can't afford another hard drive or a dvd burner -- and I never felt like backing up 60GB to CDs).
Another note: "reieserfsck --rebuild-sb /dev/hdb1" is the only thing that doesn't report an error, but it doesn't help either. Here's the output though, just in case it's helpful
Code: | Will check superblock and rebuild it if needed
Will put log info to 'stdout'
Reiserfs super block in block 16 on 0x341 of format 3.6 with standard journal
Count of blocks on the device: 15012880
Number of bitmaps: 459
Blocksize: 4096
Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 147560
Root block: 9718346
Filesystem is NOT clean
Tree height: 5
Hash function used to sort names: "r5"
Objectid map size 48, max 972
Journal parameters:
Device [0x0]
Magic [0x16d76df4]
Size 8193 blocks (including 1 for journal header) (first block 18)
Max transaction length 1024 blocks
Max batch size 900 blocks
Max commit age 30
Blocks reserved by journal: 0
Fs state field: 0x0:
sb_version: 2
inode generation number: 6227444
UUID: 73770868-fed1-4b7c-a634-87a57d218023
LABEL:
Set flags in SB:
ATTRIBUTES CLEAN
Super block seems to be correct |
The hard drive is only a two months old, so it should be working just fine. But, maybe it is a hardware problem.
Is there any way to get my data back... or is it lost forever? _________________ What is the best [insert-type-of-program-here]?
Last edited by Given M. Sur on Tue Jul 12, 2005 5:55 am; edited 1 time in total |
|
Back to top |
|
|
Moloch Apprentice
Joined: 17 Mar 2003 Posts: 293 Location: Albuquerque, NM, US
|
Posted: Sun Jul 10, 2005 11:04 pm Post subject: |
|
|
No more ideas at the moment, but let's get a little more information. In particular to check for possible hardware failure. Check the output of 'dmesg'. Paste any error messages or anything that sounds bad. _________________ Understanding is a three-edged sword: your side, their side, and the truth. --Kosh
1010011010 |
|
Back to top |
|
|
Given M. Sur l33t
Joined: 03 Feb 2004 Posts: 648 Location: No such file or directory
|
Posted: Sun Jul 10, 2005 11:13 pm Post subject: |
|
|
Well, most of the output looks bad.
Code: | hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680127, sector=14680127
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680127
Buffer I/O error on device hdb1, logical block 14680064
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680128, sector=14680128
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680128
Buffer I/O error on device hdb1, logical block 14680065
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680129, sector=14680129
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680129
Buffer I/O error on device hdb1, logical block 14680066
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680130, sector=14680130
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680130
Buffer I/O error on device hdb1, logical block 14680067
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680132, sector=14680131
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680131
Buffer I/O error on device hdb1, logical block 14680068
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680132, sector=14680132
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680132
Buffer I/O error on device hdb1, logical block 14680069
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680133, sector=14680133
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680133
Buffer I/O error on device hdb1, logical block 14680070
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680134, sector=14680134
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680134
Buffer I/O error on device hdb1, logical block 14680071
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680127, sector=14680127
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680127
Buffer I/O error on device hdb1, logical block 14680064
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680128, sector=14680128
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680128
Buffer I/O error on device hdb1, logical block 14680065
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680129, sector=14680129
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680129
Buffer I/O error on device hdb1, logical block 14680066
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680130, sector=14680130
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680130
Buffer I/O error on device hdb1, logical block 14680067
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680132, sector=14680131
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680131
Buffer I/O error on device hdb1, logical block 14680068
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680132, sector=14680132
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680132
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680133, sector=14680133
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680133
printk: 1 messages suppressed.
Buffer I/O error on device hdb1, logical block 14680070
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680134, sector=14680134
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680134
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680127, sector=14680127
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680127
printk: 1 messages suppressed.
Buffer I/O error on device hdb1, logical block 14680064
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680128, sector=14680128
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680128
Buffer I/O error on device hdb1, logical block 14680065
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680129, sector=14680129
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680129
Buffer I/O error on device hdb1, logical block 14680066
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680130, sector=14680130
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680130
Buffer I/O error on device hdb1, logical block 14680067
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680132, sector=14680131
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680131
Buffer I/O error on device hdb1, logical block 14680068
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680132, sector=14680132
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680132
Buffer I/O error on device hdb1, logical block 14680069
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680133, sector=14680133
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680133
Buffer I/O error on device hdb1, logical block 14680070
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680134, sector=14680134
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680134
Buffer I/O error on device hdb1, logical block 14680071
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680127, sector=14680127
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680127
Buffer I/O error on device hdb1, logical block 14680064
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680128, sector=14680128
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680128
Buffer I/O error on device hdb1, logical block 14680065
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680129, sector=14680129
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680129
Buffer I/O error on device hdb1, logical block 14680066
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680130, sector=14680130
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680130
Buffer I/O error on device hdb1, logical block 14680067
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680132, sector=14680131
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680131
Buffer I/O error on device hdb1, logical block 14680068
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680132, sector=14680132
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680132
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680133, sector=14680133
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680133
printk: 1 messages suppressed.
Buffer I/O error on device hdb1, logical block 14680070
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680134, sector=14680134
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680134
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680127, sector=14680127
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680127
printk: 1 messages suppressed.
Buffer I/O error on device hdb1, logical block 14680064
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680128, sector=14680128
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680128
Buffer I/O error on device hdb1, logical block 14680065
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680129, sector=14680129
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680129
Buffer I/O error on device hdb1, logical block 14680066
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680130, sector=14680130
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680130
Buffer I/O error on device hdb1, logical block 14680067
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680132, sector=14680131
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680131
Buffer I/O error on device hdb1, logical block 14680068
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680132, sector=14680132
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680132
Buffer I/O error on device hdb1, logical block 14680069
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680133, sector=14680133
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680133
Buffer I/O error on device hdb1, logical block 14680070
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680134, sector=14680134
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680134
Buffer I/O error on device hdb1, logical block 14680071
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680127, sector=14680127
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680127
Buffer I/O error on device hdb1, logical block 14680064
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680128, sector=14680128
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680128
Buffer I/O error on device hdb1, logical block 14680065
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680129, sector=14680129
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680129
Buffer I/O error on device hdb1, logical block 14680066
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680130, sector=14680130
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680130
Buffer I/O error on device hdb1, logical block 14680067
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680132, sector=14680131
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680131
Buffer I/O error on device hdb1, logical block 14680068
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680132, sector=14680132
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680132
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680133, sector=14680133
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680133
printk: 1 messages suppressed.
Buffer I/O error on device hdb1, logical block 14680070
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14680134, sector=14680134
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14680134 |
_________________ What is the best [insert-type-of-program-here]? |
|
Back to top |
|
|
Moloch Apprentice
Joined: 17 Mar 2003 Posts: 293 Location: Albuquerque, NM, US
|
Posted: Sun Jul 10, 2005 11:23 pm Post subject: |
|
|
Yup bad news. Same thing happened to me. Here's what you can try. Chances are... consider your data lost.
First get a replacement hard drive with the warranty. Western Digital has a warranty program where they will send you the new HDD and let you keep the old one for 30 days. Then download and burn this bootable linux CD. Use the program 'ddrescue' to copy the contents of the bad HDD to the replacement HDD. The idea is you will be able to run fsck tools and attempt to recover data from a good HDD. A note of warning with this. This process takes a very long time. I had to do it on a 250GB HDD and it was running for over 2 weeks. If you have a spare lesser computer, you may want to consider putting these drives in that. So your main computer won't be occupied for that long. Still after doing all this. I was only able to recover a few GBs.
Sorry for the bad news. Sounds like you just got a dud. It happens. Good luck.
EDIT: BTW, I did some serious googling on this. There is very little information out there dealing with recovering from a HDD failure. Most of the information is.... "You didn't back up your data? Well you are fucked." Which sadly is mostly true. I had posted in the Gentoo forums as well. You will find that you will get few responses with these sorts of problems. This is just rare, shitty, bad luck. _________________ Understanding is a three-edged sword: your side, their side, and the truth. --Kosh
1010011010 |
|
Back to top |
|
|
Given M. Sur l33t
Joined: 03 Feb 2004 Posts: 648 Location: No such file or directory
|
Posted: Sun Jul 10, 2005 11:41 pm Post subject: |
|
|
Well, thanks for the info.
Looks like I won't be buying Maxtor drives anymore. I noticed several other complaints about them when I was searching before creating this thread.
And I unfortunately can't afford a new hard drive right now. But, at least I can use the free space on hda as my /home for now and just consider my data gone until I can afford a new drive.
Really sucks too, as my entire music collection is on there, some of which I still have the CDs for, but most of which I don't. Unfortunately, when you're broke and hungry $1 per CD from the pawn shop sounds like a good idea when the music is on your HD anyways.
The rest of the data sucks to have lost too, but it's not nearly as important to me as my music was.
The really fcked up thing is I just bought this hard drive a few months ago because my previous hard drive failed (although that one made loud clicks for the entire year that I used it -- so I never kept anything important on that one -- just system files). Who would've thought that the stock emachines HD would outlast two others. _________________ What is the best [insert-type-of-program-here]? |
|
Back to top |
|
|
Moloch Apprentice
Joined: 17 Mar 2003 Posts: 293 Location: Albuquerque, NM, US
|
Posted: Sun Jul 10, 2005 11:58 pm Post subject: |
|
|
Well I don't think this is an issue of Maxtor. I've got an older Maxtor about 4 years old. 27GB. Still fine. When my 250GB Western Digital failed is was just like this. Only after a few months. Plain and simple you are a victim of a dud. I don't care what brand is behind it duds happen in the manufacturing process.
However, if the HDD is only a few months old. Then you don't have to buy a new one. Use the warranty. They have an 'advance' RMA plan. Which is what I described with mine where they will ship you the replacement first. _________________ Understanding is a three-edged sword: your side, their side, and the truth. --Kosh
1010011010 |
|
Back to top |
|
|
Given M. Sur l33t
Joined: 03 Feb 2004 Posts: 648 Location: No such file or directory
|
Posted: Mon Jul 11, 2005 12:53 am Post subject: |
|
|
I'll definately do that. But, they make you run a diagnostic program on the drive first. And, I don't have a floppy disk to put it on (and I'm not even sure my floppy drive works in vmware -- never tried it -- never even tried using my floppy drive with Gentoo at all now that I think about it). So, I'll have to wait until tomorrow, and get a floppy from my mom (and the program -- since she runs windows).
I may try the drive again later tonight too. It is currently very hot, so maybe after it cools down I'll get lucky and be able to use it long enough to at least get some of my music back. I'm certainly not counting on that happening, but I'll give it a shot anyways.
Thanks again for all the info. _________________ What is the best [insert-type-of-program-here]? |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|