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 <dev...@gmail.com> 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: > ============================== > > => 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) > -- Corrupted file system ext3 after Jaunty 64 upgrade https://bugs.launchpad.net/bugs/371191 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
