You are not logged in.
Hi, I have just finished setting up a portable arch USB drive but I'm having a few issues. the Portable install boots fine on the laptop I made it on but I've noticed that when I try and boot it on another machine it tries to boot and I get "failed to start remount root and kernel file system"
I have looked into it and it looks like my drive is changing its /dev/sdx identifier when I put it into another machine and I think that's why it's failing. when I check my fstab the drive is there and the UUID= is uncommented but for some reason, it still changes and I can't get my head around the persistent block device naming wiki page. the wiki recommends using UUID in fstab and bootloader but i can't see any instructions on how to do this?
any help is appreciated. Thanks!
Offline
Please post your bootloader configuration and fstab.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
the wiki recommends using UUID in fstab and bootloader but i can't see any instructions on how to do this?
fstab has its own wiki article: https://wiki.archlinux.org/title/Fstab# … stem_UUIDs
Grub uses uuid by default: https://wiki.archlinux.org/title/Grub#A … _arguments
This page about kernel parameters has some examples where an UUID is used in different bootloader configurations: https://wiki.archlinux.org/title/Kernel_parameters
Last edited by progandy (2022-05-26 06:46:10)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
Also try to boot the fallback kernel as the system you used to install may use different drivers for the block devices than the one you're currently trying to boot from.
Offline
Thanks for the replies! I managed to figure it out. turns out it had my old root drives from before I cloned my install where at the top of the fstab config file. removing the old drives seems to have fixed it it as it now boots fine
Last edited by sarch2022 (2022-05-26 14:12:01)
Offline