Re: [expert] Errors on startup
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 problem; still, it's worth a shot. Otherwise, I'm afraid I don't know. You might be able to pass some kernel parameters to tell it that you don't have those devices, but I'm afraid I don't know what you'd say for "nothing"; eg, append="hdc=null, hdd=null" (something to that effect), but this is getting beyond what I really know, I'm afraid. On Fri, 25 Feb 2000, you wrote: | 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 the file instead of saying it | was unable to find the hard drive. There has to be a setting somewhere where I | can disable the hard drive search for the two devices... I am completely at a | loss here. I triple checked my CMOS settings and re-installed RedHat 4 times now | to try to get rid of that. No luck... Any other suggestions? I am willing to | try anything. | | Thanks for quickly responding. | | "Brian T. Schellenberger" wrote: | | > 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 drive | > checks. You'd still get an error, presumably, but it ought to be a | > much faster error. -- I am "Brian, the man from babble-on" (Brian T. Schellenberger). I can be reached at [EMAIL PROTECTED] . I support http://www.eff.org & http://www.programming-freedom.org . I boycott amazon.com. See http://www.gnu.org/philosophy/amazon.html .
Re: [expert] Errors on startup
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), and hdd is the second device on the second controller. So it is getting the misimpression that there is a device for which it must probe on the the second (slave) position) on each of the controllers. This is most likely a problem with either your bios settings--the first thing I'd do is go into my bios setup and try disabling them there--or with the physical cabling. If that itsn't enough to solve the problem, perhaps you could a) go back to /dev and MAKEDEV to reverse my earlier advice, b) post the dmesg (/var/log/messages) messages relating to this to the list, and c) If you have a dual-boot system, watch Windows coming up and see what it thinks about your devices. On Fri, 25 Feb 2000, Michael D. Kirkpatrick wrote: | Here is what is in my fstab file: | | /dev/hda8 / ext2defaults1 1 | /dev/hda1 /boot ext2defaults1 2 | /dev/hda6 /home ext2defaults1 2 | /dev/hda5 /usrext2defaults1 2 | /dev/hda7 /varext2defaults1 2 | /dev/hda9 swapswapdefaults0 0 | /dev/fd0/mnt/floppy auto | sync,user,noauto,nosuid,nodev,unhide 0 0 | none/proc procdefaults0 0 | none/dev/ptsdevpts mode=0622 0 0 | | It looks correct to me. I don't know why it tries to detect 2 additional hard | drives. It would not be so bad if it would not take 1-2 minutes to do that. On | top of that (To add insult to injury), it tries to optimize them and errors out... | | 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 is common between the 3 boxes are | they are the same type of computer. I need to figure out how to manipulate the | boot routine to tell it not to try checking for 2 non-existing hard drives. The 3 | boxes that have the problem are PIII 550 with 512 Meg of ram and 2-27 GIG HDs. | They are the new boxes I just purchased. The other 7 are old pieces of sh*t that | I picked up at $50 each. They seem to have fewer problems then the new ones do... | | John Aldrich wrote: | | > Check your /etc/fstab file. Make sure only /dev/hda is | > defined (as far as HARD drives are concerned floppy and | > other devices in there should, of course, be left alone!) | > John -- I am "Brian, the man from babble-on" (Brian T. Schellenberger). I can be reached at [EMAIL PROTECTED] . I support http://www.eff.org & http://www.programming-freedom.org . I boycott amazon.com. See http://www.gnu.org/philosophy/amazon.html .
Re: [expert] Errors on startup
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 that it takes a little longer to start up and displays those 2 > error, nothing seems to be affected. Is there a setting somewhere (Other > then CMOS) to tell linux not to bother checking for anything other then hda. > > Thanks in advance. > Mike Kirkpatrick Disable drive autodetection in your bios, make sure the secondary controler(s) are enabled, and that all the drive jumpers are set correct and the cables correctly seated. If it still hangs waiting for ide to timeout, Post your. Bios version, Mainboard brand and revison, Harddrive layout brand and revisions, and the dmesg output from when it's probeing. -- MandrakeSoft http://www.mandrakesoft.com/ --Axalon
RE: [expert] Errors on startup
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 is common between the 3 boxes are they are the same type of computer.
Re: [expert] Errors on startup
Here is what is in my fstab file: /dev/hda8 / ext2defaults1 1 /dev/hda1 /boot ext2defaults1 2 /dev/hda6 /home ext2defaults1 2 /dev/hda5 /usrext2defaults1 2 /dev/hda7 /varext2defaults1 2 /dev/hda9 swapswapdefaults0 0 /dev/fd0/mnt/floppy auto sync,user,noauto,nosuid,nodev,unhide 0 0 none/proc procdefaults0 0 none/dev/ptsdevpts mode=0622 0 0 It looks correct to me. I don't know why it tries to detect 2 additional hard drives. It would not be so bad if it would not take 1-2 minutes to do that. On top of that (To add insult to injury), it tries to optimize them and errors out... 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 is common between the 3 boxes are they are the same type of computer. I need to figure out how to manipulate the boot routine to tell it not to try checking for 2 non-existing hard drives. The 3 boxes that have the problem are PIII 550 with 512 Meg of ram and 2-27 GIG HDs. They are the new boxes I just purchased. The other 7 are old pieces of sh*t that I picked up at $50 each. They seem to have fewer problems then the new ones do... John Aldrich wrote: > Check your /etc/fstab file. Make sure only /dev/hda is > defined (as far as HARD drives are concerned floppy and > other devices in there should, of course, be left alone!) > John
RE: [expert] Errors on startup
Michael, this seems to indicate that there's a problem with your hard disk partition table or possibly the hard drive itself. -Original Message- From: Michael D. Kirkpatrick [mailto:[EMAIL PROTECTED]] Sent: Friday, February 25, 2000 12:07 PM To: [EMAIL PROTECTED] Subject: Re: [expert] 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 it was unable to find the file instead of saying it was unable to find the hard drive. There has to be a setting somewhere where I can disable the hard drive search for the two devices... I am completely at a loss here. I triple checked my CMOS settings and re-installed RedHat 4 times now to try to get rid of that. No luck... Any other suggestions? I am willing to try anything. Thanks for quickly responding. "Brian T. Schellenberger" wrote: > 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 drive > checks. You'd still get an error, presumably, but it ought to be a > much faster error.
Re: [expert] Errors on startup
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 longer to start up and displays those 2 > error, nothing seems to be affected. Is there a setting somewhere (Other > then CMOS) to tell linux not to bother checking for anything other then hda. > Check your /etc/fstab file. Make sure only /dev/hda is defined (as far as HARD drives are concerned floppy and other devices in there should, of course, be left alone!) John
Re: [expert] 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 it was unable to find the file instead of saying it was unable to find the hard drive. There has to be a setting somewhere where I can disable the hard drive search for the two devices... I am completely at a loss here. I triple checked my CMOS settings and re-installed RedHat 4 times now to try to get rid of that. No luck... Any other suggestions? I am willing to try anything. Thanks for quickly responding. "Brian T. Schellenberger" wrote: > 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 drive > checks. You'd still get an error, presumably, but it ought to be a > much faster error.
Re: [expert] Errors on startup
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 drive checks. You'd still get an error, presumably, but it ought to be a much faster error. 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 longer to start up and displays those 2 | error, nothing seems to be affected. Is there a setting somewhere (Other | then CMOS) to tell linux not to bother checking for anything other then hda. | | Thanks in advance. | Mike Kirkpatrick -- I am "Brian, the man from babble-on" (Brian T. Schellenberger). I can be reached at [EMAIL PROTECTED] . I support http://www.eff.org & http://www.programming-freedom.org . I boycott amazon.com. See http://www.gnu.org/philosophy/amazon.html .
[expert] Errors on startup
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 longer to start up and displays those 2 error, nothing seems to be affected. Is there a setting somewhere (Other then CMOS) to tell linux not to bother checking for anything other then hda. Thanks in advance. Mike Kirkpatrick
