Thread: mdadm --create question

hi,

i've been having problems w/ raid 5 array, , after extensive investigation, i'm sure last resort rebuilding array. i'd tried --assemble, b/c it's created array, didn't seem that. so, checked --create, , re-create array w/out destroying data, if superblocks persistent, seem be. however, here's get:

code:

sudo fdisk -l disk /dev/sdb: 1000.2 gb, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 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: 0x5745e6e0     device boot      start         end      blocks   id  system /dev/sdb1               1      121601   976760001   fd  linux raid autodetect  disk /dev/sdc: 1000.2 gb, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 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: 0xf8844ad1     device boot      start         end      blocks   id  system /dev/sdc1               1      121601   976760001   fd  linux raid autodetect  disk /dev/sde: 1000.2 gb, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 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: 0xc6603c74     device boot      start         end      blocks   id  system /dev/sde1               1      121601   976760001   fd  linux raid autodetect  disk /dev/sdd: 1000.2 gb, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 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: 0x05563535     device boot      start         end      blocks   id  system /dev/sdd1               1      121601   976760001   fd  linux raid autodetect  disk /dev/sdf: 1000.2 gb, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 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: 0xff2ebb89     device boot      start         end      blocks   id  system /dev/sdf1               1      121601   976760001   fd  linux raid autodetect  disk /dev/sdg: 1000.2 gb, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 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: 0x5be14e4a     device boot      start         end      blocks   id  system /dev/sdg1               1      121601   976760001   fd  linux raid autodetect  disk /dev/sdh: 1000.2 gb, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 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: 0xbe4fb07e     device boot      start         end      blocks   id  system /dev/sdh1               1      121601   976760001   fd  linux raid autodetect  disk /dev/sdi: 1000.2 gb, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 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: 0x7135fa61     device boot      start         end      blocks   id  system /dev/sdi1               1      121601   976760001   fd  linux raid autodetect

code:

sudo mdadm --create /dev/md0 --level=5 --raid-devices=8 /dev/sd[b-i]1 mdadm: /dev/sdb1 appears contain ext2fs file system     size=-1752615040k  mtime=wed jul 22 12:48:10 2009 mdadm: /dev/sdb1 appears part of raid array:     level=raid5 devices=8 ctime=tue jun 16 20:03:13 2009 mdadm: /dev/sdc1 appears part of raid array:     level=raid5 devices=8 ctime=tue jun 16 20:03:13 2009 mdadm: /dev/sdd1 appears part of raid array:     level=raid5 devices=8 ctime=tue jun 16 20:03:13 2009 mdadm: /dev/sde1 appears part of raid array:     level=raid5 devices=8 ctime=tue jun 16 20:03:13 2009 mdadm: /dev/sdf1 appears part of raid array:     level=raid5 devices=8 ctime=tue jun 16 20:03:13 2009 mdadm: /dev/sdg1 appears part of raid array:     level=raid5 devices=8 ctime=tue jun 16 20:03:13 2009 mdadm: /dev/sdh1 appears part of raid array:     level=raid5 devices=8 ctime=tue jun 16 20:03:13 2009 mdadm: /dev/sdi1 appears contain ext2fs file system     size=-2021050496k  mtime=wed jul 22 12:48:10 2009 mdadm: /dev/sdi1 appears part of raid array:     level=raid5 devices=8 ctime=tue jun 16 20:03:13 2009 continue creating array? no mdadm: create aborted.

my question is: why /dev/sdb1 , /dev/sdi1 show both ext2fs , part of raid array? appreciated. thank you.


jeff

no one's ever seen behavior before?

Forum The Ubuntu Forum Community Ubuntu Specialised Support Ubuntu Servers, Cloud and Juju Server Platforms [ubuntu] mdadm --create question

Ubuntu