fstools: x86_64: after restart mount of root is read only
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
Package Name
fstools
Maintainer
@blogic
OpenWrt Version
r28597-0425664679
OpenWrt Target/Subtarget
x86/64
Steps to Reproduce
- restart device.
Actual Behaviour
cat grub.cfg
serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1 --rtscts=off
terminal_input console serial; terminal_output console serial
set default="0"
set timeout="5"
search -l kernel -s root
menuentry "OpenWrt" {
linux /boot/vmlinuz root=PARTUUID=e9bad6fa-7d1c-4dd0-c46b-4b84e666df02 rootwait console=tty1 console=ttyS0,115200n8 noinitrd
}
menuentry "OpenWrt (failsafe)" {
linux /boot/vmlinuz failsafe=true root=PARTUUID=e9bad6fa-7d1c-4dd0-c46b-4b84e666df02 rootwait console=tty1 console=ttyS0,115200n8 noinitrd
}
blkid:
/dev/sda2: LABEL="rootfs" UUID="ff313567-e9f1-5a5d-9895-3ba130b4a864" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="e9bad6fa-7d1c-4dd0-c46b-4b84e666df02"
line of fstab that is not applied:
config mount
option target '/'
option uuid 'ff313567-e9f1-5a5d-9895-3ba130b4a864'
option enabled '1'
option options 'rw,noatime,commit=15'
[ 5.180332] EXT4-fs (sda2): mounted filesystem ff313567-e9f1-5a5d-9895-3ba130b4a864 ro with ordered data mode. Quota mode: disabled.
[ 10.144736] EXT4-fs (sda2): re-mounted ff313567-e9f1-5a5d-9895-3ba130b4a864 r/w. Quota mode: disabled.
[ 10.595226] EXT4-fs (sda2): re-mounted ff313567-e9f1-5a5d-9895-3ba130b4a864 ro. Quota mode: disabled
See full dmesg and fstab in attach
Confirmation Checklist
- The package is maintained in this repository.
- I understand that issues related to the base OpenWrt repository or LuCI repository will be closed.
- I am reporting an issue for OpenWrt, not an unsupported fork.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the attached fstab.txt and dm_out.txt, then compare the GRUB root=PARTUUID setting with the fstab UUID and the reported mount/remount sequence. Trace why the root filesystem changes from read/write back to read-only after restart. Done means identifying a reproducible cause and confirming a correction for the read-only root mount.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100