[Bug 693537] Re: read error problem on ubuntu 10.10. ext4 filesystem

2012-09-24 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/693537

[Bug 693537] Re: read error problem on ubuntu 10.10. ext4 filesystem

2012-07-26 Thread Christopher M. Penalver
Viktor Hampl, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012. Please see this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We were wondering if this is still an issue in a supported release? If so, can you

[Bug 693537] Re: read error problem on ubuntu 10.10. ext4 filesystem

2011-05-04 Thread Brad Figg
** Changed in: linux (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/693537 Title: read error problem on ubuntu 10.10. ext4 filesystem -- ubuntu-bugs mailing

Re: [Bug 693537] Re: read error problem on ubuntu 10.10. ext4 filesystem

2011-02-12 Thread Viktor Hampl
I don't know, my system reported disabling IRQ 19 And Kernel panic errors, when it was happen, system ran very slowly, freeze and i can't run the applications too. Viktor Hampl -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 693537] Re: read error problem on ubuntu 10.10. ext4 filesystem

2011-02-09 Thread Jeoffrey Stiernon
Hello, I have a read error on boot too (grub2 and ext4 fs) Is it hardware related like Viktor seems to conclude ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/693537 Title: read error problem on

[Bug 693537] Re: read error problem on ubuntu 10.10. ext4 filesystem

2011-02-08 Thread Viktor Hampl
Kernel panic - Motherboard error: Motherboard changed! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/693537 Title: read error problem on ubuntu 10.10. ext4 filesystem -- ubuntu-bugs mailing list

[Bug 693537] Re: read error problem on ubuntu 10.10. ext4 filesystem

2011-01-12 Thread Fabio Marconi
** Changed in: linux (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/693537 Title: read error problem on ubuntu 10.10. ext4 filesystem -- ubuntu-bugs

[Bug 693537] Re: read error problem on ubuntu 10.10. ext4 filesystem

2011-01-12 Thread Jeremy Foshee
** Tags added: kj-triage -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/693537 Title: read error problem on ubuntu 10.10. ext4 filesystem -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 693537] Re: read error problem on ubuntu 10.10. ext4 filesystem

2011-01-11 Thread Viktor Hampl
apport information ** Description changed: Read error problem when ubuntu runs only one on pc on ext4 filesystem. System not booting and report Read error. Solution is to use ext3 filesystem instead of ext4. I have MSI G41 M4-L with N10/ICH7 SATA controller, Celeron 430 CPU and Seagate

[Bug 693537] Re: read error problem on ubuntu 10.10. ext4 filesystem

2011-01-11 Thread Viktor Hampl
System ran very slowly today, so it was restarted. After restart system not boot and reports 2 errors ELF (or EFL) header is smaller than expected and msdos5 out of disk I have Ubuntu installed beside win XP in ext4 partition. -- You received this bug notification because you are a member of

[Bug 693537] Re: read error problem on ubuntu 10.10. ext4 filesystem

2011-01-10 Thread Viktor Hampl
apport information ** Tags added: apport-collected ** Description changed: Read error problem when ubuntu runs only one on pc on ext4 filesystem. System not booting and report Read error. Solution is to use ext3 filesystem instead of ext4. I have MSI G41 M4-L with N10/ICH7 SATA

Odp: [Bug 693537] Re: read error problem on ubuntu 10.10. ext4 filesystem

2010-12-28 Thread Viktor Hampl
Sorry i am longly out my pc. I will return to home on 31 december than i will answer to you. V. Hampl Hello Can you please, reproduce the bug then run in a terminal apport-collect 693537 Thanks Fabio ** Package changed: ubuntu = linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New =

[Bug 693537] Re: read error problem on ubuntu 10.10. ext4 filesystem

2010-12-25 Thread Gary M
** Changed in: ubuntu Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/693537 Title: read error problem on ubuntu 10.10. ext4 filesystem -- ubuntu-bugs mailing list

[Bug 693537] Re: read error problem on ubuntu 10.10. ext4 filesystem

2010-12-25 Thread Fabio Marconi
Hello Can you please, reproduce the bug then run in a terminal apport-collect 693537 Thanks Fabio ** Package changed: ubuntu = linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 693537] Re: read error problem on ubuntu 10.10. ext4 filesystem

2010-12-22 Thread Fabio Marconi
hello You have installed with grub2 and it don't works? fabio ** Changed in: ubuntu Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/693537 Title: read error problem

Re: [Bug 693537] Re: read error problem on ubuntu 10.10. ext4 filesystem

2010-12-22 Thread Viktor Hampl
Yes i used grub2 pc/bios version. Is helping start from CD, remove and install grub2 on a while, after several boots it don't works again. Sometimes i must to use The Sea Tools to repair drive which is healthy else. On ext3 it works correctly. -- You received this bug notification because