[plug] Ext3: attempt to access beyond end of device

[Daniel J. Axtens]

> 23:55:52 EXT3-fs abort (device hdc2): ext3_journal_start: Detected
> aborted journal
> 23:55:52 Remounting filesystem read-only
> 23:55:52 EXT3-fs error (device hdc2) in start_transaction: Journal has
> aborted

The journal is corrupted. My opinion is that you should back up your
drive, wipe it, run a bad block test, and. if the drive is not
destroyed, reformat it and put your data back.

(sorry if they're are any typos, some idiot has rearranged the keys on
this school keyboard from qwerty to abcdefhij, swapped the numbers
with the function keys, and generally made life annoying - good thing
I can touch type!)

HTH,
Daniel Axtens

On 5/12/05, Alex Nordstrom <lx at se.linux.org> wrote:
> Ran into some nastiness with the filesystem today. After a brief panic
> attack, it seems the damage was (knock on wood) quite limited, but it's
> always an uneasy feeling when things like this happen, so I'd like to
> hear your views as to what may be the cause.
> 
>--snip-- 
> 23:55:52 attempt to access beyond end of device
> 23:55:52 hdc2: rw=0, want=1073741832, limit=43775424
> 23:55:52 EXT3-fs error (device hdc2): ext3_free_blocks: Freeing blocks
> not in datazone - block = 134217728, count = 1
> 23:55:52 Aborting journal on device hdc2.
> 23:55:52 ext3_abort called.
> 23:55:52 EXT3-fs abort (device hdc2): ext3_journal_start: Detected
> aborted journal
> 23:55:52 Remounting filesystem read-only
> 23:55:52 EXT3-fs error (device hdc2) in start_transaction: Journal has
> aborted
> 23:55:52 last message repeated 2 times
> 23:55:52 ext3_reserve_inode_write: aborting transaction: Journal has
> aborted in __ext3_journal_get_write_access<2>EXT3-fs error (device
> hdc2) in ext3_reserve_inode_write: Journal has aborted
> 
> ...and so on. After a reboot, an fsck was forced, and unsurprisingly, an
> inode pointing to somewhere that didn't exist was found, which I
> cleared. After another reboot, things seem relatively normal, apart
> from a bunch of.
> 
> 00:14:34 Device not ready.  Make sure there is a disc in the drive.
> 00:14:34 Device sda not ready.
> 
> For sda through sdd, which weren't there before. sda and sdb as
> specified in the fstab are manually mounted USB MSDs. I have no idea
> what would try to reach them, much less sdc and sdd.
> 
> hdc is sitting at 49 degrees, and I guess that might be a bit on the
> toasty side. I also know very little about its history, having bought
> it as part of a second-hand (s)crap system, but it's held up nicely for
> about a year now, having been in constant use for the past two or three
> months. Still, it doesn't seem hardware-ish when the kernel tries to
> grab a sector on the disk one milliard sectors off the end of the disk.
> 
> So the questions present themselves: what may have caused this, and how
> can I avoid it happening again? What's more likely: impending hardware
> failure of doom, or software glitch (of equal doom)?
> 
> --
> Alex Nordstrom
> http://lx.n3.net/
> Please do not CC me in followups; I am subscribed to plug.
> 
> 
> _______________________________________________
> PLUG discussion list: plug at plug.org.au
> http://www.plug.org.au/mailman/listinfo/plug
> Committee e-mail: committee at plug.linux.org.au
> 
> 
> 
> 


-- 
Neuronstorm: neuronstorm.sourceforge.net
The Neuronstorm Blog: leinad-golb.blogspot.com