Upgrading to 12.10 get main hd not ready

[Giovanni Bortolozzo]

Since the upgrade to 12.10 at boot time, I often get the message that one partition of the main hd it not ready. The system runs from two partition on the same SATA disk.
/dev/sdc1 on / type ext4 (rw,relatime,errors=remount-ro)
/dev/sdc2 on /disk2 type ext4 (rw,errors=remount-ro)

It stops on /disk2, but when I press M to manually recover, the partition is already mounted and when e2fsck don't find any problems. Then almost every day it starts to get errors from the disk and the disk are automatically remounted read-only (obviusly at the moment I don't have a log of these errors since the log files can't be written... but I will add them to the report the next time). After the reboot all the partition must be checked since the journaling file is corrupted.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-18-generic 3.5.0-18.29
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Uname: Linux 3.5.0-18-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu6
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: borto 2812 F.... pulseaudio
 /dev/snd/controlC1: borto 2812 F.... pulseaudio
 /dev/snd/controlC0: borto 2812 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Sun Oct 28 07:30:47 2012
HibernationDevice: RESUME=UUID=bcf548d7-27f5-4833-a040-bb768d9f4b82
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 002 Device 002: ID 413c:3010 Dell Computer Corp. Optical Wheel Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System manufacturer System Product Name
MarkForUpload: True
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=6501ccba-6176-47e1-8cec-45fc88a76cb4 ro splash quiet
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-18-generic N/A
 linux-backports-modules-3.5.0-18-generic N/A
 linux-firmware 1.95
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to quantal on 2012-10-07 (20 days ago)
WifiSyslog:

dmi.bios.date: 11/18/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 1406
dmi.board.name: P5N-E SLI
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision1406:bd11/18/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Giovanni Bortolozzo (giovanni-bortolozzo)]

Today I got the problem with the disk (see the end of the attached dmesg.out file).

I googled around I find again these information:

http://www.j-schmitz.net/blog/today-i-fixed-my-hdd-breakdowns

Seems to be related to the mix of the irq-balancing and the nforce chips.

I already try to disable the irq-balancing (I add the option noirqbalance to grub)... but then I got the problem with the network card... so yesterday I reenable it (and today I got this error).

It is really related to the disk usage.

[penalvch (penalvch)]

Giovanni Bortolozzo, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc4

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

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