All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Truschnigg <johannes@truschnigg.info>
To: Phil Turmel <philip@turmel.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: What just happened to my disks/RAID5 array?
Date: Fri, 6 Jan 2012 14:46:25 +0100	[thread overview]
Message-ID: <20120106134625.GA3027@vault.local> (raw)
In-Reply-To: <4F06F410.4070807@turmel.org>


[-- Attachment #1.1: Type: text/plain, Size: 1615 bytes --]

Good morning Phil,

thanks for tuning in again! :)

On Fri, Jan 06, 2012 at 08:16:00AM -0500, Phil Turmel wrote:
> Warning!  I saw bug report on LKML yesterday involving LVM and the brand new
> kernel v3.2, so you might want to pull back.  v3.1.5 was known good in that
> report.

Ok, thanks for the warning - will try to find the thread where the bug is
described, and consider downgrading to 3.1.x instead!

> I'm guessing that /dev/sda contains your boot and root filesystems, and that
> this isn't an error.

You are correct, sorry I did not mention that initially. These devices are not
supposed to end up as parts of any md arrays.

> Those slot numbers are *really* important.

What is the significance of the individual slot numbers there?


> Yes, --assemble --force.

Ok, will fire that command as soon as I checked out the LVM bug you mentioned.

> May I suggest getting an lsdrv [1] report, which will give you the serial numbers
> of your disks versus the device assignments, for later reference.  And again
> after it's all running, for completeness.

I have attached a file with the relevant lsdrv (great little program btw) to
this message - should I expect changes to it after my array is up (well,
except for the components not to be recognized as spare, of course)?

> HTH,

It sure did - thanks a bunch! :)

-- 
with best regards:
- Johannes Truschnigg ( johannes@truschnigg.info )

www:   http://johannes.truschnigg.info/
phone: +43 650 2 133337
xmpp:  johannes@truschnigg.info

Please do not bother me with HTML-eMail or attachments. Thank you.

[-- Attachment #1.2: lsdrv-output.txt --]
[-- Type: text/plain, Size: 1899 bytes --]

# ./lsdrv 
PCI [pata_via] 04:00.0 IDE interface: VIA Technologies, Inc. VT6415 PATA IDE Host Controller
├scsi 0:0:0:0 ATA TRANSCEND {20090625_D40D51BB}
│└sda 1.87g [8:0] Partitioned (dos)
│ └sda1 1.87g [8:1] ext2 'VIRTUE' {ff586bcd-b1fd-4c08-a0ea-08e2e1c7b8f9}
│  └Mounted as /dev/root @ /
└scsi 1:x:x:x [Empty]
PCI [ahci] 00:11.0 SATA controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40)
├scsi 2:0:0:0 ATA SAMSUNG HD154UI {S1XWJDWS803396}
│└sdb 1.36t [8:16] MD raid5 (none/5) (w/ sdd,sdf,sdc,sde) spare 'virtue:0' {19e260e6-db3c-ad86-0541-487da1bae605}
│ └md0 0.00k [9:0] MD vNone None (None) inactive, None (None) 0/sec
│                  Empty/Unknown
├scsi 3:0:0:0 ATA SAMSUNG HD154UI {S1XWJDWZ419775}
│└sdc 1.36t [8:32] MD raid5 (none/5) (w/ sdb,sdd,sdf,sde) spare 'virtue:0' {19e260e6-db3c-ad86-0541-487da1bae605}
│ └md0 0.00k [9:0] MD vNone None (None) inactive, None (None) 0/sec
│                  Empty/Unknown
├scsi 4:0:0:0 ATA SAMSUNG HD154UI {S1XWJDWS803467}
│└sdd 1.36t [8:48] MD raid5 (none/5) (w/ sdb,sdf,sdc,sde) spare 'virtue:0' {19e260e6-db3c-ad86-0541-487da1bae605}
│ └md0 0.00k [9:0] MD vNone None (None) inactive, None (None) 0/sec
│                  Empty/Unknown
├scsi 5:0:0:0 ATA SAMSUNG HD154UI {S1XWJDWS803469}
│└sde 1.36t [8:64] MD raid5 (none/5) (w/ sdb,sdd,sdf,sdc) spare 'virtue:0' {19e260e6-db3c-ad86-0541-487da1bae605}
│ └md0 0.00k [9:0] MD vNone None (None) inactive, None (None) 0/sec
│                  Empty/Unknown
├scsi 6:0:0:0 ATA SAMSUNG HD154UI {S1XWJDWS803405}
│└sdf 1.36t [8:80] MD raid5 (none/5) (w/ sdb,sdd,sdc,sde) spare 'virtue:0' {19e260e6-db3c-ad86-0541-487da1bae605}
│ └md0 0.00k [9:0] MD vNone None (None) inactive, None (None) 0/sec
│                  Empty/Unknown
└scsi 7:x:x:x [Empty]

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-01-06 13:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-13  8:27 What just happened to my disks/RAID5 array? Johannes Truschnigg
2011-09-13 11:37 ` Phil Turmel
2011-09-13 18:56   ` Johannes Truschnigg
2011-09-14 11:41     ` Phil Turmel
2011-09-14 18:17       ` Johannes Truschnigg
2011-09-14 19:19         ` Phil Turmel
2012-01-06 10:51           ` Johannes Truschnigg
2012-01-06 13:16             ` Phil Turmel
2012-01-06 13:46               ` Johannes Truschnigg [this message]
2012-01-06 14:51                 ` Phil Turmel
2012-01-06 15:28                   ` Johannes Truschnigg
2012-01-07 14:23                     ` John Robinson

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=20120106134625.GA3027@vault.local \
    --to=johannes@truschnigg.info \
    --cc=linux-raid@vger.kernel.org \
    --cc=philip@turmel.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.