Je reprend la suite de mon problème, en espérant une conclusion aussi heureuse que la 1er étape.
Un apt-get upgrade m’a au suivant planter mon démarrage d’un de mes disque raid qui ne démarre plus.
~# mdadm --assemble /dev/md0 /dev/sdb1 /dev/sdc1
mdadm: cannot open device /dev/sdc1: Device or resource busy
mdadm: /dev/sdc1 has no superblock - assembly aborted
et dans les logs dmesg:
[quote][ 264.078038] md: md0 stopped.
[ 264.191778] md: bind
[ 264.200406] md: sdb1 has same UUID but different superblock to sdc1
[ 264.208287] md: sdb1 has different UUID to sdc1
[ 264.216377] md: export_rdev(sdb1)
[/quote]
Ai je fait une connerie? En tout cas grace a lol j’ai réussi a monter de façon non destructive un seul volume de mon RAID1, donc ce coup ci je me lance.
J’ai donc plusieurs questions:
Q1) mdadm: cannot open device /dev/sdc1: Device or resource busy
Il a fumer ? Mon device il est libre.
Q2) sdb1 has same UUID but different superblock to sdc1
sdb1 has different UUID to sdc1
Faudrait savoir!
Q3) /dev/sdc1 has no superblock
Ouille ca doit etre le soucis.
Voici ma config:
/proc/mdstat
[code]# cat /proc/mdstat
Personalities : [raid1]
md0 : inactive sdc11
488383936 blocks
md1 : active raid1 sdd1[0] sde1[1]
1465135936 blocks [2/2] [UU]
md2 : active raid1 sdf1[0] sdg1[1]
1465134841 blocks super 1.2 [2/2] [UU]
unused devices: [/code]
mdadm --detail --scan
ARRAY /dev/md2 metadata=1.2 name=nasdeb:2 UUID=d3d17803:c1bf9cb9:a327a0cf:d4eea6a7
ARRAY /dev/md1 metadata=0.90 UUID=893dfb9a:554055f5:2ba6685a:2761cbe9
mdadm: md device /dev/md0 does not appear to be active.
/etc/mdadm/mdadm.conf
ARRAY /dev/md0 level=raid1 num-devices=2 metadata=0.90 UUID=6b1921e3:4bba6671:cb4e4b4f:3d01d9e6
devices=/dev/sdb1,/dev/sdc1
ARRAY /dev/md1 level=raid1 num-devices=2 metadata=0.90 UUID=893dfb9a:554055f5:2ba6685a:2761cbe9
devices=/dev/sdd1,/dev/sde1
ARRAY /dev/md2 level=raid1
devices=/dev/sdf1,/dev/sdg1
fdisk -l
[code]# fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0005f543
Device Boot Start End Blocks Id System
/dev/sda1 * 1 382 3068383+ 83 Linux
/dev/sda2 383 443 489982+ 82 Linux swap / Solaris
/dev/sda3 444 60801 484825635 f W95 Ext’d (LBA)
/dev/sda5 445 60801 484817602+ 83 Linux
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xf4baf4ba
Device Boot Start End Blocks Id System
/dev/sdb1 1 60801 488384001 fd Linux raid autodetect
Disk /dev/sdd: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000d923c
Device Boot Start End Blocks Id System
/dev/sdd1 1 182401 1465136001 fd Linux raid autodetect
Disk /dev/sdf: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x6f018f9b
Device Boot Start End Blocks Id System
/dev/sdf1 1 182401 1465136001 83 Linux
Disk /dev/sde: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xbbbbbbbb
Device Boot Start End Blocks Id System
/dev/sde1 1 182401 1465136001 fd Linux raid autodetect
Disk /dev/sdg: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x6f018f9a
Device Boot Start End Blocks Id System
/dev/sdg1 1 182401 1465136001 83 Linux
Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xf4baf4bb
Device Boot Start End Blocks Id System
/dev/sdc1 1 60801 488384001 fd Linux raid autodetect
Disk /dev/md2: 1500.3 GB, 1500298077184 bytes
2 heads, 4 sectors/track, 366283710 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/md2 doesn’t contain a valid partition table
Disk /dev/md1: 1500.3 GB, 1500299198464 bytes
2 heads, 4 sectors/track, 366283984 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/md1 doesn’t contain a valid partition table[/code]
Q4) et ce # md0 : inactive sdc11
Est ce que cela veut dire que mon sdc1 est déjà dans ma grappe?