and afterwards archlinux failed to boot properly. saying
/init line 21 udevd not found
/init line 21 udevadm not found
it then goes on to say how it could findthe hard disk that grub2 told it about.
OK, I was then presented with a fairly spartan cmdline, and looked up that line in init and it is "parse_cmdline".
So what I'd like is to get an orientation on the problem. Naturally I've done a bit of searching on it, though the search was brief.
In any case, my ideas are:
- this is not a grub2 problem. Without udev a good grub won't work.
- the cmdline I get is the ramdisk, and mounting the harddisk will be futile without udev.
- the ramdisk is messed up and not the harddisk (this is a hope, rather than a conclusion)
Accordingto this short thread https://mailman.archlinux.org/pipermail … 32762.html
where I noticed that yes indeed, there is a seemingly broken symlink in the ramdisk's /lib64.
So I expect I should recreate the ramdisk, but though there is a bunch of information on this, I'm not clear how I can do it from the ramdisk image. I suspect I can't. So, seeing as I can't get in to my archlinux HD installation, I need to try the archlinux install CD. However Im not sure I can generate it there. Maybe I need to mount the installation from the CD and chroot?
Any helpful advice/guidance welcome. Cheers!
]]>