occasionally recovery required on readonly filesystem

Bug #1187032 reported by andschuster
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

After the kernel update prior to linux-image-3.2.0-45-generic and still continuing after the update to linux-image-3.2.0-45-generic I occasionally get the following message at boot time: "recovery required on readonly filesystem" (of my root partition). So it seems that at shutdown time the root filesystem sometimes isn't cleanly unmounted after the second last update of the kernel package.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-45.70-generic 3.2.44
Uname: Linux 3.2.0-45-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.2
Architecture: amd64
Date: Mon Jun 3 17:28:23 2013
InstallationMedia: Kubuntu 10.04.2 LTS "Lucid Lynx" - Release amd64 (20110215.1)
MarkForUpload: True
ProcEnviron:
 LANGUAGE=
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to precise on 2012-03-30 (429 days ago)

Revision history for this message
andschuster (andreas-schuster2) wrote :
affects: xorg (Ubuntu) → linux (Ubuntu)
dino99 (9d9)
tags: added: i386 raring saucy
Revision history for this message
dino99 (9d9) wrote :

Confirm that issue accross ubuntu. Some times ago, most of the affected users and devs was blaming the network config, and it have been baked to stop cleanly now (at least it seems to).
But it makes no doubt that the system is still not unmounted cleanly: is it an udev/systemd race or else. The logs cant help to find something usefull right now; maybe its time to add some tests here too.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux (Ubuntu):
status: New → Confirmed
dino99 (9d9)
tags: added: bot-stop-nagging
Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.10 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc4-saucy/

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.