All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: "Fr?d?ric L. W. Meunier" <fredlwm@fredlwm.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Floppy: drive, floppy or driver problem ?
Date: Sun, 11 Sep 2011 17:51:26 +0100	[thread overview]
Message-ID: <20110911165126.GA26442@gallifrey> (raw)
In-Reply-To: <20110911025509.GB18956@pervalidus>

* Fr?d?ric L. W. Meunier (fredlwm@fredlwm.net) wrote:
> I tried 'dd if=/dev/fd0 of=foo.img' on a few floppy drives, and the first 
> returned
> 
> Sep 10 21:53:58 pervalidus kernel: ------------[ cut here ]------------
> Sep 10 21:53:58 pervalidus kernel: WARNING: at /usr/local/src/kernel/linux-3.0/drivers/block/floppy.c:1041 setup_rw_floppy+0x1ab/0x276 [floppy]()
> Sep 10 21:53:58 pervalidus kernel: Hardware name: GA-MA69VM-S2
> Sep 10 21:53:58 pervalidus kernel: floppy_disable_hlt() scheduled for removal in 2012

OK, well that's a kernel warning; doesn't look like too much to be worried about.

> Sep 10 21:54:09 pervalidus kernel: floppy0: data CRC error: track 18, head 1, sector 14, size 2
> Sep 10 21:54:10 pervalidus kernel: floppy0: data CRC error: track 18, head 1, sector 14, size 2
> Sep 10 21:54:10 pervalidus kernel: end_request: I/O error, dev fd0, sector 679
> Sep 10 21:54:10 pervalidus kernel: Buffer I/O error on device fd0, logical block 84

Well that looks like a bad sector read - either the drive or the floppy; if
you're getting the same values in multiple drives then probably the floppy.
I'm not convinced any 1.44MB floppies manage to survive more than 1 or 2
reads (if you're lucky....).   So from that error you're at head 1 on cylinder
18, and with 18 sectors/track we get to sector 666 (!!) + 14 -> 680 - which
is close enough to the 679 reported for me think that's about right.
Not quite sure where the 84 comes from - 4KB blocks?

Anyway, sounds like duff disk.

> With the others, some didn't return any error, while others returned the 
> same errors from the last four lines.
> 
> But I then retried with the first floppy, and it didn't return anything in 
> two runs.
> 
> Anyway, looking in my logs, I also got it once in the past:
> 
> Aug 25 19:29:51 pervalidus kernel: ------------[ cut here ]------------
> Aug 25 19:29:51 pervalidus kernel: WARNING: at /usr/local/src/kernel/linux-3.0/drivers/block/floppy.c:1041 setup_rw_floppy+0x1ab/0x276 [floppy]()
> Aug 25 19:29:51 pervalidus kernel: Hardware name: GA-MA69VM-S2
> Aug 25 19:29:51 pervalidus kernel: floppy_disable_hlt() scheduled for removal in 2012

Same warning as above.

Dave
-- 
 -----Open up your eyes, open up your mind, open up your code -------   
/ Dr. David Alan Gilbert    |       Running GNU/Linux       | Happy  \ 
\ gro.gilbert @ treblig.org |                               | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/

      reply	other threads:[~2011-09-11 16:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-11  2:55 Floppy: drive, floppy or driver problem ? Frédéric L. W. Meunier
2011-09-11 16:51 ` Dr. David Alan Gilbert [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=20110911165126.GA26442@gallifrey \
    --to=linux@treblig.org \
    --cc=fredlwm@fredlwm.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.