You are not logged in.
Anyone else having this problem?
After upgrading to testing after boot the root filesystem is readonly with arch init and with systemd...
That's happening for me since 1 or 2 days, maybe the problem was earlier too, don't really know.
Downgraded util-linux (and its dependency mkinitcpio, but not rebuilding the initramfs) to repo version and my / filesystem is rw again after boot...
I have not seen anything on the mailinglist...
Last edited by Cdh (2012-03-09 09:47:22)
฿ 18PRsqbZCrwPUrVnJe1BZvza7bwSDbpxZz
Offline
Zero info to go on here. No logs, no config files...
output of blkid, bootloader config and /etc/fstab all seem relevant. Probably 'systemctl --full --all -t mount' as well since you mention systemd.
Last edited by falconindy (2012-03-08 16:50:09)
Offline
Sorry, I first wanted to check if I am the only one or if there are already hundreds of minions working on it.
Logs are complicated on a read only filesystem. Couldn't find anything in dmesg, it just seems that it wasn't remounted rw while booting for some reason.
Nothing fancy here, using the util-linux from core with the rest from testing:
/dev/sda1: UUID="1ec5d4eb-f2c2-445a-88bd-41b5717fab29" TYPE="ext4"
/dev/sda2: UUID="2e8619f0-1f4f-423b-8dd9-8cb1be8b6e2a" TYPE="ext4"
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/cdrom /media/cdrom auto ro,user,noauto,unhide 0 0
/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#UUID= swap swap defaults 0 0
UUID=83a138cd-f2a5-4bdc-bbce-fbc9b8b20212 / ext4 defaults,relatime,user_xattr 0 0
UUID="2e8619f0-1f4f-423b-8dd9-8cb1be8b6e2a" /home/chris ext4 defaults,relatime,user_xattr 0 0
/swapfile swap swap defaults,noauto 0 0
none /sys/kernel/debug debugfs auto 0 0
none /proc/bus/usb usbfs auto,busgid=108,busmode=0775,devgid=108,devmode=0664 0 0
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
-.mount loaded active mounted /
dev-hugepages.mount loaded active mounted Huge Pages File System
dev-mqueue.mount loaded active mounted POSIX Message Queue File System
home-chris-.gvfs.mount loaded active mounted /home/chris/.gvfs
home-chris.mount loaded active mounted /home/chris
media-cdrom.mount loaded inactive dead /media/cdrom
media-dvd.mount loaded inactive dead /media/dvd
media.mount loaded active mounted Media Directory
proc-sys-fs-binfmt_misc.mount loaded inactive dead Arbitrary Executable File Formats File System
sys-fs-fuse-connections.mount loaded active mounted FUSE Control File System
sys-kernel-config.mount loaded inactive dead Configuration File System
sys-kernel-debug.mount loaded active mounted Debug File System
sys-kernel-security.mount loaded active mounted Security File System
var-lock.mount loaded inactive dead Lock Directory
var-run.mount loaded inactive dead Runtime Directory
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.
15 units listed.
I mentioned the inistscripts and systemd together because it seems not to be a problem in one of them (or in both of them...)
mount -o remount,rw /dev/sda1 /
Gives ma a rw system with testing util-linux with no problems at all...
฿ 18PRsqbZCrwPUrVnJe1BZvza7bwSDbpxZz
Offline
this happend to mee in a fresh install using a btrfs for / and /home
only ussing default,compress=lzo in fstab for the / and /home
i resolve this "temporaly" replacing default fo rw in fstab
you can try adding rw to the fstab and using ro in grub
note: this happend to me in a fresh install, and a fresh install using testing in installation
Well, I suppose that this is somekind of signature, no?
Offline
That's... interesting. I haven't seen that the UUID does not match.
Now I'm wondering how arch ever knew to mount /dev/sda1 to / when booting...
The bootloader sets it correctly with root=/dev/disk/by-uuid/1ec5d4eb-f2c2-445a-88bd-41b5717fab29 but who remounts it rw?
I fixed the fstab entry and will try if it remounts to rw correctly, thanks for spotting that.
edit: It did fix my problem.
My guess: util-linux until now just remounted / rw on boot and now actually looks at the fstab.
Last edited by Cdh (2012-03-09 09:46:58)
฿ 18PRsqbZCrwPUrVnJe1BZvza7bwSDbpxZz
Offline
That's... interesting. I haven't seen that the UUID does not match.
Now I'm wondering how arch ever knew to mount /dev/sda1 to / when booting...
Because it's the bootloader's job to define root and pass it along to the initramfs to actually mount. /etc/fstab isn't involved (how could it? root isn't mounted yet).
The bootloader sets it correctly with root=/dev/disk/by-uuid/1ec5d4eb-f2c2-445a-88bd-41b5717fab29 but who remounts it rw?
/etc/rc.sysinit remounts root.
Offline