From: Tejun <htejun@gmail.com>
To: James Lamanna <jlamanna@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: I/O errors while dding between 2 SATA drives
Date: Tue, 31 Jan 2006 00:04:52 +0900 [thread overview]
Message-ID: <43DE2B14.7090309@gmail.com> (raw)
In-Reply-To: <aa4c40ff0601261021m1fe746feq172f0a34b6afd9ad@mail.gmail.com>
James Lamanna wrote:
> I received the following errors while executing a
> dd if=/dev/sdb of=/dev/sda bs=1M
> between 2 500GB SATA Seagate Barracuda drives on 2.6.12 (Gentoo 2005.1
> "Live" CD)
>
> ata1: command 0x35 timeout stat 0xd1 host_stat 0x21
> ata1: status=0xd1 { Busy }
> end request: I/O Error dev sda, sector 51188392
> Buffer I/O Error on device sda, logical block 6398549
> lost page write due to I/O Error on sda
> ATA: abnormal status 0xD1 on port 0x9F7
> ATA: abnormal status 0xD1 on port 0x9F7
> ATA: abnormal status 0xD1 on port 0x9F7
>
> The message repeats every so often with the sector count increasing by
> 8 and logical block count increasing by 1.
>
> Is it bad hardware? (sda is brand new)
> And is the copy hosed?
>
[CC'ing linux-ide]
Hi, James.
Please post full dmesg and yeah the copy is probably hosed. dd's exit
code will tell you. Do 'echo $$'.
--
tejun
parent reply other threads:[~2006-01-30 15:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <aa4c40ff0601261021m1fe746feq172f0a34b6afd9ad@mail.gmail.com>]
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=43DE2B14.7090309@gmail.com \
--to=htejun@gmail.com \
--cc=jlamanna@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).