incongruent
asked on
previously had 1 500GB sata, added 1 1000GB SATA.. then days later old SATA 500GB no longer recognized.
Ok. This one is probably a easy win.
I have a Asus M3A78-EM mobo running Windows XP 64bit. This machine has been running fine for about 6 months with a single 500GB SATA hard drive. As I just ran out of space, I popped in a new 1000GB Western Digital and everything worked just fine. I created a partition in XP on the new drive and copied all my data from old drive to new drive. I then ran a defrag on the 500GB disk and continued for 3 days to use the PC as normal.
After the Windows update ran on its own last night (i think it installed IE 8), XP no longer booted up. Well actually it did boot up to the regular page that appears just before the GUI username password entry page.. but then got stuck (no username/pw entry window appeared).
I could still connect to it via openSSH, and run tasklist from the console but couldn't get the UI login to popup.
Eventually I hit the reset button on my PC and after this the BIOS screen takes a long time to load (30seconds) and the old 250 GB SATAdrive is not recognized automatically. IT also is not recognized after i get into BIOS. The LED activity light for the HDD turns on for a long time while waiting for the bios setup page to appear.
So any ideas what could be the problem? I'm planning to check the wire connections and run a diag tool this evening on the disk itself, but can anyone suggest any other causes? It would be kind of strange if my 1st HDD died by coincidence a couple of days after I installed a new HDD and backed everything up... normally the HDD comes AFTER the backups are lost...
I have a Asus M3A78-EM mobo running Windows XP 64bit. This machine has been running fine for about 6 months with a single 500GB SATA hard drive. As I just ran out of space, I popped in a new 1000GB Western Digital and everything worked just fine. I created a partition in XP on the new drive and copied all my data from old drive to new drive. I then ran a defrag on the 500GB disk and continued for 3 days to use the PC as normal.
After the Windows update ran on its own last night (i think it installed IE 8), XP no longer booted up. Well actually it did boot up to the regular page that appears just before the GUI username password entry page.. but then got stuck (no username/pw entry window appeared).
I could still connect to it via openSSH, and run tasklist from the console but couldn't get the UI login to popup.
Eventually I hit the reset button on my PC and after this the BIOS screen takes a long time to load (30seconds) and the old 250 GB SATAdrive is not recognized automatically. IT also is not recognized after i get into BIOS. The LED activity light for the HDD turns on for a long time while waiting for the bios setup page to appear.
So any ideas what could be the problem? I'm planning to check the wire connections and run a diag tool this evening on the disk itself, but can anyone suggest any other causes? It would be kind of strange if my 1st HDD died by coincidence a couple of days after I installed a new HDD and backed everything up... normally the HDD comes AFTER the backups are lost...
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Its not exactly an eventful experience, its usually just a major bummer. What type of drive is it? With a 6 month failure, I'm guessing Seagate Barracuda...
Check out this site, its pretty useful for determining the type of drive failure:
http://datacent.com/hard_d
Check out this site, its pretty useful for determining the type of drive failure:
http://datacent.com/hard_d
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
oh more links...
http://hardware.slashdot.org/article.pl?sid=09%2F01%2F17%2F0115207&from=rss
http://it.slashdot.org/comments.pl?sid=1098793&cid=26542735
It seems this was a big issue earlier in the year but I've been away from home and not using the PC since March so I guess now that I'm back I encounter the problem months after everyone else.
http://hardware.slashdot.org/article.pl?sid=09%2F01%2F17%2F0115207&from=rss
http://it.slashdot.org/comments.pl?sid=1098793&cid=26542735
It seems this was a big issue earlier in the year but I've been away from home and not using the PC since March so I guess now that I'm back I encounter the problem months after everyone else.
I think I pretty clearly answered the original question - "so any ideas what could be the problem?" The drive model was never even mentioned...
ASKER
Although your answer is helpful generically, I would rather leave my answer as the solution incase someone with the same problem is looking for an answer. I'll let the question expire and moderator can split the points or award them to you but I'd like for my comment to be recorded as the solution.
ASKER
will report back shortly.