Andre Cruz wrote:
>
> [root@lx12pc164 /]# mkraid --really-force /dev/md0
> DESTROYING the contents of /dev/md0 in 5 seconds, Ctrl-C if unsure!
> handling MD device /dev/md0
> analyzing super-block
> disk 0: /dev/hdc1, 1306336kB, raid superblock at 1306240kB
> disk 1: /dev/hdd2, 1183392kB, raid superblock at 1183296kB
> mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
> [root@lx12pc164 /]# tail /var/log/messages
> Jan 12 10:18:03 localhost sshd2[373]: Daemon is running.
> Jan 12 10:18:03 localhost keytable: Loading keymap:
> Jan 12 10:18:04 localhost keytable: Loading
> /usr/lib/kbd/keymaps/i386/qwerty/pt-latin1.kmap.gz
> Jan 12 10:18:04 localhost keytable: Loading system font:
> Jan 12 10:18:04 localhost rc: Starting keytable succeeded
> Jan 12 10:18:05 localhost gpm: gpm startup succeeded
> Jan 12 10:18:05 localhost linuxconf: Linuxconf final setup
> Jan 12 10:18:08 localhost rc: Starting linuxconf succeeded
> Jan 12 10:18:12 localhost PAM_pwdb[440]: (login) session opened for user
> root by LOGIN(uid=0)
> Jan 12 10:27:13 localhost PAM_pwdb[441]: (login) session opened for user
> cruza by LOGIN(uid=0)
> [root@lx12pc164 /]# cat /proc/mdstat
> Personalities : [2 raid0]
> read_ahead not set
> md0 : inactive
> md1 : inactive
> md2 : inactive
> md3 : inactive
> [root@lx12pc164 /]#
>
> Can anyone tell me what's the problem? thanks
Your FIRST problem is that you don't know how to read the documentation
for the command 'mkraid --force'. Please go back and read this a couple
more times until it makes sense. Your problem creating the RAID is
quite possibly that you don't have the RAID 0.90 patches applied to your
kernel. If you're running 2.2.x where x is less than 14, then you can
get the patches from kernel.org, in one of the directories under
"people". If you're running 2.2.14, you'll need to download Ingo
Molar's latest patches from http://www.redhat.com/~mingo/raid-2.2.14-B1.
Greg
