From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] New disk, i/o error
Date: Sun, 16 Oct 2011 13:29:20 -0400 [thread overview]
Message-ID: <3378f6e35964291ae04699ff510ef3d3@chula.quanstro.net> (raw)
In-Reply-To: <CAEaiYYxsDmZ_O8N0BwK5Ch071NGbgrb_MyAnupxCyWgRioSTrw@mail.gmail.c>
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
next prev parent reply other threads:[~2011-10-16 17:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEaiYYwtJPmt-utC12NwucXQhJ6kKs0CzBXZRT6PU=fCZnjpbA@mail.gmail.c>
2011-10-16 15:20 ` erik quanstrom
2011-10-16 15:51 ` slash
[not found] ` <CAEaiYYxsDmZ_O8N0BwK5Ch071NGbgrb_MyAnupxCyWgRioSTrw@mail.gmail.c>
2011-10-16 17:29 ` erik quanstrom [this message]
2011-10-16 19:19 ` slash
2011-10-16 20:13 ` slash
[not found] ` <CAEaiYYwfHD0d+SyTLqVVi-si=knjSqH6FKP61pkR-XRo5ixegA@mail.gmail.c>
2011-10-16 20:40 ` erik quanstrom
2011-10-17 1:54 ` slash
2011-10-17 7:44 ` David du Colombier
2011-10-17 10:23 ` Steve Simon
2011-10-17 11:17 ` slash
2011-10-17 12:15 ` David du Colombier
2011-10-17 11:56 ` David du Colombier
2011-10-17 15:43 ` Lyndon Nerenberg
2011-10-17 16:15 ` erik quanstrom
2011-10-17 16:46 ` Lyndon Nerenberg
[not found] ` <CAEaiYYys==oFZ7Umr4SD+rT6wtRo=j4K6wd0950gU94cGiR6kw@mail.gmail.c>
2011-10-17 3:28 ` erik quanstrom
2011-10-16 20:43 ` Steve Simon
2011-10-19 11:48 ` Peter A. Cejchan
2011-10-16 14:11 slash
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3378f6e35964291ae04699ff510ef3d3@chula.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).