From: Grant Coady <grant_lkml@dodo.com.au>
To: CyberOptic <mail@cyberoptic.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ppa / kernel 2.6.12.2 / fsck results in kernel error
Date: Sun, 03 Jul 2005 21:31:24 +1000 [thread overview]
Message-ID: <1eifc1ll55jemm78e2deefqt6hu4j4t2ij@4ax.com> (raw)
In-Reply-To: <42C7B5F0.40003@cyberoptic.de>
On Sun, 03 Jul 2005 11:54:56 +0200, CyberOptic <mail@cyberoptic.de> wrote:
>this error (see blow) occours, if I "fsck -c" (bad cluster test) a
>medium in my parallel IOmega ZIP-Drive 100MB.
Unable to reproduce, sorry...
>
>A complete dd from /dev/zero to the device works like a charm.
Only if you read zeroes back again? :)
I wrote zeroes, format ext2, e2fsck -c, write kernel tarball,
diff -> okay, used ATAPI zip drive in another box for 'diff'
so no cache issue/confusion. Used low quality media (Nomai)
that reported errors prior to format / zero / format again.
dmesg?
ppa: Version 2.07 (for Linux 2.4.x)
ppa: Found device at ID 6, Attempting to use EPP 32 bit
ppa: Found device at ID 6, Attempting to use PS/2
ppa: Communication established with ID 6 using PS/2
scsi0 : Iomega VPI0 (ppa) interface
Vendor: IOMEGA Model: ZIP 100 Rev: D.17
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sda: 196608 512-byte hdwr sectors (101 MB)
sda: Write Protect is off
sda: Mode Sense: 25 00 00 08
sda: cache data unavailable
sda: assuming drive cache: write through
SCSI device sda: 196608 512-byte hdwr sectors (101 MB)
sda: Write Protect is off
sda: Mode Sense: 25 00 00 08
sda: cache data unavailable
sda: assuming drive cache: write through
sda: sda1
Attached scsi removable disk sda at scsi0, channel 0, id 6, lun 0
Only complaint is 'eject' doesn't for parport nor ATAPI :(
--Grant.
prev parent reply other threads:[~2005-07-03 11:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-03 9:54 CyberOptic
2005-07-03 11:31 ` Grant Coady [this message]
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=1eifc1ll55jemm78e2deefqt6hu4j4t2ij@4ax.com \
--to=grant_lkml@dodo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@cyberoptic.de \
/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
all inboxes | Powered by JetHome®