You are not logged in.
Pages: 1
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
Offline
Hello X-tra!
This iso works for me.
Is your /etc/fstab okay ? Is there any error at boot sequence to mount it in read-only mode ?
Offline
i got in this trouble before, i did not find any solution so i reinstall the arch again
Offline
I don't think it's new ISO related problem, but if it's quicker for you, do it.
"Is there any bug with the latest 2009.08 images ?" Did it work with earlier ISO for you x-tra ?
Offline
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
Offline
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
Offline
"/dev/sda3 / ext4 defaults 0 1" -> It's ext4 not ext3/ext2 that the procedure searches.
Offline
"/dev/sda3 / ext4 defaults 0 1" -> It's ext4 not ext3/ext2 that the procedure searches.
yes the / director is ext4 i dont understnd why ir mentions it as ext3 ....
Offline
"I f the device is valid and it really contains ext2/ext3 then the superblock is corrupt"
Please run efsck -b <block> /dev/sda3" -> From above, did you try fsck ?
Offline
"I f the device is valid and it really contains ext2/ext3 then the superblock is corrupt"
Please run efsck -b <block> /dev/sda3" -> From above, did you try fsck ?
yes, i ve tried and it does not give memany errors
Offline
Any help please the problem still remains.
Offline
I had the same problem with the default fs settings (running on VirtualBox). I happened to change the partitioning to
sda1 (primary) ext3 /boot
sda2 (primary) swap
sda5 (extended) ext4 /
(no separate partition for /home)
and reinstalled, expecting to run into the same problem again, but for some reason, I didn't. I have nooo idea why/how this would effect proper mounting on boot, but it might be someplace to start poking around. I'm going to try to do this configuration again on another VM; I'll report back if it doesn't work.
(Edit:) Well forget the above; I tried doing a default partitioned install on another VM first, and everything was fine. My custom partitioning likely had nothing to do with the error in question, which I can't seem to re-create.
Last edited by olaguera (2009-08-19 20:16:03)
Offline
I found it at last:):):):):):):):)
I ve changed the disks to my fstab to UUID naming and it worked.
it seems that there was a problem with the detection of my hard drives.
Sometimes my disk was sda and sometimes was detected as sdb, this of course was causing a problem with naming used in fstab. That is way my / was mounted as read-only.
I hope it helps
Offline
Yes it does! Similarly, I had a problem with fstab: entries were sometimes installed as hda instead of sda.
Offline
I can't believe it. Same thing happened to me.
It asked me to "mount -n -o remount,rw /" else it woudln't save my PPPoE settings (required for internet access). I too used the netinstall.img, burned to a USB stick. I too used ext4 for both / and /home (no /boot tho). So I'm not the only one with these "issues".
http://bbs.archlinux.org/viewtopic.php?id=78804
So you fixed it by editing fstab (nano /etc/fstab ?) and changing sda instead of hda. Thanks. I'll try that next time. Gonna try the core.img version and see if it helps. Wait... kernel panics ??
Last edited by DSpider (2009-08-25 18:10:56)
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).
Offline
Thank you thank you thank you. I thought I was going nuts.
Offline
tip: look up the -L option for mkfs.* and use it. This gives you the opportunity to make an fstab like this:
# <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
LABEL=swap none swap defaults 0 0
LABEL=root / ext4 defaults,noatime 0 1
LABEL=boot /boot ext2 defaults,noatime 0 2
LABEL=home /home ext4 defaults,noatime 0 2
LABEL=var /var ext4 defaults,noatime 0 2
and a grub entry like this:
# (0) Arch Linux
title Arch Linux [/boot/vmlinuz26]
root (hd0,0)
kernel /vmlinuz26 root=/dev/disk/by-label/root ro vga=864
initrd /kernel26.img
Stand back, intruder, or i'll blast you out of space! I am Klixon and I don't want any dealings with you human lifeforms. I'm a cyborg!
Offline
I know this thread is ageing, but I just wanted to say that I had the same problem. I'm installing Arch on my EEE 900A and suddenly, after a reboot, / was being mounted as read-only. After pulling some of my remaining hairs out I found the problem between the chair and the keyboard: while editing the / entry in fstab, I misspelled "noatime".
While trying to find the problem, my eyes passed right over the error a couple of times before I finally caught it.
Just in case someone else is having that problem....
Offline
Pages: 1