chmod +x /etc/rc.d/rc.udev
Reason I ask is because during boot process there is always a message that says "udev trigger" failed? So I'm thinking udev has to be activated like 'Messagebus' & 'HAL' did after a fresh install of Slackware 13.37.
i downloaded a openvz template for my lxc server to create a new centos 6.3 guest.
Now the guest is not starting because udev is hanging in the boot process.
Last time i didn't had this problem but now i have to disable or remove udev from the guest.
Own an xps 15z for about a year. A few things happened in past couple months: hard drive started clicking (telling me it was on its way out) and during boot up, boot hangs on udev. about 3 days ago i went from 2 udev-boot hangs per every 10 boot ups to 95% of bootups.I then ran smartctl on the disk and see one bad block over and over. Futile attempts to fix this block did not work.
Thank you for your replies brebs wrote:Systemd is (almost certainly) starting udev *before* remounting the disk as read/write.Yes this seems to be the problem somehow.What I still do not understand is, why my script then does not see the remounted filesystem, as the udev event is triggered way after the system is initialized completely.Currently I have to restart udev everytime, after I reboot my