From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Borislav Petkov <bp@alien8.de>
Cc: Jan Engelhardt <jengelh@inai.de>,
Andy Lutomirski <luto@amacapital.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org, Bjoern Franke <bjo@nord-west.org>,
Tim Nufire <linux_ide_tim@ibink.com>
Subject: Re: Which disk is ata4?
Date: Thu, 30 Aug 2012 17:39:56 +0100 [thread overview]
Message-ID: <20120830173956.3a29d511@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <20120830162938.GA24523@x1.osrc.amd.com>
On Thu, 30 Aug 2012 18:29:38 +0200
Borislav Petkov <bp@alien8.de> wrote:
> On Thu, Aug 30, 2012 at 06:14:46PM +0200, Jan Engelhardt wrote:
> > This tells me everything to replace a disk.
> > 1. sdparm -C stop /dev/sdb
> > 2. Removing Z1F0KR3H from the chassis.
>
> Yep, the serial number is the best suggestion so far.
>
> Are we sure this serial number is always programmed in by the hdd
> vendors so that sdparm can read it out?
With three known exceptions
- fake ones generated by some IT821X adapters in RAID mode
- certain old Maxtor PATA drives had a peculiar firmware failure where
they changed to some kind of default serial number. Very unusual. Was
never really fully explained and seems to have been very rare.
- drives so ancient they don't support IDENTIFY, and we don't support
them in libata anyway !
Alan
next prev parent reply other threads:[~2012-08-30 16:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 4:38 Which disk is ata4? Andy Lutomirski
2012-08-30 8:49 ` Bjoern Franke
2012-08-30 15:17 ` Andy Lutomirski
2012-08-30 15:22 ` Borislav Petkov
2012-08-30 16:08 ` Jan Engelhardt
2012-08-30 15:15 ` Tim Nufire
2012-08-30 15:27 ` Andy Lutomirski
2012-08-30 16:14 ` Jan Engelhardt
2012-08-30 16:29 ` Borislav Petkov
2012-08-30 16:39 ` Alan Cox [this message]
2012-08-30 16:57 ` Andy Lutomirski
2012-08-30 17:13 ` Jan Engelhardt
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=20120830173956.3a29d511@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bjo@nord-west.org \
--cc=bp@alien8.de \
--cc=jengelh@inai.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_ide_tim@ibink.com \
--cc=luto@amacapital.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 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.