Allright I run a file server, on a aptiva 400 p2 300-someodd ram cant rember with a 60 gig and a 120 gig. The 60 gig is atleast 4 years old, the 120 is about 1 year. Today it started to reboot its self. The 60 gig has Windows on it and the 120 is the slave, but today forsome resone the 60 gig would stop working and reboot its self. I can get it in to windows for about 2 mins then it reboots. I tryed to reformat it but I get a error something that says "Error on D:\dir\dir\dir ect" and cant format it. So I tryed to format my 120 and it did the same. I thought this is werid and stuck the 60 gig in this rig, and it dosnt boot in towindows, just stops at a blue screen saying scan for a vrisu ect ect. That is where I stoped to think, maybe a virus but I don't know, anyone have an idea whats going on with these drives? I thought maybe the psu is doing it,but not sure how to test it. Thanks
![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
-
Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.
Both HD's Dead?
- Thread starter real
- Start date
The_Mage18
[H]ard|Gawd
- Joined
- Jul 31, 2004
- Messages
- 1,712
Actually it sounds more like your slave drive is faulty. If you're getting a message when you're trying to format the OS drive stating something like "Error on D:\dir\dir\dir", it's not your C: drive.
Microsoft OSes always assign C to the first drive, then D, E, F, etc. Simple logic, C is the 60 drive since you installed Windows on it and D is the 120GB. Even though you're formating the 60GB, the format utility in the Win2K and XP still verifies the boot records of all drives to ensure that if you're wiping the drive where the boot.ini resides, the install will need to create a new one.
Unplug your 120GB drive, then rerun the XP setup.
Microsoft OSes always assign C to the first drive, then D, E, F, etc. Simple logic, C is the 60 drive since you installed Windows on it and D is the 120GB. Even though you're formating the 60GB, the format utility in the Win2K and XP still verifies the boot records of all drives to ensure that if you're wiping the drive where the boot.ini resides, the install will need to create a new one.
Unplug your 120GB drive, then rerun the XP setup.
unhappy_mage
[H]ard|DCer of the Month - October 2005
- Joined
- Jun 29, 2004
- Messages
- 11,455
Check the power supply voltages. Most of the HD problems I've had have been solved by a PSU upgrade.
The_Mage18
[H]ard|Gawd
- Joined
- Jul 31, 2004
- Messages
- 1,712
unhappy_mage said:Check the power supply voltages. Most of the HD problems I've had have been solved by a PSU upgrade.
Good call, didn't think about that.
unhappy_mage
[H]ard|DCer of the Month - October 2005
- Joined
- Jun 29, 2004
- Messages
- 11,455
Well, unless you install say winXP and win2k on the same machine, on different drives. Then it can get complicated. And adding SCSI drives into the mix can make things act really weird in terms of drive letters.The_Mage18 said:
But in this case, we can stick to "C is first, D is second".
The_Mage18
[H]ard|Gawd
- Joined
- Jul 31, 2004
- Messages
- 1,712
Now you're just splitting hairs.unhappy_mage said:Well, unless you install say winXP and win2k on the same machine, on different drives. Then it can get complicated. And adding SCSI drives into the mix can make things act really weird in terms of drive letters.
But in this case, we can stick to "C is first, D is second".
Have you ever installed XP/2K w/ an internal zip drive plugged in? That's fun....