Hi,

> 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...
No, this is a low end server for some simple tasks. All other servers we
use are indeed with hardware raid (like BL-460c blades). But cool you
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?

00:1f.2 RAID bus controller: Intel Corporation 631xESB/632xESB SATA RAID
Controller (rev 09)
    Subsystem: Hewlett-Packard Company Unknown device 31fe
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr+ Stepping- SERR- FastB2B-
    Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
    Latency: 0
    Interrupt: pin B routed to IRQ 74
    Region 0: I/O ports at 1890 [size=8]
    Region 1: I/O ports at 1884 [size=4]
    Region 2: I/O ports at 1888 [size=8]
    Region 3: I/O ports at 1880 [size=4]
    Region 4: I/O ports at 1860 [size=32]
    Region 5: Memory at dfe00400 (32-bit, non-prefetchable)
[size=1K]
    Capabilities: [70] Power Management version 2
          Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot+,D3cold-)
          Status: D0 PME-Enable- DSel=0 DScale=0 PME-
    Capabilities: [a8] #12 [0010]

> What does lsmod look like? If you can get the output of dmesg from
> booting into rescue mode, what does it look like?

Well it's working now, had to modify initrd and add some modules:

- part from RH version :
insmod /lib/dm-snapshot.ko
echo Waiting for driver initialization.
stabilized --hash --interval 250 /proc/scsi/scsi
mkblkdevs
echo Scanning and configuring dmraid supported devices
dmraid -ay -i -p "ddf1_System"
kpartx -a -p p "/dev/mapper/ddf1_System"

- Modified version
insmod /lib/dm-snapshot.ko
insmod /lib/xor.ko
insmod /lib/raid0.ko
insmod /lib/raid1.ko
insmod /lib/raid10.ko
insmod /lib/raid456.ko
insmod /lib/raid_class.ko
echo Waiting for driver initialization.
stabilized --hash --interval 250 /proc/scsi/scsi
mkblkdevs
echo Scanning and configuring dmraid supported devices
dmraid -ay -i -p ".ddf1_disks"
kpartx -a -p p "/dev/mapper/ddf1_System"

But after a kernel update via yum RHN, it's modify time again ...

> 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.
Yeah, I think I jump on the JBOD band wagon for this server, seems to be
the less difficult and stable way.

All thanks for you time!

Cheers,
Ander

> -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
>
>


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