[SOLVED] Root mounted as "Read-only filesystem". mkinitcpio issue?

I am currently in the middle of setting up system encryption with LUKS. I have been making good progress so far, but I do have one remaining issue.
After typing my LUKS password, the Linux kernel starts to complain that root is a read-only filesystem. "Starting NetworkManager... cannot touch file XYZ: Read-only filesystem". When it has finally finished booting, I am dropped into a TTY. I can log in and cat my files, but I cannot write to any files our use any programs that do (like pacman).
I wonder if this is an mkinitcpio issue, but I am not sure. For whatever it's worth, here's my basic setup:
* /dev/sda1: Boot
* /dev/sda2: Swap
* /dev/sda3: Root (LUKS/ext4)
* menu.lst looks like this
* /etc/fstab contains this line:
/dev/mapper/root / ext4 defaults 0 1
* /etc/mkinitcpio.conf contains these lines:
MODULES="ext4"
HOOKS="base udev pata scsi sata encrypt filesystems"
edit: I should note that I did reinstall the kernel after making those edits to mkinitcpio.conf.
Any idea what I'm doing wrong? As always, I really do appreciate the help. Thanks in advance!
Last edited by jalu (2011-04-16 22:14:20)

So it looks like this major problem was caused by a minor mistake. The file /etc/rc.sysinit was not executable. This made it impossible for the kernel to run the script, which in turn made it impossible for the kernel to mount /dev/sda2 (the swap partition) at /dev/mapper/swap. For some unknown reason, this in turn caused /dev/sda2 to be mounted at /, messing everything up.
Anyway, a simple sudo chmod +x /etc/rc.sysinit fixed the problem. Thanks for the help, MadTux!

Similar Messages

[partially solved] Root mounted as read-only, lots of errors

I started my laptop without the power cord, and the boot stopped at several steps. I could continue the boot with pressing the power button for a second. XFCE booted fine, but some things were broken. Then I rebooted, and I cannot boot to xfce anymore at all (with or without power cord), since the root is mounted as read-only, and other partitions are not mounted at all. I didn't change my system at all so it is difficult to fix the problem. Now when I boot I just get lots of errors due to the read-only root partition. Fstab should be okay since it worked before, and has not been modified in months.
# /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/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
UUID=141f10a8-d0f2-43e0-b71e-5d01f1b3b126 /boot ext2 defaults 0 0
UUID=7f0ebf97-6e66-4e39-9db8-05fabd53180b swap swap defaults 0 0
UUID=859ac481-922b-4126-a575-462b145581fd / jfs defaults 0 0
UUID=3439fb11-ee6f-443a-9635-73ee7268e31c /media/disk ext3 defaults,data=writeback 0 0
UUID=82e37328-095e-4fd8-87ca-a74c6decc746 /media/oldroot ext3 defaults,data=writeback 0 0
I found related errors in daemon.log
Jun 23 13:15:26 nawi laptop-mode: Remounting filesystems.
Jun 23 13:15:26 nawi laptop-mode: /dev/sda6 not found in PARTITIONS.
Jun 23 13:15:26 nawi laptop-mode: / not found in PARTITIONS.
Jun 23 13:15:26 nawi laptop-mode: Checking /dev/sda6 against HD because PARTITIONS contains "auto".
Jun 23 13:15:26 nawi laptop-mode: Considering /dev/sda.
Jun 23 13:15:26 nawi laptop-mode: /dev/sda6 contains /dev/sda, which is in HD, so we will remount it.
Jun 23 13:15:26 nawi laptop-mode: Original options: rw
Jun 23 13:15:26 nawi laptop-mode: Reducing file system type.
Jun 23 13:15:26 nawi laptop-mode: Executing: mount /dev/sda6 / -t jfs -o remount,rw,atime,norelatime
Jun 23 13:15:26 nawi laptop-mode: Executing: /sbin/blockdev --setfra 256 /dev/sda6
Jun 23 13:15:26 nawi laptop-mode: none not found in PARTITIONS.
Jun 23 13:15:26 nawi laptop-mode: /dev not found in PARTITIONS.
Jun 23 13:15:27 nawi laptop-mode: Checking none against HD because PARTITIONS contains "auto".
Jun 23 13:15:27 nawi laptop-mode: Considering /dev/sda.
Jun 23 13:15:27 nawi laptop-mode: none not found in PARTITIONS.
Jun 23 13:15:27 nawi laptop-mode: /proc not found in PARTITIONS.
Jun 23 13:15:27 nawi laptop-mode: Checking none against HD because PARTITIONS contains "auto".
Jun 23 13:15:27 nawi laptop-mode: Considering /dev/sda.
Jun 23 13:15:27 nawi laptop-mode: none not found in PARTITIONS.
Jun 23 13:15:27 nawi laptop-mode: /sys not found in PARTITIONS.
Jun 23 13:15:27 nawi laptop-mode: Checking none against HD because PARTITIONS contains "auto".
Jun 23 13:15:27 nawi laptop-mode: Considering /dev/sda.
Jun 23 13:15:27 nawi laptop-mode: none not found in PARTITIONS.
Jun 23 13:15:27 nawi laptop-mode: /dev/pts not found in PARTITIONS.
Jun 23 13:15:27 nawi laptop-mode: Checking none against HD because PARTITIONS contains "auto".
Jun 23 13:15:27 nawi laptop-mode: Considering /dev/sda.
Jun 23 13:15:27 nawi laptop-mode: none not found in PARTITIONS.
Jun 23 13:15:27 nawi laptop-mode: /dev/shm not found in PARTITIONS.
Jun 23 13:15:27 nawi laptop-mode: Checking none against HD because PARTITIONS contains "auto".
Last edited by nawitus (2009-06-23 20:57:47)

