Corrupted file system ext3 after Jaunty 64 upgrade

[halcwb]

Source Package: Not applicable
Ubuntu release: 9.04 64 bit version using ext3 filesystem

Hardware: Lenovo T61P laptop

Description:
Upgraded Ubuntu Intrepid 8.10 64 bit version, which was working fine to 9.04 version. Upgrade went smoothly, everthing seemed to work fine. Then after resume after suspend a lot of error messages and it appeared that there were 'orphaned inodes'. Used fsck to fix the problems. After that I could use the system again, but weird things started to happen:
- The system would suddenly log me out, after which I had to log in again
- Some applications would not start at all
- This ended in a Grub error 17 after a restart

Using the live CD it seemed that the file system is not recognized any more, so it seems to be corrupted. I also did a hardware diagnostic check of my harddrive, but that seems to be OK.

Unfortunately, I cannot get to the system any more, or even mount the harddisk to get additional information. I have attached info on the hardware and the filesystem. Any help will be much appreciated as I am severely stuck.

The output of boot_info_script032.sh shows:

============================= Boot Info Summary: ==============================

 => Grub0.97 is installed in the MBR of /dev/sda and looks on the same drive
    in partition #1 for /boot/grub/stage2 and /boot/grub/menu.lst.

sda1: _________________________________________________________________________

    File system:
    Boot sector type: -
    Boot sector info:
    Mounting failed:
mount: unknown filesystem type ''

sda2: _________________________________________________________________________

    File system: Extended Partition
    Boot sector type: -
    Boot sector info:

sda5: _________________________________________________________________________

    File system: swap
    Boot sector type: -
    Boot sector info:

=========================== Drive/Partition Info: =============================

Drive: sda ___________________ _____________________________________________________

Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x8fd923f7

Partition Boot Start End Size Id System

/dev/sda1 * 63 601,778,834 601,778,772 83 Linux
/dev/sda2 601,778,835 625,137,344 23,358,510 5 Extended
/dev/sda5 601,778,898 625,137,344 23,358,447 82 Linux swap / Solaris

blkid -c /dev/null: ____________________________________________________________

/dev/loop0: TYPE="squashfs"
/dev/sda5: UUID="abfc595f-64a7-4235-81a1-d6817589ad0a" TYPE="swap"

=============================== "mount" output: ===============================

proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /lib/modules/2.6.28-11-generic/volatile type tmpfs (rw,mode=0755)
tmpfs on /lib/modules/2.6.28-11-generic/volatile type tmpfs (rw,mode=0755)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
varrun on /var/run type tmpfs (rw,nosuid,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
rootfs on / type rootfs (rw)
/dev/sr0 on /cdrom type iso9660 (ro,noatime)
/dev/loop0 on /rofs type squashfs (ro,noatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
gvfs-fuse-daemon on /home/ubuntu/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=ubuntu)

[halcwb (halcwb)]

After I disabled wireless network, through the Lenovo hardware switch (disables both bluetooth as wireless network) I was able to suspend/resume and hibernate the machine which was not possible before. So, I suspect that my problem has something to do with the wireless network.

I also discovered some segfaults in the syslog. You can find them on the 2nd of May at which time the problems and weird behavior occurred (see attachment).

[Hans Ole (hrafaelsen)]

I have observed the same problem with my Lenovo T61 laptop. After the upgrade it started to loose files and behave strange (I guess the strange behavior is a result of corrupted files.) After the failed upgrade, I tried reinstall 9.04, this time using ext4. But soon after, it started corrupting files and even the boot loader. I have scanned memory for errors and changed the hard disk to a brand new one. The IT-support department has installed Windows on it to run their usual set of diagnostic tools without finding any problems.

After I got it back from IT support I upgraded the BIOS to the latest version and tried to reinstall 9.04. Same problem. Now I'm back on 8.10 and for the last 6 hours it seems to be running fine. So I'm quite convinced this is a 9.04 related problem and not hardware.

[halcwb (halcwb)]

Actually, I managed to restore the system after running fsck. I also had Opera installed which I removed. At the moment Ubuntu 9.04 64 bit runs stable and I can use the wireless. Also I can hibernate and suspend but sometimes after suspend the caps lock light starts blinking. So I do not have a real clue what caused the problems. It could be:

1. I forcefully shutdown the machine after a period of no response which corrupted the filesystem.
2. The error was caused by a faulty Opera install (which I have now removed)
3. Either suspend or hibernate caused the problems at the first place followed by problem 1 and 2
4. I use the machine on different networks and I am in the habit of suspending the machine on the one network and starting the machine up on the other network.

On a Dell home computer I now experience the same problem. The filesystem is corrupted as well. So I will have to run fsck there as well. Which by the way defaults to the ext2 filesystem, so you have to specify ext3 explicitly!!

Still I think these are quite a serious problems and if Ubuntu wants to get rid of their first and main bug, then these kind of problems should be addressed. As much as I sympathize with the philosophy behind Ubuntu, I have to admit that Windows XP has never failed me in this way. But I will continue to use Ubuntu as operating system of choice for now.

[JeffRoberts (walzmyn)]

I have had similar issues to those described. I am using a Lenovo T61 thinkpad laptop. I have reinstalled Kubuntu 9.04 64bit three times. Upon my upgrade from 8.10 and on the first two re-installs I used the PPA for KDE 4.2.3 and my file system errors happened with in an hour. On the forth try, I did not use the PPA and it took 24 hours for the problems to start.
I have since installed Xubuntu to try to determine if the problem were Ubuntu or KDE specific. Xubuntu has been running for 48 hours now, problem free.
Halcwb mentioned Opera, I had opera installed at the upgrade and reinstalled it on the first re-install, but not on the last two.

[Pablo Besysoft (pablo-cerella)]

I had the same problem as describe here.

I have being using my Lenovo Thinkpad T61 with all its feature (wireless included) without Ubuntu 8.10 64bits. I upgrade to 9.04 and everything was working correctly the first day. At the following day firefox start to fail with a segmentation fault... A couple of hours laters, Opera and Update Manager start to fail too with segmentation faults. On a restart I make a filesystem check and I get some inode errors. After this my .mozilla profiles was lost, and my firefox and others things start to work correctly... But then I start having errors again. And on a restart I get a GRUB error 2. After booting from the live CD and doing a fsck that resolve the new inodes problems, could log in again, but then I get more filesystem errors. :(

I try to reinstall everything fresh from the 9.04 CD and my happiness was gone in a couple of minutes when I start getting new filesystem errors.

I made a complete harddisk check with a tool included in my bios, and the disk was ok. I have a Windows Vista in the same disk, in it own NTFS partition, and it is working correctly without any disk problem.

:(. It is a real pity I have lost some useful information and I am loosing to much time also with this filesystem error.

[Pedro Santos (zubiru)]

I can confirm the exact same problem running a 64bit Jaunty under a Compal FL90 using GNOME or KDE. I just they fix this problem soon, I hate using Windows all the time :P

[maver1ck (jarett-lear)]

I am getting the same exact problem on my T61. I have tried to install 9.04 about 3 times, and it's always the same. It installs fine, and it boots fine, but after a while on first boot, applications stop working, and then I reboot and I get a file system error that never recovers.

Lenovo T61
Intel Centrino
4Gb RAM
Nvidia NVS140

I have tried on my factory 160Gb hard drive, and this morning I went out and got a 320Gb WD drive which had the same results. I have never seen anything like this before, crazy bug.

[wimm (wim-machiels)]

I am also getting that problem on my dell E6500. Currently running live ubuntu and fsck... fingers crossed. I didn 't have the problem in 8.10, but I don 't remember if I used auto-suspend at that time. I strongly suspect that the suspend function is the culprit, so I will turn it of (if I 'm able to boot anyway)

I really hope this can be pinpointed and solved, since I use this machine for work and loosing data is not an option.

[Frédéric PICA (frederic-pica)]

Same problem for me, I have also a Thinkpad T61.
I don't think the problem is related to suspend, after a fresh install, I just have to do some upgrades and to install new packages to get the corruption.
I'm also using the wifi connection, don't know if it's related.
I will try using XFS to see if I got the same problem.

[Frédéric PICA (frederic-pica)]

The problem is not related to ext3, I have done a fresh install using xfs as root file system and after installing some packages :
Reading package lists... Error!
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/fr.archive.ubuntu.com_ubuntu_dists_jaunty_universe_binary-amd64_Packages
E: The package lists or status file could not be parsed or opened.

I can't test without the wifi actually but I will try when I will be at my home at the end of the week.

[maver1ck (jarett-lear)]

I have installed with ext4 and have had better results, or I guess different results. I got a Kernel panic in the middle of the night, and after reboot it froze solid shortly after login. Another reboot and it has been running for about 5 hours with out any errors. I was able to install the updates. I still don't trust it, but it does look like ext4 is working better for some reason.

[tts (tommythesaint)]

I have the same problem on Dell M6300. After upgrade Ubuntu 8.10 64 bit to Ubuntu 9.04 64 bit sometimes after system shutdown, and turn it on disk is checked and fcsk report errors on ext3 partition. Sometimes durring normal work ext3 partition stop being writable or I can't access to my home folder. Yesterday I have to fix grub because it stoped with error code 2.

[Pablo Besysoft (pablo-cerella)]

same as me :(... As it was the laptop I use for work, I had to move back
to 8.10.... I reinstall 8.10 over 9.04 without problems. I have force to
use kernel 2.6.27-14-generic just to avoid potential problems.

Regards
Pablo

> I have the same problem on Dell M6300. After upgrade Ubuntu 8.10 64 bit
> to Ubuntu 9.04 64 bit sometimes after system shutdown, and turn it on
> disk is checked and fcsk report errors on ext3 partition. Sometimes
> durring normal work ext3 partition stop being writable or I can't access
> to my home folder. Yesterday I have to fix grub because it stoped with
> error code 2.
>
>

[maver1ck (jarett-lear)]

After some initial problems the T61 seems to be stable after some updates. ext4 is the file system I'm using right now, there were some minor problems but the computer has been running for almost 24 hours with out any corruption or any kernel panics. I am still a little leery or using it for work, it is my work computer, but I have years of data that take a long time to move around, and I'm really worried that I'm going to start copying the files and they are going to just corrupt again.

I guess the only thing I can do is try and see what happens. The issue, for me at least, seems to be a problem with ext3.

[maver1ck (jarett-lear)]

I don't get the same corruption with ext4, but the T61 is freezing, locking up solid when there is a lot of hard drive work going on. I started copying files, eventually firefox locked up, and then the whole computer, I let it sit over night to see if it would come out of it, but it was still locked up tight this morning. I restarted it and am still able to use the computer with no corruption, but the periodic lock ups is a problem.

[tts (tommythesaint)]

After all updates Ubuntu 9.04 64bit behaves in the same way - sometimes reports errors on ext3 partition.
Yesterday I installed fresh copy of Ubuntu 9.04 64bit from official alternate CD. System installed successfully but, after second reboot, GRUB stopped with error code 17.

[sk (extsknk)]

I can confirm the issues here, even after applying updates:

- Two different T61s (4GB RAM) have these issues:
-- File system corruption either within a few hours or within a couple of days
-- Happens with both ext4 and ext3

I hope the issues are fixed. I learnt an important lesson after wasting several days: never to upgrade on a new Ubuntu distro immediately.

[tts (tommythesaint)]

With reference to my previous posts on file system crash on Dell M6300, I must say that this issue doesnt apear on my second workstation (PC: Asus P5E Deluxe, 4GB RAM, C2D@3GHz, etc...). First I used this workstation with Ubuntu Studio 8.10 64bit, and after upgrade to Ubuntu Studio 9.04 64bit with ext3 file system everything works fine. Even after last upgrade ext3 to ext4.

[maver1ck (jarett-lear)]

tts: that's true, I am using 9.04 on my desktop, and have been since beta and it's been working flawlessly so far. Just my laptop that's having some major issues. My T61 with 9.04 and ext4 file system has been running for about 4 days now with out a restart. It's not showing the same signs of corruptions that I got with ext3, but last week it did freeze when copying files to it. It seems normal other than that, but I'm still scared to try to use it for work.

[John Prather (john-c-prather)]

Here's some info which may (or may not?) help track this down.

In the past 6 days, I've installed ubuntu jaunty 9.04 64bit on a new T500 laptop no less than 6 times. As others here report, I would start doing updates/upgrades, and shortly afterward would run into various issues which appear to all be symptoms of corrupted filesystem:

   * Faulty tree errors doing apt-get update
   * Errors about /var/lib/dpkg/status content
   * Errors about /var/lib/dpkg/info/something.list having blank lines

Then, at some point, dmesg would indicate that there was some ext3-fs or ext4-fs issue, and that journaling is aborted, and that the filesystem is remounted read-only, which would of course then cause all variety of desktop app misbehavior.

A coworker with another T500 that was shipped with mine, is experiencing the same issue on his hardware.

Another coworker with a T500, who got theirs in a different order, had been running Jaunty 64bit for a month now with no such problems, so we started to compare lspci output to see what chips might differ in the two T500's that would have one work solidly for a month while the other can't go 36 hours without corrupting its fs.

The only glaring difference we could see was that his laptop, which wasn't experiencing any problems, had a disk controller with device 20f8, using ahci driver, while mine was using the same model controller, but was listed with a device id 20f7, and which was controlled by ata_piix driver.

Working:

00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03) (prog-if 01)
 Subsystem: Lenovo Device 20f8
 Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 2298
 I/O ports at 1c40 [size=8]
 I/O ports at 1834 [size=4]
 I/O ports at 1838 [size=8]
 I/O ports at 1830 [size=4]
 I/O ports at 1c20 [size=32]
 Memory at fc226000 (32-bit, non-prefetchable) [size=2K]
 Capabilities: <access denied>
 Kernel driver in use: ahci

Failing:

00:1f.2 IDE interface: Intel Corporation ICH9M/M-E 2 port SATA IDE Controller (rev 03) (prog-if 8a [Master SecP PriP])
        Subsystem: Lenovo Device 20f7
        Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 16
        I/O ports at 01f0 [size=8]
        I/O ports at 03f4 [size=1]
        I/O ports at 0170 [size=8]
        I/O ports at 0374 [size=1]
        I/O ports at 1c20 [size=16]
        I/O ports at 1830 [size=16]
        Capabilities: [70] Power Management version 3
        Capabilities: [b0] PCIe advanced features <?>
        Kernel driver in use: ata_piix

I discovered that I could switch my disk controller device from 20f7 to 20f8, and use the ahci driver instead of ata_piix driver by going into my Bios settings, and under Config for the SATA controller, set it to "AHCI" instead of "compatible".

I'd suggest that compatible mode might have had issues, except from the amount of complaints here, it's just as likely that ata_piix is buggy when used on this hardware.

It'll be a couple days before I'm 100% comfortable that the issue is resolved for me, but I'm pretty sure switching the disk controller/behavior to match what has been working for other coworkers should account for the only difference between their hardwar...

[Frédéric PICA (frederic-pica)]

You found it John, I have done that change just before doing all my tests... That's why I've got not problems with XFS, ext4, and ext3 for several days.
The hardware report from halcwb confirm that he's also using ata_piix.
The piix driver in that kernel is buggy, it worked fine previously with the 8.10

[wimm (wim-machiels)]

Hi John,

That might be it... my output of lspci shows I 'm using the same
driver. However,I only have problems once and a while when waking up
the laptop from a suspend, I turned auto-suspend off and it 's running
ok for a week now. I 'm not a real linux expert, what is your advice ?
Should I also switch to another driver ? If so, how is that done ?

thanks in advance,

Wim

00:1f.2 IDE interface: Intel Corporation ICH9M/M-E 2 port SATA IDE
Controller (rev 03) (prog-if 8f [Master SecP SecO PriP PriO])
    Subsystem: Dell Device 024f
    Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 19
    I/O ports at 6e70 [size=8]
    I/O ports at 6e78 [size=4]
    I/O ports at 6e80 [size=8]
    I/O ports at 6e88 [size=4]
    I/O ports at 6ea0 [size=16]
    I/O ports at 6e90 [size=16]
    Capabilities: [70] Power Management version 3
    Capabilities: [b0] PCIe advanced features <?>
    Kernel driver in use: ata_piix

John Prather wrote:
> Here's some info which may (or may not?) help track this down.
>
> In the past 6 days, I've installed ubuntu jaunty 9.04 64bit on a new
> T500 laptop no less than 6 times. As others here report, I would start
> doing updates/upgrades, and shortly afterward would run into various
> issues which appear to all be symptoms of corrupted filesystem:
>
> * Faulty tree errors doing apt-get update
> * Errors about /var/lib/dpkg/status content
> * Errors about /var/lib/dpkg/info/something.list having blank lines
>
> Then, at some point, dmesg would indicate that there was some ext3-fs or
> ext4-fs issue, and that journaling is aborted, and that the filesystem
> is remounted read-only, which would of course then cause all variety of
> desktop app misbehavior.
>
> A coworker with another T500 that was shipped with mine, is experiencing
> the same issue on his hardware.
>
> Another coworker with a T500, who got theirs in a different order, had
> been running Jaunty 64bit for a month now with no such problems, so we
> started to compare lspci output to see what chips might differ in the
> two T500's that would have one work solidly for a month while the other
> can't go 36 hours without corrupting its fs.
>
> The only glaring difference we could see was that his laptop, which
> wasn't experiencing any problems, had a disk controller with device
> 20f8, using ahci driver, while mine was using the same model controller,
> but was listed with a device id 20f7, and which was controlled by
> ata_piix driver.
>
> Working:
>
> 00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03) (prog-if 01)
> Subsystem: Lenovo Device 20f8
> Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 2298
> I/O ports at 1c40 [size=8]
> I/O ports at 1834 [size=4]
> I/O ports at 1838 [size=8]
> I/O ports at 1830 [size=4]
> I/O ports at 1c20 [size=32]
> Memory at fc226000 (32-bit, non-prefetchable) [size=2K]
> Capabilities: <access denied>
> Kernel driver in use: ahci
>
> Failing:
>
> 00:1f.2 IDE interface: Intel Corporation ICH9M/M-E 2 port SATA IDE Controller (rev 03) (prog-if 8a [Master SecP PriP])
> Subsystem: Lenovo Device 20f7
> Flags: bus master, 66MHz, medium devsel, late...

[halcwb (halcwb)]

John,

I think I can confirm your solution. I haven't had any corrupted file system problems any more since the 10th of May. I changed a couple of things, among which switching from SATA compatibility mode to AHCI. Since then the system is more or less stable. More or less, because I have an occasional freeze up of the system.

So, I probably solved the file system problem without knowing and by mere accident.

Thanks for your research.

Casper

[maver1ck (jarett-lear)]

Same goes for me, I switched to AHCI and the corruption problem is gone, but I too am getting the occasional freeze, especially when the hard drive is working hard, like copying large files.

Thanks,

Jarett

[John Prather (john-c-prather)]

Wim,

I'm not very familiar with ubuntu, so am probably not the best source for advice. Your controller device appears to be some dell which differs slightly from the one I have, although they both were using ata_piix. It's possible that the driver doesn't have such big issues with some controllers as it does with others. If your system really seems stable and isn't experiencing regular filesystem corruption, then my advice might be "if it ain't broke, don't fix it." There's no reason to go looking for a solution if you don't have a problem.

On the other hand, if you would like to be able to use suspend/standby, and you have the patience, you may wish to see if switching from compatibility to ahci helps let you use the suspend feature again without causing you the corruption headaches.

My filesystem corruption had been happening all the time, sometimes while doing apt-get update or dist-upgrade, other times while i was away from the keyboard with the screen locked, it definitely wasn't as limited to a specific action as appears to be the case with your controller.

Good luck!

-john

[wimm (wim-machiels)]

Hi John,

Thanks for your answer ! I was celebrating too soon... Just recovered
from another crash without going into suspend mode. Very annoying since
this is my work machine.
by switching to ahci, you probably mean switching in the bios ?
Currently I have no rights doing so, but I think I have a good reason
for the switch.

regards,

Wim

John Prather wrote:
> Wim,
>
> I'm not very familiar with ubuntu, so am probably not the best source
> for advice. Your controller device appears to be some dell which
> differs slightly from the one I have, although they both were using
> ata_piix. It's possible that the driver doesn't have such big issues
> with some controllers as it does with others. If your system really
> seems stable and isn't experiencing regular filesystem corruption, then
> my advice might be "if it ain't broke, don't fix it." There's no reason
> to go looking for a solution if you don't have a problem.
>
> On the other hand, if you would like to be able to use suspend/standby,
> and you have the patience, you may wish to see if switching from
> compatibility to ahci helps let you use the suspend feature again
> without causing you the corruption headaches.
>
> My filesystem corruption had been happening all the time, sometimes
> while doing apt-get update or dist-upgrade, other times while i was away
> from the keyboard with the screen locked, it definitely wasn't as
> limited to a specific action as appears to be the case with your
> controller.
>
> Good luck!
>
> -john
>
>

[tts (tommythesaint)]

I think I can confirm solution too. I haven't had any corrupted file system problems any more since I switched from SATA compatibility mode to AHCI. Yesterday I converted ext3 to ext4 partition and system is still stable.

[sk (extsknk)]

Thanks for the 'workarounds' reported here.
(let's distinguish between fix for the issue & AHCI 'workaround' - if folks don't mind)

[maver1ck (jarett-lear)]

The workaround might work for some, but while I don't get corruptions, I still have random kernel panics. I just reinstalled 8.10 :) Happy with that for now.

[Scott (scott-lhommedieu)]

I also seem to have run into this issue. I have a Dell D810.
I upgraded from 8.10 to 9.04. System seemed stable but after reboot the disk is corrupt and mounted read only.

This bug seems serious enough to get more attention that it currently has.

[Khudsa (povale69)]

I'm also affected on a Compal fl90, 4GB, 250 GB HD (WDC WD2500BEVS), 1GB Robson memory, PM965 and NVIDIA 8600M.

[JeffRoberts (walzmyn)]

After my troubles with this bug, I went back to Kubuntu 8.10.
I have now compiled the 2.6.30 kernel myself. I used it with 8.10 for 2 days and then upgraded to 9.04. I have been on 9.04 for 4 days and everything seems to be running fine.
I ran 4 very large bit torrents for a couple of days and have purposefully installed lots of packages and removed several to test out the file system. Everything seems to be running like a top.
So, as best as I can tell, this problem is fixed in the 2.6.30 kernel.
If that makes its way into the repo, I would think that an upgrade would be safe, but I don't think it's going to be in the repo anytime soon.

[Pablo Besysoft (pablo-cerella)]

Hi, have some else try 9.04 with kernel 2.6.30? is the issue resolve in
that kernel?
thanks
Pablo

PD: I am still running 8.10 until I found an stable version of 9.04 for
my thinkpad t61 that I use for work

JeffRoberts wrote:
> After my troubles with this bug, I went back to Kubuntu 8.10.
> I have now compiled the 2.6.30 kernel myself. I used it with 8.10 for 2 days and then upgraded to 9.04. I have been on 9.04 for 4 days and everything seems to be running fine.
> I ran 4 very large bit torrents for a couple of days and have purposefully installed lots of packages and removed several to test out the file system. Everything seems to be running like a top.
> So, as best as I can tell, this problem is fixed in the 2.6.30 kernel.
> If that makes its way into the repo, I would think that an upgrade would be safe, but I don't think it's going to be in the repo anytime soon.
>
>

[MatB (matteo-brusa)]

Same problem with a DELL M4300, the controller ( Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 02) (prog-if 01)) was using the ata_piix driver.
Switched to AHCI in the BIOS, no problems so far.

[Garrett (floft)]

Same problem for me, but switching to use AHCI also fixed it. So I'm happy with Ubuntu once more. I had been enduring just doing a fsck multiple times a week for a long time, but so far I haven't had to do that anymore. I hope this continues.

[Crunchy the Headcrab (m-greb)]

I'm having the same problem. I'm using an Asus G50vt-X1 laptop. The options in my bios for controllers are: enhanced, raid, and compatibility. I have to use compatibility mode for Linux to recognize my drives properly. However, in Ubuntu I get a corrupted file system frequently and often when I run in compatibility mode. It happens in Ubuntu and Kubuntu. It happens randomly, not just on boot and causes install problems and segmentation faults. When I reboot, I'm informed that the file system is corrupted sometimes beyond repair. This doesn't happen in ANY other distribution, so it seems that it isn't Linux specific but Ubuntu specific.

It's the only system stopping bug that keeps me from using Ubuntu. Live CD works fine.

[Crunchy the Headcrab (m-greb)]

I'm sorry. I meant to say that it causes problems with installing software from within Ubuntu. Not installing the OS itself.

[Adam Dickmeiss (adam-indexdata)]

Bug #360952 mentioned HPET (in fact I was the only one to comment on it). In any case.. The problem persists even after messing with HPET. So this did not solve it.

However, manually installing Linux kernel 2.6.29.3 from source DID solve the problem (or at least the symptoms).

Seems like a serious bug to me!

[Kenneth P. Turvey (ktectropy)]

I've had the same problem over the last couple of days on a new Jaunty install. My machine is a Dell Inspiron 1525. I'm already using AHCI mode according to the bios. I'm going to try one reinstall and if I can't get it to work, I'm going to have to back the version back down. This is a really severe bug.

I'll check to see what driver I'm using and see if it matches that specified above. I should note that this is still a problem on July 31st with all the latest updates. It really needs to be corrected.

[Kenneth P. Turvey (ktectropy)]

My computer is using the ata_piix driver, so it looks like we all have that in common. My bios already says that I'm using the AHCI mode though... so that's strange.

[Niklas Therning (niklas-therning)]

I think I have experienced the same bug om my Dell XPS M1330 laptop recently after installing 9.04. The disk has behaved strangely now twice. Had to run e2fsck on it to fix things. Not good!

Anyway, my bios was set to SATA mode instead of AHCI, which is the default, since I've tried to install Mac OS X on this laptop and that was required to get OS X to work. My old 8.10 installation worked just fine with the SATA setting. Have reset the bios to AHCI. Hopefully that will prevent the same from occurring again.

lspci says:

00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port (rev 0c)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 02)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 02)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 02)
00:1c.5 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 6 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f2)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation GeForce 8400M GS (rev a1)
03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05)
03:01.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22)
03:01.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 12)
03:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12)
03:01.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev ff)
09:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5906M Fast Ethernet PCI Express (rev 02)
0c:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)

