S
Stefan Malte Schumacher
Hello
I am currently suffering from multiple harddisk problems and I am
really at my wit's emd how to get my system working again. The
situation is rather complex, please do not hesiate to ask if some part
of my posting needs clarification.
My original setup consisted of 3 HDs, two 120 Gig Maxtors, connected
to Primary Master and Slave and another 250 Gigabyte Maxtor
connected to a Promise 133TX-Controller. The troubles began when the
second of the 120 Gig Maxtor Drives began to malfunction. Powermax
showed bad sectors, so there is probably nothing mysterious about
that. I removed the disc in question and then moved the 250 Gigabyte
Maxtor from the Promise-Controller to the now free position of Primary
Slave. The drive had two partitions, one FAT32, the other NTFS, both
using about 50 % of the available space. While booting for the first
time after that Win2k's chkdsk began to complain about error in the
seconds partition and started to "repair" them. The result was that
all files on the second partition were destroyed - the files could
still be seen in explorer, but none of them could be opened. I assumed
that this was some problem with NTFS - after all the FAT32-Partition
on that drive still worked - and so decided just to reformat the
corrupt partition with FAT32. Imagine my joy as I realized that after
formatting the second partition now even the first FAT32-Partition had
become corrupt.
I was given the information that the problems on the second drive
might be caused by the lack of support for 48bit-LBA in Win2k and was
told to set the registry value "EnableBigLba" which I did. I decided
that before I did anything more with Windows I probably should make a
backup. My normal procedure in this case is to restore a Ghost image
to Drive C, then make the necessary changed and then save the image
and use it as basis for the next restore process. So I copied the
image - the images on this PC were lost but I had copies on another PC
on the network - over to the second partition of first harddisk, which
at least had now made any problems so far, and went on to restore
Drive C with Ghost. After 3 seconds Ghost aborted with an Error 19225,
which is according to the Symantec Support a sign of the image being
corrupt. I always keep 4-5 older revisions of the image on hold, but I
always got the same error message. Strangely only Ghost complains,
md5check reports identical values for the images on the network and
the ones I copied to the local drive.
The only cause of all this malfunctions I can currently think of would
be a defect motherboard controller, but I do not have any idea how to
check this.
I am grateful for any input on this issue. As you can image my
patience is wearing thin and I don't have any idea how to get this
working again.
Thanks in advance
Stefan
I am currently suffering from multiple harddisk problems and I am
really at my wit's emd how to get my system working again. The
situation is rather complex, please do not hesiate to ask if some part
of my posting needs clarification.
My original setup consisted of 3 HDs, two 120 Gig Maxtors, connected
to Primary Master and Slave and another 250 Gigabyte Maxtor
connected to a Promise 133TX-Controller. The troubles began when the
second of the 120 Gig Maxtor Drives began to malfunction. Powermax
showed bad sectors, so there is probably nothing mysterious about
that. I removed the disc in question and then moved the 250 Gigabyte
Maxtor from the Promise-Controller to the now free position of Primary
Slave. The drive had two partitions, one FAT32, the other NTFS, both
using about 50 % of the available space. While booting for the first
time after that Win2k's chkdsk began to complain about error in the
seconds partition and started to "repair" them. The result was that
all files on the second partition were destroyed - the files could
still be seen in explorer, but none of them could be opened. I assumed
that this was some problem with NTFS - after all the FAT32-Partition
on that drive still worked - and so decided just to reformat the
corrupt partition with FAT32. Imagine my joy as I realized that after
formatting the second partition now even the first FAT32-Partition had
become corrupt.
I was given the information that the problems on the second drive
might be caused by the lack of support for 48bit-LBA in Win2k and was
told to set the registry value "EnableBigLba" which I did. I decided
that before I did anything more with Windows I probably should make a
backup. My normal procedure in this case is to restore a Ghost image
to Drive C, then make the necessary changed and then save the image
and use it as basis for the next restore process. So I copied the
image - the images on this PC were lost but I had copies on another PC
on the network - over to the second partition of first harddisk, which
at least had now made any problems so far, and went on to restore
Drive C with Ghost. After 3 seconds Ghost aborted with an Error 19225,
which is according to the Symantec Support a sign of the image being
corrupt. I always keep 4-5 older revisions of the image on hold, but I
always got the same error message. Strangely only Ghost complains,
md5check reports identical values for the images on the network and
the ones I copied to the local drive.
The only cause of all this malfunctions I can currently think of would
be a defect motherboard controller, but I do not have any idea how to
check this.
I am grateful for any input on this issue. As you can image my
patience is wearing thin and I don't have any idea how to get this
working again.
Thanks in advance
Stefan