Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


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

The never-ending upgrade: RAID problem/question



Quoting Don Levey <lug at the-leveys.us>:

> I've looked at the mdadm.conf file again, and I see no difference after
> adding the partitions again.  It's still in "recovery" mode, and I haven't
> been through a reboot, so I don't know if that will be dynamic.

Yea, I dont think that mdadm would modify mdadm.conf by itself...

> By the way - I don't know if anyone else is as paranoid as I am (or as
> messy).  Were I the organised sort, I'd have a configuration book with
> neatly printed charts of all my settings, notes on what I've done, etc,
> including the partition information on each drive in case I need to replace
> a drive in the RAID.  But I'm perpetually messy and disorganised.
> Therefore, I've just printed up "fdisk -l" for this system, and taped it to
> the inside cover of the server.  That way, if a drive goes down, I can have
> the partition information to reconstruct a new one right away (without
> having to think about how I could get it easily - "...what was that command
> again?").

I wrote a script that assumes it can use sfdisk to copy the partition table
from disk1 to disk2..  and then rebuilds the disk arrays.  But I haven't
tested the script on my FC4 machine.

> -Don

-derek

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org