It seems that laptop-mode remounted the partitions as read-only, because of bug in laptop-mode(?). I disabled that daemon, and now boot works. After that I can boot normally even with laptop-mode daemon, but now I'm afraid of booting without the power cord as that can break the system..

[SOLVED] Appending Quiet forces Read-Only filesystem

After the update to initscripts I tried to append quiet to the kernel command line of GRUB and it simply causes my system to start-up as a read-only filesystem.
Last edited by horrormaster (2011-08-01 15:36:21)

title Arch Linux x64
root (hd0,1)
kernel /boot/vmlinuz26 root=/dev/disk/by-label/gnu_linux ro rootflags=data=writeback,commit=90,orlov,barrier=0,async
initrd /boot/kernel26.img
If I add "quiet" before "rootflags" everything fails to load on boot (udev, mounting HDD rw, alsa, cupsd, etc.) and after all of those it simply states "Read-Only Filesystem". If I add "quiet" after "async" it fails to boot altogether due to an unrecognized option.
Last edited by horrormaster (2011-08-01 02:04:07)

USB flash storage mounted as read-only filesystem

Hello all,
I'm new to Arch Linux and trying to migrate all my works to arch. Installed KDE, GNOME3, and hardware drivers successfully But I have problems with USB flash disks. When plugging a usb device, system mounts it as a readonly filesystem. so I can't change its contents. It always happens to my flash disk, but flash disk of my friend is ok!
I tried to mount manually with super user access, but no hope. It says:
[root@myhost soroush]# mount /dev/sdb1 /mnt/
mount: warning: /mnt/ seems to be mounted read-only.

roygbiv wrote:Maybe you can post your /etc/fstab?
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
/dev/sda2 / ext4 defaults 0 1
/dev/sda3 /home ext4 defaults 0 1
/dev/sda4 swap swap defaults 0 0

Ipod now mounts as read only filesystem.

had to re-install base, as I ran amuk with mixing testing and non testing repos.
after re-install, the only packages from testing I installed were amorak-base and it's dependancies, and libgpod.
it recognizes my ipod when I plug it in, but mounts it as read only. Even though my user has write access to the mount point. Ipod is new classic, and I have followed the guide on amarok. ipod is formated hfs+. It was working great, until I re-installed the base system. Everything I had put on the ipod under linux is still there, so the database shouldn't be borked.
any help? I modprobed hfs, hfsplus, and still read only

The "problem" is libgpod. There is a new version in testing, it will be moved to extra this weekend. With the old version of libgpod it seems, that you write the songs to your ipod, but they don't appear after plugging it off. From the wiki of libgpod:
Starting with the 2007 generation of iPods, libgpod needs an additional configuration step to correctly modify the iPod content. libgpod
needs to know the so-called iPod "firewire id", otherwise the iPod won't recognize what libgpod wrote to it and will behave as if it's empty.
Wait until the new libgpod is moved this weekend, and follow the steps here: http://gtkpod.wikispaces.com/Sysinfo+File#ClassicNano3g
Then it should work again.
Daniel

