help! can i recover my data?

[gaf-mNDKBlG2WHs at public.gmane.org (Jerry Feldman)]

If all else fails, there are some good (and bad) companies who can get
your data off. last year I had a similar predicament, and I ended up
sending my drive to one of the recovery companies where the data was
completely recovered. Actually, I sent it to one place, and they told me
they could not recover it, so they shipped it free of charge to ESS Data
Recovery who gave me a 10% discount. The data  was completely recovered,
and they sent me a USB 250GB drive for the price of a 150 as they were
out of stock. While much of my data was backed up, the backup itself was
damaged, and what I wanted to recover was my checkbook and 10 years
worth of email. I did some research to make sure that the company was
reliable. The first place I looked at was in Cambridge, but after
calling them and looking at complaints I decided to do what I did. Some
companies get quite a bit of cash up front, even if they can't recover
any data. Some, do not charge you anything if they are unable to recover.=


On 08/13/2009 06:17 PM, Robert La Ferla wrote:
> Is it possible for me to recover my data?  I saw errors in the logs =20
> (see below) and tried fscking the drive (see part of the log below - =20
> in the middle of this email) and then now when I try to fsck I get this=
:
>
>
> Current situation:
>
> # fsck /dev/sdc1
> fsck 1.40.6 (09-Feb-2008)
> e2fsck 1.40.6 (09-Feb-2008)
> fsck.ext2: Attempt to read block from filesystem resulted in short =20
> read while trying to open /dev/sdc1
> Could this be a zero-length partition?
>
>
>
> Previous attempts at fsck:
>
>
>
> # fsck /dev/sdc1
> fsck 1.40.6 (09-Feb-2008)
> e2fsck 1.40.6 (09-Feb-2008)
> Superblock has an invalid ext3 journal (inode 8).
> Clear<y>? yes
>
> *** ext3 journal has been deleted - filesystem is now ext2 only ***
>
> /dev/sdc1 contains a file system with errors, check forced.
> Pass 1: Checking inodes, blocks, and sizes
> Error reading block 65538 (Attempt to read block from filesystem =20
> resulted in short read) while getting next inode from scan.  Ignore =20
> error<y>? yes
>
> Force rewrite<y>? yes
>
> Error reading block 65539 (Attempt to read block from filesystem =20
> resulted in short read) while getting next inode from scan.  Ignore =20
> error<y>? yes
>
> Force rewrite<y>? yes
>
> ...
> ....
>
>
> I was getting these errors:
>
> 98/00:00:39:00:00/e0 tag 0 dma 32768 in
>           res 51/40:00:11:5c:98/00:00:39:00:00/f0 Emask 0x9 (media =20
> error)
> ata5.00: status: { DRDY ERR }
> ata5.00: error: { UNC }
> ata5.00: configured for UDMA/100
> ata5: EH complete
> ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> ata5.00: BMDMA2 stat 0x181c8109
> ata5.00: cmd 25/00:40:0f:5c:98/00:00:39:00:00/e0 tag 0 dma 32768 in
>           res 51/40:00:11:5c:98/00:00:39:00:00/f0 Emask 0x9 (media =20
> error)
> ata5.00: status: { DRDY ERR }
> ata5.00: error: { UNC }
> ata5.00: configured for UDMA/100
> ata5: EH complete
> ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> ata5.00: BMDMA2 stat 0x181c8109
> ata5.00: cmd 25/00:40:0f:5c:98/00:00:39:00:00/e0 tag 0 dma 32768 in
>           res 51/40:00:11:5c:98/00:00:39:00:00/f0 Emask 0x9 (media =20
> error)
> ata5.00: status: { DRDY ERR }
> ata5.00: error: { UNC }
> ata5.00: configured for UDMA/100
> ata5: EH complete
> ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> ata5.00: BMDMA2 stat 0x181c8109
> ata5.00: cmd 25/00:40:0f:5c:98/00:00:39:00:00/e0 tag 0 dma 32768 in
>           res 51/40:00:11:5c:98/00:00:39:00:00/f0 Emask 0x9 (media =20
> error)
>
>
> _______________________________________________
> Discuss mailing list
> Discuss-mNDKBlG2WHs at public.gmane.org
> http://lists.blu.org/mailman/listinfo/discuss
>
>  =20


--=20
Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org>
Boston Linux and Unix
PGP key id: 537C5846
PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB  CA3B 4607 4319 537C 5846