[SOLVED] Gentoo's read only root fs after installing from live image

LiFo14 · 01-05-2018, 04:35 PM

Hello!

Recently I discovered Gentoo. It's a beautiful distro to explore! So I did try to install it alongside my Fedora 27. It's UEFI laptop so both linux distros use /boot/efi partition. Fedora's Grub2 does boot process.
I built Gentoo from live image. It took me about a day. I did installation in according to amd64 Handbook with systemd and KDE Plasma.
After that, I tried boot new system. Then I found out that root fs was in the read only mode and host name was just "(none)". So no Xorg, KDE and otherseven after remount with "rw". Journalctl shows me none of boot records, dmesg shows:

Code:

[ 0.083613] ACPI Error: [\_SB_.PCI0.PEG0.PEGP.NHDA] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364)
[ 0.083620] ACPI Error: Method parse/execution failed \_SB.PCI0.PEG0.PG00._ON, AE_NOT_FOUND (20170728/psparse-550)
[ 5.625851] abrt-dump-journ[887]: segfault at 7ffca468c000 ip 00007f60c72999c2 sp 00007ffca467ad98 error 6 in libc-2.26.so[7f60c71ea000+1da000]
[ 26.984549] wlp2s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)

No troubles inside fstab:

Code:

UUID=ccf6661a-0c63-427c-a285-9f0f1aca5dbc / ext4 defaults,noatime,discard 1 1
UUID=9E76-F770 /boot/efi vfat defaults,noatime,discard 0 2

And grub's menu looks like this:

Code:

savedefault
insmod part_gpt
insmod ext2
set root='hd0,gpt4'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4  ccf6661a-0c63-427c-a285-9f0f1aca5dbc
else
  search --no-floppy --fs-uuid --set=root ccf6661a-0c63-427c-a285-9f0f1aca5dbc
fi
linuxefi /boot/kernel-genkernel-x86_64-4.9.72-gentoo root=/dev/sda4 
initrdefi /boot/initramfs-genkernel-x86_64-4.9.72-gentoo

Also there is some probs with @world:

Code:

* Messages for package app-text/iso-codes-3.75:

* ERROR: app-text/iso-codes-3.75::gentoo failed (prepare phase):
* USE Flag 'linguas_ar' not in IUSE for app-text/iso-codes-3.75
*
* Call stack:
* ebuild.sh, line 124: Called src_prepare
* environment, line 3044: Called use 'linguas_ar'
* phase-helpers.sh, line 200: Called die
* The specific snippet of code:
* die "USE Flag '${u}' not in IUSE for ${CATEGORY}/${PF}"
*
* If you need support, post the output of `emerge --info '=app-text/iso-codes-3.75::gentoo'`,
* the complete build log and the output of `emerge -pqv '=app-text/iso-codes-3.75::gentoo'`.
* The complete build log is located at '/var/tmp/portage/app-text/iso-codes-3.75/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/app-text/iso-codes-3.75/temp/environment'.
* Working directory: '/var/tmp/portage/app-text/iso-codes-3.75/work/iso-codes-3.75/iso_15924'
* S: '/var/tmp/portage/app-text/iso-codes-3.75/work/iso-codes-3.75'

Pls give me some suggestions or ways to fix this... I'd really like to do further Gentoo explorations :>

Soitgoes · 01-05-2018, 07:24 PM

I can offer this link for the iso-codes:
https://forums.gentoo.org/viewtopic-...ighlight-.html
Apart from that I would join the Gentoo forum because there are some guys/girls on the forum who really know what they are doing(much more than myself). I hope the link helps though.

** Edit **
Seems you are already on the Gentoo forums. Sometimes it may take a bit for people to respond but there is a wealth of information.

jefro · 01-05-2018, 09:26 PM

I'd guess issue here. ??? dunno.

https://wiki.gentoo.org/wiki/Handboo...root_partition

Test some of the stuff from the book again maybe.