[Devin Walters (devinw)]

Confirming this problem is still ongoing for my T61p. I have installed Ubuntu x64 3 times. It does seem to oddly correspond with the use of the wireless connection. I was at the command line and installed liferea. I started liferea and started setting things up. It died for no reason, so I tried to restart it. I pulled up the terminal to check syslog and I get something about "module not loaded" -- approximately 5 lines long. This is the second time I've seen this same behavior with x64 9.04. It almost seemed as if someone was rm -rf'ing my /. Things just drop out, directories are empty, etc. When I reboot I get grub error 17. Luckily this did not tank my other work-related windows install. On the last disk I was using, this disk corruption managed to ruin everything on the entire disk.

I am running in Compatability mode, not AHCI. I will try and switch and see if that helps anything. Hopefully I have not wasted yet another day on configuring Ubuntu x64, only to be met with this same issue.

Originally I thought it was a bad disk, so I switched to a brand new disk, and this issue is still a problem.

I have to suggest that the severity of this bug be set to critical. Something is very, very wrong here.

[Devin Walters (devinw)]

I should also add that my file system corruption seems to coincide with the use of my wireless.

After using my wireless for ~30min I was met with massive corruption, not the slow corruption others have mentioned.

Could anyone confirm that expressly using their wireless drivers speeds up the problem?

