zeeman
17.06.05, 16:14
Hallo zusammen!
Ich habe ein normale /etc/raidtab:
raiddev /dev/md0
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
chunk-size 4
persistent-superblock 1
device /dev/hde1
raid-disk 0
device /dev/hdg1
raid-disk 1
# raidtab config-file
raiddev /dev/md1
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
chunk-size 4
persistent-superblock 1
device /dev/hdf1
raid-disk 0
device /dev/hdh1
raid-disk 1
beim booten haut mir der kernel aber das hier um die ohren:
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: considering hdh1 ...
md: adding hdh1 ...
md: hdg1 has different UUID to hdh1
md: adding hdf1 ...
md: hde1 has different UUID to hdh1
md: created md1
md: bind<hdf1>
md: bind<hdh1>
md: running: <hdh1><hdf1>
md: personality 3 is not loaded!
md: do_md_run() returned -22
md: md1 stopped.
md: unbind<hdh1>
md: export_rdev(hdh1)
md: unbind<hdf1>
md: export_rdev(hdf1)
md: considering hdg1 ...
md: adding hdg1 ...
md: adding hde1 ...
md: created md0
md: bind<hde1>
md: bind<hdg1>
md: running: <hdg1><hde1>
md: personality 3 is not loaded!
md: do_md_run() returned -22
md: md0 stopped.
md: unbind<hdg1>
md: export_rdev(hdg1)
md: unbind<hde1>
md: export_rdev(hde1)
md: ... autorun DONE.
md: raid1 personality registered as nr 3
md: md0 stopped.
md: bind<hdg1>
md: bind<hde1>
md: md1 stopped.
md: bind<hdh1>
md: bind<hdf1>
so weit. so gut.
das lustige ist aber, ein
# mdrun /dev/md0
# mdrun /dev/md1
erstellt die raids ohne probleme.
was soll das?
Ich habe ein normale /etc/raidtab:
raiddev /dev/md0
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
chunk-size 4
persistent-superblock 1
device /dev/hde1
raid-disk 0
device /dev/hdg1
raid-disk 1
# raidtab config-file
raiddev /dev/md1
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
chunk-size 4
persistent-superblock 1
device /dev/hdf1
raid-disk 0
device /dev/hdh1
raid-disk 1
beim booten haut mir der kernel aber das hier um die ohren:
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: considering hdh1 ...
md: adding hdh1 ...
md: hdg1 has different UUID to hdh1
md: adding hdf1 ...
md: hde1 has different UUID to hdh1
md: created md1
md: bind<hdf1>
md: bind<hdh1>
md: running: <hdh1><hdf1>
md: personality 3 is not loaded!
md: do_md_run() returned -22
md: md1 stopped.
md: unbind<hdh1>
md: export_rdev(hdh1)
md: unbind<hdf1>
md: export_rdev(hdf1)
md: considering hdg1 ...
md: adding hdg1 ...
md: adding hde1 ...
md: created md0
md: bind<hde1>
md: bind<hdg1>
md: running: <hdg1><hde1>
md: personality 3 is not loaded!
md: do_md_run() returned -22
md: md0 stopped.
md: unbind<hdg1>
md: export_rdev(hdg1)
md: unbind<hde1>
md: export_rdev(hde1)
md: ... autorun DONE.
md: raid1 personality registered as nr 3
md: md0 stopped.
md: bind<hdg1>
md: bind<hde1>
md: md1 stopped.
md: bind<hdh1>
md: bind<hdf1>
so weit. so gut.
das lustige ist aber, ein
# mdrun /dev/md0
# mdrun /dev/md1
erstellt die raids ohne probleme.
was soll das?