You are not logged in.
- Topics: Active | Unanswered
#1 2010-09-14 21:25:22
- sputnick
- Member
- From: Near Paris
- Registered: 2009-05-27
- Posts: 40
[RAID1 + LVM2] can't assemble arrays at boot time
Hi,
when I boot from a live-cd, I can assemble my two arrays with
mdadm --assemble /dev/md0 /dev/sda1 /dev/sdb1
mdadm --assemble /dev/md1 /dev/sda2 /dev/sdb2and LVM after with
modprobe dm-mod
vgchange -aybut I never can have my 2 arrays in a non degraded state after boot time.
my config :
archlinux x86_64
noyau 2.6.35-ARCH
mdadm - v3.1.3 - 6th August 2010
errors in /var/log/messages.log
(...)
Sep 14 21:35:04 localhost kernel: md: md0 stopped.
Sep 14 21:35:04 localhost kernel: md: bind<sdb>
Sep 14 21:35:04 localhost kernel: md/raid1:md0: active with 1 out of 2 mirrors
Sep 14 21:35:04 localhost kernel: md0: detected capacity change from 0 to 995908780032
Sep 14 21:35:04 localhost kernel: md0: detected capacity change from 0 to 995908780032
Sep 14 21:35:04 localhost kernel: md0: p1 p2
Sep 14 21:35:04 localhost kernel: md0: p2 size 1953327285 extends beyond EOD, truncated
Sep 14 21:35:04 localhost kernel: md: md1 stopped.
Sep 14 21:35:04 localhost kernel: md: bind<sda2>
Sep 14 21:35:04 localhost kernel: md/raid1:md1: active with 1 out of 2 mirrors
Sep 14 21:35:04 localhost kernel: md1: detected capacity change from 0 to 1000103477248
Sep 14 21:35:04 localhost kernel: md1: detected capacity change from 0 to 1000103477248
Sep 14 21:35:04 localhost kernel: md1: unknown partition table
(...)fdisk -l:
# fdisk -l /dev/sda
Disque /dev/sda: 1000.2 Go, 1000204886016 octets
255 têtes, 63 secteurs/piste, 121601 cylindres, total 1953525168 secteurs
Unités = secteurs de 1 * 512 = 512 octets
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Identifiant de disque : 0x38000000
Périphérique Amorce Début Fin Blocs Id Système
/dev/sda1 63 192779 96358+ fd Linux raid autodetect
/dev/sda2 * 192780 1953520064 976663642+ fd Linux raid autodetect# fdisk -l /dev/sdb
Disque /dev/sdb: 1000.2 Go, 1000204886016 octets
255 têtes, 63 secteurs/piste, 121601 cylindres, total 1953525168 secteurs
Unités = secteurs de 1 * 512 = 512 octets
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Identifiant de disque : 0x21776e3d
Périphérique Amorce Début Fin Blocs Id Système
/dev/sdb1 2048 192779 95366 fd Linux raid autodetect
/dev/sdb2 * 192780 1953520064 976663642+ fd Linux raid autodetect root@FreAkyLab:/home/sputnick# mdadm --misc --detail /dev/md0
/dev/md0:
Version : 0.90
Creation Time : Tue Sep 14 17:14:27 2010
Raid Level : raid1
Array Size : 95296 (93.08 MiB 97.58 MB)
Used Dev Size : 95296 (93.08 MiB 97.58 MB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Tue Sep 14 23:14:45 2010
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : b08286a4:8038b9e3:3d186b3c:53958f34
Events : 0.18
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1root@FreAkyLab:/home/sputnick# mdadm --examine --scan
ARRAY /dev/md0 UUID=94d4fa88:191c7f9a:ca590ef5:9ced69dd
ARRAY /dev/md0 UUID=b08286a4:8038b9e3:3d186b3c:53958f34
ARRAY /dev/md1 UUID=e4ed079a:c54a98a5:ca590ef5:9ced69dd/etc/mdadm.conf
ARRAY /dev/md0 metadata=0.90 UUID=94d4fa88:191c7f9a:ca590ef5:9ced69dd
ARRAY /dev/md0 metadata=0.90 UUID=b08286a4:8038b9e3:3d186b3c:53958f34
ARRAY /dev/md1 metadata=0.90 UUID=e4ed079a:c54a98a5:ca590ef5:9ced69dd /etc/mkinitcpio.conf
MODULES="raid1 md_mod xor async_xor async_memcpy async_tx"
BINARIES=""
FILES="/etc/mdadm.conf"
HOOKS="base udev autodetect pata scsi sata mdadm lvm2 filesystems" /boot/grub/menu.cfg
timeout 5
default 0
color light-blue/black light-cyan/blue
# (0) Arch Linux
title Arch Linux [/boot/vmlinuz26]
root (hd0,0)
kernel /vmlinuz26 root=/dev/mapper/vg0-lvSlash ro
initrd /kernel26.img fstab:
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
none /proc/bus/usb usbfs devgid=100,devmode=664 0 0
/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
/dev/vg0/lvHome /home ext4 defaults 0 1
/dev/vg0/lvSlash / ext4 defaults 0 1
/dev/vg0/lvSwap swap swap defaults 0 0
/dev/vg0/lvTmp /tmp ext4 defaults 0 0
/dev/md0 /boot ext4 defaults 0 0
/dev/vg0/lvData /mnt/datas ext4 defaults 0 1If I boot normally, I always have degraded arrays :
# cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sda2[0]
976663552 blocks [2/1] [U_]
md0 : active raid1 sdb[1]
972567168 blocks [2/1] [_U]
unused devices: <none>then if I run
partprobe
mdadm --assemble /dev/md0 /dev/sda1 /dev/sdb1I recover a stable state for md0 :
# cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sdb1[1] sda1[0]
95296 blocks [2/2] [UU]
md1 : active raid1 sda2[0]
976663552 blocks [2/1] [U_]
unused devices: <none>So what can I set to be able to boot with a non degraded arrays please ?
Last edited by sputnick (2010-09-15 16:28:24)
Offline
#2 2010-09-14 21:29:48
- lilsirecho
- Veteran
- Registered: 2003-10-24
- Posts: 5,000
Re: [RAID1 + LVM2] can't assemble arrays at boot time
Perhaps you should run ...mdadm -D /etc/mdadm.conf...and mkinitcpio -p kernel26...
I think the commands are provided in the wiki in case my post is incorrect.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
#3 2010-09-14 21:51:56
- sputnick
- Member
- From: Near Paris
- Registered: 2009-05-27
- Posts: 40
Re: [RAID1 + LVM2] can't assemble arrays at boot time
I ran multiples times
pacman -Syf kernel26that run mkinitcpio both for fall-back and regular images.
For
mdadm -D /etc/mdadm.confthat's incorrect, -D is
-D, --detail
Print details of one or more md devices.
Offline
#4 2010-09-14 22:49:18
- lilsirecho
- Veteran
- Registered: 2003-10-24
- Posts: 5,000
Re: [RAID1 + LVM2] can't assemble arrays at boot time
The mdadm -D /etc/mdadm.conf sets up the arrays in mdadm.conf. Then run mkinitcpio -p kernel26 to establish the mdadm.conf details for array assembly. You must have mdadm as a daemon.
Examine /etc/mdadmconf at the very end of the file for the array details.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
#5 2010-09-15 02:32:40
- sputnick
- Member
- From: Near Paris
- Registered: 2009-05-27
- Posts: 40
Re: [RAID1 + LVM2] can't assemble arrays at boot time
fstab added.
Offline
#6 2010-09-15 10:19:07
- falconindy
- Developer
- From: New York, USA
- Registered: 2009-10-22
- Posts: 4,111
- Website
Re: [RAID1 + LVM2] can't assemble arrays at boot time
The mdadm -D /etc/mdadm.conf sets up the arrays in mdadm.conf. Then run mkinitcpio -p kernel26 to establish the mdadm.conf details for array assembly. You must have mdadm as a daemon.
Examine /etc/mdadmconf at the very end of the file for the array details.
The mdadm daemon is for error reporting only. It is not a requirement while the arrays are active.
Offline
#7 2010-09-15 16:27:41
- sputnick
- Member
- From: Near Paris
- Registered: 2009-05-27
- Posts: 40
Re: [RAID1 + LVM2] can't assemble arrays at boot time
heh, I've found a workaround : I must use old style grub kernel config line :
kernel /vmlinuz26 root=/dev/mapper/vg0-lvSlash ro md=0,/dev/sda1,/dev/sdb1 md=1,/dev/sda2,/dev/sdb2What a pain in my ... to build this f...ing RAID1 !
Offline