On 09/24/2012 03:30 PM, STeve Andre' wrote: > Is there a way, with something like the scsi(1) command, to tell > the sd driver to ignore the error below? I've some data on this > disk that I'd like to get back. I realize that all hell may break > loose trying something like this but I'd like to try.. Any other > ideas on how to get the disk stable enough to look at a few > files would be appreciated. I have a backup but wouldn't mind > the latest data. > > tnx, STeve Andre' > > > > Sep 24 15:22:18 paladin /bsd: umass0 at uhub0 > Sep 24 15:22:18 paladin /bsd: port 1 configuration 1 interface 0 > "JMicron USB to ATA/ATAPI Bridge" rev 2.00/1.00 addr 2 > Sep 24 15:22:18 paladin /bsd: umass0: using SCSI over Bulk-Only > Sep 24 15:22:18 paladin /bsd: scsibus4 at umass0: 2 targets, initiator 0 > Sep 24 15:22:18 paladin /bsd: sd3 at scsibus4 targ 1 lun 0: <WDC WD25, > 00JS-75NCB3, > SCSI2 0/direct fixed serial.152d2352DCA4469971FF > Sep 24 15:22:18 paladin /bsd: sd3: 238418MB, 512 bytes/sector, > 488281250 sectors > Sep 24 15:22:18 paladin /bsd: sd3(umass0:1:0): Check Condition (error > 0x70) on opcode 0x28 > Sep 24 15:22:18 paladin /bsd: SENSE KEY: Media Error > Sep 24 15:22:18 paladin /bsd: ASC/ASCQ: Unrecovered Read Error > Sep 24 15:22:18 paladin /bsd: sd3(umass0:1:0): Check Condition (error > 0x70) on opcode 0x28 > Sep 24 15:22:18 paladin /bsd: SENSE KEY: Media Error > Sep 24 15:22:18 paladin /bsd: ASC/ASCQ: Unrecovered Read Error > Sep 24 15:22:18 paladin /bsd: sd3(umass0:1:0): Check Condition (error > 0x70) on opcode 0x28 > Sep 24 15:22:18 paladin /bsd: SENSE KEY: Media Error > Sep 24 15:22:18 paladin /bsd: ASC/ASCQ: Unrecovered Read Error It's unlikely that anything would help. This looks like reading block 0 fails. If the disk goes click-click-click, nothing will help.
Attempting to mount any partition will probably fail. Try: dd if=/dev/rsd3c of=/dev/null count=1 skip=50000 If this command succeeds, then you have a chance of finding something. You have two options: search through the raw disk for possibly useful data or attempt to make a partial disk image on a new drive, filling in the correct fdisk and disklabel data. In either case, don't attempt any operation on block 0 or anything in the first (say) 1000 blocks. If you get errors from attempting to read blocks far away from 0, it's likely that the disk is now a paperweight or a source of two powerful magnets. Geoff Steckel
