Root is mounted as read-only

Hello,
I 've installed arch 2009.08 but when i am booting into my system a message appears that my / is mounted as ro (read-only)
I ve to run mount -n -o remount,rw / to make it writtable.
I ve used ext4 for / and /home partitions and ext3 for /boot
Is there any bug with the latest 2009.08 images ?
Thanks

x-tra wrote:
I amm gettin the folowing message during boot
#The superblock could not be read or does not describe a correct ext2 filesystem (FUNNY because i prepared ext4 partions for / and /home).
I f the device is valid and it really contains ext2/ext3 then the superblock is corrupt"
Please run efsck -b <block> /dev/sda3
Then my root partition has to be mounted using the command
mount -n -o remount,rw /
Any idea ?????
I ve done the installation using netisnstall cd because with the core one i had kernel panics
Here is my fstab
# /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
/dev/sda1 /boot ext3 defaults 0 1
/dev/sda2 swap swap defaults 0 0
/dev/sda3 / ext4 defaults 0 1
/dev/sda4 /home ext4 defaults 0 1
/dev/sdb1 /mnt/DATA ext4 defaults 0 1

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

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

Auto-remount of root file system, like read only

Hello, I'm a newbie compiling kernels, but wanna learn. (I came here bacause i don't know how to solve this or where to find an answer). I compiled some few... but, in the last days i'm suffering an strange auto-remount of the root fs "/", (remounts like read only) it's temporally fixed using fsck and rebooting. But a time later of reboot, i'm working, and suddenly the same error comes again. it's really disturbing, because force to reboot often.
I think that is not a physical error. I did not have problems with badblocks. Something creates logical errors, either the auto-remount did
Surely I have something bad on the kernel, and probably have more things there than i must.
On the other hand my /var/log/lastlog is always full of an strange ASCII and i can't see the boot info.
this is my fstab:
/dev/sda6 / ext4 noatime 0 1
/dev/sda3 /home ext3 noatime 0 2
/dev/sda5 none swap sw 0 0
/dev/sr0 /media/cdrom auto noauto,ro,user 0 0
#/dev/fd0 /media/floppy auto noauto 0 0 No hay unidad de disco flsexible
proc /proc proc defaults 0 0
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
And a summary of my dmesg report
[ 55.917194] EXT4-fs (sda6): re-mounted. Opts: commit=0
[10195.993335] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target
to attach helpers instead.
[10229.239298] ata1.00: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x0
[10229.239305] ata1.00: irq_stat 0x40000001
[10229.239318] ata1.00: cmd 60/80:00:a8:4d:6e/00:00:2d:00:00/40 tag 0 ncq 65536 in
[10229.239318] res 41/40:80:1e:4e:6e/00:00:2d:00:00/00 Emask 0x409 (media error) <F>
[10229.239330] ata1.00: cmd 60/20:08:b0:98:bb/00:00:07:00:00/40 tag 1 ncq 16384 in
[10229.239330] res 41/04:00:1e:4e:6e/00:00:2d:00:00/00 Emask 0x1 (device error)
[10229.239342] ata1.00: cmd 61/08:10:47:98:c0/00:00:37:00:00/40 tag 2 ncq 4096 out
[10229.239342] res 41/04:00:1e:4e:6e/00:00:2d:00:00/00 Emask 0x1 (device error)
[10229.239354] ata1.00: cmd 61/28:18:17:96:21/00:00:38:00:00/40 tag 3 ncq 20480 out
[10229.239354] res 41/04:00:1e:4e:6e/00:00:2d:00:00/00 Emask 0x1 (device error)
[10229.243923] ata1.00: configured for UDMA/133
[10229.243944] sd 0:0:0:0: [sda] Unhandled sense code
[10229.243948] sd 0:0:0:0: [sda]
[10229.243951] Result: hostbyte=0x00 driverbyte=0x08
[10229.243955] sd 0:0:0:0: [sda]
[10229.243957] Sense Key : 0x3 [current] [descriptor]
[10229.243963] Descriptor sense data with sense descriptors (in hex):
[10229.243966] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[10229.243980] 2d 6e 4e 1e
[10229.243988] sd 0:0:0:0: [sda]
[10229.243990] ASC=0x11 ASCQ=0x4
[10229.243995] sd 0:0:0:0: [sda] CDB:
[10229.243997] cdb[0]=0x28: 28 00 2d 6e 4d a8 00 00 80 00
[10229.244156] end_request: I/O error, dev sda, sector 935368775
[10229.244161] Buffer I/O error on device sda6, logical block 1336321
[10229.244164] lost page write due to I/O error on sda6
[10229.244177] sd 0:0:0:0: [sda]
[10229.244179] Result: hostbyte=0x00 driverbyte=0x08
[10229.244183] sd 0:0:0:0: [sda]
[10229.244185] Sense Key : 0xb [current] [descriptor]
[10229.244189] Descriptor sense data with sense descriptors (in hex):
[10229.244192] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[10229.244206] 2d 6e 4e 1e
[10229.244213] sd 0:0:0:0: [sda]
[10229.244215] ASC=0x0 ASCQ=0x0
[10229.244219] sd 0:0:0:0: [sda] CDB:
[10229.244221] cdb[0]=0x2a: 2a 00 38 21 96 17 00 00 28 00
[10229.244233] end_request: I/O error, dev sda, sector 941725207
[10229.244251] ata1: EH complete
[10229.244268] JBD2: Detected IO errors while flushing file data on sda6-8
[10229.244281] Aborting journal on device sda6-8.
[10229.439264] EXT4-fs error (device sda6): ext4_journal_start_sb:348: Detected aborted journal
[10229.439272] EXT4-fs (sda6): Remounting filesystem read-only
[10232.111686] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
[10232.111692] ata1.00: irq_stat 0x40000008
[10232.111705] ata1.00: cmd 60/08:00:18:4e:6e/00:00:2d:00:00/40 tag 0 ncq 4096 in
[10232.111705] res 41/40:08:1e:4e:6e/00:00:2d:00:00/00 Emask 0x409 (media error) <F>
[10232.264635] ata1.00: configured for UDMA/133
[10232.264653] sd 0:0:0:0: [sda] Unhandled sense code
[10232.264657] sd 0:0:0:0: [sda]
[10232.264660] Result: hostbyte=0x00 driverbyte=0x08
[10232.264664] sd 0:0:0:0: [sda]
[10232.264666] Sense Key : 0x3 [current] [descriptor]
[10235.143085] Descriptor sense data with sense descriptors (in hex):
[10235.143088] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[10235.143103] 2d 6e 4e 1e
[10235.143110] sd 0:0:0:0: [sda]
[10235.143113] ASC=0x11 ASCQ=0x4
[10235.143117] sd 0:0:0:0: [sda] CDB:
[10235.143119] cdb[0]=0x28: 28 00 2d 6e 4e 18 00 00 08 00
[10235.143132] end_request: I/O error, dev sda, sector 762203678
[10235.143156] ata1: EH complete
Please, anybody could help me to undesrtand and solve this problem?
Is it a driver problem?
Regards

