There is probably a mess of the "Drive not ready" errors in your dmesg output (or var log syslog).
dd will fail when it encounters errors. What you are looking for is ddrescue which ignores errors. If you have enough space elsewhere on the network you might be able to get away with an rsync, though you'll have to successfully mount the partition first (try -o ro). Best of luck. On Friday 15 July 2005 16:27, Shawn wrote: > More on this. No matter what I try to do, I can't mount the partition. So > I tried the "fsck.reiserfs --rebuild-tree" option. this failed with the > following: > > 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 (1713): (Input/output error). > > Aborted > > So, it appears I have a bad block somewhere critical. Next I tried to use > "dd" to backup the partition before doing anything more drastic. This > resulted in the following: > > sage workspace # dd if=/dev/hda4 of=home_backup > dd: reading `/dev/hda4': Input/output error > 13776+0 records in > 13776+0 records out > > so is there anyway I can get to the data on this partition?? I guess I'm > looking at rebuilding my workstation this weekend.... again.... :( > > Thanks for any tips. > > Shawn > > On Friday 15 July 2005 13:53, Shawn wrote: > > I was working late last night when my workstation started behaving badly > > - running apps freezing, new processes taking forerver to start, etc. > > So, I decided to shut down the system, and reboot. I had to go to tty1 > > to make this happen - KDE/X refused to behave by this point. > > > > Once I restarted, KDE started behaving as though it had never been run > > before. So I switched to console mode and began investigating. Turns out > > that /home was not mounted. That explains KDE acting like a new install, > > but this doesn't explain the underlying problem. > > > > When I try to mount /home manually I get the following error: > > mount: wrong fs type, bad option, bad superblock on /dev/hda4, > > or too many mounted file systems > > _______________________________________________ > clug-talk mailing list > [email protected] > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying
pgpxEtaaTg4PE.pgp
Description: PGP signature
_______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
