In the situation also reported on bug 735866 an rmmod error pops up:
[ 12.974328] udevd: failed to execute '/sbin/initqueue' '/sbin/initqueue --settled --onetime --unique /sbin/dmsquash-live-root /dev/sdc': No such file or directory
[ 130.927626] udevadm: udevadm settle - timeout of 120 seconds reached, the event queue contains:
[ 130.927758] udevadm: /sys/devices/virtual/tty/tty4 (2124)
[ 130.932233] systemd: udev-settle.service: main process exited, code=exited, status=1
[ 130.965870] systemd: Unit udev-settle.service entered failed state.
[ 131.030223] rmmod: ERROR: Module scsi_wait_scan does not exist in /proc/modules
I guess that is because systemd now logs all output, and the "try to rmmod and see what happens" approach used in /lib/systemd/system/fedora-wait-storage.service shows up as being less elegant.
I confirm this bug in F16.
vascom2: do you also see bug 735866?
No. I see only this string:
rmmod: ERROR: Module scsi_wait_scan does not exist in /proc/modules
vascom2: it would probably be helpful if you could attach the whole dmesg and report the potentially-involved package versions.
Created attachment 533034 [details]
Dmesg from Virtualbox
Created attachment 533035 [details]
Dmesg from hardware
I'am see this string in all Fedora 16 installations.
Right, it will likely come up, but it's a harmless error.
Fixed with: http://git.fedorahosted.org/git/?p=initscripts.git;a=commitdiff;h=c0e2c32eebea3c99807ca5f0505dcb020250a2a6
This will go out in some future Fedora 16 update.
*** Bug 752344 has been marked as a duplicate of this bug. ***
initscripts-9.35-1.fc17 has been submitted as an update for Fedora 17.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing initscripts-9.35-1.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
initscripts-9.34.1-1.fc16 has been submitted as an update for Fedora 16.
initscripts-9.34.2-1.fc16 has been submitted as an update for Fedora 16.
initscripts-9.34.2-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
Yes, it solve problem.