From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1GkHfj-0002jT-LR for garchives@archives.gentoo.org; Wed, 15 Nov 2006 10:07:12 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.8) with SMTP id kAFA4cgC026604; Wed, 15 Nov 2006 10:04:38 GMT Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by robin.gentoo.org (8.13.8/8.13.8) with ESMTP id kAFA0Dii021660 for ; Wed, 15 Nov 2006 10:00:13 GMT Received: by ug-out-1314.google.com with SMTP id z38so82491ugc for ; Wed, 15 Nov 2006 02:00:12 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=l7yq0ieI0IFBuOduLlInr4nz40NIqHWYjOrkXBEcMrZW8l0WB8nPGpKLlotZuDvnag7O8CqNZQcvnbCXTkTZK92FgbRDdZElAeCQBQRdNsQ63q/yWPbqg+7mRYd/jyTjUKsAN+lB+qV88mptowtNNgnXzCiwOE0dCHZSjppDsig= Received: by 10.67.121.15 with SMTP id y15mr2567349ugm.1163584812512; Wed, 15 Nov 2006 02:00:12 -0800 (PST) Received: by 10.67.30.14 with HTTP; Wed, 15 Nov 2006 02:00:12 -0800 (PST) Message-ID: Date: Wed, 15 Nov 2006 11:00:12 +0100 From: "Huib van Wees" To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] raid does not autostart Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_78131_3038074.1163584812443" X-Archives-Salt: ff0c896b-b5d8-4fd8-8b3d-57b0eb126b94 X-Archives-Hash: ad8edbe62cb2838760a61d9755612eef ------=_Part_78131_3038074.1163584812443 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 md: running: 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 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. ------=_Part_78131_3038074.1163584812443 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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. ------=_Part_78131_3038074.1163584812443-- -- gentoo-user@gentoo.org mailing list