You are not logged in.
Hi,
I had a working dual boot EFI system with Arch & Win 7 co-existing quite happily. After upgrading to Windows 10, Arch appears to boot OK, but on attempting to log into KDE I get an error along the lines of "can't log onto home. Using /." This fails to work presumably because I can't log into KDE as root user.
fdisk shows that the windows upgrade has created an additional partition shifting all the linux ones (original / was sda3, now it is sda4 etc.). I tried to get refind to recognise these changes by removing 'refind.conf' and running 'refind-install' as per the wiki, but this does not work.
This seems to be a simple problem to solve but I don't have the knowledge, and it is not obvious from searching the web. Any help or pointers gratefully received.
Last edited by chsims1 (2015-08-12 12:25:44)
Offline
You probably just need to update your fstab to either compensate for the partition numbering changes, or use something more sensible like labels or UUIDs.
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 fstab already uses UUIDs.
Offline
In that case you need to investigate why your home partition is not being mounted. Check your journal.
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
Apologies WorMzy,
on rechecking my fstab, the UUID entries had been hashed out and replaced with direct references to the old partioning numbers. So, problem solved ty.
Offline