Bugzilla – Bug 114596
udev throws error messages while booting the system
Last modified: 2005-09-03 14:42:03 UTC
While booting I saw some udev error messages and in /var/log/boot.msg I found: <6>hda: cache flushes not supported <6> hda: hda1 hda3 hda4 < hda5 hda6 hda7 hda8 > <7>Probing IDE interface ide1... <3>udev[862]: run_program: exec of program '/sbin/udev.mount.sh' failed <3>udev[863]: run_program: exec of program '/sbin/udev.mount.sh' failed <3>udev[864]: run_program: exec of program '/sbin/udev.mount.sh' failed <3>udev[865]: run_program: exec of program '/sbin/udev.mount.sh' failed <3>udev[866]: run_program: exec of program '/sbin/udev.mount.sh' failed <4>hdc: LTN483, ATAPI CD/DVD-ROM drive
Created attachment 48387 [details] /var/log/boot.msg
Some lines later in the log you'll find the same error message.
Same for me.
*** This bug has been marked as a duplicate of 112820 ***
No, it's not a duplicate of bug 112820 (hal.hotplug). This is about udev.mount.sh
Christian, any idea if this is still an issue?
beta3 and beta4 doens't work here on a "serverwork" based FSC Server RX-300 (sles8 and imho sles9 certified hardware). I got b3 and b4 installing the stuff from the 1st CD (smal system with the "text mode" package selection) but during the 1st boot suse hangs at the bount where boot.local should be started. the firts abnormal informations I found i boot.msg: <<--snip-->> <5>Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 <5> Vendor: SDR Model: GEM318 Rev: 0 <5> Type: Processor ANSI SCSI revision: 02 <3>udev[865]: run_program: exec of program '/sbin/udev.mount.sh' failed <5>Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0 <5>Attached scsi generic sg1 at scsi0, channel 0, id 8, lun 0, type 3 <3>udev[909]: run_program: exec of program '/sbin/udev.mount.sh' failed <3>udev[910]: run_program: exec of program '/sbin/udev.mount.sh' failed <<--snap--->> would you like to have the whole boot.msg or could I help with other tests/informations? btw: since the machine doesn't boot here I would preferre to increase the severity, nor? greetings, stephan
I see these as well. I'll check it. But this should not be the reason for a failing boot.
ok, i'll search in the depth of the installation. ;) at first I try to change the default runlevel - maybe some kernel modules for the network caused the problem. if you're sure that the problem here has nothing to do with the udev I'll open this as a new bug.
These come from initramfs. Kay, please remove these rule from initramfs. Why do we have all rules in initrd? That makes IMHO no sense. How can i enable udev_log=info in initramfs, except manual tuning? to comment 7: I cannot imagine how this could stop booting, because this had nothing to to in initramfs at all. And it fails because of missing files. So please file a seperate bugreport about failing boot process.
There is no infrastructure to select rules for initramfs. I'm not sure how to do this without making bigger changes. We may split the rules file in small files and make an explicit list for initramfs, don't know what's the right fix for this...
we continue on bug #115133 *** This bug has been marked as a duplicate of 115133 ***