Andre,

uh-oh... I wasn't expecting to see anything about dmraid. I just
*assumed* you were using a hardware RAID controller. I have similar
configurations to you; DL140s with add-in RAID cards, but I use LSI
MegaRAID SATA/SAS controllers. I have had issues from time to time
moving (i.e. cloning, etc) disks from server to server, which has lead
me to troubleshooting boot issues from time to time. And that's why I
jumped in...

I am not sure if I can be any help. The things I would try are; since
you know what the init script does and which modules are loaded in
initrd, try booting into rescue mode and running the commands manually
(trying to mount the disks). RHEL installed right? So you should be able
to mount this disk somehow. What does the output of lspci -vv look like?
What does lsmod look like? If you can get the output of dmesg from
booting into rescue mode, what does it look like?

Maybe some software ATARAID folks can chime in. Which model card do you
have? Are you sure it's supported? From the dmraid man page, it seems
like not all metadata formats are supported. Maybe you will have to
break the RAID and do what Leos suggested; JBOD and use software RAID.

-Allen


>
> Hi Allen,
>
> > I would check your initrd for the proper modules (sata_*.ko
> > maybe?). It
> > sounds like they aren't getting loaded via the init script in your
> > initrd.
> I've compared them with the modules loaded during install, and it
seems
> all the proper modules are loaded.
>
> > Do you have an "alias scsi_hostadapter <something>" line in your
> > /etc/modprobe.conf file?
> Indeed :
>
> ]# cat /etc/modprobe.conf
> alias eth0 tg3
> alias eth1 tg3
> alias scsi_hostadapter ahci
> alias scsi_hostadapter1 usb-storage
>
> Adding verbose and debug options to dmraid in the init script in
> initrd,
> gives some more detail about the possible cause :
>
> dmraid -vvv -ddd -ay -i -p "ddf1_System"
> NOTICE: /dev/sda: ddf1   discovering
> NOTICE: /dev/sda: ddf1 metadata discovered
> NOTICE: /dev/sdb: ddf1   discovering
> NOTICE: /dev/sdb: ddf1 metadata discovered
> DEBUG: _find_set: searching ddf1_System
> DEBUG: _find_set: not found ddf1_System
> DEBUG: _find_set: searching .ddf1_disks
> DEBUG: _find_set: not found .ddf1_disks
> DEBUG: _find_set: searching ddf1_System
> DEBUG: _find_set: searching ddf1_System
> DEBUG: _find_set: not found ddf1_System
> DEBUG: _find_set: not found ddf1_System
> NOTICE: added /dev/sda to RAID set ".ddf1_disks"
> NOTICE: dropping unwanted RAID set ".ddf1_disks"
> DEBUG: freeing devices of RAID set "ddf1_System"
> DEBUG: freeing device "ddf1_System", path "/dev/sda"
> DEBUG: freeing devices of RAID set ".ddf1_disks"
> DEBUG: freeing device ".ddf1_disks", path "/dev/sda"
>
> kpartx -a -p p "/dev/mapper/ddf1_System"
> failes because the /dev/mapper device is not there (seems fair).
>
> I've named the RAID 1 set "System" in the internal RAID controller
> utility. During RH installation it's called ddf1_System, but booting
> the
> server after installation dmraid does not finds "System" but "disks"
> and
> calls it .ddf1-disks , correct?
>
> Thanks,
> Andre
>
> > The /dev/mapper/* devices are getting created because "vgscan" and
> > "vgchange -ay" isn't finding any volume groups (the SATA disk can't
> be
> > found).
> >
> > -Allen
> >



_______________________________________________
rhelv5-list mailing list
rhelv5-list@(protected)
https://www.redhat.com/mailman/listinfo/rhelv5-list