Date:  Thu, 28 Sep 2006 10:46:43 +0200
From:  Dennis <dennis (at mark) mixfans.org>
Subject:  [coba-e:07259] software raid & booting
To:  coba-e (at mark) bluequartz.org
Message-Id:  <451B8BF3.9070702 (at mark) mixfans.org>
In-Reply-To:  <001201c6e2cc$55b2ba20$6400a8c0@YOUR4105E587B6>
References:  <001201c6e2cc$55b2ba20$6400a8c0@YOUR4105E587B6>
X-Mail-Count: 07259

Checking why the server cannot boot until I rewrite the LILO conf I am 
trying multiple things

when checking mdchk I see an error .. with a fatal: open/dev/dis
is this normal? How can I prevent a fatal message? And/or can it be the 
issue why Lilo is not correctly updated?

-- Reading system configuration from /etc/raidtab
   /dev/md0 [raid1]: <hda1> <hdc1>
   /dev/md1 [raid1]: <hda2> <hdc2>
   /dev/md2 [raid1]: <hda3> <hdc3>
   /dev/md3 [raid1]: <hda5> <hdc5>

-- Reading current status from /proc/mdstat
   /dev/md0 [raid1]: <hdc1> <hda1>  (ACTIVE)
   /dev/md1 [raid1]: <hdc2> <hda2>  (ACTIVE)
   /dev/md2 [raid1]: <hdc3> <hda3>  (ACTIVE)
   /dev/md3 [raid1]: <hdc5> <hda5>  (ACTIVE)
boot = /dev/hda, map = /boot/map.0301
Added 2.6.9-42.0.2.EL *
Added 2.6.9-22.0.2.EL
boot = /dev/dis, map = /boot/map.1601
Fatal: open /dev/dis: No such file or directory
Public domain syslinux master boot record successfully written to /dev/hda
Public domain syslinux master boot record successfully written to /dev/hdc