You are not logged in.
Pages: 1
Hi guys,
Sorry if I didn't post this message in the good section but I didn't find any support section, so I supposed that this section was the most apropriate.
So, I have a really ennoying problem with udevd since the latest kernel upgrade (3.2.2-1) during the boot.
I have the following error at the boot:
"udevd[37]: No such file or directory." and then the OS is unable to mount the disks and give me the weakest shell ever while saying me "You're on your own". Thank you Arch!
I can't find any informations on google about this error, and I d'ont find a complete explanation of udev debug (specialy because no logs are written at this moment).
Thank you very much guys.
Offline
Hello. I have the same problem after last upgrade today.
udevd[64]: no such file or directory
ERROR: Unable to find root device 'UUID=...'
...
Looks like /dev/sd* files are missing.
Anyone have a soulution or ideas? Thanks.
Offline
Just find the issue, the problem come from the fact that the kernel is actually not present!
Delete all your files concerning the kernel, then reinstall it.
(this assumes that you have a rescue kernel ... always have a rescue kernel, the lts seems to be a good way)
If you don't have any rescue kernel, just download something manually and install it in the dirtiest way as possible then install the kernel then delete the dirty one.
Offline
This sounds like you didn't make your initramfs image.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
I took installation cd and reinstalled kernel. Now it works.
Thans to csmik. Now i have backup kernel also.
Offline
qaws or someone else:
Could you elaborate on how to just reinstall the kernel? Somehow I'm stuck
Offline
qaws or someone else:
Could you elaborate on how to just reinstall the kernel? Somehow I'm stuck
Usually, you'll need a live CD (I recommend an ArchLinux Installation CD) or an LTS kernel sitting around on the same machine that can get you more or less into your favored machine. It can also be done, by pxe/diskless booting from an installation (I'm a fan of quick and efficient)! Then you have to mount all the necessary partitions /, /usr (sometimes /var if you need your packages) and most importantly /boot. They have to be mounted underneath the rescue system being used , usually under /mnt. Also needed is a mock-up of your /proc. /sys and /dev. Once they are mounted accordingly, then you chroot into your installation you need to fix. It helps if the rescue system has the same kernel, because the chroot'ed system usually tries to build your kernel based on the rescue system, but if you have your kernel package handy, it will build it with the packages modules & kernel.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
That worked, thanks! Apparently my last update messed up nearly everything, most of my libs were empty, Xorg drivers were wrong and as a result gnome didn't start... had to reinstall most of these things. I just hope that will never happen again
Offline
Pages: 1