On Fri, Feb 18, 2000 at 01:37:10PM -0800, Jeff Krueger wrote:
From Will Partain on Fri, 18 Feb 2000 18:46:53 GMT:
I'm not familiar with this particular boot-time gotcha, but it sounds consistent with getting the disks mixed up and possibly not issuing both of the required "disk swap" commands.
Ehe. If you can't boot the kernel off the SCSI disks, but you can off floppies then you have ...
- ... a horked set of boot blocks on your SCSI disks
2a) above pretty common in 5.1.x releases, i see it probably about once every 5 months
In this situation, just running download from the console will update the boot block image on your disks from the currently installed OS in /etc.
As a tip - label the hell out of your shelves. You never know when the amber failure light won't light up on the problem disk or if its a 3AM swap when your brain just isn't in gear. Our filers are labeled to the extreme and probably ISO 9001 compliant. =) Its tedious, but we've found that eliminating the easy mistakes is worth the effort.
i am a visual sort of person, i like to see the red lights. take a look at the disks, if the bad disk LED isn't on, turn it on if you can. i'm not at a filer right now, but IIRC led_on will turn it on. if the disk isn't recognized by the system ( failed startup might show up in sysconfig -d ) you can turn on the 2 LEDs on either side of the failed drive, and pull the middle one. then remember to turn the LEDs off again.
-s