Filesystem seems damaged

Using TestDisk to repair the filesystem
Message
Author
gerone
Posts: 4
Joined: 27 Mar 2012, 06:30

Filesystem seems damaged

#1 Postby gerone » 27 Mar 2012, 07:08

I have an HP Pavilion Elite whose Mobo failed and appears to have damaged the HDD. After reading through this active forum, I transferred the HDD to a working PC and have gone through the steps using TestDisk. The HDD had two partitions and initially, TestDisk could only find one used by HP labeled as its Factory_image but could not find the main bootable partition. Through the forums, I learned to change the Geometry from 255 to 240 as the Quick Search and Deep Search could not find the partition. Deep Search ultimately found the partition with the change in Geometry. However, choosing "P:" to list files wouldn't work saying that it 'Can't open filesystem. Filesystem seems damaged'. Nonetheless, the partition structure was saved as instructed. It then stated that my boot sector was Bad but the Backup boot sector was OK. I then chose [Backup BS] to copy the backup into the boot sector and it reported it to have done so and instructed me to reboot. However, after the reboot, this partition still remained raw to Windows. I ran TestDisk again to check and it seems to recognize the partition but could not list its files stating that it "Can't open filesystem. Filesystem seems damaged." Is there anything else I can do? I appreciate your help and grateful that people like you in this forum are out there extending their expertise to home users like us who are in need to recover from such a mishap. Thanks.

Sponsored links

User avatar
Fiona
Posts: 2839
Joined: 18 Feb 2012, 17:19
Location: Ludwigsburg/Stuttgart - Germany

Re: Filesystem seems damaged

#2 Postby Fiona » 27 Mar 2012, 07:52

3.5 inches HDD's normally using 255 heads.
What OS did you use on your previous HP and now.
It's recommendable not to change anything to your HDD anymore.
Can you repeat your diagnose using TestDisk 6.14-32bit?
I'd need infos from Analyse (current partition structur), Quick Search (result) and Deeper Search (result
).
Please upload the testdisk.log.
In case, you must zip or rename it to testdisk.txt.
You can also copy and paste the content.

gerone
Posts: 4
Joined: 27 Mar 2012, 06:30

Re: Filesystem seems damaged

#3 Postby gerone » 27 Mar 2012, 12:24

Thank you for responding Fiona. Does this mean that I should have used 255 heads instead of 240? I switch only because it did not find the partition and this message appeared:

pTestDisk 6.14-WIP, Data Recovery Utility, March 2012
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org

Disk /dev/sdb - 320 GB / 298 GiB - CHS 38913 255 63

Warning: the current number of heads per cylinder is 255
but the correct value may be 240.
You can use the Geometry menu to change this value.
It's something to try if
- some partitions are not found by TestDisk
- or the partition table can not be written because partitions overlaps.


The OS in the defunct HP Pavilion Elite was Windows7 but it was originally Vista (upgraded a year after). The PC I am using now to run TestDisk is running Vista. Based on the header above, I am running TestDisk 6.14-32 bit right?

I have rerun Analyse, quick Search and currently running Deeper Deeper Search with a new log and will copy/paste it on a different reply box (don't know how to upload it in this forum).

gerone
Posts: 4
Joined: 27 Mar 2012, 06:30

Re: Filesystem seems damaged

#4 Postby gerone » 27 Mar 2012, 13:45

Attached here is the log file as a result of the rerun of the Analyse, Quick Scan and Deep Scan. Sincerely appreciate your attention to the matter, Fiona.
Attachments
testdisk rerun.zip
log file of the rerun of Analyze and scans
(1.87 KiB) Downloaded 228 times

gerone
Posts: 4
Joined: 27 Mar 2012, 06:30

Re: Filesystem seems damaged

#5 Postby gerone » 27 Mar 2012, 13:51

As added information, I have some screen captures on when I started to use TestDisk in searching for the partition, switching the Geometry to 240, performing Deep Scan to find it, writing, then copying the backup boot sector to the bad boot sector. I hope these screen captures can facilitate your study of my dilemma. I can't thank you enough.
Attachments
test disk v1.zip
screen captures
(238.89 KiB) Downloaded 356 times

User avatar
Fiona
Posts: 2839
Joined: 18 Feb 2012, 17:19
Location: Ludwigsburg/Stuttgart - Germany

Re: Filesystem seems damaged

#6 Postby Fiona » 06 Apr 2012, 19:02

TestDisk found your partition using 240 heads.
Unfortunately, it looks like, that your file system is damaged.
You could give PhotoRec a try to find important files.
http://www.cgsecurity.org/wiki/PhotoRec

codrut
Posts: 1
Joined: 30 Dec 2013, 00:53

Re: Filesystem seems damaged

#7 Postby codrut » 30 Dec 2013, 01:11

I've used testdisk 6.14 -64bit to check a SSD that crashes when reading certain files.

It's a 120GB Kingston HyperX drive, that used to have Windows Vista on it (NTFS).

Initial Analyse couldn't read any partition information, even I could use the drive until accessing some of the files.
A linux benchmark gave me the following error, before using testdisk:
Bad Cluster 0xa26bc, on SH103S3120G ATA KINGSTON
telling me that I have a index referenced twice.

I've deleted the partiotion, formated the drive NTFS, and re-run the testdisk.
I had to rewrite the MBR before it saw my partition informatio.

After detecting partitions, when I've tryed to access the files (shortcut P) it says "Filesystem seems damaged".
Do you think this is a logical, or hardware error?

The drive haven't suffered any physical type of damage.

For any case, I've wanted to upload the zipped .log file (but stil large - 4MB) - the original have 70MB
I've cut the begin and end of it ...

Thanks you in advance,
Codrut

testdisk-cutted.zip
Testdisk log after analyse (cut the middle)
(2.31 KiB) Downloaded 143 times

User avatar
cgrenier
Site Admin
Posts: 3072
Joined: 18 Feb 2012, 15:08
Location: Le Perreux Sur Marne, France
Contact:

Re: Filesystem seems damaged

#8 Postby cgrenier » 04 Jan 2014, 10:49

The log shows a lot of errors: "Data error (cyclic redundancy check)".
It's a hardware problem. Use the warranty to get a new disk.


Return to “Filesystem repair”

Who is online

Users browsing this forum: No registered users and 2 guests