From: Eric Mudama <edmudama@gmail.com>
To: Tupshin Harper <tupshin@tupshin.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Re: /dev/hdl not showing up because of fix-ide-probe-double-detection patch
Date: Mon, 9 Aug 2004 14:18:10 -0600 [thread overview]
Message-ID: <311601c90408091318699d0141@mail.gmail.com> (raw)
In-Reply-To: <4117C028.7080905@tupshin.com>
On Mon, 09 Aug 2004 11:19:20 -0700, Tupshin Harper <tupshin@tupshin.com> wrote:
> I originally thought that the problem might be not enough bytes being
> checked, but now I'm concerned that Maxtor has some problem with not
> having a proper serial number recorded for some drives. hdparm -i also
> show M0000000000000000000 for both of these drives. Below is the output
> of hdparm -i for the two drives, and below that, the output of catting
> /dev/ide/hdk and hdl.
>
> Doing a google search on "M0000000000000000000" shows that there have a
> been a handful of reports of maxtor drives showing this as the serial
> number, but I don't see any explanation of why.
The SN# is garbage in the ID block, I don't know why this is occurring
with our drives. I am going to forward this note to our program lead
for that product to see if he's aware of the issue. Unfortunately, if
the utility zone configuration is corrupt, I am not sure anything can
be done in the field to fix it... the drives might require an RMA. =/
--eric
prev parent reply other threads:[~2004-08-09 20:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 22:38 /dev/hdl not showing up with 2.6.8-rc2-mm1 Tupshin Harper1
2004-08-04 22:37 ` /dev/hdl not showing up because of fix-ide-probe-double-detection patch Tupshin Harper1
2004-08-05 5:47 ` Andrew Morton
2004-08-05 15:36 ` Alan Cox
2004-08-05 23:04 ` Mark Lord
2004-08-05 23:58 ` Alan Cox
2004-08-09 18:19 ` Tupshin Harper
2004-08-09 19:06 ` Alan Cox
2004-08-09 20:39 ` Joel Jaeggli
2004-08-09 20:18 ` Eric Mudama [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=311601c90408091318699d0141@mail.gmail.com \
--to=edmudama@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tupshin@tupshin.com \
/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.