From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: [9fans] ATA oddities
Date: Sun, 18 Apr 2010 11:17:39 +0200 [thread overview]
Message-ID: <0ea4900ea4ec2af6ba06c22dc86eeaaa@proxima.alt.za> (raw)
Just out of curiosity, seeing as most of my equipment is antiquated,
to say the least...
I'm using a PATA drive with the old low-density cabling connecting the
master and slave drives. The master drive is Fujitsu MPE3054AT and
the slave is a CD-writer. First I got read and write errors from
fossil. When I rebooted, the CD wasn't there. It came back when I
power cycled.
I have been running flchk and it went smoothly (no errors detected)
until I decide to turn DMA on (something that applied to my first
efforts). The following error appeared (manual):
sdata: command C8
data f004c200 limit f004c400 dlen 512 status 0 error 0
lba 205120 -> 205120, count 1 -> 1 (1)
It seems that flchk is continuing.
Of course, I'll replace the cable and possibly alter the jumper
settings on the master drive to make sure it is aware of the slave.
But perhaps there is something less obvious here that I need to know?
++L
next reply other threads:[~2010-04-18 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 9:17 lucio [this message]
2010-04-18 9:45 ` lucio
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=0ea4900ea4ec2af6ba06c22dc86eeaaa@proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).