From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Sun, 16 Oct 2011 16:40:43 -0400
To: 9fans@9fans.net
Message-ID: <6659e9463becea044243c34cb8c857c0@chula.quanstro.net>
In-Reply-To: <CAEaiYYwfHD0d+SyTLqVVi-si=knjSqH6FKP61pkR-XRo5ixegA@mail.gmail.c>
References: <CAEaiYYwtJPmt-utC12NwucXQhJ6kKs0CzBXZRT6PU=fCZnjpbA@mail.gmail.c>
	<e7a2ebb85a1afbcb9265121504ebe7c0@chula.quanstro.net>
	<CAEaiYYxsDmZ_O8N0BwK5Ch071NGbgrb_MyAnupxCyWgRioSTrw@mail.gmail.c>
	<3378f6e35964291ae04699ff510ef3d3@chula.quanstro.net>
	<CAEaiYYzyVu20R-mJr_qs6pbAuUv0Fzj4mBa2DXu3wMUBW6h8Dw@mail.gmail.com>
	<CAEaiYYwfHD0d+SyTLqVVi-si=knjSqH6FKP61pkR-XRo5ixegA@mail.gmail.c>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] New disk, i/o error
Topicbox-Message-UUID: 38c97d82-ead7-11e9-9d60-3106f5b1d025

On Sun Oct 16 16:13:58 EDT 2011, slash.9fans@gmail.com wrote:
> > No errors, but I noticed it stopped just before 200 gigabytes.
> I kept reading the disk and got several read errors. Here is the first one:
>
> fossil: diskReadRaw failed: /dev/sdE0/fossil: score 0x016d1389:
> part=data block 23925641: eof reading disk
>
> Bad sector or something else?

to me that looks like a mismatch between fossil's expectations for the
partition and that actual partition size.  i think you're just reading past
the end of the partition.

- erik