[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Problem with Raid Array persistence across reboots.



[Apologies this doesn't thread properly, but I didn't get the messages from 
the list covering the time my mail server was down - the reason was I had 
forgotten to allocate swap space in my new configuration - so I have had to 
reply to the message by copy and pasting from an archive]
On 2006-08-25 13:36:14, Scott Reese wrote:
...
>You don't mention which version of Debian you're using - the raid tools
>have varied a lot between the last few releases - but assuming Sarge:

Actually this machine is Debian unstable, my server is Debian Etch (which I 
have to do next).
>
>
> The configuration is stored in /etc/mdadm/mdadm.conf and looks like:
>
> DEVICE partitions
> ARRAY /dev/md3 level=raid1 num-devices=2
> UUID=62297b2a:13d5cbb3:b889437a:6095a0d0
>    devices=/dev/sda6,/dev/sdb6
> ARRAY /dev/md2 level=raid1 num-devices=2
> UUID=27192fb9:88d9191f:bbbf6c42:8656233f
>    devices=/dev/sda5,/dev/sdb5
> ARRAY /dev/md1 level=raid1 num-devices=2
> UUID=b483771d:b60355eb:afe973c0:92db52e2
>    devices=/dev/sda2,/dev/sdb2
> ARRAY /dev/md0 level=raid1 num-devices=2
> UUID=aa772038:8b2a1989:339b0f8f:f93b96b5
>    devices=/dev/sda1,/dev/sdb1

But I guess the installer wrote this into your mdadm.conf file

From Miles Fidelman

>- I found the guidance at 
>http://www.planamente.ch/emidio/pages/linux_howto_root_lvm_raid.php
>to be very helpful

Indeed, in there it says you need to do 

  cd /etc/mdadm 
   echo 'DEVICE /dev/hd*[0-9] /dev/sd*[0-9]' > mdadm.conf 
   mdadm --detail --scan >> mdadm.conf 

particularly the last line of that - which writes the data 
into /etc/mdadm/mdadm.conf

By doing that it seems to work

An intersting aside - I was just experimenting with booting the rescue CD 
(www.rescuecd.org) from a usb stick, and I could see its bootup sequence 
clearly running in a 1024 framebuffer.  In there it scanned for md 
superblocks and said mine were invalid.  My mdadm.conf file came 
(preconfigured) with 

# auto-create devices with Debian standard permissions and v1 superblocks
CREATE owner=root group=disk mode=0660 auto=yes metadata=1

So I wonder if that is why they are not being found mdadm without explicitly 
being told




-- 
Alan Chandler
http://www.chandlerfamily.org.uk



Reply to: