![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
mdlbearSometimes the Mandelbear wins. Sometimes the dust bunnies win.
There were two goals for today: install a new 9GB SCSI drive (on which I had installed and mostly configured a copy of RedHat 7.3, with which to upgrade the server from 6.2), and take out the IDE drive that the system wasn't using anymore.
Taking the IDE drive out was, of course, trivial, after I evicted the dust bunnies from the case (it's been over a year since the last reboot). I only had to verify that I'd installed LILO correctly for booting off the first SCSI drive (which I had researched since the last time I tried to do it, a year or so ago -- that time I wasn't sure what the problem was, and it was easier to just leave the IDE drive, with its working LILO, than to fix it).
Cool. I also found out how to configure the Tekram SCSI card so it wouldn't keep complaining about how the geometry of the second SCSI drive (the one with /home, /opt, and so on on it) would cause trouble with Windows. This machine doesn't do Windows, so don't tell the BIOS about it.
Installing the new drive is almost equally trivial, modulo removing the ethernet card to make room behind the drive bay.
Next step is to add the new drive to LILO and see if we can boot from it. And by the way, why does the BIOS keep complaining about a power error?
Hmm, the -12V supply is fluctuating madly between -8 and -13. Could it be the new drive? No, it keeps on doing it. Not good. Swap the power supply. The new one is significantly noisier, but it's new and delivers more power. Fine; that's one for the dust bunnies.
Now why is the drive giving parity errors and causing the driver to reset the card? BAAAAAD! Does a reboot fix it? Maybe. What happens if we try to traverse the directory tree with a
Chalk up another win for the dust bunnies, take out the ethernet card again, pull the drive, and go back to pretty-much the original configuration.
Total score:![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif)
mdlbear 1.5, dust bunnies 2. Three hours for a job that was originally scheduled for 10 minutes. Good thing I didn't have any plans for the afternoon.
There were two goals for today: install a new 9GB SCSI drive (on which I had installed and mostly configured a copy of RedHat 7.3, with which to upgrade the server from 6.2), and take out the IDE drive that the system wasn't using anymore.
Taking the IDE drive out was, of course, trivial, after I evicted the dust bunnies from the case (it's been over a year since the last reboot). I only had to verify that I'd installed LILO correctly for booting off the first SCSI drive (which I had researched since the last time I tried to do it, a year or so ago -- that time I wasn't sure what the problem was, and it was easier to just leave the IDE drive, with its working LILO, than to fix it).
- For future reference, the magic phrase is
bios=0x80. It's needed in the case where there's a drive on the system when you install LILO that isn't going to be there the next time you boot.
Cool. I also found out how to configure the Tekram SCSI card so it wouldn't keep complaining about how the geometry of the second SCSI drive (the one with /home, /opt, and so on on it) would cause trouble with Windows. This machine doesn't do Windows, so don't tell the BIOS about it.
Installing the new drive is almost equally trivial, modulo removing the ethernet card to make room behind the drive bay.
Next step is to add the new drive to LILO and see if we can boot from it. And by the way, why does the BIOS keep complaining about a power error?
Hmm, the -12V supply is fluctuating madly between -8 and -13. Could it be the new drive? No, it keeps on doing it. Not good. Swap the power supply. The new one is significantly noisier, but it's new and delivers more power. Fine; that's one for the dust bunnies.
Now why is the drive giving parity errors and causing the driver to reset the card? BAAAAAD! Does a reboot fix it? Maybe. What happens if we try to traverse the directory tree with a
du? Answer: a continuous string of driver resets, which requires a power-down to get out of.Chalk up another win for the dust bunnies, take out the ethernet card again, pull the drive, and go back to pretty-much the original configuration.
Total score:
mdlbear 1.5, dust bunnies 2. Three hours for a job that was originally scheduled for 10 minutes. Good thing I didn't have any plans for the afternoon.
Finishing the quote
Date: 2003-08-04 10:37 pm (UTC)You forgot the third line: "But the dust bunnies have more fun."