| View previous topic :: View next topic |
| Author |
Message |
bpaddock
Apprentice
Joined: 04 Nov 2005
Posts: 195
Location: Franklin, PA
|
 Posted: Sun Aug 26, 2007 5:57 pm Post subject: Howto restart broken RAID LVM2 install? |
 |
|
I am trying to bring up a new system, on an x86_64 AMD Athlon 64 X2
Dual Core Processor 4600.
I was following these instructions to bring up the disks:
http://gentoo-wiki.com/Installing_on_LVM2_And_Raid5
I did something wrong in the install process, unrelated to that,
and wanted to start over. So I deleted all of the partitions
on the disk and started again at Step One, with fdisk etc.
When I got back to this step again:
| Code: |
mdadm --create --verbose /dev/md0 --level=1 --raid-devices=2 /dev/sda1 /dev/sdb1 --spare-devices=2 /dev/sdc1 /dev/sdd1
|
The system told me that there was something already there and that it
was going to rebuild the array, which it has now been doing for three hours.
How do I simply start over like these are virgin drives without mdadm
trying to rebuild something?
What is the correct way to restart a broken install when using RAID and
LVM2? |
|
| Back to top |
|
 |
Rob1n
l33t
Joined: 29 Nov 2003
Posts: 714
Location: Cambridge, UK
|
| Posted: Sun Aug 26, 2007 6:12 pm Post subject: |
|
|
You'll need to zero the RAID superblocks to force it to restart from scratch. For each of the disks run:
| Code: |
mdadm --zero-superblock /dev/sd?1
|
|
|
| Back to top |
|
|
bpaddock
Apprentice
Joined: 04 Nov 2005
Posts: 195
Location: Franklin, PA
|
| Posted: Sun Aug 26, 2007 8:37 pm Post subject: |
|
|
| Rob1n wrote: | You'll need to zero the RAID superblocks to force it to restart from scratch. For each of the disks run:
| Code: |
mdadm --zero-superblock /dev/sd?1
|
|
I tried that, and it is still slowly rebuilding the array per:
| Code: |
mdadm --detail /dev/md0
|
At this point I'll just let it finish as I have other things to do right now.
I'm starting to wonder if /dev/sdd is a bad drive?
The other problem I'm having here is what to do when I need
to restart the process, when something goes wrong?
I've got all of my logical volumes created etc. but if I have to reboot
I assume I don't want to use the mdadm --create command again? |
|
| Back to top |
|
|
Rob1n
l33t
Joined: 29 Nov 2003
Posts: 714
Location: Cambridge, UK
|
| Posted: Sun Aug 26, 2007 8:41 pm Post subject: |
|
|
| Rebuilding the array is normal - when mdadm creates an array it creates it in degraded mode, then rebuilds it. This makes the array available a lot quicker (and is no slower overall) than building the array fully synced in the first place. |
|
| Back to top |
|
|
bpaddock
Apprentice
Joined: 04 Nov 2005
Posts: 195
Location: Franklin, PA
|
| Posted: Mon Aug 27, 2007 12:01 am Post subject: |
|
|
| Rob1n wrote: | | Rebuilding the array is normal - when mdadm creates an array it creates it in degraded mode, then rebuilds it. This makes the array available a lot quicker (and is no slower overall) than building the array fully synced in the first place. |
That explains what is going on. Is there any good documentation on such things,
beyound mdadm's man page?
The next problem I'm having with this RAID system is that when I mount
the root partition:
| Code: |
mount /dev/md2 /mnt/gentoo
|
I get:
| Code: |
warning: Created .reiserfs_priv on md2 -reserved for xattr storage.
|
What is up with that? I had wanted to use Beagle on the system, which requires
use of xattr. |
|
| Back to top |
|
|
Rob1n
l33t
Joined: 29 Nov 2003
Posts: 714
Location: Cambridge, UK
|
| Posted: Mon Aug 27, 2007 11:39 am Post subject: |
|
|
| bpaddock wrote: | | Rob1n wrote: | | Rebuilding the array is normal - when mdadm creates an array it creates it in degraded mode, then rebuilds it. This makes the array available a lot quicker (and is no slower overall) than building the array fully synced in the first place. |
That explains what is going on. Is there any good documentation on such things,
beyound mdadm's man page? |
No that I know of, no - the mdadm man page is pretty good though.
| Quote: |
The next problem I'm having with this RAID system is that when I mount
the root partition:
| Code: |
mount /dev/md2 /mnt/gentoo
|
I get:
| Code: |
warning: Created .reiserfs_priv on md2 -reserved for xattr storage.
|
What is up with that? I had wanted to use Beagle on the system, which requires
use of xattr. |
That's normal - it'll only happen the first time you mount it. What happens is that when you create the reiserfs filesystem it doesn't know whether you want xattr or not, so it doesn't create any special directories for it. The first time you mount it with the xattr option it'll then create this directory - this is where reiserfs stores the xattr information (the xattr support was added fairly late on so isn't completely integrated). |
|
| Back to top |
|
|
|
Installing Gentoo
