Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello,
To fix a hdd ext3 crash, I tried testdisk but it cannot do deep job or much actually.
Is there any non free programs or opensources programs to fix our harddisk crashes, when it happens ??
The testdisk program after deep searching gives me two possibilities of my crashed (ext3-20gb ext3-140gb swap-855mb) ; the testdisk after depe seeking tells me :
thanks, but well the thing is that the headers of the harddisk are totally crashed. the harddisk is partitionned in 3 partitions : ext3 ext3 and a swap, but the linux cannot see them at all...
DESCRIPTION
fsck is used to check and optionally repair one or more Linux file systems. filesys can be a device name (e.g. /dev/hdc1, /dev/sdb2), a mount point (e.g. /, /usr,
/home), or an ext2 label or UUID specifier (e.g. UUID=8868abf6-88c5-4a83-98b8-bfc24057f7bd or LABEL=root). Normally, the fsck program will try to handle filesystems on
different physical disk drives in parallel to reduce the total amount of time needed to check all of the filesystems.
thanks, but well the thing is that the headers of the harddisk are totally crashed. the harddisk is partitionned in 3 partitions : ext3 ext3 and a swap, but the linux cannot see them at all...
would fsck work in such case ?
it says:
Use testdisk to get the partition table straightened out and then use fsck to fix the file systems once the partitions are OK.
If you can't get testdisk to fix the partition table then you are probably out of luck.
Use testdisk to get the partition table straightened out and then use fsck to fix the file systems once the partitions are OK.
If you can't get testdisk to fix the partition table then you are probably out of luck.
-------------------
Steve Stites
TESTDISK:
nope
testdisk do not see the in between partition ext3
It confuse the two ext3 in one, looks like (deeper search);
or he says it's a ntfs with wrong size a bit. When you say it's a 83 type partition (the in between), it tells you that you that no data in it. Also the testdisk, I am not sure that he let me write those 3 partitions since it did see not much. ... pffff not enough possibility with that tool.
I am wondering why it is so famous. Just simple headers crash and the testdisk is not capable of fixing. The data are just messed up in the disk (full 100 pct), that's why the harddisk crash happened (and no regular fsck)).
I'll try the alternative ... you proposed. lot of luck you told me/passed by !!
I hope there is more ... welll in case this one does not do the job... Let's hope !
Also, do search the forums a bit, I've posted this before, for sure at least 2-3 times.
Installed. Well ... foremost recovers from a disk image
I just would like to reset the 20GB / 140GB / 855MB, write and then to read files of the cluster per cluster the middle partition and write the partition file header... (on real disk)... (since not big crash)
Code:
SYNOPSIS
foremost[-h][-V][-d][-vqwQT][-b<blocksize>][-o<dir>] [-t<type>][-s<num>][-i<file>]
BUILTIN FORMATS
Recover files from a disk image based on file types specified by the user using the -t switch.
jpg Support for the JFIF and Exif formats including implementations used in modern digital cameras.
gif
Filling up a disk to onehundred percent doesn't kill the partition table, so maybe explain in detail what you really did. What version of Testdisk are you running? Where are you running it from? Another on-disk distro or Live CD? Was this drive previously partitioned differently (so the NTFS isn't a programmatical glitch)? Was it ever (re)partitioned with some Windows tool like Partition Magic or other (partition order)? Did the quick scan ever show any partitions marked in green? If you know (verify!) the disk geometry, does setting it explicitly show other results? Did you check the advanced options like expert mode, boundaries and partial cylinders before doing a deep search? Can you run deep mode again with the "/log" setting, upload or pastebin the log somewhere and post the URI here?
Quote:
Originally Posted by H_TeXMeX_H
No, you're not out of luck, try foremost.
Foremost is for header and footer-based file recovery, not for partition table recovery, AFAIK. Maybe you got confused because of Testdisks companion app Photorec which is kinda like Foremost?
Foremost is for header and footer-based file recovery, not for partition table recovery, AFAIK. Maybe you got confused because of Testdisks companion app Photorec which is kinda like Foremost?
Yes, I know that, I was responding mostly to this comment:
Quote:
Originally Posted by jailbait
If you can't get testdisk to fix the partition table then you are probably out of luck.
I was saying, you're not quite out of luck yet if testdisk doesn't work. You can still recover files from the disk with foremost. That's all. First, try to use testdisk, that would be the best way to recover your data, but often it doesn't work, in which case use foremost to get the files off of there.
Filling up a disk to onehundred percent doesn't kill the partition table, so maybe explain in detail what you really did. What version of Testdisk are you running? Where are you running it from? Another on-disk distro or Live CD? Was this drive previously partitioned differently (so the NTFS isn't a programmatical glitch)? Was it ever (re)partitioned with some Windows tool like Partition Magic or other (partition order)? Did the quick scan ever show any partitions marked in green? If you know (verify!) the disk geometry, does setting it explicitly show other results? Did you check the advanced options like expert mode, boundaries and partial cylinders before doing a deep search? Can you run deep mode again with the "/log" setting, upload or pastebin the log somewhere and post the URI here?
Foremost is for header and footer-based file recovery, not for partition table recovery, AFAIK. Maybe you got confused because of Testdisks companion app Photorec which is kinda like Foremost?
I used knoppix live cd, and then in /tmp downloaded teh wip 6.10
the log is not saying much since nothing is done by testdisk
by the way which log / where is the log ?
testdisk.log says:
Code:
Fri Apr 25 19:44:25 2008
Command line: TestDisk
TestDisk 6.9, Data Recovery Utility, February 2008
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org
Linux version (ext2fs lib: 1.39, ntfs lib: 10:0:0, reiserfs lib: 0.3.1-rc8, ewf lib: 20070512)
Hard disk list
Disk /dev/hdf - 730 MB / 696 MiB - CHS 23 255 63 (RO), sector size=2048 - LITE-ON DVDRW SHM-165P6S
Disk /dev/sda - 250 GB / 232 GiB - CHS 30401 255 63, sector size=512 - ATA MAXTOR STM325082
TestDisk exited normally.
made with 6.9 that day.
all went super until harddisk reached 100pct with downloading a big then problem started ;
I had a .dmrc error at the gdm and segmentation. I used mv and rm command lines to make bit space in my harddisk.
i removed lot of games deleted ISO cdroms. and rebooted again
still that .dmrc at gdm boot, did e2fsck and all disk got crashed.
If 100pct isnt for something, well, not true, since the pc is runnign since 3 years (lower than 100pct full) (/home went 100pct full).
Last edited by frenchn00b; 04-27-2008 at 01:32 PM.
I was saying, you're not quite out of luck yet if testdisk doesn't work.
I see, other angle.
Quote:
Originally Posted by frenchn00b
testdisk.log says
It doesn't list any disk with a capacity of 160GB.
Quote:
Originally Posted by frenchn00b
did e2fsck and all disk got crashed.
Can you recall if you ran fsck in automatic mode? Any errors it spat out? What does "all disk got crashed" mean? You mean *during* fscking the disk? Any crash messages?
And was this drive previously partitioned differently (so the NTFS isn't a programmatical glitch)? Was it ever (re)partitioned with some Windows tool like Partition Magic or other (partition order)? Did analysing with testdisk ever mark any partitions green? If you know (verify!) the disk geometry, does setting it explicitly show other results? Did you check the advanced options like expert mode, boundaries and partial cylinders before doing a deep search?
It doesn't list any disk with a capacity of 160GB.
Can you recall if you ran fsck in automatic mode? Any errors it spat out? What does "all disk got crashed" mean? You mean *during* fscking the disk? Any crash messages?
And was this drive previously partitioned differently (so the NTFS isn't a programmatical glitch)? Was it ever (re)partitioned with some Windows tool like Partition Magic or other (partition order)? Did analysing with testdisk ever mark any partitions green? If you know (verify!) the disk geometry, does setting it explicitly show other results? Did you check the advanced options like expert mode, boundaries and partial cylinders before doing a deep search?
Thanks! Well I try to give a reply asap of that. I am trying again...
Oh .. I have a btw-question for you, Unspaw, since you are expert in replying difficult linux-questions. I just installed a linux pc with a very large flat screen, with great contrast (samsung), on my big fridge in my kitchen... looks like hi-tech kitchen Well would you know if there is a way that I can dictate with voice to my fridge (well the pc next to) my shopping-list. would you know a lightweight possibility (since you know so much with linux) that would possibly work (ie a voice recognition with learning would be greatest (not a wined DragonNat.Speaking))?
Last edited by frenchn00b; 04-28-2008 at 02:24 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.