kernel-2.6.17-1.2139_FC5 won't boot

Andrew Gray andrewg at linnetsol.co.uk
Sun Jun 25 12:01:04 UTC 2006


On Sat, 2006-06-24 at 11:51 +0100, Andrew Gray wrote: 
> I can't boot kernel-2.6.17-1.2139 it hangs at:-
> 
> device-mapper: 4.6.0-ioctl (2006-02-17) 
> 
> When it hang the screen on monitor looks identical to
> kernel-2.6.16-1.2133_FC5 dmesg entry except version of device-mapper:-
> 
> SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
> sda: Write Protect is off
> sda: Mode Sense: 00 3a 00 00
> SCSI device sda: drive cache: write back
> SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
> sda: Write Protect is off
> sda: Mode Sense: 00 3a 00 00
> SCSI device sda: drive cache: write back
>  sda: sda1 sda2
> sd 0:0:0:0: Attached scsi disk sda
>   Vendor: ATA       Model: WDC WD1600SD-01K  Rev: 08.0
>   Type:   Direct-Access                      ANSI SCSI revision: 05
> SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
> sdb: Write Protect is off
> sdb: Mode Sense: 00 3a 00 00
> SCSI device sdb: drive cache: write back
> SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
> sdb: Write Protect is off
> sdb: Mode Sense: 00 3a 00 00
> SCSI device sdb: drive cache: write back
>  sdb: unknown partition table
> sd 1:0:0:0: Attached scsi disk sdb
> device-mapper: 4.6.0-ioctl (2006-02-17) initialised: dm-devel at redhat.com
> 
> System:- 
> 
> Motherboard ASUS A7V8X 
> AMD Athlon 2200+ 
> 1GB ram 
> Promise PDC20376 (FastTrak 376) BIOS defined RAID 0 on pair of 160GB
> Western Digital drives
> 
> Have to use kernel-2.6.16-1.2133_FC5 for now!!
> 
> --Andrew Gray 
> 
I am presuming kernel-2.6.17-1.2139 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
                                ]
                        }
                }
        }
}


Since kernel-2.6.17-1.2139 doesn't get pass the initally device-mapper
invocation how can I debug this further so I can submit a bug!

--Andrew Gray






More information about the fedora-list mailing list