You are not logged in.
Pages: 1
Now only can use arch linux fallback
when I choose arch linux
then this happen
waitting 10 seconds for device /dev/disk/by-uuid/b2f2714f-f1da-40aa-bb8c-880d56673f9d...
root device' /dev/disk/by-uuid/b2f2714f-f1da-40aa-bb8c-880d56673f9d' doesn't exitst,
error: failed to parse block elevice ids for' /dev/disk/by-uuid/b2f2714f-f1da-40aa-bb8c-880d56673f9d'
error: unable to detect or create root device ' /dev/disk/by-uuid/b2f2714f-f1da-40aa-bb8c-880d56673f9d'
If the device' /dev/disk/by-uuid/b2f2714f-f1da-40aa-bb8c-880d56673f9d' gets created while you are here, try adding 'rootdelay=10' or higher to the kernel command-line
ramfs$ ^@
How to fix this? Thank you very much.
I'm learning English. If there are any grammar or other mistakes, please tell me. Thank you.
Offline
Looks like the kernel has updated at some point and failed. So with this in mind failback is currently only working (Think of failback as a backup or your previous kernel) I would boot up in failback and reinstall your kernel and you should be good.
Offline
FWIW, I had several issues with the /dev/disk/by-uuid/ stuff, I switched back to /dev/sdX and it was all good.
Offline
thesimpsons - if fallback is working, that means your normal init image is broken. Try regenerating it with mkinitcpio.
crankyadmin - fyi, fallback has nothing to do with your previous kernel. It is an init image generated without autodetection, which means it includes a lot more modules. The mkinitcpio wiki page has more details.
Offline
thesimpsons - if fallback is working, that means your normal init image is broken. Try regenerating it with mkinitcpio.
crankyadmin - fyi, fallback has nothing to do with your previous kernel. It is an init image generated without autodetection, which means it includes a lot more modules. The mkinitcpio wiki page has more details.
Gotcha!
Offline
Pages: 1