Error on dual boot when choosing BackTrack 2

[jackol]

I have partition my drive and have windows xp on hda1 and BackTrack 2 final installed on hda2. The first time I restarted after installing BackTrack I used LILO to create an option to boot either to windows or backtrack. When I choose BackTrack it starts booting but I get the following error:

***ERROR: Root partition has already been mounted read-write. Cannot check!

For filesystem checking to work properly, your system must initially mount the root partition as read only. Please modify your kernel with 'rdev' so that it does. If you're booting with LILO, add a line:

read-only

to the Linux section in your /etc/lilo.conf and type 'lilo' to reinstall it.

This will fix the problem *AND* eliminate this annoying message.

Press Enter to continue.

I followed the instructions in the post
forums.remote-exploit.org/newthread.php?do=postthread&f=17

What do I need to do to fix this error from appearing. I am not sure whether to change the read-write option back to read-only. I don't want to get all the write errors the post indicates you will get.

[m-mode]

same problem, same question

[xtreme04]

Bump this, same problem also. As of now im just hitting enter to continue, any ideas anyone?

[lund99]

I just switched my lilo conf to read-only - no errors after that

[m-mode]

And I am just wondering! Read only means it reads only that partition...?!

[brighamr]

And I am just wondering! Read only means it reads only that partition...?!

the boot code checks the file system (ie. reads it) before mounting it read/write, at least that is what it should be doing. Try following the instructions supplied by the error message (RDEV). If it's still happening, post back.

Here's some more info gleaned from google:

9.12 EXT2-fs: warning: mounting unchecked filesystem.
You need to run e2fsck (or fsck -t ext2 if you have the fsck front-end program) with the -a option to get it to clear the `dirty' flag, and then cleanly unmount the partition during each shutdown.

The easiest way to do this is to get the latest fsck, umount and shutdown commands, available in Rik Faith's util-linux package. You have to make sure that your /etc/rc* scripts use them correctly.

NB: don't try to check a filesystem that's mounted read-write -- this includes the root partition if you don't see

VFS: mounted root ... read-only

at boot time. You must arrange to mount the root filesystem readonly to start with, check it if necessary, and then remount it read-write. Read the documentation that comes with util-linux to find out how to do this.
Note that you need to specify the -n option to mount to get it not to try to update /etc/mtab, since the root filesystem is still read-only and this will otherwise cause it to fail!

[michelinok]

the boot code checks the file system (ie. reads it) before mounting it read/write, at least that is what it should be doing. Try following the instructions supplied by the error message (RDEV). If it's still happening, post back.

Here's some more info gleaned from google:

9.12 EXT2-fs: warning: mounting unchecked filesystem.
You need to run e2fsck (or fsck -t ext2 if you have the fsck front-end program) with the -a option to get it to clear the `dirty' flag, and then cleanly unmount the partition during each shutdown.

The easiest way to do this is to get the latest fsck, umount and shutdown commands, available in Rik Faith's util-linux package. You have to make sure that your /etc/rc* scripts use them correctly.

NB: don't try to check a filesystem that's mounted read-write -- this includes the root partition if you don't see

VFS: mounted root ... read-only

at boot time. You must arrange to mount the root filesystem readonly to start with, check it if necessary, and then remount it read-write. Read the documentation that comes with util-linux to find out how to do this.
Note that you need to specify the -n option to mount to get it not to try to update /etc/mtab, since the root filesystem is still read-only and this will otherwise cause it to fail!

Same problem here...please can you be more specific?
I'm a total newbie, and i don't want to make some mistake...and my english is very poor!

Again...thanks!

[michelinok]

I just switched my lilo conf to read-only - no errors after that

I've tryed your solution, but the problem persists

[timstewart]

Just make sure the bt2 kernel line in your boot loader menu has ro at the end and not rw. It just needs to be mounted as read only. This is for grub anyway.

[michelinok]

Just make sure the bt2 kernel line in your boot loader menu has ro at the end and not rw. It just needs to be mounted as read only. This is for grub anyway.

Yes...i've tryed, but i'm using lilo.
Any info about this problem with lilo?
It's very annoying!