How about the time of day the problem occurs? I know this seems pretty far-fetched and I haven't confirmed it, but the massive corruption I've witnessed happened between 12:45pm and 1:15pm. Could there be something happening during that time, a sync problem, that throws everything massively out of whack?

[Hans Ole (hrafaelsen)]

The worst problems was solved for me when I switched to AHCI. However,
the system never became stable. The wireless link often died, and I
had to reconnect. Also there was lots of crashes, but no corruption of
the file system. Some time it crashed just out of the blue, while
other times it went for a longer death spiral. Some processes refused
to die, file system was suddenly mounted in read-only mode, etc... and
then you know if was going to die quite soon. I got the feeling that
it most often died related to suspending, configuring network, and
when adding/removing another screen (have a 'nVidia Corporation Quadro
NVS 140M (rev a1)' card).

A few days ago I got so fed up with it that I decided to switch to
9.10 (development branch). So far it has been running flawless. I
guess it's still to early to say that all problems will be fixed with
the next release, but it really looks promising. So if you are having
lots of problems you might want to give the next version a try. It
looks far better as far as I can tell.

Hans Ole

On Wed, Oct 7, 2009 at 10:12 PM, samadhi <email address hidden> wrote:
> I should also add that my file system corruption seems to coincide with
> the use of my wireless.
>
> After using my wireless for ~30min I was met with massive corruption,
> not the slow corruption others have mentioned.
>
> Could anyone confirm that expressly using their wireless drivers speeds
> up the problem?
>
> How about the time of day the problem occurs?  I know this seems pretty
> far-fetched and I haven't confirmed it, but the massive corruption I've
> witnessed happened between 12:45pm and 1:15pm.  Could there be something
> happening during that time, a sync problem, that throws everything
> massively out of whack?
>
> --
> Corrupted file system ext3 after Jaunty 64 upgrade
> https://bugs.launchpad.net/bugs/371191
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: Confirmed
>
> Bug description:
> Source Package: Not applicable
> Ubuntu release: 9.04 64 bit version using ext3 filesystem
>
> Hardware: Lenovo T61P laptop
>
> Description:
> Upgraded Ubuntu Intrepid 8.10 64 bit version, which was working fine to 9.04 version. Upgrade went smoothly, everthing seemed to work fine. Then after resume after suspend a lot of error messages and it appeared that there were 'orphaned inodes'. Used fsck to fix the problems. After that I could use the system again, but weird things started to happen:
> - The system would suddenly log me out, after which I had to log in again
> - Some applications would not start at all
> - This ended in a Grub error 17 after a restart
>
> Using the live CD it seemed that the file system is not recognized any more, so it seems to be corrupted. I also did a hardware diagnostic check of my harddrive, but that seems to be OK.
>
> Unfortunately, I cannot get to the system any more, or even mount the harddisk to get additional information. I have attached info on the hardware and the filesystem. Any help will be much appreciated as I am severely stuck.
>
> The output of boot_info_script032.sh shows:
>
> ============================= Boot Info Summary: ====================...

[Victor Vargas (kamus)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage , so I have classified this bug as a bug in linux kernel package.

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.