Arch Linux

pyrole

Member

Registered: 2022-07-11

Posts: 90

[Solved] The root device is not configured to be mounted read-write!

While boot I see this warning out of nowhere:

WARNING

The root device is not configured to be mounted
read-write! It may be fsck'd again later.

I have already read several threads regarding this about changing ro to rw, etc.

The problem is my config contains both rw and ro with ro after rw, after removing ro and rebooting there is no change and ro gets added back again.

Any clue to why this is happening and how to fix it.

Last edited by pyrole (2022-07-15 22:56:36)

dogknowsnx

Guest

Re: [Solved] The root device is not configured to be mounted read-write!

Please post the output of

cat /etc/default/grub
cat /etc/mkinitcpio.conf
cat /etc/fstab

If you don't use grub, post your bootloader's config.

pyrole

Member

Registered: 2022-07-11

Posts: 90

Re: [Solved] The root device is not configured to be mounted read-write!

Please post the output of

cat /etc/default/grub
cat /etc/mkinitcpio.conf
cat /etc/fstab

If you don't use grub, post your bootloader's config.

Yes I do use grub and here is the output you requested:

# /etc/default/grub
# GRUB boot loader configuration

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 audit=0"
GRUB_CMDLINE_LINUX="ro resume=/dev/nvme0n1p3"

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable booting from LUKS encrypted devices
GRUB_ENABLE_CRYPTODISK=y

# Set to 'countdown' or 'hidden' to change timeout behavior,
# press ESC key to display menu.
GRUB_TIMEOUT_STYLE=menu

# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console

# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper
# modes only.  Entries specified as foreground/background.
GRUB_COLOR_NORMAL="white/black"
GRUB_COLOR_HIGHLIGHT="light-cyan/black"

# Uncomment one of them for the gfx desired, a image background or a gfxtheme
GRUB_BACKGROUND="/usr/share/backgrounds/xfce/real-wood.jpg"
#GRUB_THEME=

# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"

# Uncomment to make GRUB remember the last selection. This requires
# setting 'GRUB_DEFAULT=saved' above. Change 0 into saved.
# Do not forget to 'update-grub' in a terminal to apply the new settings
#GRUB_SAVEDEFAULT="true"

# Uncomment to make grub stop using submenus
#GRUB_DISABLE_SUBMENU=y

#New GRUB update disables OS prober by default. We don't want that.
GRUB_DISABLE_OS_PROBER=false

# /etc/mkinitcpio.conf
# SPDX-License-Identifier: GPL-3.0-or-later

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(piix ide_disk reiserfs)
MODULES=""

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=""

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect block filesystems)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev block filesystems)
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS=(base udev block mdadm encrypt filesystems)
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS=(base udev block lvm2 filesystems)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block keyboard keymap consolefont filesystems fsck"

# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
#COMPRESSION="zstd"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

# /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=ED95-CC90                            /boot/efi      vfat    umask=0077 0 2
UUID=ea2fc5f2-69e0-475d-b42f-9282ede42b47 /              ext4    defaults,noatime 0 1
UUID=5a047785-501d-47eb-b77d-8d2f831283a6 /home          ext4    defaults,noatime 0 2
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,547

Re: [Solved] The root device is not configured to be mounted read-write!

Is

UUID=ED95-CC90                            /boot/efi      vfat    umask=0077 0 2

the device you get the warning for?
(In doubt remove the <swearing> "quiet" kernel parameter)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

pyrole

Member

Registered: 2022-07-11

Posts: 90

Re: [Solved] The root device is not configured to be mounted read-write!

(In doubt remove the <swearing> "quiet" kernel parameter)

So I have already removed the quiet parameter but how do I find out which device is giving the warning?

1. I don' know which line of the boot messages to look for
2. I don't know how to read the boot messages, they scroll down too quickly.

dogknowsnx

Guest

Re: [Solved] The root device is not configured to be mounted read-write!

So I have already removed the quiet parameter

Since I don't see any 'quiet' in your kernel command line (hence hasn't been edited after @seth s comment), I assume that you probably didn't regenerate your 'grub.cfg' after initially removing 'ro' from

GRUB_CMDLINE_LINUX="ro resume=/dev/nvme0n1p3"

Remove 'ro' once again and issue

# grub-mkconfig -o /boot/grub/grub.cfg

then reboot...

Last edited by dogknowsnx (2022-07-13 17:18:51)

pyrole

Member

Registered: 2022-07-11

Posts: 90

Re: [Solved] The root device is not configured to be mounted read-write!

So I have already removed the quiet parameter

Since I don't see any 'quiet' in your kernel command line (hence hasn't been edited after @seth s comment), I assume that you probably didn't regenerate your 'grub.cfg' after initially removing 'ro' from

GRUB_CMDLINE_LINUX="ro resume=/dev/nvme0n1p3"

Remove 'ro' once again and issue

# grub-mkconfig -o /boot/grub/grub.cfg

then reboot...

Oh I was editing the wrong file dayumm, this worked thanks a ton again.

dogknowsnx

Guest

Re: [Solved] The root device is not configured to be mounted read-write!

Oh I was editing the wrong file

Which file, if I may ask? Please make sure to not create potential new issues that way...

(Since you have several threads going), please always remember to mark those that have been solved by adding [SOLVED] to the title

pyrole

Member

Registered: 2022-07-11

Posts: 90

Re: [Solved] The root device is not configured to be mounted read-write!

Oh I was editing the wrong file

Which file, if I may ask? Please make sure to not create potential new issues that way...

(Since you have several threads going), please always remember to mark those that have been solved by adding [SOLVED] to the title

I was editing grub.cfg i had to edit the other one.....
thanks tho