That doesn't sound too good. I've got no idea what's wrong with it, it's working fine here now for over two days :x.
Have you tried to just reconnect all the cables and/or check if they're nog broken? Though that sounds unlikely to me since you're using sata disks. Also try a e2fsck -f <disk> This will force a check on your disk. Do the error's stop after one or two times? Jos On Fri, Mar 14, 2008 at 6:55 PM, Fred <[EMAIL PROTECTED]> wrote: > Now, I was listening to music in Rhythm box. > The music was even on sda5, not sdb1. > > I was a little bit afk, then came back, and saw applications dim as I > sat down. > > System was going haywire again. > > [numbers] EXT3-fs error (device sdb1): ext3_journal_start_sb: Detected > aborted journal > [numbers] Remounting filesystem read-only > [numbers] EXT3-fs error (device sdb1) in ext3_reserve_inode_write: Journal > has aborted > > Then I boot the 7.10 LiveCD. > [EMAIL PROTECTED]:/var/log$ cat debug | grep -i "ext3" > Mar 14 17:44:26 ubuntu kernel: [ 207.614203] ext3_orphan_cleanup: > deleting unreferenced inode 1485348 > Mar 14 17:44:26 ubuntu kernel: [ 207.614227] ext3_orphan_cleanup: > deleting unreferenced inode 1485353 > [EMAIL PROTECTED]:/var/log$ > > [EMAIL PROTECTED]:/var/log$ cat kern.log | grep -i "ext3" > Mar 14 17:44:26 ubuntu kernel: [ 46.415302] EXT3-fs: INFO: recovery > required on readonly filesystem. > Mar 14 17:44:26 ubuntu kernel: [ 46.415305] EXT3-fs: write access will > be enabled during recovery. > Mar 14 17:44:26 ubuntu kernel: [ 207.614198] EXT3-fs: sdb1: orphan > cleanup on readonly fs > Mar 14 17:44:26 ubuntu kernel: [ 207.614203] ext3_orphan_cleanup: > deleting unreferenced inode 1485348 > Mar 14 17:44:26 ubuntu kernel: [ 207.614227] ext3_orphan_cleanup: > deleting unreferenced inode 1485353 > Mar 14 17:44:26 ubuntu kernel: [ 207.614251] EXT3-fs error (device sdb1): > ext3_free_branches: Read failure, inode=1485353, block=3000002 > Mar 14 17:44:26 ubuntu kernel: [ 207.617633] EXT3-fs error (device sdb1): > ext3_get_inode_loc: unable to read inode block - inode=1485246, > block=2981893 > Mar 14 17:44:26 ubuntu kernel: [ 207.621596] EXT3-fs warning (device > sdb1): ext3_orphan_get: bad orphan inode 1485246! e2fsck was run? > Mar 14 17:44:26 ubuntu kernel: [ 207.621600] ext3_test_bit(bit=125, > block=2981889) = -1 > Mar 14 17:44:26 ubuntu kernel: [ 207.621607] EXT3-fs: sdb1: 2 orphan > inodes deleted > Mar 14 17:44:26 ubuntu kernel: [ 207.621608] EXT3-fs: recovery complete. > Mar 14 17:44:26 ubuntu kernel: [ 207.621811] EXT3-fs: mounted filesystem > with ordered data mode. > Mar 14 17:44:26 ubuntu kernel: [ 207.622146] EXT3-fs error (device sdb1): > ext3_find_entry: reading directory #2 offset 0 > > [EMAIL PROTECTED]:/var/log$ cat messages | grep -i "ext3" > Mar 14 17:44:26 ubuntu kernel: [ 46.415302] EXT3-fs: INFO: recovery > required on readonly filesystem. > Mar 14 17:44:26 ubuntu kernel: [ 46.415305] EXT3-fs: write access will > be enabled during recovery. > Mar 14 17:44:26 ubuntu kernel: [ 207.614198] EXT3-fs: sdb1: orphan > cleanup on readonly fs > Mar 14 17:44:26 ubuntu kernel: [ 207.621596] EXT3-fs warning (device > sdb1): ext3_orphan_get: bad orphan inode 1485246! e2fsck was run? > Mar 14 17:44:26 ubuntu kernel: [ 207.621600] ext3_test_bit(bit=125, > block=2981889) = -1 > Mar 14 17:44:26 ubuntu kernel: [ 207.621607] EXT3-fs: sdb1: 2 orphan > inodes deleted > Mar 14 17:44:26 ubuntu kernel: [ 207.621608] EXT3-fs: recovery complete. > Mar 14 17:44:26 ubuntu kernel: [ 207.621811] EXT3-fs: mounted filesystem > with ordered data mode. > > [EMAIL PROTECTED]:/var/log$ cat syslog | grep -i "ext3" > Mar 14 17:44:26 ubuntu kernel: [ 46.415302] EXT3-fs: INFO: recovery > required on readonly filesystem. > Mar 14 17:44:26 ubuntu kernel: [ 46.415305] EXT3-fs: write access will > be enabled during recovery. > Mar 14 17:44:26 ubuntu kernel: [ 207.614198] EXT3-fs: sdb1: orphan > cleanup on readonly fs > Mar 14 17:44:26 ubuntu kernel: [ 207.614203] ext3_orphan_cleanup: > deleting unreferenced inode 1485348 > Mar 14 17:44:26 ubuntu kernel: [ 207.614227] ext3_orphan_cleanup: > deleting unreferenced inode 1485353 > Mar 14 17:44:26 ubuntu kernel: [ 207.614251] EXT3-fs error (device sdb1): > ext3_free_branches: Read failure, inode=1485353, block=3000002 > Mar 14 17:44:26 ubuntu kernel: [ 207.617633] EXT3-fs error (device sdb1): > ext3_get_inode_loc: unable to read inode block - inode=1485246, > block=2981893 > Mar 14 17:44:26 ubuntu kernel: [ 207.621596] EXT3-fs warning (device > sdb1): ext3_orphan_get: bad orphan inode 1485246! e2fsck was run? > Mar 14 17:44:26 ubuntu kernel: [ 207.621600] ext3_test_bit(bit=125, > block=2981889) = -1 > Mar 14 17:44:26 ubuntu kernel: [ 207.621607] EXT3-fs: sdb1: 2 orphan > inodes deleted > Mar 14 17:44:26 ubuntu kernel: [ 207.621608] EXT3-fs: recovery complete. > Mar 14 17:44:26 ubuntu kernel: [ 207.621811] EXT3-fs: mounted filesystem > with ordered data mode. > Mar 14 17:44:26 ubuntu kernel: [ 207.622146] EXT3-fs error (device sdb1): > ext3_find_entry: reading directory #2 offset 0 > > -- > EXT3-fs error corruption > https://bugs.launchpad.net/bugs/200747 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in Ubuntu: New > Status in Debian GNU/Linux: New > > Bug description: > I am running Ubuntu 8.04 "Hardy Heron" (alpha). > > MSI P35 Neo > Samsung SpinPoint T166 500 gb (7200 rpm, SATA-2, 16 mb cache) > Samsung SpinPoint T166 250 gb (7200 rpm, SATA-2, 16 mb cache) > > sda1 = Windows XP > sdb1 = Linux > > So I am listening to MP3 music in Rhythmbox 0.11.4, and surfing with > Mozilla Firefox 3.0b3 and perhaps doing some other stuff, like maybe > running apt-update && upgrade && clean && autoclean && autoremove or > something in a Terminal or something. > > And then my computer becomes unresponsive. The HDD LED shine all the time > on the computer case. > > Then I do Ctrl+Alt+F2 and try to login, and I type my username and press > enter, and it waits there for a while, then it start spit some error > messages, and wont let me in. > > Like: > EXT3-fs error (device sdb1): ext3_get_inode_loc: unable to read node block > - inode=1599522, block=3211298 > And it can spam the console with that kind of stuff. > > Then I shut down the computer (by PSU switch), restart and it borked out > again. > Shut down computer by PSU switch again, and runned HUTIL v2.10 by Samsung, > a disk diagnostic tool that checks SMART, does disk spin up, spin down, read > surface scan, and couple other diagnostic stuff. It reported no errors, and > said the disk were okay. > > Then I rebooted into my old Ubuntu 7.04 "Gutsy Gibbon" LiveCD and run some > commands to fix it. > $ sudo e2fsck -pcf /dev/sdb1 > $ sudo badblocks -sv /dev/sdb1 > > After that, computer worked again. > But today (next day), my computer borked out again. > In the same way and started spitting out error messages... > > [20061.478996] journal commit I/O error > [numbers] EXT3-fs error (device sdb1): ext3_find_entry: reading directory > #2399041 offset 0 > > and stuff like: > [numbers] EXT3-fs error (device sdb1): ext3_reserve_inode_write: Journal > has aborted > > It happened when I was using the 2.6.24-11-386 kernel. > I am scared, I don't know if my hard disk maybe is broken. Samsung's HUTIL > said the hard disk was okay. > But now it happened more than once, and maybe its a bug in the kernel, or > ext3 file system? I don't know. =/ > -- EXT3-fs error corruption https://bugs.launchpad.net/bugs/200747 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
