kernel-2.6.17-1.2145_FC5 still won't boot Promise Raid 0 LVM Set

[Andrew Gray <andrewg@xxxxxxxxxxxxxxx>]

Under kernel-2.6.16-1.2133 my system boots a raid 0 volume on a Promise
PDC 20376 that looks like:-

[root@www ~]# dmraid -s
*** Active Set
name   : pdc_fiagfhab
size   : 625163264
stride : 128
type   : stripe
status : ok
subsets: 0
devs   : 2
spares : 0

All FC5 kernel-2.6.17's including 2145  won't boot on my system. The
boot volume is a raid
0 array on a Promise PDC20376 (FastTrak) :-

#Loading jbd.ko module
#Loading ext3.ko module
#Locading dm-mod.ko module
#device-mapper: 4.6.0-ioctl (2006-02-17) initialised:
dm-devel@xxxxxxxxxx
#Loading dm-mirror.ko module
#Loading dm-zero.ko module
#Loading dm-snapshot.ko module  
#Making device-mapper control mode 

Kernel 2.6.17-2145_FC5 Then hangs !!

I am presuming kernel-2.6.17 kernels doesn't boot because it is not
recognising my LVM volume setup with 2.6.16 kernel
using /dev/mapper/pdc_fiagfhabp2 on the Promise PDC20376. Maybe it has
changed the device mapper name for this device? :-

VolGroup00 {
        id = "4NcUZI-LeMy-MC6H-V3hJ-vRmm-BVK5-OKEi8R"
        seqno = 3
        status = ["RESIZEABLE", "READ", "WRITE"]
        extent_size = 65536             # 32 Megabytes
        max_lv = 0
        max_pv = 0
        physical_volumes {
                pv0 {
                        id = "Pf0oSr-CTGB-9iGn-42Xz-TYOt-z0DT-t2YUIK"
                        device = "/dev/mapper/pdc_fiagfhabp2" #Hint only
                        status = ["ALLOCATABLE"]
                        pe_start = 384
                        pe_count = 9535 # 297.969 Gigabytes
                }
        }
        logical_volumes {
                LogVol00 {
                        id = "7ZvkdR-OZbv-N5T6-aqNW-44io-H2pv-wIgN43"
                        status = ["READ", "WRITE", "VISIBLE"]
                        segment_count = 1
                        segment1 {
                                start_extent = 0
                                extent_count = 9472     # 296 Gigabytes
                                type = "striped"
                                stripe_count = 1        # linear
                                stripes = [
                                        "pv0", 0
                                ]
                        }
                }
               LogVol01 {
                        id = "D1PqSj-Giji-IhD3-AtXU-jtFk-hl2D-3fP24h"
                        status = ["READ", "WRITE", "VISIBLE"]
                        segment_count = 1
                        segment1 {
                                start_extent = 0
                                extent_count = 62     # 1.9375 Gigabytes
                                type = "striped"
                                stripe_count = 1      # linear
                                stripes = [
                                        "pv0", 9472
                                ]
                        }
                }
        }
}

Any ideas how to debug the boot problem with Kernel 2.6.17 FC5 and
Promise RAID controllers when the system won't boot with a 2.6.17 FC5
kernel?

--Andrew Gray


-- 
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe: 
https://www.redhat.com/mailman/listinfo/fedora-test-list