You are not logged in.
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)
Offline
Not sure if that helps, but I once had the same problem and the reason was that I had an error (to be precise, a typo) in /etc/fstab.
Offline
Interesting. Someone did say the same thing in the forums. In fact... was that you?
Offline
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!
Offline