Linux Mint Forums

I'm running Linux Mint 6 Felicia. I recently upgraded to kernel 2.6.27-9-generic. Subsequently the boot process halted with error messages about the filesystem being read-only. I was able to boot to recovery mode and able to continue the normal boot process from the recovery menu. I discovered that if I remove the splash kernel option from the grub menu.lst file then the boot process continues properly, but with the splash option the kernel fails to remount the filesystem as read-write and I consequently get the read-only filesystem error messages and a halted boot process. I tried a number of different options before stumbling on this discovery, but I have confirmed this behavior on my system repeatedly.

It's not that big of a problem, but I would like to know why this is happening. Any ideas?

Here is the pertinent part of my menu.lst file:

title Linux Mint 6, kernel 2.6.27-9-generic
root (hd0,0)
#kernel /boot/vmlinuz-2.6.27-9-generic root=/dev/sda1 ro quiet splash
#kernel /boot/vmlinuz-2.6.27-9-generic root=/dev/sda1 ro quiet
#kernel /boot/vmlinuz-2.6.27-9-generic root=/dev/sda1 ro splash
kernel /boot/vmlinuz-2.6.27-9-generic root=/dev/sda1 ro
#kernel /boot/vmlinuz-2.6.27-9-generic root=/dev/sda1 rw
initrd /boot/initrd.img-2.6.27-9-generic

title Linux Mint 6, kernel 2.6.27-9-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.27-9-generic root=/dev/sda1 ro single
initrd /boot/initrd.img-2.6.27-9-generic

This is odd and hard to find anything out about it
What happens if you have quiet and not splash after ro or splash but not quiet?

hapihakr,

kernel 2.6.27-9 seems to be a problem child kernel. There are reports of numerous problems related to the boot process. I imagine your best bet would be to either drop back 1 intergeneration or go on to the 2.6.27-11 kernel.

Fred