*** This bug is a duplicate of bug 346691 ***
https://bugs.launchpad.net/bugs/346691
** Changed in: linux (Fedora)
Status: Confirmed = Invalid
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You received this bug notification because you are a member of
Upgrading to a newer kernel *see links on bug 346691 to get installable
debs* fixed my problems.
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
*** This bug is a duplicate of bug 346691 ***
https://bugs.launchpad.net/bugs/346691
** This bug has been marked a duplicate of bug 346691
jaunty kernel 2.6.28-11 kernel update renders the system un-usable.
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You
*** This bug is a duplicate of bug 346691 ***
https://bugs.launchpad.net/bugs/346691
this is actually a duplicate of bug 346691, since you have about the same
hardware config (intel mobo with nvidia gfx etc) as we do.
errors won't occur if you use kernel version 2.6.28-9-generic.
otherwise
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I reinstalled Intrepid 64 bits, no problem at all… It is definitely a
software problem appeared between jaunty alpha 4 and jaunty alpha 6.
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You received this
I just installed Jaunty 32 bits (instead of 64 bits) EXT4, it seems to
work without any problem until now…
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Same issue on brand new hard drive (320 Gb Western Digital Scorpio
Black). I installed 64-bit Jaunty beta/ RC on a new hard drive and got
broken apt, segfaults and random loss of data. I returned the hard drive
thinking it may be a faulty drive. I just got a replacement for the
initial hard drive
** Attachment added: syslog-ext4
http://launchpadlibrarian.net/26010527/syslog-ext4.txt
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: lspci -vvnn
http://launchpadlibrarian.net/26010500/lspcivvn.txt
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: kern_log
http://launchpadlibrarian.net/26010592/kern.log
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I am now pretty certain this has to do with the kernel as the comments
in the below bug report reflect exactly my epxeriences after a fresh
install of Jaunty 64-bit:
jaunty kernel 2.6.28-11 kernel update renders the system un-usable
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/346691
--
After a fresh reinstallation of jaunty final, during an apt-get install :
Write error on output file - write (30 read-only file system)
I will attach the requested files.
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You received this bug notification because you
** Attachment added: lspci --vvnn
http://launchpadlibrarian.net/25970260/lspci
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: /etc/fstab
http://launchpadlibrarian.net/25970279/fstab
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
During reboot : EXT4-fs error (device sda1): __ext4_get_inode_loc:
unable to read inode block - inode=377, block=3941531671
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: kern.log
http://launchpadlibrarian.net/25970267/kern.log
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Since Jaunty is released, I installed it on a partition on my harddisk, hoping
that the released version would work for me.
As soon as I installed a few packages, these file system errors show up again,
so I used an intrepid live-cd to fix the errors and than booted to intrepid. As
usual, no
** Attachment added: fstab
http://launchpadlibrarian.net/25950737/fstab
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
note that while kern.log and fstab are from the jaunty partition, the
result of lspci-vvnn was obtained from intrepid.
** Attachment added: lspci -vvnn
http://launchpadlibrarian.net/25950755/lspcivvnn
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You received
to be clear about it, i also used the 64 bit jaunty version, but in the
meantime i went back to intrepid
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
same phenomenon here, in case it has not been noted I just want to add
that all (r)om, kaliif (according to ubuntuforums) and the fedora user
all use 64 bit jaunty.
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You received this bug notification because you are a
** Changed in: linux (Fedora)
Status: Unknown = Confirmed
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
looks a bit like https://bugzilla.redhat.com/show_bug.cgi?id=488343 and
http://ubuntuforums.org/showthread.php?t=1130123
** Bug watch added: Red Hat Bugzilla #488343
https://bugzilla.redhat.com/show_bug.cgi?id=488343
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
** Also affects: linux (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=488343
Importance: Unknown
Status: Unknown
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It does look similar to my conditions. But my files corrupted with both
ext3 and ext4 and I'm pretty sure it's not the hd (problems started with
jaunty install, hd is new, smartmontools showed no errors)
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You received
Please replace about 2 weeks using jaunty alpha 6 EXT4, but after an upgrade…
by :
about 2 weeks using jaunty alpha 4 EXT4, but after an upgrade… in my previous
message.
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You received this bug notification because you
I said a bit too quickly that the problem was hardware, because jaunty
alpha/beta/rc had problems both with EXT3 and EXT4.
As I saw several people having the same problems as me, I reinstalled
Intrepid (ext3), and I have no problem at all !
I think there was a regression between jaunty alpha 4
** Changed in: linux (Ubuntu)
Status: New = Incomplete
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Per conversation on irc, waiting for lspci -vvnn, /var/log/kern.log and
/etc/fstab
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The problems seems to be my harddrive. I reinstalled using EXT3, I have
still a lot of problems :(
--
[Jaunty beta] many ext4-fs errors
https://bugs.launchpad.net/bugs/350268
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Hi rom1v,
Sounds like this might be leaning towards being a hw issue. Please keep
us posted if you happen to get a new hard drive and are able to test.
Thanks.
** Changed in: linux (Ubuntu)
Status: New = Incomplete
--
[Jaunty beta] many ext4-fs errors
** Attachment added: syslog-ext4
http://launchpadlibrarian.net/24449383/syslog-ext4
** Description changed:
For about one week, I have a lot of ext4 problems, in ubuntu jaunty
alpha 6 then jaunty beta.
I had a file system check failed during a boot, so I fsck it and repaired
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
34 matches
Mail list logo
