From: NeilBrown <neilb@suse.de>
To: John Valarti <mdadmuser@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Server down-failed RAID5-asking for some assistance
Date: Sun, 24 Apr 2011 12:54:01 +1000 [thread overview]
Message-ID: <20110424125401.3de3720d@notabene.brown> (raw)
In-Reply-To: <BANLkTimDqEWZ6843RvekRGu4Z0XvNLgOwA@mail.gmail.com>
On Sat, 23 Apr 2011 18:07:37 -0600 John Valarti <mdadmuser@gmail.com> wrote:
> On Sat, Apr 23, 2011 at 3:51 PM, NeilBrown <neilb@suse.de> wrote:
> > On Sat, 23 Apr 2011 10:19:31 -0600 John Valarti <mdadmuser@gmail.com> wrote:
> >
> >> On Sat, Apr 23, 2011 at 2:48 AM, NeilBrown <neilb@suse.de> wrote:
> >> >> No luck
> >> >> Same thing:
> >> >> "no devices found.."
> >> >
> >> > I'm sure it said more than just that. Complete error messages really are
> >> > helpful..
> >> >
> >> > But the implication seems to be that /dev/sd[acd] don't exist... That is
> >> > weird.
> >> > What does "cat /proc/partitions" show?
> >> > If e.g. sda is there but sda2 is not, does "blockdev --rereadpt /dev/sda"
> >> > help?
> >> >
> >> > NeilBrown
> >>
> >> They exist.
> >> I have physically removed the dead drive, so now the 3 remaining ones
> >> are at sd[abc]
> >> I have a usb thumb drive plugged in to capture outputs as needed, it is sdd.
> >> blockdev does not seem to exist on this system.
> >>
> >> If useful I now have some more of the same 250GB drives, and I can
> >> plug one in to the sdb port and make partitions on it, and so on..
> >>
> >> For example fdisk -l shows all my partitions. I also show the output
> >> you asked for proc/partitions:
> >>
> >> Disk /dev/sda: 251.0 GB, 251000193024 bytes
> >> 255 heads, 63 sectors/track, 30515 cylinders
> >> Units = cylinders of 16065 * 512 = 8225280 bytes
> >>
> >> Device Boot Start End Blocks Id System
> >> /dev/sda1 * 1 17 136521 fd Linux raid autodetect
> >> /dev/sda2 18 30515 244975185 fd Linux raid autodetect
> >>
> >> Disk /dev/sdb: 251.0 GB, 251000193024 bytes
> >> 255 heads, 63 sectors/track, 30515 cylinders
> >> Units = cylinders of 16065 * 512 = 8225280 bytes
> >>
> >> Device Boot Start End Blocks Id System
> >> /dev/sdb1 * 1 17 136521 fd Linux raid autodetect
> >> /dev/sdb2 18 30515 244975185 fd Linux raid autodetect
> >>
> >> Disk /dev/sdc: 251.0 GB, 251000193024 bytes
> >> 255 heads, 63 sectors/track, 30515 cylinders
> >> Units = cylinders of 16065 * 512 = 8225280 bytes
> >>
> >> Device Boot Start End Blocks Id System
> >> /dev/sdc1 * 1 17 136521 fd Linux raid autodetect
> >> /dev/sdc2 18 30515 244975185 fd Linux raid autodetect
> >>
> >> Disk /dev/sdd: 1039 MB, 1039663104 bytes
> >> 255 heads, 63 sectors/track, 126 cylinders
> >> Units = cylinders of 16065 * 512 = 8225280 bytes
> >>
> >> Device Boot Start End Blocks Id System
> >> /dev/sdd1 * 1 127 1015264+ c W95 FAT32 (LBA)
> >> Partition 1 has different physical/logical endings:
> >> phys=(125, 254, 63) logical=(126, 101, 39)
> >> ===================================
> >> major minor #blocks name
> >>
> >> 7 0 111000 loop0
> >> 8 0 245117376 sda
> >> 8 1 136521 sda1
> >> 8 2 244975185 sda2
> >> 8 16 245117376 sdb
> >> 8 17 136521 sdb1
> >> 8 18 244975185 sdb2
> >> 8 32 245117376 sdc
> >> 8 33 136521 sdc1
> >> 8 34 244975185 sdc2
> >> 8 48 1015296 sdd
> >> 8 49 1015264 sdd1
> >>
> >> --
> >> John
> >
> >
> > I really cannot help you until you show me the output of "mdadm --assemble
> > --verbose ..." like I asked.
> >
> > NeilBrown
> >
>
> I really WAS NOT lying!
I never thought you were lying. But you were summarising. And when people
summarise instead of giving exact messages I cannot be sure exactly what was
excluded. I could guess - but the chances are that I would be wrong.
>
> I just did it again, and redirected output to a file
>
> The file ( located on my USB stick) contains:
>
> mdadm: looking for devices for /dev/md1
> mdadm: no devices found for /dev/md1
Thank you. This is helpful.
It implies that there mdadm didn't actually try including any devices in the
array, which is very odd because you listed some devices on the command line
for it to try.
So I'm a bit confused.
Could you please run this set of commands exactly as given and send me the
complete output. Maybe put them in a file and run
sh -x file > /path/on/usb 2>&1
cat /proc/mdstat
mdadm --stop --verbose /dev/md1
ls -l /dev/sd[acd]2
mdadm -E /dev/sd[acd]2
mdadm -Afvv /dev/md1 /dev/sd[acd]2
cat /proc/mdstat
dmesg | tail -100
Thanks,
NeilBrown
--
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:[~2011-04-24 2:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 18:29 Server down-failed RAID5-asking for some assistance John Valarti
2011-04-21 19:59 ` David Brown
[not found] ` <BANLkTim18Sx6JdZO5PiAqnrakDPzy5PNJQ@mail.gmail.com>
2011-04-22 2:32 ` John Valarti
2011-04-22 2:57 ` Server " NeilBrown
2011-04-22 3:31 ` John Valarti
[not found] ` <BANLkTin0SoBzRAear8Jt+26MnVJWouXoNA@mail.gmail.com>
[not found] ` <20110423074411.78fef94f@notabene.brown>
[not found] ` <BANLkTik_ZY4uoV3E=ua1p+tUD9g8xqQDVg@mail.gmail.com>
[not found] ` <20110423184824.55ee7893@notabene.brown>
[not found] ` <BANLkTi=sCfFFfmZTzj2g8-aDNhDqVK8e-A@mail.gmail.com>
[not found] ` <20110424075101.6763309f@notabene.brown>
2011-04-24 0:07 ` John Valarti
2011-04-24 0:37 ` John Robinson
2011-04-24 1:49 ` John Valarti
2011-04-24 2:12 ` John Robinson
2011-04-24 2:28 ` John Valarti
2011-04-24 2:58 ` NeilBrown
2011-04-24 6:30 ` John Valarti
2011-04-24 2:54 ` NeilBrown [this message]
2011-04-24 7:06 ` John Valarti
2011-04-24 8:41 ` NeilBrown
2011-04-24 11:57 ` John Robinson
2011-04-24 12:29 ` NeilBrown
2011-04-24 16:04 ` John Valarti
2011-04-24 16:15 ` John Valarti
2011-04-24 16:31 ` Mathias Burén
2011-04-24 18:41 ` John Valarti
2011-04-22 11:19 ` David Brown
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=20110424125401.3de3720d@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=mdadmuser@gmail.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 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).