[kinda solved, hd broken]Salvaged hard drive mounted as read-only

My old netbook died recently (if a guy in a shady computer store in Edinburgh tells you that "this adapter will surely work" -- what ever you do, don't believe him). Got a new netbook, and an external usb hd case for the old hard drive in the hope of salvaging it.
The old hd seems to have survived, as it mounts just fine and all my old partitions show up (home folder, root, swap...). However, I cannot change the permissions of the files using thunar as root, nor can I copy them to my internal hd --probably because the drive is mounted as read-only. The /home partition, which is the one I'm interested in copying things from, is formated in ext4.
I'm guessing I should change something in my fstab, though I'm not sure what exactly. What's weird though is that the drive does not show up when I run sudo fdisk -l, nor does it show in gparted (which is run as root, of course) -- meaning I don't know what rule I should put in my fstab file, as I dont know what mount point to apply it to. I use xfce on my current laptop, but seeing as the problem persists when I try on my partners ubuntu laptop I figure that the DE hasn't got much to do with it.
I guess I could open up the computer, put in the old hard drive and change some configs, install drivers etc. to make my new computer boot properly from it. Does seem like a drag though, so I figured I'd try asking here first. I suspect this is a fairly common problem, but my google-fu does not appear to be strong enough as I've failed to find a solution on my own.
Last edited by caligo (2010-07-19 20:09:01)

karol wrote:'mount: /dev/sdd2: cannot read superblock' is quite different from mounting read-only - I'd call it read ... NOT!
I hope you have some sort of backup.
Yes, "cannot read" is indeed a more disheartening message... When trying to copy the files through thunar, I can see them but not move or open them -- and trying to change the permissions results in an error message about the file system being "read-only".
itsbrad212 wrote:# fsck /dev/sdd2
results in
Attempt to read block from filesystem resulted in short read
The thing might indeed be dead...
I have backups of all the important things -- just wanted to save some recent random files and a bunch of wallpapers, but I think I'll survive the loss. Thanks for the help guys. Might try to format the whole thing, see if its just the data that's corrupted or of the harware is busted as well.

Reset lost root password and now have read only filesystem

Hello,
I have recently had to reset a locked root password by booting from cdrom, mounting the first boot disk, editing the shadow file to remove root's password and rebooting the system.
The system has booted OK but, I now have a read only filesystem - everything in / cannot be edited, passwd doesnt work etc.
df -k shows the root (/) filesystem has been mounted on the physical disk I edited:
Filesystem kbytes used avail capacity Mounted on
/pci@83,4000/FJSV,ulsa@2,1/disk@0,0:a 10085836 185862 9799116 2% /
but in the vfstab it still references the disksuite metadevice:
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
/dev/md/dsk/d30 /dev/md/rdsk/d30 / ufs 1 no -
So, can I simply boot from CDROM again, amend the vfstab to be /dev/dsk/c0t0d0s0 (instead of /dev/md/dsk/d03) and reboot?
Any help with this is appreciated!
Thanks,
Emma

df -k should have shown root mounted on md0
e.g. on my machine
# df -k
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d0 8260691 4366317 3811768 54% /
what does /etc/system show for rootdev?
# grep rootdev /etc/system
* rootdev: Set the root device. This should be a fully
* rootdev:/sbus@1,f8000000/esp@0,800000/sd@3,0:a
rootdev:/pseudo/md@0:0,0,blk
Remember if this is a mirrored drive, when you boot from CD you may need to mount both sides of the mirror and make changes on both sides- otherwise the replication may not goes as expected.
Actually, I have run into problems with the modifying one side of a mirror this way. In the past Sun tech support would recommend that I break the mirror and then rebuild it once the system is up and running. So in your case you may want to boot from CD, mount the 1st disk slice, edit /etc/vfstab AND /etc/system, boot into the OS and use the various meta commands to delete and rebuild the mirror- or at least maybe to drop and reattach the 2nd 1/2 of the mirror.

[SOLVED] Strange Hard Drive Errors - Read Only Filesystem?

Solution: Discard old laptop, buy new laptop
I have an Acer Aspire 5103WLMi. For about 2 months now, Arch has been running smoothly. Until 2 weeks ago.
It all started when I tried to install and configure autofs on Arch x86_64. On the next reboot, all manner of errors were printed to the screen, to the effect that the internal hard drive was only being mounted read-only, rendering the system unusable. I tried to find a solution, but there were no references to read-only anywhere; fstab, grub etc. None that I could find.
I tried reinstalling. However, x86_64 Arch refused to boot properly first time due to the exact same error; and I *know* that I'm configuring everything correctly. I managed (somehow) to coerce i686 Arch to install, and things "work".
Seemingly out of the blue, during normal operation, all running applications will stop, and spit out error after error to the effect of "Cannot Write to Read Only Filesystem!". Sakura won't load (Input/Output error, apparently), and the only way to shut down the laptop is a hard reset (I can't log in as root or use sudo because it wants to write to the filesystem first, which it obviously can't.
Now, I'm going to be giving the insides of this laptop a good cleanout this weekend, and I'm in the process of backing up all of my data, but I was wondering if anyone else has come across a similar form of misbehaviour; or (with a bit of luck) some potential solutions?
This is very peculiar, because there seems to be no reason why the laptop suddenly loses write permissions to the hard drive. Cheers.
Edit: I think I should point out that my /boot partition is Ext2, and / and /home are Ext3
Last edited by aphirst (2013-03-27 14:51:38)

Smartctl gives me the impression it's my Hard Drive:
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1711
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 6194
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 3291
10 Spin_Retry_Count 0x0033 223 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1218
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 294
193 Load_Cycle_Count 0x0032 088 088 000 Old_age Always - 123904
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 34 (Lifetime Min/Max 15/62)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 17
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 118
222 Loaded_Hours 0x0032 094 094 000 Old_age Always - 2425
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 444
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
Everything being either Old_age or Pre-fail is not encouraging. Additionally, in the output is what I believe to be records of what caused my strange read-only behaviour:
Error 19 occurred at disk power-on lifetime: 3287 hours (136 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
84 51 01 11 18 6a e1 Error: ICRC, ABRT 1 sectors at LBA = 0x016a1811 = 23730193
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 48 c4 17 6a e1 00 04:43:08.023 READ DMA
c8 00 48 14 e3 69 e1 00 04:43:08.022 READ DMA
c8 00 a0 5c e2 69 e1 00 04:43:08.010 READ DMA
c8 00 08 9c e5 69 e1 00 04:43:08.010 READ DMA
c8 00 20 5c e5 69 e1 00 04:43:08.009 READ DMA
Could this truly be referring to my problem, since the 'logs' show that the *exact same* error occurred many times.
Not that this tells me how to fix it...
Well, if anyone knows if there is a solution, I'd love to know. If the only solution is to ditch the Hard Drive, fair enough. Either way: I'm backing up all of my important data ASAP.
Cheers.
Oh, and kclive18, after I noticed that I couldn't get onto my Drive, I reinstalled arch, leaving no trace of /etc/autofs/auto.media.
Additionally, somehow I have now been able to install Arch x86_64, but the problems still occur...

[solved] External drive automatically mounted as read-only

Hi folks,
I have a strange issue with an external drive automatically mounted as read-only whenever I plug it to my laptop :
[sclarckone@archLaptop ~]$ mount
/dev/sdb1 on /run/media/sclarckone/dd type ntfs (ro,nosuid,nodev,relatime,uid=1000,gid=100,fmask=0177,dmask=077,nls=utf8,errors=continue,mft_zone_multiplier=1,uhelper=udisks2)
And I can't remount it as read-write :
[sclarckone@archLaptop ~]$ sudo mount -o remount,rw /dev/sdb1
mount: cannot remount /dev/sdb1 read-write, is write-protected
But of course, I'm able to mount it as read-write on other operating systems.
I have udisks and udisks2 installed on my system. I also belong to the storage group so I thought I could mount a filesystem as a normal user but I can't :
[sclarckone@archLaptop ~]$ mount /dev/sdb1 dd/
mount: only root can do that
I don't know whether it is relevant to this problem, but I have systemd and polkit installed as well... Does anybody has an idea of where the problem could come from ?
Thanks for your help !
Last edited by sclarckone (2012-12-13 21:45:04)

Check out following file :
/usr/share/polkit-1/actions/org.freedesktop.udisks.policy
Look for mount a device and It should have configuration like :
<action id="org.freedesktop.udisks.filesystem-mount">
<description>Mount a device</description>
<description xml:lang="da">MontÃ©r en enhed</description>
<message>Authentication is required to mount the device</message>
<message xml:lang="da">Autorisering er pÃ¥krÃ¦vet for at montere et fil system</message>
<defaults>
<allow_any>no</allow_any>
<allow_inactive>no</allow_inactive>
<allow_active>yes</allow_active>
</defaults>
</action>

[Solved]External HDD only mounts as read only

Okay, I have a general log, but I'm not completely sure what all information you need. Ask and you will receive.
So I run udiskie through i3, works great, but my file systems get mounted as read-only, which is..not great. It's pretty irritating. So I thought, hey, let's just chown that shit, right? No. It's a read only file system.
Anyway, so I did killall udiskie, tried mounting it manually and all as demonstrated in lsblk, and it's still read only, for some interesting reason. (Sorry the lsblk log isn't clean). If there's some other output you'd like, let me know...
I run the thunar file manager, which is alright, but it doesn't auto-mount (I tried setting it up, googled it a lot, it just didn't auto-mount, and udiskie looked like it worked fine until I realized it was all read-only).
In lsblk I ran sudo thunar to view the drive, since permission was denied to myself. It was still read-only, meaning it's not necessarily a udiskie problem? I could mount my other flash drive alright it appeared, but when I did it with udiskie it was also readonly.
The flash drive was made with dd, so it had two partitions, the second one mounted fine, the first one not so much, and with udiskie it just mounted what looked like the second one with more files (So maybe both? I was a bit confused).
lsblk: http://pastebin.com/WdJbky9j
udiskie -a: http://pastebin.com/RT2sQE01
On a side note, those awesome arrows on the side of my terminal thanks to zsh and oh-my-zsh? They're just empty rectangles in rxvt-unicode, and I have no idea why. They display fine in pastebin. If anyone happens to know what I'm missing there, much obliged.
Solution:
Actually understand NTFS in linux (Working on it)
Install ntfs-3g
Last edited by Rojikku (2014-07-02 02:06:18)

