From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Sun, 16 Oct 2011 13:29:20 -0400
To: 9fans@9fans.net
Message-ID: <3378f6e35964291ae04699ff510ef3d3@chula.quanstro.net>
In-Reply-To: <CAEaiYYxsDmZ_O8N0BwK5Ch071NGbgrb_MyAnupxCyWgRioSTrw@mail.gmail.c>
References: <CAEaiYYwtJPmt-utC12NwucXQhJ6kKs0CzBXZRT6PU=fCZnjpbA@mail.gmail.c>
	<e7a2ebb85a1afbcb9265121504ebe7c0@chula.quanstro.net>
	<CAEaiYYxsDmZ_O8N0BwK5Ch071NGbgrb_MyAnupxCyWgRioSTrw@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: 38a812d2-ead7-11e9-9d60-3106f5b1d025

On Sun Oct 16 11:51:48 EDT 2011, slash.9fans@gmail.com wrote:
> > i've also had trouble with usb disks.
>
> The errors come from sdE0 which is connected to sata port on the
> motherboard. Even when there are no usb disks attached at all.
>

eeeh.  sorry.

> I am beginning to think my new disk has bad sectors. Looking at the
> reviews on the internet I wouldn't be the first one. Is there a way to
> tell for sure? Or could it be the usb transfers corrupted my fossil
> and I need to check it? Can I do this while booting off it?

dd -if /dev/sdE0/fossil -of /dev/null -bs 512k	# or whatever partition.

if you can narrow it down to a particular sector, you can use atazz to get
the exact contents of the error register, etc.

- erik