Re: [smartmontools-support]Maxtor 2B020H1, passes all on and off line tests but has 1253 errors in the Error Log and causes Ext3 failures

[<kn...@tv...>]

On Tue, 3 Aug 2004, Steven Maenhout wrote:
> I was wondering if this disk can be saved. It only has 70 hours of up t=
ime,
> but can no longer be written to. When I copy file to it using nfs, the =
copy
> job starts normal but after about 5 minutes of copying I get:
>=20
> Igor:/# attempt to access beyond end of device
> hda3: rw=3D1, want=3D18446744073574807544, limit=3D35021700
> attempt to access beyond end of device
> hda3: rw=3D1, want=3D18446744073574807544, limit=3D35021700
> attempt to access beyond end of device
> hda3: rw=3D1, want=3D34224994296, limit=3D35021700
> Buffer I/O error on device hda3, logical block 4278124286
> lost page write due to I/O error on hda3
> Aborting journal on device hda3.
> journal commit I/O error
> ext3_abort called.
> EXT3-fs abort (device hda3): ext3_journal_start: Detected aborted journ=
al
> Remounting filesystem read-only
> EXT3-fs error (device hda3) in start_transaction: Journal has aborted

Looks like something has screwed up the filesystem. Have you tried=20
reformatting the partition?

Could be a memory error, a most common cause of grief in my experience.

Or are you using any rather experimental linux kernel versions? :)

--=20
Erik I. Bols=F8