[Bug 343919] Re: Nvidia MCP67 AHCI ata timeout exception with data loss
I'm actually leaning towards that being a hardware problem and I have replaced that harddrive now. Never happened on another disk and I have a number of other ext4 filesystems now. Closing, but I can't test of cource! -- Nvidia MCP67 AHCI ata timeout exception with data loss https://bugs.launchpad.net/bugs/343919 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
[Bug 343919] Re: Nvidia MCP67 AHCI ata timeout exception with data loss
** Changed in: linux (Ubuntu) Status: In Progress = Invalid -- Nvidia MCP67 AHCI ata timeout exception with data loss https://bugs.launchpad.net/bugs/343919 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
[Bug 343919] Re: Nvidia MCP67 AHCI ata timeout exception with data loss
** Tags added: ext4 -- Nvidia MCP67 AHCI ata timeout exception with data loss https://bugs.launchpad.net/bugs/343919 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
[Bug 343919] Re: Nvidia MCP67 AHCI ata timeout exception with data loss
Hi Ernst Persson, Are you still using an ext4 filesystem? If so, do you still see this issue with the latest 2.6.28-15.48 Jaunty kernel? If so, I've backported some additional ext4 related patches and put some test kernels at: http://people.canonical.com/~ogasawara/ext4-jaunty/ There is currently an amd64 test kernel there but I'll be adding i386 once it finishes building. Please let us know your results if you are able to test. Also, the latest Karmic 9.10 Alpha images contain a newer 2.6.31 kernel with additional ext4 related patches. If you wanted to test that ISO CD images are available at http://cdimage.ubuntu.com/releases/karmic/ . Thanks. -- Nvidia MCP67 AHCI ata timeout exception with data loss https://bugs.launchpad.net/bugs/343919 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
[Bug 343919] Re: Nvidia MCP67 AHCI ata timeout exception with data loss
I found somewhere on launchpad.net that adding all_generic_ide to kernel command line can be helpful and it worked in my case with very similar errors (although on Dell XPS m1530). -- Nvidia MCP67 AHCI ata timeout exception with data loss https://bugs.launchpad.net/bugs/343919 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
[Bug 343919] Re: Nvidia MCP67 AHCI ata timeout exception with data loss
Just for fun I compiled my own kernel with CONFIG_PREEMPT=y Seems like this stops the error from happening on my system. -- Nvidia MCP67 AHCI ata timeout exception with data loss https://bugs.launchpad.net/bugs/343919 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
[Bug 343919] Re: Nvidia MCP67 AHCI ata timeout exception with data loss
My comment above.. ...and it's workaround, may be more relevant to the Alert! /dev/disk busybox failure to boot problem, than this thread which was said to be the original duplicate bug. That's why it's here. I do not know if this bug is in fact the cause of being dropped to busybox but the workaround worked for me and I just wanted to leave a trail for those of us that might wide up here. I posted this (previously VERY hard to find) workaround in the other bug duplicate and in the forums. Hopefully this will cause many to stick with (K)ubuntu. We had no other kernel to boot, once the upgrade process nixed the newly installed one. Now we can move ahead. Obviously, this workaround can be used with any singular kernel boot failure (to get another one). Because SOMETIMES, another clean install wastes time (but clean installs are recommended). -- Nvidia MCP67 AHCI ata timeout exception with data loss https://bugs.launchpad.net/bugs/343919 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
[Bug 343919] Re: Nvidia MCP67 AHCI ata timeout exception with data loss
From my saved partition and chroot with Hardy 8.04 (you could use a live CD), this is how I fixed my Jaunty 9.04 fresh, beta install; where I could boot again. I look everywhere and tries everything. NONE of th buzybox commands worked for me. I do NOT have raid and their was no UUID or /dev naming error. Only the following worked for me and I still do not know why the newly installed kernal failed to boot after upgrading it. Perhaps it didn't upgrade or something because once I got back in using chroot, I had to run the apt-get fix command it recommends. Unless that was a limit of the chroot, I don't know. This was ugly and I almost gave up. In a terminal (we're using sudo for root here) Where X is your correct drive number, like /dev/sda2 for example sudo mount /dev/sdaX /mnt (You can cut and paste the commands below) sudo mount --bind /dev /mnt/dev sudo mount --bind /proc /mnt/proc sudo mount --bind /sys /mnt/sys sudo cp /etc/resolv.conf /mnt/etc/resolv.conf sudo chroot /mnt /bin/bash Then: apt-get install etc. I believe I did a: apt-get update (then the suggested fix command and...) apt-get upgrade While the kernel didn't appear to be different I not sure that it wasn't a newer fix. It booted. Now, after doing upgrades back in Jaunty again, I'm about to reboot and try the newest kernel (it just installed). I hope this helps you as much as it did me! -- Nvidia MCP67 AHCI ata timeout exception with data loss https://bugs.launchpad.net/bugs/343919 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
[Bug 343919] Re: Nvidia MCP67 AHCI ata timeout exception with data loss
Still happened. Interesting note from the exception though: [ 1212.290506] Aborting journal on device sda4:8. [ 1212.293404] EXT4-fs error (device sda4) in ext4_reserve_inode_write: Journal has aborted ** Attachment added: dmesg 5 http://launchpadlibrarian.net/24143920/fel5.txt -- Nvidia MCP67 AHCI ata timeout exception with data loss https://bugs.launchpad.net/bugs/343919 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
[Bug 343919] Re: Nvidia MCP67 AHCI ata timeout exception with data loss
Ran 7 hours more on ext3 with 2.6.28-02062807-generic, no exceptions. -- Nvidia MCP67 AHCI ata timeout exception with data loss https://bugs.launchpad.net/bugs/343919 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
[Bug 343919] Re: Nvidia MCP67 AHCI ata timeout exception with data loss
Most similar thing I could find on kernel.org: http://bugzilla.kernel.org/show_bug.cgi?id=11148 -- Nvidia MCP67 AHCI ata timeout exception with data loss https://bugs.launchpad.net/bugs/343919 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
[Bug 343919] Re: Nvidia MCP67 AHCI ata timeout exception with data loss
Can you try the work-arouns suggested in comment 8 ? Add libata.force=nohrst to the kernel command-line while doing an 'ext4' test? -- Nvidia MCP67 AHCI ata timeout exception with data loss https://bugs.launchpad.net/bugs/343919 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
[Bug 343919] Re: Nvidia MCP67 AHCI ata timeout exception with data loss
** Summary changed: - [jaunty] ata timeout exception with data loss + Nvidia MCP67 AHCI ata timeout exception with data loss -- Nvidia MCP67 AHCI ata timeout exception with data loss https://bugs.launchpad.net/bugs/343919 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
[Bug 343919] Re: Nvidia MCP67 AHCI ata timeout exception with data loss
As a point to note right now - may mean something or nothing. For each error log, no matter which kernel, it is accompanied by: ext4_journal_start_sb: Detected aborted journal And the bug reporter tells us that ext3 file-systems don't suffer the same issue. -- Nvidia MCP67 AHCI ata timeout exception with data loss https://bugs.launchpad.net/bugs/343919 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
[Bug 343919] Re: Nvidia MCP67 AHCI ata timeout exception with data loss
Guess this should be posted in the kernel bugzilla also. Ran dpkg straigth for 5 hours with 2.6.28-02062807-generic on ext3, no exceptions. Will continue to run it tonight. -- Nvidia MCP67 AHCI ata timeout exception with data loss https://bugs.launchpad.net/bugs/343919 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