What's problem with my first hard disk?

[sungirl]

Hello,

I have 2 hard disk... first hard disk is maxtor and then second hard disk is western digital!

I have problem with first hard disk maxtor! when i try for install any software or copy music or video... my system hang and i can't do anything! but i haven't this problem with second hard disk western digital!

i try for chkdsk for all drive first hard disk for bad sector but i don't get report for bad secotr!

Also i download PowerMax is for test hard disk maxtor and all report was passed!!

How i can find problem for first hard disk?

Also when i try by Partition magic 8.5 for check errors i don't get any error just drive D: i get error:

http://www.imagebann.com/images/tqsrk9oy1e0xc2uysfkd.jpg

http://www.imagebann.com/images/fthpdajve48oxoek8ax.jpg

If drive D have problem why i have this problem with other drive first hard disk like C E F G ??

Thank you

[Paul Komski]

What do you have on D and what might be open that is using it. I would run
chkdsk D: /R
from a command prompt allowing a dismount or reboot or try the same command in Safe Mode.

The results of a scan run on reboot can be viewed from the latest winlogon value in event viewer.

[nuz]

Your unused MB column (5th column) shows little or no space in drives D:, E: and G:. That's probably why you can't write to those drives.

[Paul Komski]

It isn't good when drives are too full but just because they are full/fullish doesn't mean that PM should report errors. It is also bad news when you see puntuation marks in the label name for any drive; that is very often a sign of bad sectors or a corrupt file system.

The attached pic shows a "full" drive that PM is quite happy with.

[nuz]

I agree. The file system in D: probably is damaged, but I don't think that should affect the other partitions. Unless, all the independent file systems are separately damaged. Note, she says that she got errors on D: only, E: and G: are full, but F: still has 3GB or so free.

sungirl: You probably want to back up anything important on D:. In the worst case you might have to format it to fix the file system.

[Paul Komski]

I wouldn't at the moment believe anything that is reported by the PM screenshot. We don't even know which drive is the system hard drive or which operating system or systems are in use. Also it is not straightforward to backup data from inaccessible partitions and that could well take specialist recovery software such as GetDataBack or cloning of the data using dd or dd_rescue from a Linux live CD if data recovery is important.

Basically we need to know more about the system as whole (in particular the make and model of the mobo or PC and which OS and what SP version) and a better understanding of whatever sequence of events has occured. There could be, for example, some BIOS related problem (an inappropriate change from DMA to PIO or a 48bitLBA related problem as a couple of examples). Until sungirl posts back we are going to be shooting in the dark.

To my mind there's something screwy/unusual going on and despite the reports by maxblast and chkdsk I wouldn't discount a faulty hard drive or of its power or data connections. To have (at least apparently) "filled up" so many partitions at the same time and have a nonsensical label on a drive might also implicate some kind of viral infection.

[Fruss Tray Ted]

Paul's post here is excellent and spot on, I just am curious as to how full Disk2 is as well. The primary drive seems to indicate an XP partition and has been storing data on each of the other partitions.

The inability of Copy, or Cut, and Paste or Save As, etc may be a problem in how things are configured or assigned to do.

If I were using this Drive 'A', I would immediately burn off boatloads of data to CD's (DVD's) etc and clean it out a bit,,, no, on second thought, ALOT! :eek:

[Paul Komski]

I just am curious as to how full Disk2 is as well. The primary drive seems to indicate an XP partition and has been storing data on each of the other partitions.Absolutely. We have details about Disk1 but none about Disk2; noting also that either Disk1 or Disk2 could be the system drive that the BIOS has booted from (though that IS unlikely seeing that there is a C: drive on Disk1). A screenshot of DiskManagement would have given more information than that from Partition Magic.

Assuming an NT OS is running (since this could even theoretically be a DOS based OS looking at NTFS partitions via Partition Magic) then, with three full/fullish partitions, one would have expected to have been having all sorts of messages about "running low on disk space" from system tray balloons. The fact that the C: drive appears to have adequate space for an OS to operate is probably why booting etc has been OK inititially.

I'm not saying that clearing some data from the full/fullish partitions wont be helpful or a total cure if it can be done. I'm just saying, rightly or wrongly, that I 'smell a rat'. It also looks increasingly unlikely that sungirl will report back - but you never know.

PS Edit "since this could even theoretically be a DOS based OS looking at NTFS partitions via Partition Magic" is, on reflexion, virtually a non-runner since C: would have to be the system partition for DOS and DOS wouldn't have booted from an NTFS partition unless it was as a bootsect.dos reference in boot.ini; pretty unlikely seeing that no FAT partitions are in sight for its Windows partition.