From: Maxime Boissonneault <maxime.boissonneault@usherbrooke.ca>
To: "Keld Jørn Simonsen" <keld@dkuug.dk>
Cc: Bill Davidsen <davidsen@tmr.com>,
robin@robinhill.me.uk, linux-raid@vger.kernel.org
Subject: Re: Upgrading a software RAID
Date: Sun, 31 May 2009 01:21:32 -0400 [thread overview]
Message-ID: <4A2213DC.9000100@usherbrooke.ca> (raw)
In-Reply-To: <20090531001730.GA16311@rap.rap.dk>
I finally succeeded in getting my system back. To remind you, I started
with this configuration :
/proc/mdstat :
md2 : active raid5 sda3[0] sdc3[2] sdb3[1]
957040000 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU]
md1 : active raid0 sda2[0] sdc2[2] sdb2[1]
19534848 blocks level 0 [3/3] [UUU]
md0 : active raid1 sda1[0] sdc1[2] sdb1[1]
96256 blocks [3/3] [UUU]
mount :
/dev/md1 on / type ext3 (rw,relatime,errors=remount-ro)
/dev/md0 on /boot type ext3 (rw,relatime)
/dev/md2 on /home type ext3 (rw,relatime)
And I wanted to change md1 to a RAID5. So, here is what I did and what
worked.
1- Booted with a LiveCD (Ubuntu 8.04.2 Alternate CD)
2- Backed-up / using tar, put the file on /home
3- Destroyed the array, with mdadm --zero-superblock /dev/sd*2 and mdadm
--stop /dev/md1
4- Created the new RAID5 array
5- Installed a fresh Ubuntu with the install disc
6- Copied the /boot, /etc/mdadm/mdadm.conf and /etc/fstab from the fresh
install
7- Restored the backup over the fresh install
8- Restore the files copied at step 6
9- Booted
At this point, it gave me an error saying that the filesystem could not
be mounted with some number. I found this web page
http://linux.byexamples.com/archives/321/fstab-with-uuid/
which told me how to get the uid for my disks, and I updated the
/etc/fstab consequently.
Tadam! It works! I can now plan and buy my new 1TB HD and let the RAID
reconstruct the files, then grow the arrays.
I wrote this email in the hope that it might be usefull to someone someday.
Thanks everyone for your help throughout the day.
Maxime Boissonneault
next prev parent reply other threads:[~2009-05-31 5:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 15:32 Adaptec 2405 : hardware or software raid? Janek Kozicki
2009-05-25 16:52 ` Andrew Burgess
2009-05-25 17:05 ` Upgrading a software RAID Maxime Boissonneault
2009-05-28 13:38 ` Bill Davidsen
2009-05-28 13:44 ` Maxime Boissonneault
2009-05-28 14:05 ` Bill Davidsen
2009-05-28 14:14 ` Robin Hill
2009-05-28 14:32 ` Maxime Boissonneault
2009-05-28 15:08 ` Robin Hill
2009-05-30 18:11 ` Maxime Boissonneault
2009-05-30 19:03 ` Robin Hill
2009-05-30 20:03 ` Maxime Boissonneault
2009-05-30 20:15 ` Robin Hill
2009-05-30 22:18 ` Maxime Boissonneault
2009-05-30 22:52 ` Maxime Boissonneault
2009-06-02 18:23 ` Bill Davidsen
2009-06-02 18:32 ` Thomas Fjellstrom
2009-06-02 19:57 ` Bill Davidsen
2009-06-02 20:03 ` Thomas Fjellstrom
2009-06-02 21:13 ` CoolCold
2009-06-03 16:30 ` Bill Davidsen
2009-05-29 8:58 ` Keld Jørn Simonsen
2009-05-30 18:32 ` Bill Davidsen
2009-05-30 18:35 ` Maxime Boissonneault
2009-05-30 19:10 ` Robin Hill
2009-05-30 22:39 ` Bill Davidsen
2009-05-31 0:17 ` Keld Jørn Simonsen
2009-05-31 5:21 ` Maxime Boissonneault [this message]
2009-06-02 18:33 ` Bill Davidsen
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=4A2213DC.9000100@usherbrooke.ca \
--to=maxime.boissonneault@usherbrooke.ca \
--cc=davidsen@tmr.com \
--cc=keld@dkuug.dk \
--cc=linux-raid@vger.kernel.org \
--cc=robin@robinhill.me.uk \
/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).