Arch Linux

goldilocks

Member

Registered: 2012-10-14

Posts: 4

Read only after install [SOLVED -- systemd related]

Anyone know why a new (booted ~2-3 times) install would suddenly mount read-only?  /etc/fstab is fine, /etc/mtab reports rootfs / as rw, and I am logged in as root, but I get "read-only filesystem", hence there are no logs, etc.

Last edited by goldilocks (2012-10-14 18:01:41)

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: Read only after install [SOLVED -- systemd related]

Have you tried running an fsck on the / ?

goldilocks

Member

Registered: 2012-10-14

Posts: 4

Re: Read only after install [SOLVED -- systemd related]

The fsck post boot says clean, as does one from the live cd.

I'm running e2fsck -c on it now, but I do not think a few bad blocks would cause this.

Last edited by goldilocks (2012-10-14 17:49:45)

DSpider

Member

From: Romania

Registered: 2009-08-23

Posts: 2,273

Re: Read only after install [SOLVED -- systemd related]

You probably removed "ro" from syslinux.cfg.

https://wiki.archlinux.org/index.php/Sy … sic_Config

Otherwise, post your fstab.

---

"How to Succeed with Linux"

I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).

JLloyd13

Member

Registered: 2012-06-24

Posts: 107

Re: Read only after install [SOLVED -- systemd related]

are you dualbooted and have another install using the same /boot? I just say this not because I know anything but because (I am guessing that its because of /boot) in my grub menu I have two entrys for arch, one of which is normal and the other one is read only, and both are labed the same

goldilocks

Member

Registered: 2012-10-14

Posts: 4

Re: Read only after install [SOLVED -- systemd related]

You probably removed "ro" from syslinux.cfg.

Nope.   I have a startup service I use on fedora, and since the target I usually use wasn't apparent, I casually systemctl enabled it with WantedBy=local-fs.target, figuring if that was too early it would just fail (it writes to to disk).

Using "mount -o remount,rw /" worked, so I tried a few things like switching fstab to use a UUID instead of a device node, that didn't work.  Finally I disabled the service and everything is back to normal.

I did this a couple of times (enabling, rebooting, disabling, rebooting) just to confirm that was the cause. I guess that target runs before the rw remount, maybe this causes systemd to crap out in some way.  Shame it can't just fail the service, log it, and continue.  Maybe even an oversight verging on "bug", though I am sure they are aware of it already.

I'd mark this "SOLVED" but I don't see a button...

Last edited by goldilocks (2012-10-14 17:49:16)

karol

Archivist

Registered: 2009-05-06

Posts: 25,440

Re: Read only after install [SOLVED -- systemd related]

I'd mark this "SOLVED" but I don't see a button...

Read https://bbs.archlinux.org/viewtopic.php?id=130309

goldilocks

Member

Registered: 2012-10-14

Posts: 4

Re: Read only after install [SOLVED -- systemd related]

I'd mark this "SOLVED" but I don't see a button...

Read https://bbs.archlinux.org/viewtopic.php?id=130309

Thanks