I would have expected this solution to make it not take very long,
since it's usually pretty snappy to see that a file isn't there at all.
Oh, well, it was worth a shot.
As a suggested by another list member, I'd see if these drives are
listed in /etc/fstab, though I suspect that not the proble
Should have read this one first.
I think I know what might be, though . . .
In case you aren't aware, hda is the first device on the first
controller (usually the hard drive), hdb is the second device on the
first controller, hdc is the first device on the second controller
(usuallly the CD-ROM
On Fri, 25 Feb 2000, Michael D. Kirkpatrick wrote:
> For some reason, on startup, a couple of my boxes wand to scan for hdb and
> hdd devices. There are none. After that, it tries to run Hard Drive
> Optimization on those 2 non-existing devices and of course it fails. Other
> then the fact tha
You've probably already checked this, but the BIOSes aren't set to
autodetect on all 4 of the IDE drives, are they?
Just a though,
Wayne
-Original Message-
Argh... This only happens on 3 of my boxes. I currently running 10 boxes
and the
other 7 have no problems. The only factor that
Here is what is in my fstab file:
/dev/hda8 / ext2defaults1 1
/dev/hda1 /boot ext2defaults1 2
/dev/hda6 /home ext2defaults1 2
/dev/hda5 /usr
xpert] Errors on startup
Sorry, but that did not work. I just got a different error upon startup.
The big
time waster is when it sits there trying to detect the non existent hard
drives.
It takes longer at that step the it takes to completely come up... The only
real
difference in the error was i
On Fri, 25 Feb 2000, you wrote:
> For some reason, on startup, a couple of my boxes wand to scan for hdb and
> hdd devices. There are none. After that, it tries to run Hard Drive
> Optimization on those 2 non-existing devices and of course it fails. Other
> then the fact that it takes a little
Sorry, but that did not work. I just got a different error upon startup. The big
time waster is when it sits there trying to detect the non existent hard drives.
It takes longer at that step the it takes to completely come up... The only real
difference in the error was it was unable to find th
Not sure why it wants to check those two, but if you have a "typical"
modern PC system, you don't want to limit it to hda; you want hdc as
well, which will be your CD-ROM drive.
You could presumably just
rm /dev/hdb* /dev/hdd*
if you wanted a crude approach to short-circuiting the bogus driv