lsblk -f: http://pastebin.com/KeHpDtF6
Anything I could say would be repetitive of the data. >>; But for record purposes, btrfs and the external is ntfs.
Edit: I don't have ntfs-3g installed, FYI. It seemed like an alternative to udiskie and I dislike installing things frivolously. I noticed another user fixed a somewhat similar problem like that, would that be my issue?
Last edited by Rojikku (2014-07-02 01:37:24)

Single User Mode : Read Only Filesystem

I can't edit files in single user mode as Root. When I try to edit them I get a msg saying "Read Only Filesystem".
I have tried chmod with no evial. I want to change my .profile as root so cls='clear'.
Any ideas?
Also when I try to login to my account in single user mode it says that account does not exist. However I'm in that accunt right now!
Thank You.

When you boot up into single user mode, there is a single recognized user -- root. That's why they call it single-user mode and not multi-user mode.
When you boot up into single user mode, the disk mounts as read-only. You have to make it writeable in order to do anything to it. I forget the actual command but it displays on the monitor nearby where it gives the "fsck" command syntax when you first boot into it. It's something like "mount -uw /" or something to that effect. It is saying to mount the root drive ("/") with user write privileges.
Then just "pico /Users/Mephux/.profile" (although I profess that I don't understand why you have to edit this file as root).
(if you find that this solves your problem, or is actually helpful towards arriving at a solution to your problem, please consider clicking on either the "helpful" or "solved" buttons above)

[SOLVED] util-linux causing read only /

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)

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...