Your drive must be dying.
You can use SMART tools to check it.

All USB drives mount as read only for user

I have searched a bunch and thee results I find seem to be irrelevant to my situation. Most relate to a single USB media that is a problem and won't read or write.
On a new Arch install on a new computer (my third base system install). Running Gnome.
All USB mass storage devices mount as read only for the logged in user. Root has write permissions and I can mkdir no problem. It is not an issue with the USB drive itself as this occurs with multiple USB media (I've tested several SD cards on a reader and at least two drives, all the media works correctly on my existing installations)
I'm posting the contents of my /etc/group file in case there's an obvious error there I don't see, and my dmesg output upon plugging in the drive. User name is changed in the group file posted to "archie"
This is a single-user system.
/ect/group
root:x:0:root
bin:x:1:root,bin,daemon
daemon:x:2:root,bin,daemon
sys:x:3:root,bin
adm:x:4:root,daemon
tty:x:5:
disk:x:6:root
lp:x:7:daemon
mem:x:8:
kmem:x:9:
wheel:x:10:root,archie
ftp:x:11:
mail:x:12:
uucp:x:14:archie
log:x:19:root
utmp:x:20:
locate:x:21:
rfkill:x:24:
smmsp:x:25:
http:x:33:
games:x:50:
lock:x:54:
uuidd:x:68:
dbus:x:81:
network:x:90:
video:x:91:
audio:x:92:
optical:x:93:
floppy:x:94:
storage:x:95:
scanner:x:96:
power:x:98:
nobody:x:99:
users:x:100:archie
systemd-journal:x:190:
archie:x:1000:
avahi:x:84:
polkitd:x:102:
rtkit:x:133:
gdm:x:120:
brlapi:x:999:
kvm:x:78:
ntp:x:87:archie
dmesg output
[ 968.044188] usb 4-3: new high-speed USB device number 4 using ehci-pci
[ 968.170628] usb-storage 4-3:1.0: USB Mass Storage device detected
[ 968.171435] scsi7 : usb-storage 4-3:1.0
[ 969.174450] scsi 7:0:0:0: Direct-Access Generic USB SD Reader 1.00 PQ: 0 ANSI: 0
[ 969.175068] scsi 7:0:0:1: Direct-Access Generic USB MS Reader 1.03 PQ: 0 ANSI: 0
[ 969.939417] sd 7:0:0:0: [sdb] 15572992 512-byte logical blocks: (7.97 GB/7.42 GiB)
[ 969.941028] sd 7:0:0:0: [sdb] Write Protect is off
[ 969.941037] sd 7:0:0:0: [sdb] Mode Sense: 03 00 00 00
[ 969.944664] sd 7:0:0:1: [sdc] Attached SCSI removable disk
[ 969.945509] sd 7:0:0:0: [sdb] No Caching mode page found
[ 969.945517] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[ 969.952682] sd 7:0:0:0: [sdb] No Caching mode page found
[ 969.952693] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[ 969.956396] sdb: sdb1
[ 969.965003] sd 7:0:0:0: [sdb] No Caching mode page found
[ 969.965011] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[ 969.965015] sd 7:0:0:0: [sdb] Attached SCSI removable disk
I'm sure I'm just missing something in user management, but I can't find what.
Last edited by hooya (2014-04-27 03:10:49)

I am also having the same problem. Root can read and write to automounted drives, but my user cannot. I've tried with a variety of drives, I am assuming they are being automounted by root instead of the logged-in user somehow. (I am running x directly, and am not using a display manager, if that has anything to do with it).
When I look at how it is mounted it is as follows:
/dev/sdc1 on /run/media/myuser/drivename type vfat (rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2)

External drives mount as read only

I am running OS X 10.6, on a MacPro. Something happened recently to make my external hard drives mount as read only. The only way I've found to be able to fix them is to run Disk Utility every time I start up my computer. Does anyone have an solution to this?
Also every time I run the Disk Utility, at the end of the repairs it says "Updating boot support partitions for the volume as required." I do not know if this is related, but I haven't been able to find anything relevant in relation to my problem with the drives mounting as read only.
Message was edited by: HeatherK

You might give this a try:
Select the drive and Press COMMAND-I to open the Get Info window. At the bottom open the Ownership and Sharing section. Be sure the box labeled "Ignore permissions on this volume" is unchecked. If it is checked then click on the lock icon, authenticate, then uncheck that box. Close the window.
Open the Terminal application in your Utilities folder and at the prompt enter or paste the following:
sudo chown root:admin
Put a space after "admin" then drag the drive's icon into the Terminal window. Press RETURN. You will be prompted to enter your admin password which will not be echoed.
See if this fixes the problem.

[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)

Disk image mounts as read only

I have a set of disk images that are mounting as read only. How can I change the permissions for these images? The image files themselves have r/w permission, but when they get mounted, they are mounted as read only. The images are formatted as "Mac OS standard". I notice that Disk Utility now can only create images in Mac OS Extended. Is that the problem?

That obsolete volume format is no longer fully supported in Mavericks. You can read it, but you can't write to it.

[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!

[SOLVED]External HD: Auto-mount in read-only and only root can access

So I followed the advice in http://bbs.archlinux.org/viewtopic.php? … 88#p583088 regarding using udev to auto-mount my external 60gb harddrive, and it works. The only problem is, it is being mounted read-only and I can only view the contents via sudo or as the superuser.
Can anyone guide me in the right direction I need to go to get this changed? I have already once tried to recursively chown everything on the harddrive, but that didn't seem to work. The syntax I used from that above article specifies "rw" as one of the options for the mount command, so I am stumped as to why this happened.
Thanks
Last edited by trann (2009-11-13 16:24:36)

Wattanut wrote:
Have you installed ntfs-3g?
I think I've had that problem before.
WoW, perfect solution. This is why I love this distro.

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

Arch is mounting / as read-only post-install

Okay, so I have no idea what I'm missing (I've done several Arch installs.) Machine is i686, no unusual hardware, and it's had Arch installed on it in the past. I run through the configuration, partitions, packages, etc., and when I reboot, Arch mounts my root as read-only..
Any ideas as to why this would be happening?

I understand, and thanks for your help. Fortunately I had just installed the system and didn't have anything valuable on it; Arch installs so fast that I figured it would be faster for me to run the install again and verify that my fstab was correct rather than try and chroot in

I want to mount / partition Read-Only !

I have Arch installed on my Acer Aspire One... and it works great on this little machine!
The Acer One has no hard disk, but uses SSD, so to reduce writes to disk i use EXT2, I have my /home on a separate SD card, and I mounted log and temp directories on tmpfs:
/var/log, /var/tmp, /tmp, /var/cache/pacman/pkg .
now i would like to mount the root partition (/) read only.
the reason is that i want that filesystem (EXT2) to be safe in case of improper power-off or any other disaster ...
this guide for Opensuse shows how to take care of resolv.conf and mtab files (which are, I suppose, the only files that need to be writable, after i moved the log and temp directoryes in tmpfs and the home on SD card)
http://en.opensuse.org/How-To_Make_the_ … _read-only
but then the guide advises to change some configuration files, so that the sistem doesn't remount the root partition read-write after fsck.
unfortunately the files named in the gyuide are related to Suse, and i didn't find them in Arch...:/
In fact i tried to add the "ro" option to the / partition in my /etc/fstab and i rebooted the system, but as root i can still write to the partitions..
Ideas and Info ..?!
THX
xirtyllo

Other post here. http://bbs.archlinux.org/viewtopic.php?id=65414
Closing

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

Root is mounted as read-only

Similar Messages

Maybe you are looking for