Fun times with computers
Jun. 21st, 2007 10:48 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
riariUgh. I think my primary harddrive is having difficulties.
A while ago, I pushed power on the computer and saw it report that it didn't see the primary drive. I turned it off then rebooted and it showed up properly. I decided to leave it alone for then, maybe it was just a fluke. I've also had it report that it couldn't find the Windows bootsector and after a restart it ran fine.
I did do a backup of one of the partitions after that first primary misread on one of the shiny new drives I had just gotten. Just in case. Nothing else happened for months so I didn't worry.
Now today it didn't see the primary drive on load. I didn't see that part because it runs by fast. It then spent time on the Novell Netware screen cycling through some numbers. When it cycled through the first time, I restarted. After a couple of tries to coax it on, I cleaned out the case a bit and made sure both fans were running properly. (The video card fan had been making noises again lately.) I cold started and went into the BIOS. I had let the BIOS just auto find the drives, but its now set to each specific drive for the primary, slave and second primary and slave spots. It found it with no problems and booted up Windows.
*Sigh* Don't have the money for a new drive. Nor the bandwidth to redownload all the patches after Windows 2000 SP4. (I'm pretty sure I have a SP4 disc around here somewhere. Need to make a current version. Or upgrade to XP.) It's running again though right now and I'll run backups again tonight.
Ah well. We'll see.
That does remind me that I need to figure out which of the three harddrives I have in this machine is the primary one. That way I'm not taking out two different harddrives to find the one I need.
A while ago, I pushed power on the computer and saw it report that it didn't see the primary drive. I turned it off then rebooted and it showed up properly. I decided to leave it alone for then, maybe it was just a fluke. I've also had it report that it couldn't find the Windows bootsector and after a restart it ran fine.
I did do a backup of one of the partitions after that first primary misread on one of the shiny new drives I had just gotten. Just in case. Nothing else happened for months so I didn't worry.
Now today it didn't see the primary drive on load. I didn't see that part because it runs by fast. It then spent time on the Novell Netware screen cycling through some numbers. When it cycled through the first time, I restarted. After a couple of tries to coax it on, I cleaned out the case a bit and made sure both fans were running properly. (The video card fan had been making noises again lately.) I cold started and went into the BIOS. I had let the BIOS just auto find the drives, but its now set to each specific drive for the primary, slave and second primary and slave spots. It found it with no problems and booted up Windows.
*Sigh* Don't have the money for a new drive. Nor the bandwidth to redownload all the patches after Windows 2000 SP4. (I'm pretty sure I have a SP4 disc around here somewhere. Need to make a current version. Or upgrade to XP.) It's running again though right now and I'll run backups again tonight.
Ah well. We'll see.
That does remind me that I need to figure out which of the three harddrives I have in this machine is the primary one. That way I'm not taking out two different harddrives to find the one I need.