Emerson · 01-05-2018, 10:14 PM

I see the emerge problem has been answered. Do you still have problem with read-only root filesystem?
Consider following. Kernel mounts root read-only during boot. It is up to the init system to remount it rw. Either your systemd does not run properly or the filesystem is corrupted - Linux mounts damaged filesystems ro to avoid further damage. Sometimes there is just the dirty bit set as a result of no umount during poweroff and the filesystem itself is OK.

LiFo14 · 01-06-2018, 12:13 AM

Quote:

Originally Posted by Soitgoes

I can offer this link for the iso-codes:
https://forums.gentoo.org/viewtopic-...ighlight-.html
Apart from that I would join the Gentoo forum because there are some guys/girls on the forum who really know what they are doing(much more than myself). I hope the link helps though.

** Edit **
Seems you are already on the Gentoo forums. Sometimes it may take a bit for people to respond but there is a wealth of information.

Yeah, thanks for the advice, it's like a old habit to ask Qs here c:

LiFo14 · 01-06-2018, 12:24 AM

Quote:

Originally Posted by jefro

I'd guess issue here. ??? dunno.

https://wiki.gentoo.org/wiki/Handboo...root_partition

Test some of the stuff from the book again maybe.

Thanks for the reply!
Unfortunately it doesn't solve mount probs as it happens (in my opinion) during boot time. Handbook describes mount preps before system is being installed. Mount options during boot are inside /etc/fstab which I posted earlier.
Nevertheless, I will look through Gentoo's Handbook again. I might miss something :c

LiFo14 · 01-06-2018, 12:41 AM

Quote:

Originally Posted by Emerson

I see the emerge problem has been answered. Do you still have problem with read-only root filesystem?
Consider following. Kernel mounts root read-only during boot. It is up to the init system to remount it rw. Either your systemd does not run properly or the filesystem is corrupted - Linux mounts damaged filesystems ro to avoid further damage. Sometimes there is just the dirty bit set as a result of no umount during poweroff and the filesystem itself is OK.

Thanks for the reply!
Yeah, simple tree sync solved it.

No dirty bits found...

Code:

~❯tune2fs -l /dev/sda4 |awk -F':' '/^Filesystem s/ {print $2}'
         clean

I also did "Check and repair" on that partition from GParted. No success :c

btw I noticed after system boots, /dev/sda1 is not mounted in /boot/efi. "mount" command shows a couple pseudo fs like "proc" and "sys" and /dev/sda4 which is root. Although inside /etc/fstab it's clearly defined how both partitions should be handled.
It's might be a hit for prob resolution...

LiFo14 · 01-06-2018, 05:48 AM

Looks like it was my mistake.
After I switched profiles with eselect, I forgot to clearly point to boot Gentoo with systemd. "init=/usr/lib/systemd/systemd" should be appended to GRUB_CMDLINE_LINUX inside /etc/default/grub and to grub's menuentry.
Hostname issue was also solved after that string was placed.

Code:

~❯ cat /etc/default/grub     
GRUB_TIMEOUT="5"
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT="saved"
GRUB_DISABLE_SUBMENU="true"
GRUB_CMDLINE_LINUX="nouveau.modeset=0 rd.driver.blacklist=nouveau rhgb quiet init=/usr/lib/systemd/systemd"
GRUB_DISABLE_RECOVERY="true"
GRUB_SAVEDEFAULT="true"

Grub's menu entry:

Code:

savedefault
insmod part_gpt
insmod ext2
set root='hd0,gpt4'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4  ccf6661a-0c63-427c-a285-9f0f1aca5dbc
else
  search --no-floppy --fs-uuid --set=root ccf6661a-0c63-427c-a285-9f0f1aca5dbc
fi
linuxefi /boot/kernel-genkernel-x86_64-4.9.72-gentoo root=/dev/sda4 init=/usr/lib/systemd/systemd
initrdefi /boot/initramfs-genkernel-x86_64-4.9.72-gentoo