LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices


Reply
  Search this Thread
Old 04-21-2012, 11:22 AM   #1
abd_bela
Member
 
Registered: Dec 2002
Location: algeria
Distribution: redhat 7.3, debian lenny
Posts: 623

Rep: Reputation: 31
how to retrieve info from a bad disk?


hi,
I have a disk ( I tera Bytes it contains important data!!!) formatted with nfts,
somebody used it in wind$ a virus seems destroy "something" in partition table ???!!

Now no access is possible, although the partition is recognized as /dev/sdb1 with correct sie, but no possibility to
retive files.
I tried ntfs-3g /dev/sdb1 t gave segmentaion fault
I tried testdisk it analysed the disk and gathered the data, I tried to list the files , it gave same error as ntfs-3g, I mean segmentation fault??


Is there another rescue software ??
thanks for help

regards
 
Old 04-21-2012, 11:28 AM   #2
zakame
Member
 
Registered: Apr 2012
Distribution: Debian, Ubuntu, Slackware
Posts: 258

Rep: Reputation: 162Reputation: 162
Have you tried testdisk's partner, photorec?
 
Old 04-21-2012, 01:13 PM   #3
abd_bela
Member
 
Registered: Dec 2002
Location: algeria
Distribution: redhat 7.3, debian lenny
Posts: 623

Original Poster
Rep: Reputation: 31
Hi,
Yes I tried it !!
I used ntfs-3g too here is the test:

I check ntfs-3g ( tool on linux to manage ntfs file system) to fix the error.

ntfsfix /dev/sdc1 gives the output: mft corrupted ... is there a chance to recover something ???


"
Mounting volume... MFT is corrupt, cannot read its unmapped extent record 280867
Note : chkdsk cannot fix this, try ntfsfix
Inode is corrupt (0): Input/output error
Failed to load runlist for $MFT/$DATA.
highest_vcn = 0x3, last_vcn - 1 = 0x1a53f
Failed to load $MFT: Input/output error
FAILED
Attempting to correct errors... MFT is corrupt, cannot read its unmapped extent record 280867
Note : chkdsk cannot fix this, try ntfsfix
Inode is corrupt (0): Input/output error
Failed to load runlist for $MFT/$DATA.
highest_vcn = 0x3, last_vcn - 1 = 0x1a53f
Failed to load $MFT: Input/output error
FAILED
Failed to startup volume: Input/output error
Checking for self-located MFT segment... ntfs_mst_post_read_fixup_warn: magic: 0xc0468167 size: 1024 usa_ofs: 43309 usa_count:
58159: Invalid argument
OK
MFT is corrupt, cannot read its unmapped extent record 280867
Note : chkdsk cannot fix this, try ntfsfix
Inode is corrupt (0): Input/output error
Failed to load runlist for $MFT/$DATA.
highest_vcn = 0x3, last_vcn - 1 = 0x1a53f
Failed to load $MFT: Input/output error
"


thanks a lot
regards
bela
 
Old 04-21-2012, 03:53 PM   #4
widget
Senior Member
 
Registered: Oct 2008
Location: S.E. Montana
Distribution: Debian Testing, Stable, Sid and Manjaro, Mageia 3, LMDE
Posts: 2,628

Rep: Reputation: 496Reputation: 496Reputation: 496Reputation: 496Reputation: 496
I think you may be best off to quit while you are ahead and get professional help if the data is important.

Testdisk was probably your best chance.

Every time you do anything with that drive it makes it harder to recover the data.

When you do get it straightened out, one way or the other, think seriously about partitioning the thing into something like 400 or 500gig partitions. One huge partitions is kind of putting all your eggs in one basket.
 
Old 04-21-2012, 04:29 PM   #5
craigevil
Senior Member
 
Registered: Apr 2005
Location: OZ
Distribution: Debian Sid
Posts: 4,734
Blog Entries: 12

Rep: Reputation: 463Reputation: 463Reputation: 463Reputation: 463Reputation: 463
Safecopy is a data recovery tool which tries to extract as much data as
possible from a seekable, but problematic (i.e. damaged sectors) source - like
floppy drives, harddisk partitions, CDs, ..., where other tools like dd would
fail due to I/O errors.
Homepage: http://safecopy.sourceforge.net

gddrescue
Quote:
The gddrescue tool copies data from one file or block device
(hard disc, cdrom, etc) to another, trying hard to rescue data
in case of read errors.
.
gddrescue does not truncate the output file if not asked to.
So, every time you run it on the same output file, it tries to
fill in the gaps.
.
The basic operation of gddrescue is fully automatic. That is,
you don't have to wait for an error, stop the program, read the
log, run it in reverse mode, etc. If you use the logfile
feature of gddrescue, the data is rescued very efficiently (only
the needed blocks are read). Also you can interrupt the rescue
at any time and resume it later at the same point.
.
Automatic merging of backups: If you have two or more damaged
copies of a file, cdrom, etc, and run gddrescue on all of them,
one at a time, with the same output file, you will probably
obtain a complete and error-free file. This is so because the
probability of having damaged areas at the same places on
different input files is very low. Using the logfile, only the
needed blocks are read from the second and successive copies.
.
The logfile is periodically saved to disc. So in case of a crash
you can resume the rescue with little recopying. Also, the same
logfile can be used for multiple commands that copy different
areas of the file, and for multiple recovery attempts over
different subsets.
.
gddrescue aligns its I/O buffer to the sector size so that it
can be used to read from raw devices. For efficiency reasons,
also aligns it to the memory page size if page size is a
multiple of sector size.
.
Please note that this is the GNU ddrescue version providing
the /sbin/ddrescue executable. If you are searching for the
ddrescue version of Kurt Garloff please check out the
ddrescue package instead.
Homepage: http://www.gnu.org/software/ddrescue/ddrescue.html
 
Old 04-21-2012, 05:33 PM   #6
widget
Senior Member
 
Registered: Oct 2008
Location: S.E. Montana
Distribution: Debian Testing, Stable, Sid and Manjaro, Mageia 3, LMDE
Posts: 2,628

Rep: Reputation: 496Reputation: 496Reputation: 496Reputation: 496Reputation: 496
Learn something new all the time around here.

Both packages in the Debian repos too.
 
Old 04-25-2012, 04:07 AM   #7
Smokin...
LQ Newbie
 
Registered: Jan 2004
Distribution: Debian
Posts: 18

Rep: Reputation: 0
Talking how to retrieve info from a bad disk?

Hi,

I had a similar problem. Finally resolved it by:

1. Restarting server using 'Live Debian' Squeeze.
2. Install lvm: aptitude install lvm.
3. After install, partitions appeared in file manager, selected required partition.
4. Inserted USB Stick.
5. Copied required files to USB stick.

DONE!

Regards
Nick
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
How to retrieve info about drivers? linuxunix Linux - Newbie 6 04-29-2010 04:51 AM
Bad disk, bad disk controller, or bad memory? NULL Pointer Linux - General 2 03-01-2009 06:21 PM
getent is unable to retrieve info from OpenLDAP mesh2005 Linux - Networking 1 11-08-2007 09:25 AM
help trying to retrieve info from raid or another hge3 newusermike Linux - Newbie 4 07-30-2005 07:46 PM
Best way to retrieve system and hardware info vharishankar Programming 5 04-11-2005 07:29 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian

All times are GMT -5. The time now is 10:48 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration