-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-01-02 at 23:34 -0000, Con Hennessy wrote:
Inactive?
Try "mdadm --detail /dev/md0", it gives more detailed info. If it is inactive, it can not be fscked, nor mounted. You will have to activate it first, something went wrong.
Ok, I manually did : # mdadm --stop /dev/md0 # mkraid --really-force /dev/md0 # mkreiserfs -b 4096 /dev/md0
Which all worked. I was able to mount /dev/md0, edit a file on it, unmount and remount it several times without any problems.
However after a reboot it would not mount. /var/log/message contained the following : <5>Kernel command line: root=/dev/hda3 vga=0x31a selinux=0 splash=silent raid=noautodetect
But this ^^^ option means that the kernel will not autodetect and enable the raid device at start up; from '/usr/src/linux/Documentation/md.txt': | Boot time autodetection of RAID arrays | -------------------------------------- | | When md is compiled into the kernel (not as module), partitions of | type 0xfd are scanned and automatically assembled into RAID arrays. | This autodetection may be suppressed with the kernel parameter | "raid=noautodetect". As of kernel 2.6.9, only drives with a type 0 | superblock can be autodetected and run at boot time. I have 9.3, not 10.0 as you do, but mine works without that option. I'm not sure you need it :-?
<6>md: md driver 0.90.2 MAX_MD_DEVS=256, MD_SB_DISKS=27 <6>md: bitmap version 3.38 <6>md: md0 stopped. <6>md: Autodetecting RAID arrays.
But then I don't understand this.
<6>md: autorun ... <6>md: considering hdc6 ... <6>md: adding hdc6 ... <6>md: adding hda6 ... <6>md: created md0 <6>md: bind<hda6> <6>md: bind<hdc6> <6>md: running: <hdc6><hda6> <4>md: personality 3 is not loaded! <4>md: do_md_run() returned -22 <6>md: md0 stopped. <6>md: unbind<hdc6> <6>md: export_rdev(hdc6) <6>md: unbind<hda6> <6>md: export_rdev(hda6) <6>md: ... autorun DONE. <6>md: raid1 personality registered as nr 3 mdadm: no devices found for /dev/md0
Also # mdadm --detail /dev/md0 mdadm: md device /dev/md0 does not appear to be active.
Perhaps with that option in the kernel line you need to manually activate the raid device later on. I wonder what is the preferred method in SuSE 10.0 :-?
# mdadm -Q /dev/md0 /dev/md0: is an md device which is not active /dev/md0: is too small to be an md component.
Still not getting anywhere ! Con Hennessy
I'm confused. I can not test your system! ;-} - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDucz6tTMYHG2NR9URAh2cAJsFv8juFpRj44Xszie3TKyeWiqMIwCfRqI/ YqCrOnqNx01DrWyARpTTYxw= =Kvgf -----END PGP SIGNATURE-----