Jim, after I learned what a Konsole is and then copied the output to a
floppy, here is what dmesg | grep hd returned in a system where a disk with
Mandrake was master and the sick drive was slave:
hda: task_no_data_intr: error=0x04 { DriveStatusError }
hda: 15698592 sectors (8038 MB) w/69KiB Cache, CHS=1038/240/63
hdb: attached ide-disk driver.
hdb: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: task_no_data_intr: error=0x04 { DriveStatusError }
hdb: 8404830 sectors (4303 MB) w/128KiB Cache, CHS=555/240/63
ide-cd: passing drive hdc to ide-scsi emulation.
ide-cd: passing drive hdd to ide-scsi emulation.
hdc: attached ide-scsi driver.
hdd: attached ide-scsi driver.
hda: hda1 hda2 < hda5 hda6 >
hdb: [PTBL] [523/255/63] hdb1
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8404760,
sector=8404760
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8404760,
sector=8404760
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8404760,
sector=8404760
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8404760,
sector=8404760
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8404760,
sector=8404760
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8404760,
sector=8404760
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8404760,
sector=8404760
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8404760,
sector=8404760
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8404760,
sector=8404760
end_request: I/O error, dev 03:40 (hdb), sector 8404760
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8404760,
sector=8404760
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8404760,
sector=8404760
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8404760,
sector=8404760
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8404760,
sector=8404760
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8404760,
sector=8404760
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8404760,
sector=8404760
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8404760,
sector=8404760
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8404760,
sector=8404760
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8404760,
sector=8404760
end_request: I/O error, dev 03:40 (hdb), sector 8404760
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8403864,
sector=8403864
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8403864,
sector=8403864
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8403864,
sector=8403864
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8403864,
sector=8403864
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8403864,
sector=8403864
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8403864,
sector=8403864
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8403864,
sector=8403864
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8403864,
sector=8403864
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8403864,
sector=8403864
end_request: I/O error, dev 03:40 (hdb), sector 8403864
knoppix at ttyp0[knoppix]$
Also I do not have the dd_rescue utility installed as that is presently
beyond my capabilty to download and compile or something like that. If a
dos bootdisk showed C: (I think it does) would A:\fdisk /mbr or sys C: do
any harm to this disk?
----- Original Message -----
From: "Jim Crumley" <crumley at belka.space.umn.edu>
To: "TCLUG Mailing List" <tclug-list at mn-linux.org>
Sent: Thursday, April 22, 2004 2:52 PM
Subject: Re: [TCLUG] Can This Drive be Resurrected?
> On Tue, Apr 20, 2004 at 07:19:27PM -0500, Lawrence Clemens wrote:
> > This is an update.....
> >
> >
> >
> > Background: I thoughtlessly smoked my wife's friend's HD by reversing
the
> > power plug to the drive. Although I have reached geezerhood status, I
still
> > do stupid things. I also volunteer at rehabbing computer donations for
a
> > non-profit, and I keep an eye on linux as a possible low cost operating
> > system for our low-income, computer unsavvy clients. But as you know
> > everything we get is Windows based.
>
> <snip>
>
> > Brian also suggested dd ing the drive and pulling an image and then TCT
for
> > data. Dan Rue suggested a similar approach with dd. Ben Maas suggested
> > using dd_rescue
> > (http://www.garloff.de/kurt/linux/ddrescue/ and gave me a script
> >
> > cd ~
> > mkdir recover
> > cd recover
> > dd_rescue /dev/hdb ./bad_disk.img
> > ... up to several hours later ...
> > dosfsck -a -V ./bad_disk.img
> > mount ./bad_disk.img /mnt/tmp
> > ls /mnt/tmp
> >
> > This sounds like a very powerful approach at the dd_rescue web page,
what I
> > could understand of it.
> >
> <snip>
> >
> > So that's the update. Thanks to Brian for prodding me along. It could
be
> > a long summer, but apart from the volunteer thing that is heating up, I
may
> > yet conquer linux - out here in the garage with the dog and out of my
wife's
> > baleful eye. Mandrake 10 looks promising.
>
> Ok, I should have read more carefully before. You don't need to
> mount a drive in order to copy using dd. The hard drive icon
> that Knoppix gave you is just a convenience. It does not really
> mean that Knoppix is having any more luck with the drive than
> Mandrake.
>
> The list of commands you have above should work equally well for
> either Knoppix or Mandrake, assuming dd_rescue is installed. One
> important point is that you will have to run these commands as
> root. Also, for the mount command you will probably need to use
> something more like:
> mount -t vfat -o loop ./bad_disk.img /mnt
> where the thing -t is whatever filesystem type you are trying to
> recover - probably either vfat or ntfs.
>
> Anyway, run these commands from a Konsole or xterm, and report
> back your results.
>
> Hopefully this will work.
>
> --
> Jim Crumley |Twin Cities Linux Users Group Mailing List
(TCLUG)
> crumley at fields.space.umn.edu |Minneapolis/St. Paul, Minnesota
> Ruthless Debian Zealot |http://www.mn-linux.org/
> Never laugh at live dragons |Dmitry's free,Jon's next?
http://faircopyright.org
>
> _______________________________________________
> TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
> http://www.mn-linux.org tclug-list at mn-linux.org
> https://mailman.real-time.com/mailman/listinfo/tclug-list
_______________________________________________
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
http://www.mn-linux.org tclug-list at mn-linux.org
https://mailman.real-time.com/mailman/listinfo/tclug-list