Need help with scrambled up harddisk

  • Thread starter Thread starter tommu
  • Start date Start date
T

tommu

First of all I have to tell that I have got almost 0 experience with
harddisk
crashes so I prefer that any answer someone might give would be easy
for newbie
in these matters:

I have 160gt samsung harddisk which is partitioned to 3 partitions all
of them
are ntfs but somewhy I cannot access the first partition (my main
harddisk
crashed 1 day ago and I had a chance to backup my data to this
samsungs
last partition which had enought free space to hold almost all of my
important
things before I begun to backup my data I watched all the partitions
and I
could access them all but after the backing up was done and I did the
same
thing it begun to complain) it just says:
D:\ is not accessible
The parameter is incorrect.

I looked up these posts a bit and found some tools called findpart and
findntfs
findpart results this with command "findpart 2":

Disk: 2 Cylinders: 19457 Heads: 255 Sectors: 63 MB: 152625

--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
0 - 07 63104856192 51199 0 1 1 6526 254 63 B OK
0 - 07104856255104856255 51199 6527 0 1 13053 254 63 B OK
0 - 07209712510102864195 50226 13054 0 1 19456 254 63 B OK

No FATs found.

Partitions according to partition tables on second harddisk:

--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
0 1 07 63104856192 51199 0 1 1 6526*254 63 OK OK
0 2 07104856255104856255 51199 6527* 0 1 13053*254 63 OK OK
0 3 07209712510102864195 50226 13054* 0 1 19456*254 63 OK OK

and this with "findpart tables":

Disk: 2 Cylinders: 19457 Heads: 255 Sectors: 63 MB: 152625

--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
0 1 07 63104856192 51199 0 1 1 6526*254 63 OK OK
0 2 07104856255104856255 51199 6527* 0 1 13053*254 63 OK OK
0 3 07209712510102864195 50226 13054* 0 1 19456*254 63 OK OK

I tried also R-Studio Demo and when I access this partition it shows
files:
D:
Metafiles
$AttrDef (FileId: 4)
$Bitmap (FileId: 6)
$Boot (FileId: 7)
$LogFile (FileId: 2)
$MFT (FileId: 0)
$MFTMirr (FileId: 1)
$Volume (FileId: 3)

Plus in the lower pane it says "? MFT File [FileId: 7] Fixup 2 is
0x235a, but should be 0x162"

Could someone help me with this, I really have kind of no idea what is
going
on with that partition and I really need this partitions contents.

(why cannot computers work for even 2month without having to tune
them)

PS. Any ideas what could even have caused this :o
I taught that Windows was unable to write some of its important
information to the harddisk but dont know :/
 
findpart results this with command "findpart 2":

Disk: 2 Cylinders: 19457 Heads: 255 Sectors: 63 MB: 152625
Click to expand...
and this with "findpart tables":

Disk: 2 Cylinders: 19457 Heads: 255 Sectors: 63 MB: 152625

--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
0 1 07 63104856192 51199 0 1 1 6526*254 63 OK OK
0 2 07104856255104856255 51199 6527* 0 1 13053*254 63 OK OK
0 3 07209712510102864195 50226 13054* 0 1 19456*254 63 OK OK
Click to expand...

You can mail me the entire output files including Findpart version
number, operating system version, and the partition table output for
disk 1.
 
First of all I have to tell that I have got almost 0 experience with
harddisk
crashes so I prefer that any answer someone might give would be easy
for newbie
in these matters:

I have 160gt samsung harddisk which is partitioned to 3 partitions all
of them
are ntfs but somewhy I cannot access the first partition (my main
harddisk
crashed 1 day ago and I had a chance to backup my data to this
samsungs
last partition which had enought free space to hold almost all of my
important
things before I begun to backup my data I watched all the partitions
and I
could access them all but after the backing up was done and I did the
same
thing it begun to complain) it just says:
D:\ is not accessible
The parameter is incorrect.

I looked up these posts a bit and found some tools called findpart and
findntfs
findpart results this with command "findpart 2":

Disk: 2 Cylinders: 19457 Heads: 255 Sectors: 63 MB: 152625

--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
0 - 07 63104856192 51199 0 1 1 6526 254 63 B OK
0 - 07104856255104856255 51199 6527 0 1 13053 254 63 B OK
0 - 07209712510102864195 50226 13054 0 1 19456 254 63 B OK

No FATs found.

Partitions according to partition tables on second harddisk:

--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
0 1 07 63104856192 51199 0 1 1 6526*254 63 OK OK
0 2 07104856255104856255 51199 6527* 0 1 13053*254 63 OK OK
0 3 07209712510102864195 50226 13054* 0 1 19456*254 63 OK OK

and this with "findpart tables":

Disk: 2 Cylinders: 19457 Heads: 255 Sectors: 63 MB: 152625

--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
0 1 07 63104856192 51199 0 1 1 6526*254 63 OK OK
0 2 07104856255104856255 51199 6527* 0 1 13053*254 63 OK OK
0 3 07209712510102864195 50226 13054* 0 1 19456*254 63 OK OK

I tried also R-Studio Demo and when I access this partition it shows
files:
D:
Metafiles
$AttrDef (FileId: 4)
$Bitmap (FileId: 6)
$Boot (FileId: 7)
$LogFile (FileId: 2)
$MFT (FileId: 0)
$MFTMirr (FileId: 1)
$Volume (FileId: 3)

Plus in the lower pane it says "? MFT File [FileId: 7] Fixup 2 is
0x235a, but should be 0x162"

Could someone help me with this, I really have kind of no idea what is
going
on with that partition and I really need this partitions contents.

(why cannot computers work for even 2month without having to tune
them)

PS. Any ideas what could even have caused this :o
I taught that Windows was unable to write some of its important
information to the harddisk but dont know :/
Click to expand...

Reply no. 2.

One reason that I asked for operating system version, is that this
could be DOS output with the disk size listed correct, while the 128
GB problem could be present in Windows 2000/XP.

The output was from Windows XP with Service Pack 1, and the disk size
was correct in XP, but the disk had been in a Windows 2000 system
without 48-bit disk address support. The first partition was created
in Windows 2000, meaning that the Master File Table was in the
beginning of the partition.

When the 128 GB Windows problem is present, data are written at the
beginning of the disk in stead of more than 128 GB into the disk. When
the Master File Table of the first partition is in the beginning, it
is more like that it is lost before the problem is discovered.

One method to examine if NTFS file records are present, is to use the
Findpart Findfile program on the cylinder area, like this:

findpart findfile 2 0 6526 +filenames fp.txt

or

findpart findfile 2 0 6526 +filenames fp.txt

In this case is turned out that file records were not present. The
only way to recover files then is to search for actual file content
without the help of file system structures.

Theoretically there could be some temporary physical problem, which
confused the examination.
 
Back
Top