Pacstrap failed. Now I have a read-only filesystem that is unusable

Hello,
I have been using Linux for the past few years (primarily Ubuntu and Fedora), and have used the command line a lot.
I was just following the instructions on the Beginners guide. I set up wifi, and partitioned the disk using gdisk (all my computers since late 2009 have not used MBR). I then set up my mirrorlist (left the first one, and added my university as second).
When I ran pacstrap (without -i), it started downloading everything. I think it finished most of it. The kernel had been downloaded, and the filesystem supposedly set up. Then, I got an error. (I am not sure where it was, and I wasn't logging the output. There were many many lines of:
[timestamp] EXT4-fs (sda1): ext4_da_writepages: jpd2_start:8192 pages, ino xxxxxxx; err -30
Then:
[timestamp] EXT4-fs error (device sda1): ext4_journal_start_sb:370: [timestamp] EXT4-fs error (device sda1): ext4_journal_start_sb:370: [timestamp] EXT4-fs error (device sda1): Remounting filesystem read-only
error: command failed to execute correctly
error: could not create directory /mnt/var/lib/pacman/local/groff-1.21-2/: Read-only file system
error: could not commit transaction
error: failed to commit transaction (transaction aborted)
Errors occured, no packages were upgraded.
warning: could not remove lock file /mnt/var/lib/pacman/db.lck
==> ERROR: Failed to install packages to new root
pacstrap /mnt base base-devel 35.27s user 6.19s system 3% cpu 17:34.81 total
Trying to rerun pacstrap gets me an error that the lockfile still exists. I cannot remove it because it is a "read-only filesystem". Its permissions are 000, and the folder it is in (pacman) has 755.
I also cannot make an fstab or continue with the installation.
I tried to run the setup again, and it kept failing. (MBR failed too, with the same error.)
What do you think caused it, and what could I do to resolve it. I couldn't find anything like that in the forums, or on google.
Last edited by masasin (2012-10-27 03:18:37)

Are the ext4 errors not a dead giveaway that the FS (or physical disk) are misbehaving? It's remounted itself read-only to prevent further damage.

Usb stick is "READ ONLY FILESYSTEM"

hello.
i have a problem with my USB-Stick. since i gave it to a friend it does no longer work. unix says it is a "READ-ONLY FILESYSTEM". anny sugestions how i could change that?
it was not possible to reformat it by disk utility. i also tried to format it on a windows machine - didn´t work... any ideas?
best reagards
sepoe

Monkeymeetsrobot's suggestion is the first thing I would have suggested myself -- your original post made no mention of no write-lock switch -- many flash drives have them -- one of mine does and when locked would exhibit that behavior and the other one that doesn't, it still works properly.
That said, now that we know that yours doesn't have a write-lock switch, maybe you could try this:
It's a long shot, but what happens when you launch Terminal and type
ls -ld /Volumes/{usbStickName}?
If the permissions are not drwxrwxrwx, then, perhaps, from an admin-privileged account, you could
sudo chmod 777 /Volumes/{usbStickName}
and with any luck, you will have write privileges again.
Something to try....no guarantees....
Short of that, you may be giving your friend a slightly used usb flash drive as a Christmas present.
(if this solves your problem, or is actually helpful towards arriving at a solution to your problem, please consider marking this reply as "helpful" or "solved," in addition to, if applicable, marking this question as "answered")

Read-only filesystem after reinstallation,chmod failure

I decided to switch to a pure systemd init yesterday. Despite strictly followed wiki my system failed to init with switch to systemd emergency mode with no way to cure the problem. So I followed with reinstallation of my system (32bit on 64bit HW as recently). I went thoroughly according installation wiki, installed and configured the base system and correctly umount-ed chrooted environment. I have reformated primary root and boot partitions with ext4 and ext2 respectively and extended /var partition with reiserfs. My home ext4 partition has left unchanged. Grub has been configured OK when being compared with my two Thinkapd Arch installations. My fstab is correctly set using UUID and explicit rw option. After rebooting from Install CD all seemed going well to login prompt and successfull root login. Next proceedings failed on unchangeble read-only filesystem permissions.
How can I chmod the partitions to make them writable and add users and use pacman? One fail with systemd is followed with another one with unchangable read-only permissions... Courious and very frustrating... Any help, please? Thanks, Petr

You'll need to post files, logs etc. if you want help - according to you, everything is correct .
For example, grub.cfg, fdisk -l or gdisk -l /dev/sdX, fstab...

[SOLVED] Root mounted as "Read-only filesystem". mkinitcpio issue?

Similar Messages

Maybe you are looking for