public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Huib van Wees" <hvwees@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] raid does not autostart
Date: Wed, 15 Nov 2006 11:00:12 +0100	[thread overview]
Message-ID: <cb389f7b0611150200l39146bfdp7d39cff917c3c337@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2211 bytes --]

Hi List,

A few weeks ago I created a Raid 5 set for my data partition  using mdadm.

This works fine, but last week a short power outage caused the server to
reboot.

When I came home the server was in need of maintainance because it couldn't
check all his filesystems.

Strange fact was that the md device wasn't start...
mdadm --assemble /dev/md1 works fine, the /etc/mdadm.conf is read the the
raid device is started...

But why doesn't start it at boot?

A piece of output from dmesg:

md: Autodetecting RAID arrays.
md: autorun ...
md: considering hdb1 ...
md:  adding hdb1 ...
md: created md1
md: bind<hdb1>
md: running: <hdb1>
raid5: device hdb1 operational as raid disk 0
raid5: not enough operational devices for md1 (2/3 failed)
RAID5 conf printout:
 --- rd:3 wd:1 fd:2
 disk 0, o:1, dev:hdb1
raid5: failed to run raid set md1
md: pers->run() failed ...
md: do_md_run() returned -5
md: md1 stopped.
md: unbind<hdb1>
md: export_rdev(hdb1)
md: ... autorun DONE.

It tell's me that 2/3 devices failed, but after I assemble it.. the ouput of
mdadm --detail /dev/md1 is:

/dev/md1:
        Version : 00.90.03
  Creation Time : Fri Sep 22 22:28:43 2006
     Raid Level : raid5
     Array Size : 625137152 (596.18 GiB 640.14 GB)
    Device Size : 312568576 (298.09 GiB 320.07 GB)
   Raid Devices : 3
  Total Devices : 3
Preferred Minor : 1
    Persistence : Superblock is persistent

  Intent Bitmap : Internal

    Update Time : Wed Nov 15 10:56:36 2006
          State : active
 Active Devices : 3
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 64K

           UUID : 82544aad:a2e92ea2:72ca2d55:716dada0
         Events : 0.1486768

    Number   Major   Minor   RaidDevice State
       0       3       65        0      active sync   /dev/hdb1
       1      22        1        1      active sync   /dev/hdc1
       2      22       65        2      active sync   /dev/hdd1

No failed devices!

How it this possible?
I rebooted aferwards, but still the same issue! :-(

Anybody any clue's?!
Any help is appriciated....

-- 
Met vriendelijke groet / With kind regards,

H. van Wees
---
If UNIX isn't the solution, you've got the wrong problem.

[-- Attachment #2: Type: text/html, Size: 3390 bytes --]

             reply	other threads:[~2006-11-15 10:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15 10:00 Huib van Wees [this message]
2006-11-15 11:46 ` [gentoo-user] Re: raid does not autostart Remy Blank
2006-11-15 23:13   ` Huib van Wees

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=cb389f7b0611150200l39146bfdp7d39cff917c3c337@mail.gmail.com \
    --to=hvwees@gmail.com \
    --cc=gentoo-user@lists.gentoo.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