Bug 690934

Summary:	After installing grub.cfg rootfs (brtfs) is locked as read only
Product:	Gentoo Linux	Reporter:	Frank Daniel <fdan52>
Component:	Current packages	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED INVALID
Severity:	normal	CC:	alexander, jstein
Priority:	Normal
Version:	unspecified
Hardware:	ARM64
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	emerge --info data

Description Frank Daniel 2019-07-28 19:06:15 UTC

I have tried installing a "by the book" installation a few times using btrfs for my rootfs partition 4.
After formatting all drives boot-VFAT swap rootfs - btrfs.  The software, OS, network installed with no error.
fstab:
/dev/cdrom      /mnt/cdrom      auto    noauto,ro       0 0
UUID=5A8C-BDA4  /boot           vfat    noauto,noatime  1 2
UUID=36c1791a-b53c-4570-bff8-8d30383bb698       none    swap    sw      0 0
UUID=d275ef5b-ff6f-4c1c-a95d-751e7b1ccf70       /       btrfs   default      0 1

When I run mount the rootfs partition shows RW access.

I later did the grub installation for EFI.
It appears that when installing grub.cfg.  The rootfs partition is set to 'ro'.



Reproducible: Always

Steps to Reproduce:
1. Need to use a AMD ryzen 2700x processor
2. format rootfs partition to BRTFS. 
3. Continue standard RC installation.  Use the EFI grub installation.  reboot
Actual Results:  
The rootfs partition is 'READ ONLY'

Expected Results:  
Full access as root

All rehabilitation methods I have found on the web have been unsuccessful.

Comment 1 Frank Daniel 2019-07-28 19:12:18 UTC

Created attachment 584914 [details]
emerge --info data

Comment 2 Alexander Tsoy 2019-07-29 09:44:07 UTC

grub appends "ro" to the kernel cmdline by default. But the root file system should be remounted as "rw" by the root service (/etc/init.d/root). Please check if this service is added to the boot runlevel and is started at boot, check the logs for any errors produced by this service [1], try to start it manually and see if it works.

[1] I'm not sure, but you probably also need to enable rc logging in /etc/rc.conf

Comment 3 Alexander Tsoy 2019-07-29 09:47:56 UTC

(In reply to Frank Daniel from comment #0)
> UUID=d275ef5b-ff6f-4c1c-a95d-751e7b1ccf70       /       btrfs   default     
> 0 1
And try to change default -> defaults :)

Comment 4 Frank Daniel 2019-07-31 18:48:38 UTC

Ok..

root is include in as an rc boot item.

Questions:
    What do you mean by rc logging?
    I don't remember how to run a script line by line.  HOWTO?

Comment 5 Frank Daniel 2019-08-04 17:28:12 UTC

I lost the drive and the backup munged (cheap USB)
I am starting over.

Close bug if necessary (which to should be)


Thanks for you time.

Frank

Comment 6 Jonas Stein gentoo-dev

2019-08-11 20:20:34 UTC

The situation seems to be a bit more complicate and requires some analysis.
We can not help you efficiently via bug tracker.
https://www.gentoo.org/support/

Comment 7 Frank Daniel 2019-08-12 01:40:17 UTC

JFI

I reinstalled Gento, using the same parameters VIA the updated manual and the install of the disks worked.  Hww... what changed?

Comment 8 Alexander Tsoy 2019-08-12 01:48:10 UTC

(In reply to Frank Daniel from comment #7)
You had invalid mount option in fstab: "default" instead of "defaults" according to #comment 0. That's why root filesystem failed to remount I guess.