From: "Michael" <michael@insulin-pumpers.org>
To: linux-raid@vger.kernel.org
Subject: RE: Which (physical) disk is broken?
Date: Wed, 22 Dec 2004 12:15:31 -0800 [thread overview]
Message-ID: <41C96563.11124.597BE49@localhost> (raw)
In-Reply-To: <200412221639.iBMGdH911479@www.watkins-home.com>
<snip>
> Use a command like this to cause your disks to have activity, then look for
> the blinking lights:
> dd if=/dev/md/1 of=/dev/null bs=64k
>
Oh swell!.... I have one blinking light for ALL the disks on all 12 of
our raid systems. There has to be a better way.
Michael
> Guy
>
> -----Original Message-----
> From: linux-raid-owner@vger.kernel.org
> [mailto:linux-raid-owner@vger.kernel.org] On Behalf Of Turbo Fredriksson
> Sent: Tuesday, December 21, 2004 6:09 AM
> To: linux-raid@vger.kernel.org
> Subject: Which (physical) disk is broken?
>
> I've forgot, and I can't seem to find out which physical disk
> is broken/removed from an array...
>
> ----- s n i p -----
> aurora:~# mdadm -D /dev/md/1
> /dev/md/1:
> Version : 00.90.01
> Creation Time : Wed Oct 27 08:12:44 2004
> Raid Level : raid5
> Array Size : 141483520 (134.93 GiB 144.88 GB)
> Device Size : 17685440 (16.87 GiB 18.11 GB)
> Raid Devices : 9
> Total Devices : 8
> Preferred Minor : 1
> Persistence : Superblock is persistent
>
> Update Time : Tue Dec 21 12:04:43 2004
> State : dirty, degraded
> Active Devices : 8
> Working Devices : 8
> Failed Devices : 0
> Spare Devices : 0
>
> Layout : left-symmetric
> Chunk Size : 32K
>
> Number Major Minor RaidDevice State
> 0 8 49 0 active sync
> /dev/scsi/host3/bus0/target4/lun0/part1
> 1 8 81 1 active sync
> /dev/scsi/host3/bus0/target8/lun0/part1
> 2 8 97 2 active sync
> /dev/scsi/host3/bus0/target9/lun0/part1
> 3 8 241 3 active sync
> /dev/scsi/host4/bus0/target4/lun0/part1
> 4 65 1 4 active sync
> /dev/scsi/host4/bus0/target5/lun0/part1
> 5 65 17 5 active sync
> /dev/scsi/host4/bus0/target8/lun0/part1
> 6 65 33 6 active sync
> /dev/scsi/host4/bus0/target9/lun0/part1
> 7 65 113 7 active sync
> /dev/scsi/host4/bus0/target14/lun0/part1
> 8 0 0 -1 removed
> UUID : d0b4e775:290f5785:2e6ad7d1:5a66178b
> Events : 0.974012
> ----- s n i p -----
>
> I _THINK_ (!!) it's '/dev/scsi/host4/bus0/target15/lun0/part', but
> I'm not sure.... Don't want to yank a perfectly working disk :)
>
> ----- s n i p -----
> aurora:~# mdadm -E /dev/scsi/host4/bus0/target15/lun0/part1
> mdadm: No super block found on /dev/scsi/host4/bus0/target15/lun0/part1
> (Expected magic a92b4efc, got 00000000)
> ----- s n i p -----
>
> Is there any way I can find out exactly which disk 'number 8' is?
>
> ----- s n i p -----
> aurora:~# mdadm --version
> mdadm - v1.6.0 - 4 June 2004
> aurora:~# uname -a
> Linux aurora 2.6.8.1 #1 SMP Sun Dec 12 21:04:58 CET 2004 sparc64 unknown
> ----- s n i p -----
> --
> Ortega assassination explosion FBI president PLO Iran domestic
> disruption genetic Ft. Bragg Rule Psix $400 million in gold bullion
> Clinton Cocaine Treasury
> [See http://www.aclu.org/echelonwatch/index.html for more about this]
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2004-12-22 20:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 11:08 Which (physical) disk is broken? Turbo Fredriksson
2004-12-22 16:39 ` Guy
2004-12-22 20:15 ` Michael [this message]
2004-12-22 23:10 ` Neil Brown
2004-12-23 0:52 ` Guy
2004-12-22 22:33 ` Turbo Fredriksson
2004-12-22 23:00 ` Neil Brown
2004-12-24 11:09 ` Turbo Fredriksson
2004-12-24 11:31 ` Theepan
2004-12-24 12:32 ` Turbo Fredriksson
2004-12-24 17:14 ` Guy
2004-12-27 12:35 ` Turbo Fredriksson
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=41C96563.11124.597BE49@localhost \
--to=michael@insulin-pumpers.org \
--cc=linux-raid@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 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).