[opensuse] Need help!
Guy, My main partion, crash. I am getting I/O errors, which I know means the drive is dead. What I need is to get on that partition so I can get my config off or any thing that I can. I have ran reiserfsck --fix-fixable, I get these error, cannot read teh bock 5672. reiserfsck is tell me I can use a -B flag to fix it but when I try to use that flag, I get the help menu. Please some know what I can do to get my data. Thanks Payne -- -- Command, n.: Statement presented by a human and accepted by a computer in such a manner as to make the human feel as if he is in control. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, 2008-08-24 at 10:57 -0400, Chuck Payne wrote:
Guy,
My main partion, crash. I am getting I/O errors, which I know means the drive is dead. What I need is to get on that partition so I can get my config off or any thing that I can. I have ran reiserfsck --fix-fixable, I get these error, cannot read teh bock 5672. reiserfsck is tell me I can use a -B flag to fix it but when I try to use that flag, I get the help menu. Please some know what I can do to get my data.
First, calm down. Take a walk. Don't panic and do stuff you'll regret later. Have you got a Linux live CD? There are dozens of these; many are optimized for data rescue and recovery. See the listing at http://livecdlist.com. I like and have often used Knoppix for this, but any one of many and a USB key or external drive will do the job. Good luck. -- N. B. Day N 39° 28' 25" W 119° 48' 37" 1404 meters up Aurelius up 3:11, 2 users, load average: 0.12, 0.10, 0.06 2.6.25.11-0.1-default x86_64 GNU/Linux openSUSE 11.0 (X86-64) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I use a similar approach as well. However, I have multiple OS machines, so if any drive fails (or if I am working on a friends computer that has), I just pop it in one of my other OS machines, mount it and copy off what I can. -- Regards, Shawn Holland On Sun, 2008-08-24 at 08:28 -0700, N B Day wrote:
On Sun, 2008-08-24 at 10:57 -0400, Chuck Payne wrote:
Guy,
My main partion, crash. I am getting I/O errors, which I know means the drive is dead. What I need is to get on that partition so I can get my config off or any thing that I can. I have ran reiserfsck --fix-fixable, I get these error, cannot read teh bock 5672. reiserfsck is tell me I can use a -B flag to fix it but when I try to use that flag, I get the help menu. Please some know what I can do to get my data.
First, calm down. Take a walk. Don't panic and do stuff you'll regret later.
Have you got a Linux live CD? There are dozens of these; many are optimized for data rescue and recovery. See the listing at http://livecdlist.com.
I like and have often used Knoppix for this, but any one of many and a USB key or external drive will do the job.
Good luck.
-- N. B. Day N 39° 28' 25" W 119° 48' 37" 1404 meters up Aurelius up 3:11, 2 users, load average: 0.12, 0.10, 0.06 2.6.25.11-0.1-default x86_64 GNU/Linux openSUSE 11.0 (X86-64)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Aug 24, 2008 at 11:35 AM, Shawn Holland <sholland@sandara.ca> wrote:
I use a similar approach as well. However, I have multiple OS machines, so if any drive fails (or if I am working on a friends computer that has), I just pop it in one of my other OS machines, mount it and copy off what I can.
-- Regards, Shawn Holland
On Sun, 2008-08-24 at 08:28 -0700, N B Day wrote:
On Sun, 2008-08-24 at 10:57 -0400, Chuck Payne wrote:
Guy,
My main partion, crash. I am getting I/O errors, which I know means the drive is dead. What I need is to get on that partition so I can get my config off or any thing that I can. I have ran reiserfsck --fix-fixable, I get these error, cannot read teh bock 5672. reiserfsck is tell me I can use a -B flag to fix it but when I try to use that flag, I get the help menu. Please some know what I can do to get my data.
First, calm down. Take a walk. Don't panic and do stuff you'll regret later.
Have you got a Linux live CD? There are dozens of these; many are optimized for data rescue and recovery. See the listing at http://livecdlist.com.
I like and have often used Knoppix for this, but any one of many and a USB key or external drive will do the job.
Good luck.
-- N. B. Day N 39° 28' 25" W 119° 48' 37" 1404 meters up Aurelius up 3:11, 2 users, load average: 0.12, 0.10, 0.06 2.6.25.11-0.1-default x86_64 GNU/Linux openSUSE 11.0 (X86-64)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Well I need to tell not to read the block 5672, I think I will be ok. Right now no matter what it stops on that block. -- -- Command, n.: Statement presented by a human and accepted by a computer in such a manner as to make the human feel as if he is in control. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Aug 24, 2008 at 11:38 AM, Chuck Payne <terrorpup@gmail.com> wrote:
On Sun, Aug 24, 2008 at 11:35 AM, Shawn Holland <sholland@sandara.ca> wrote:
I use a similar approach as well. However, I have multiple OS machines, so if any drive fails (or if I am working on a friends computer that has), I just pop it in one of my other OS machines, mount it and copy off what I can.
-- Regards, Shawn Holland
On Sun, 2008-08-24 at 08:28 -0700, N B Day wrote:
On Sun, 2008-08-24 at 10:57 -0400, Chuck Payne wrote:
Guy,
My main partion, crash. I am getting I/O errors, which I know means the drive is dead. What I need is to get on that partition so I can get my config off or any thing that I can. I have ran reiserfsck --fix-fixable, I get these error, cannot read teh bock 5672. reiserfsck is tell me I can use a -B flag to fix it but when I try to use that flag, I get the help menu. Please some know what I can do to get my data.
First, calm down. Take a walk. Don't panic and do stuff you'll regret later.
Have you got a Linux live CD? There are dozens of these; many are optimized for data rescue and recovery. See the listing at http://livecdlist.com.
I like and have often used Knoppix for this, but any one of many and a USB key or external drive will do the job.
Good luck.
-- N. B. Day N 39° 28' 25" W 119° 48' 37" 1404 meters up Aurelius up 3:11, 2 users, load average: 0.12, 0.10, 0.06 2.6.25.11-0.1-default x86_64 GNU/Linux openSUSE 11.0 (X86-64)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Well I need to tell not to read the block 5672, I think I will be ok. Right now no matter what it stops on that block.
-- -- Command, n.: Statement presented by a human and accepted by a computer in such a manner as to make the human feel as if he is in control.
Maybe this will help...this is the error... Check and repair filesystem (reiserfs) on /dev/sdc3 00:00:23 ( ERROR ) calibrate /dev/sdc3 00:00:00 ( SUCCESS ) path: /dev/sdc3 start: 6618780 end: 59054939 size: 52436160 (25.00 GiB) check filesystem on /dev/sdc3 for errors and (if possible) fix them 00:00:23 ( ERROR ) reiserfsck --yes --fix-fixable --quiet /dev/sdc3 reiserfsck 3.6.19 (2003 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to reiserfs-list@namesys.com, ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will check consistency of the filesystem on /dev/sdc3 and will fix what can be fixed without --rebuild-tree Will put log info to 'stdout' ########### reiserfsck --fix-fixable started at Sun Aug 24 07:33:57 2008 ########### Replaying journal: Trans replayed: mountid 402, transid 33176325, desc 5667, len 12, commit 5680, next trans offset 5663 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 (5672): (Input/output error). -- -- Command, n.: Statement presented by a human and accepted by a computer in such a manner as to make the human feel as if he is in control. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, 2008-08-24 at 11:41 -0400, Chuck Payne wrote:
On Sun, Aug 24, 2008 at 11:38 AM, Chuck Payne <terrorpup@gmail.com> wrote:
On Sun, Aug 24, 2008 at 11:35 AM, Shawn Holland <sholland@sandara.ca> wrote:
I use a similar approach as well. However, I have multiple OS machines, so if any drive fails (or if I am working on a friends computer that has), I just pop it in one of my other OS machines, mount it and copy off what I can.
-- Regards, Shawn Holland
On Sun, 2008-08-24 at 08:28 -0700, N B Day wrote:
On Sun, 2008-08-24 at 10:57 -0400, Chuck Payne wrote:
Guy,
My main partion, crash. I am getting I/O errors, which I know means the drive is dead. What I need is to get on that partition so I can get my config off or any thing that I can. I have ran reiserfsck --fix-fixable, I get these error, cannot read teh bock 5672. reiserfsck is tell me I can use a -B flag to fix it but when I try to use that flag, I get the help menu. Please some know what I can do to get my data.
First, calm down. Take a walk. Don't panic and do stuff you'll regret later.
Have you got a Linux live CD? There are dozens of these; many are optimized for data rescue and recovery. See the listing at http://livecdlist.com.
I like and have often used Knoppix for this, but any one of many and a USB key or external drive will do the job.
Good luck.
-- N. B. Day N 39° 28' 25" W 119° 48' 37" 1404 meters up Aurelius up 3:11, 2 users, load average: 0.12, 0.10, 0.06 2.6.25.11-0.1-default x86_64 GNU/Linux openSUSE 11.0 (X86-64)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Well I need to tell not to read the block 5672, I think I will be ok. Right now no matter what it stops on that block.
-- -- Command, n.: Statement presented by a human and accepted by a computer in such a manner as to make the human feel as if he is in control.
Maybe this will help...this is the error...
Check and repair filesystem (reiserfs) on /dev/sdc3 00:00:23 ( ERROR )
calibrate /dev/sdc3 00:00:00 ( SUCCESS )
path: /dev/sdc3 start: 6618780 end: 59054939 size: 52436160 (25.00 GiB) check filesystem on /dev/sdc3 for errors and (if possible) fix them 00:00:23 ( ERROR )
reiserfsck --yes --fix-fixable --quiet /dev/sdc3
reiserfsck 3.6.19 (2003 www.namesys.com)
************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to reiserfs-list@namesys.com, ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** *************************************************************
Will check consistency of the filesystem on /dev/sdc3 and will fix what can be fixed without --rebuild-tree Will put log info to 'stdout' ########### reiserfsck --fix-fixable started at Sun Aug 24 07:33:57 2008 ########### Replaying journal: Trans replayed: mountid 402, transid 33176325, desc 5667, len 12, commit 5680, next trans offset 5663
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 (5672): (Input/output error).
-- -- Command, n.: Statement presented by a human and accepted by a computer in such a manner as to make the human feel as if he is in control.
When ever I pop in any drive (regardless of its FS) I just mount it and it never complains. Except to spit out IO errors during the copy process. I don't bother to do a FS check. Like I said, I mount, copy, unmount. If your lucky enough to have another computer running linux you can do the same thing. If you only have the one computer then a live cd should let you boot and then mount the existing drive and then copy to an external source, just like I do. But doing an FS check is going to produce those errors when you just need to copy off the data. So just copy it off :) -- Regards, Shawn Holland -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Aug 24, 2008 at 11:47 AM, Shawn Holland <sholland@sandara.ca> wrote:
On Sun, 2008-08-24 at 11:41 -0400, Chuck Payne wrote:
On Sun, Aug 24, 2008 at 11:38 AM, Chuck Payne <terrorpup@gmail.com> wrote:
On Sun, Aug 24, 2008 at 11:35 AM, Shawn Holland <sholland@sandara.ca> wrote:
I use a similar approach as well. However, I have multiple OS machines, so if any drive fails (or if I am working on a friends computer that has), I just pop it in one of my other OS machines, mount it and copy off what I can.
-- Regards, Shawn Holland
On Sun, 2008-08-24 at 08:28 -0700, N B Day wrote:
On Sun, 2008-08-24 at 10:57 -0400, Chuck Payne wrote:
Guy,
My main partion, crash. I am getting I/O errors, which I know means the drive is dead. What I need is to get on that partition so I can get my config off or any thing that I can. I have ran reiserfsck --fix-fixable, I get these error, cannot read teh bock 5672. reiserfsck is tell me I can use a -B flag to fix it but when I try to use that flag, I get the help menu. Please some know what I can do to get my data.
First, calm down. Take a walk. Don't panic and do stuff you'll regret later.
Have you got a Linux live CD? There are dozens of these; many are optimized for data rescue and recovery. See the listing at http://livecdlist.com.
I like and have often used Knoppix for this, but any one of many and a USB key or external drive will do the job.
Good luck.
-- N. B. Day N 39° 28' 25" W 119° 48' 37" 1404 meters up Aurelius up 3:11, 2 users, load average: 0.12, 0.10, 0.06 2.6.25.11-0.1-default x86_64 GNU/Linux openSUSE 11.0 (X86-64)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Well I need to tell not to read the block 5672, I think I will be ok. Right now no matter what it stops on that block.
-- -- Command, n.: Statement presented by a human and accepted by a computer in such a manner as to make the human feel as if he is in control.
Maybe this will help...this is the error...
Check and repair filesystem (reiserfs) on /dev/sdc3 00:00:23 ( ERROR )
calibrate /dev/sdc3 00:00:00 ( SUCCESS )
path: /dev/sdc3 start: 6618780 end: 59054939 size: 52436160 (25.00 GiB) check filesystem on /dev/sdc3 for errors and (if possible) fix them 00:00:23 ( ERROR )
reiserfsck --yes --fix-fixable --quiet /dev/sdc3
reiserfsck 3.6.19 (2003 www.namesys.com)
************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to reiserfs-list@namesys.com, ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** *************************************************************
Will check consistency of the filesystem on /dev/sdc3 and will fix what can be fixed without --rebuild-tree Will put log info to 'stdout' ########### reiserfsck --fix-fixable started at Sun Aug 24 07:33:57 2008 ########### Replaying journal: Trans replayed: mountid 402, transid 33176325, desc 5667, len 12, commit 5680, next trans offset 5663
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 (5672): (Input/output error).
-- -- Command, n.: Statement presented by a human and accepted by a computer in such a manner as to make the human feel as if he is in control.
When ever I pop in any drive (regardless of its FS) I just mount it and it never complains. Except to spit out IO errors during the copy process. I don't bother to do a FS check. Like I said, I mount, copy, unmount. If your lucky enough to have another computer running linux you can do the same thing. If you only have the one computer then a live cd should let you boot and then mount the existing drive and then copy to an external source, just like I do. But doing an FS check is going to produce those errors when you just need to copy off the data. So just copy it off :)
-- Regards, Shawn Holland
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Shaw, again. No matter what I get that error. That is why I am asking for HELP. I have tried everything you, and I happy that you are so lucky, I am not. Ok. That is why I have posted to mailist. FOR HELP!. -- -- Command, n.: Statement presented by a human and accepted by a computer in such a manner as to make the human feel as if he is in control. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Shawn Holland schreef:
When ever I pop in any drive (regardless of its FS) I just mount it and it never complains. Except to spit out IO errors during the copy process. I don't bother to do a FS check. Like I said, I mount, copy, unmount. If your lucky enough to have another computer running linux you can do the same thing. If you only have the one computer then a live cd should let you boot and then mount the existing drive and then copy to an external source, just like I do. But doing an FS check is going to produce those errors when you just need to copy off the data. So just copy it off :)
Would that be a copy or a dd? I never had a disk fail in that way, but what I would try: * dd the faulty disk to an image file on a *very* large good disk * make a copy of the image file * mount the image file as a loopback device * copy whatever you want from the loopback device. Of course, you would need a second hard disk that is at least twice as big as the original one. And don't bother with gzipping the image. -- Amedee -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Aug 24, 2008 at 11:28 AM, N B Day <nday@uno.edu> wrote:
On Sun, 2008-08-24 at 10:57 -0400, Chuck Payne wrote:
Guy,
My main partion, crash. I am getting I/O errors, which I know means the drive is dead. What I need is to get on that partition so I can get my config off or any thing that I can. I have ran reiserfsck --fix-fixable, I get these error, cannot read teh bock 5672. reiserfsck is tell me I can use a -B flag to fix it but when I try to use that flag, I get the help menu. Please some know what I can do to get my data.
First, calm down. Take a walk. Don't panic and do stuff you'll regret later.
Have you got a Linux live CD? There are dozens of these; many are optimized for data rescue and recovery. See the listing at http://livecdlist.com.
I like and have often used Knoppix for this, but any one of many and a USB key or external drive will do the job.
Good luck.
-- N. B. Day N 39° 28' 25" W 119° 48' 37" 1404 meters up Aurelius up 3:11, 2 users, load average: 0.12, 0.10, 0.06 2.6.25.11-0.1-default x86_64 GNU/Linux openSUSE 11.0 (X86-64)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
first thing I did was try knoppix, no luck. In fact that was the one that told I need to fix the superblock. I am doing search now. Can't walk have too much to do to get it back up. -- -- Command, n.: Statement presented by a human and accepted by a computer in such a manner as to make the human feel as if he is in control. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 24 August 2008 09:57:55 am Chuck Payne wrote:
Guy,
My main partion, crash. I am getting I/O errors, which I know means the drive is dead. What I need is to get on that partition so I can get my config off or any thing that I can. I have ran reiserfsck --fix-fixable, I get these error, cannot read teh bock 5672. reiserfsck is tell me I can use a -B flag to fix it but when I try to use that flag, I get the help menu. Please some know what I can do to get my data.
Thanks
Payne
As N B Day said, calm down first. Urge is bad adviser as many actions can make situation worse. -B expects file name with a list of bad blocks, not a bad block number itself I would use first dd_rescue to pull as much as possible from the drive, than attempt to fix it using manufacturers tool for that, or if dd_rescue fails than straight with manufacturers tool. It will solve bad blocks problem and fsck will be able to repair file system. The package is ddrescue. I'm sorry that I can't help more, but without drive type and model is not possible to search the web. From your another post it seems that bad block is in the middle of the journal. -- Regards, Rajko http://en.opensuse.org/Portal needs helpful hands. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Aug 24, 2008 at 12:09 PM, Rajko M. <rmatov101@charter.net> wrote:
On Sunday 24 August 2008 09:57:55 am Chuck Payne wrote:
Guy,
My main partion, crash. I am getting I/O errors, which I know means the drive is dead. What I need is to get on that partition so I can get my config off or any thing that I can. I have ran reiserfsck --fix-fixable, I get these error, cannot read teh bock 5672. reiserfsck is tell me I can use a -B flag to fix it but when I try to use that flag, I get the help menu. Please some know what I can do to get my data.
Thanks
Payne
As N B Day said, calm down first. Urge is bad adviser as many actions can make situation worse.
-B expects file name with a list of bad blocks, not a bad block number itself
I would use first dd_rescue to pull as much as possible from the drive, than attempt to fix it using manufacturers tool for that, or if dd_rescue fails than straight with manufacturers tool. It will solve bad blocks problem and fsck will be able to repair file system.
The package is ddrescue.
I'm sorry that I can't help more, but without drive type and model is not possible to search the web.
From your another post it seems that bad block is in the middle of the journal.
-- Regards, Rajko http://en.opensuse.org/Portal needs helpful hands. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Rajko, Thanks, your help was what I was needing. I have install the dd_rescue, and I have found this page that explain how to recover my files and remove that bad sector too. http://blog.herbertm.ca/pages/badblocks-howto Again, thanks. I don't post to the list until I have done my google search, man pages, and take a couple of power naps to clear my mind. Payne -- -- Command, n.: Statement presented by a human and accepted by a computer in such a manner as to make the human feel as if he is in control. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Aug 24, 2008 at 3:08 PM, Chuck Payne <terrorpup@gmail.com> wrote:
On Sun, Aug 24, 2008 at 12:09 PM, Rajko M. <rmatov101@charter.net> wrote:
On Sunday 24 August 2008 09:57:55 am Chuck Payne wrote:
Guy,
My main partion, crash. I am getting I/O errors, which I know means the drive is dead. What I need is to get on that partition so I can get my config off or any thing that I can. I have ran reiserfsck --fix-fixable, I get these error, cannot read teh bock 5672. reiserfsck is tell me I can use a -B flag to fix it but when I try to use that flag, I get the help menu. Please some know what I can do to get my data.
Thanks
Payne
As N B Day said, calm down first. Urge is bad adviser as many actions can make situation worse.
-B expects file name with a list of bad blocks, not a bad block number itself
I would use first dd_rescue to pull as much as possible from the drive, than attempt to fix it using manufacturers tool for that, or if dd_rescue fails than straight with manufacturers tool. It will solve bad blocks problem and fsck will be able to repair file system.
The package is ddrescue.
I'm sorry that I can't help more, but without drive type and model is not possible to search the web.
From your another post it seems that bad block is in the middle of the journal.
-- Regards, Rajko http://en.opensuse.org/Portal needs helpful hands. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Rajko,
Thanks, your help was what I was needing. I have install the dd_rescue, and I have found this page that explain how to recover my files and remove that bad sector too.
http://blog.herbertm.ca/pages/badblocks-howto
Again, thanks. I don't post to the list until I have done my google search, man pages, and take a couple of power naps to clear my mind.
Payne
-- -- Command, n.: Statement presented by a human and accepted by a computer in such a manner as to make the human feel as if he is in control.
Man, dd_rescur ROCKS!. I was able to get my data with it. I use this dd_rescue -A -v -b 4096 /dev/sdc2 /mnt/backup.img. That took about 3hrs for 5gigs. Once it was done, I ran reiserfsck --check /mnt/backup.img, it came back clean. Now, I got mount -o loop /mnt/backup.img /backup. Thanks again for the help. Payne -- -- Command, n.: Statement presented by a human and accepted by a computer in such a manner as to make the human feel as if he is in control. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 24 August 2008 04:27:49 pm Chuck Payne wrote:
Rajko,
Thanks, your help was what I was needing. I have install the dd_rescue, and I have found this page that explain how to recover my files and remove that bad sector too.
Good HOWTO. ...
Man, dd_rescue ROCKS!. I was able to get my data with it. I use this dd_rescue -A -v -b 4096 /dev/sdc2 /mnt/backup.img. That took about 3hrs for 5gigs. Once it was done, I ran reiserfsck --check /mnt/backup.img, it came back clean. Now, I got mount -o loop /mnt/backup.img /backup. Thanks again for the help.
Reiserfs was mentioned in this paper: http://www.cs.wisc.edu/wind/Publications/iron-sosp05.pdf as oversensitive to errors making sometimes situation worse than it actually is. There is from same Google search: http://www.mail-archive.com/linux-ext4@vger.kernel.org/msg02286.html It is a bit old. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Thanks that's the help I am looking for, I don't post unless I can't google ior man page it. On 8/24/08, Rajko M. <rmatov101@charter.net> wrote:
On Sunday 24 August 2008 09:57:55 am Chuck Payne wrote:
Guy,
My main partion, crash. I am getting I/O errors, which I know means the drive is dead. What I need is to get on that partition so I can get my config off or any thing that I can. I have ran reiserfsck --fix-fixable, I get these error, cannot read teh bock 5672. reiserfsck is tell me I can use a -B flag to fix it but when I try to use that flag, I get the help menu. Please some know what I can do to get my data.
Thanks
Payne
As N B Day said, calm down first. Urge is bad adviser as many actions can make situation worse.
-B expects file name with a list of bad blocks, not a bad block number itself
I would use first dd_rescue to pull as much as possible from the drive, than attempt to fix it using manufacturers tool for that, or if dd_rescue fails than straight with manufacturers tool. It will solve bad blocks problem and fsck will be able to repair file system.
The package is ddrescue.
I'm sorry that I can't help more, but without drive type and model is not possible to search the web.
From your another post it seems that bad block is in the middle of the journal.
-- Regards, Rajko http://en.opensuse.org/Portal needs helpful hands. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- Sent from my mobile device -- Command, n.: Statement presented by a human and accepted by a computer in such a manner as to make the human feel as if he is in control. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chuck Payne wrote:
Guy,
My main partion, crash. I am getting I/O errors, which I know means the drive is dead. What I need is to get on that partition so I can get my config off or any thing that I can. I have ran reiserfsck --fix-fixable, I get these error, cannot read teh bock 5672. reiserfsck is tell me I can use a -B flag to fix it but when I try to use that flag, I get the help menu. Please some know what I can do to get my data.
Thanks
Payne
Ive used say a knoppix or other live cd to get out of a bind like that before. may work for you, - -- Steve Reilly http://reillyblog.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIsZi9UpqfZIdKFyERAlNEAJ4hC0BBk9Bv3JDik0O0fq4GjY+9WwCfaCM6 C5hGaTxK+7m6nTHjZmHAhx0= =+pXM -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 08/24/2008 10:57 AM, Chuck Payne wrote:
Guy,
My main partion, crash. I am getting I/O errors, which I know means the drive is dead. What I need is to get on that partition so I can get my config off or any thing that I can. I have ran reiserfsck --fix-fixable, I get these error, cannot read teh bock 5672. reiserfsck is tell me I can use a -B flag to fix it but when I try to use that flag, I get the help menu. Please some know what I can do to get my data.
I had a worse situation. I had /home and /usr/local on a 40GB drive and the root partition on a 120. I would backup my /home to the 120 every night. Then I installed SuSE 11.0 and I bought a new computer. before I had transferred my stuff to the new computer I was not able to boot the old computer. I found the 40GB drivce would not even spin up. The 120 was fine, but I found that I had forgotten to restart my nightly backup, so my /home backup was a month out of date, and there were some important emails I couldn't get to. Then, to my consternation, the nightly backup would not fully unbzip. The reason is that I had installed Virtual Box, and the VDI file was > 4G. In any case, I can't blame it on SuSE :-). I then put the 40G in a USB case, but it still would not spin up. I tried a few things including placing the drive in the freezer. I thought that was dumb, but some IT people I know have done this successfully. I finally sent it out to be recovered costing me a few cents. BTW: I do have a good backup from a year ago, but my checkbook is also one of the unrecoverable files and updating it from the last year is cumbersome, and makes it worth paying for the recovery. My suggestion to you is if you cannot physically retrieve the data, then you might be successful sending it to a data recovery company. There are a couple that charge under $300 if they recover, if not they'll send the drive back to you or send it to a clean-room capable company that can recover it. The problem with trying to repair the file system could possibly make things worse. In my research I did look at a lot of data recovery companies. Some will charge you a fee just to look at the drive. There is a firm in Cambridge, Ma that charges $595. If they can't recover the data you lose the $95. If they can, it could be well over $1000. In my case, my drive supposedly had a massive head crash, but I doubt it. I think the company I sent it to essentially works with screwed up filesystems, and send out damaged drives to real recovery companies. But, my data was 100% restored and is enroute back to me. -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id: 537C5846 PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB CA3B 4607 4319 537C 5846
participants (7)
-
Amedee Van Gasse -
Chuck Payne -
Jerry Feldman -
N B Day -
Rajko M. -
Shawn Holland -
steve