Recovery of root partition required on every reboot

[Jani Frilander]

Hi everyone.

I installed Linux Mint 14 on 2 machines after frustration caused by Ubuntu 12.04. I'm having the same problem after reboot on these machines.

Piece of dmesg output:

Code: Select all

[    2.154970] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[    2.154975] EXT4-fs (sda1): write access will be enabled during recovery
[    3.989440] EXT4-fs (sda1): recovery complete


I first noticed this major problem after upgrade from Ubuntu 10.04 to 12.04 and still have it with LM 14. There must be something seriously wrong with system scripts that causes root partition not to be unmounted cleanly on shutdown inherited from Ubuntu or even Debian.

Could anyone try if they share the problem? Please do a

Code: Select all

dmesg | grep recovery

and paste the results here.

Sincerely,
Jani

[viking777]

I have it in Ubuntu 12.10 - exactly the same messages as yourself. It is not present at all in MInt 14 (Cinnamon).

[wayne128]

I checked a few of my Debian OS partitions , some tracking Stable, some tracking SID.
None has what you described.


typically, relevant dmesg message looks similar as below

Code: Select all

wayne@debianbox:~$ dmesg | grep recovery
wayne@debianbox:~$ dmesg | grep EXT4
[    3.738678] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
[    9.232274] EXT4-fs (sda6): re-mounted. Opts: (null)
[   10.068854] EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro

[Jani Frilander]

I'm running Linux Mint 14 Mate but I don't think it makes any difference. The workaround is the same as for Ubuntu 12.04. Switch to console [CTRL+ALT+F1] and type:

Code: Select all

sudo telinit 1
shutdown -r now


After this i get clean reboot.

[viking777]

I guess I should pay more attention to topic titles Jani, I have finally fallen into the understanding that this topic is about reboots not boots In that case I can confirm that I get the same error message as you on both Mint and Ubuntu, last time I tested Mint I did so from a cold boot not a reboot, that is why I got no result.

I can confirm that your workround works on both distros also.

[Jani Frilander]

Nice to hear someone else gets the same results, as it proves I haven't gotten out of my mind. Does anybody agree me that this is behavior that MUST NOT happen? I filed a bug a while a go but got little attention. https://bugs.launchpad.net/ubuntu/+bug/1064185

[oobetimer]

Maybe ext3 works better, because there is less stuff on the memory when shutting down the computer. Ext4 uses smart writing, so the shutting commands have not enough time for writing to the hard drive when the computer is shutting down fastly?

[Jani Frilander]

Maybe ext3 works better, because there is less stuff on the memory when shutting down the computer. Ext4 uses smart writing, so the shutting commands have not enough time for writing to the hard drive when the computer is shutting down fastly?

Actually when I first noticed this problem my root partition was on ext3, as can be seen from my bug report.

Code: Select all

[    3.951378] EXT3-fs (sda1): recovery required on readonly filesystem
[    3.951445] EXT3-fs (sda1): write access will be enabled during recovery
[    7.584278] kjournald starting.  Commit interval 5 seconds
[    7.584349] EXT3-fs (sda1): recovery complete
[    7.584769] EXT3-fs (sda1): mounted filesystem with ordered data mode


Can anyone else test if they share this problem? I think this is a serious issue, since it might lead to data loss. This doesnt affect my system since I'm running Fedora 18 at the moment.