thr3ads.net - Xen users - [Xen-users] Dom0 lvm/software raid rhel4.1 booting issues. [Feb 2006]

If this information is useful, please help other people find it:
Share via:

Michael Montgomery

2006-Feb-24 19:43 UTC

[Xen-users] Dom0 lvm/software raid rhel4.1 booting issues.

Basically the issue comes down to my Volume Groups not being found by 
this initrd, causing good ole kernel panic.

initrd-2.6.12.6-xen3_12.1_rhel4.1.img

[root@xen01 lvm]# uname -a
Linux xen01.inside.***.com 2.6.9-22.0.2.ELsmp #1 SMP Thu Jan 5 17:13:01 
EST 2006 i686 i686 i386 GNU/Linux
[root@xen01 lvm]# cat /etc/redhat-release
Red Hat Enterprise Linux ES release 4 (Nahant Update 2)

Everything was installed by the rpms, as I''ve done another machine that
wasn''t scsi, and had this work fine.

The part I''m worried about is this:

"  Couldn''t find all physical volumes for volume group
VolGroup00."
I have sda, and sdb in a software mirror, as shown below, and I''m 
thinking that has something to do with it.

[root@xen01 ~]# pvscan
  PV /dev/sdc1   VG VolGroup00   lvm2 [68.34 GB / 0    free]
  PV /dev/md2    VG VolGroup00   lvm2 [66.25 GB / 64.00 MB free]
  Total: 2 [134.59 GB] / in use: 2 [134.59 GB] / in no VG: 0 [0   ]
[root@xen01 ~]# vgscan
  Reading all physical volumes.  This may take a while...
  Found volume group "VolGroup00" using metadata type lvm2
[root@xen01 ~]# lvscan
  ACTIVE            ''/dev/VolGroup00/LogVolRoot'' [8.00 GB]
inherit
  ACTIVE            ''/dev/VolGroup00/LogVolTmp'' [4.00 GB]
inherit
  ACTIVE            ''/dev/VolGroup00/LogVolVar'' [4.00 GB]
inherit
  ACTIVE            ''/dev/VolGroup00/LogVolXen'' [118.53 GB]
inherit

sda1:sdb1 = boot (100MB)
sda2:sdb2 = swap (2048MB)
sda3:sdb3 = Lvm
sdc = Lvm

[root@xen01 boot]# lsmod | grep mpt
mptscsih               41469  0
mptbase                57757  1 mptscsih
scsi_mod              116429  3 sg,mptscsih,sd_mod

Does anyone have any suggestions on the steps I should take next to 
debug this?

Thanks everyone.


*************** Lots of dmesg output follows, beware *******************

Loading scsi_mod.ko module
scsi_mod: no version for "struct_module" found: kernel tainted.
SCSI subsystem initialized
Loading sd_mod.ko module
Loading mptbase.ko module
Fusion MPT base driver 3.01.20
Copyright (c) 1999-2004 LSI Logic Corporation
ACPI: PCI Interrupt 0000:04:05.0[A] -> GSI 18 (level, low) -> IRQ 18
mptbase: Initiating ioc0 bringup
ioc0: 53C1030: Capabilities={Initiator,Target}
ACPI: PCI Interrupt 0000:04:05.1[B] -> GSI 19 (level, low) -> IRQ 19
mptbase: Initiating ioc1 bringup
ioc1: 53C1030: Capabilities={Initiator,Target}
Loading mptscsih.ko module
Fusion MPT SCSI Host driver 3.01.20
scsi0 : ioc0: LSI53C1030, FwRev=01032300h, Ports=1, MaxQ=255, IRQ=18
  Vendor: FUJITSU   Model: MAP3735NC         Rev: 5608
  Type:   Direct-Access                      ANSI SCSI revision: 03
SCSI device sda: 143374650 512-byte hdwr sectors (73408 MB)
SCSI device sda: drive cache: write through
SCSI device sda: 143374650 512-byte hdwr sectors (73408 MB)
SCSI device sda: drive cache: write through
 sda: sda1 sda2 sda3
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
  Vendor: FUJITSU   Model: MAP3735NC         Rev: 5608
  Type:   Direct-Access                      ANSI SCSI revision: 03
SCSI device sdb: 143374650 512-byte hdwr sectors (73408 MB)
SCSI device sdb: drive cache: write through
SCSI device sdb: 143374650 512-byte hdwr sectors (73408 MB)
SCSI device sdb: drive cache: write through
 sdb: sdb1 sdb2 sdb3
Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
  Vendor: FUJITSU   Model: MAP3735NC         Rev: 5608
  Type:   Direct-Access                      ANSI SCSI revision: 03
SCSI device sdc: 143374650 512-byte hdwr sectors (73408 MB)
SCSI device sdc: drive cache: write through
SCSI device sdc: 143374650 512-byte hdwr sectors (73408 MB)
SCSI device sdc: drive cache: write through
 sdc: sdc1
Attached scsi disk sdc at scsi0, channel 0, id 2, lun 0
  Vendor: PE/PV     Model: 1x3 SCSI BP       Rev: 1.1
  Type:   Processor                          ANSI SCSI revision: 02
scsi1 : ioc1: LSI53C1030, FwRev=01032300h, Ports=1, MaxQ=255, IRQ=19
Loading dm-mod.ko module
device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
Loading md.ko module
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
Loading raid1.ko module
md: raid1 personality registered as nr 3
Loading jbd.ko module
Loading ext3.ko module
Loading dm-mirror.ko module
Loading dm-zero.ko module
Loading dm-snapshot.ko module
raidautorun: RAID_AUTORUN failed: 19
raidautorun: RAID_AUTORUN failed: 19
raidautorun: RAID_AUTORUN failed: 19
Making device-mapper control node
Scanning logical volumes
File descriptor 3 left open
  Reading all physical volumes.  This may take a while...
hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdc: packet command error: error=0x54 { AbortedCommand 
LastFailedSense=0x05 }
ide: failed opcode was: unknown
cdrom: open failed.
  /dev/hdc: open failed: No medium found
  Couldn''t find device with uuid
''v6mYx2-YWLn-1MNL-Z3nl-HKoa-qNna-Thhd6y''.
  Couldn''t find all physical volumes for volume group VolGroup00.
  Volume group "VolGroup00" not found
ERROR: /bin/lvm exited abnormally!

-- 
Michael Montgomery
Systems Administrator
http://theplanet.com


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Michael Montgomery

2006-Mar-01 17:47 UTC

head link

[Xen-users] Re: Dom0 lvm/software raid rhel4.1 booting issues.

Sorry to reply to my own post, but does anyone have any ideas what is 
going on with this panic, as I''m at a bit of a loss.

Thanks again.

Michael Montgomery wrote:
> Basically the issue comes down to my Volume Groups not being found by 
> this initrd, causing good ole kernel panic.
>
> initrd-2.6.12.6-xen3_12.1_rhel4.1.img
>
> [root@xen01 lvm]# uname -a
> Linux xen01.inside.***.com 2.6.9-22.0.2.ELsmp #1 SMP Thu Jan 5 
> 17:13:01 EST 2006 i686 i686 i386 GNU/Linux
> [root@xen01 lvm]# cat /etc/redhat-release
> Red Hat Enterprise Linux ES release 4 (Nahant Update 2)
---cut---


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Michael Montgomery

2006-Mar-01 21:36 UTC

head link

Re: [Xen-users] Re: Dom0 lvm/software raid rhel4.1 booting issues.

Well I reinstalled only making root a software raid, and now I get this 
kernel panic, which basically states

raidautorun: RAID_AUTORUN failed: 19
raidautorun: RAID_AUTORUN failed: 19
raidautorun: RAID_AUTORUN failed: 19

Does anyone have any ideas why it would do this?

----------------------------------------

Red Hat nash version 4.2.1.6 starting
Mounted /proc filesystem
Mounting sysfs
Creating /dev
Starting udev
Loading scsi_mod.ko module
scsi_mod: no version for "struct_module" found: kernel tainted.
SCSI subsystem initialized
Loading sd_mod.ko module
Loading mptbase.ko module
Fusion MPT base driver 3.01.20
Copyright (c) 1999-2004 LSI Logic Corporation
ACPI: PCI Interrupt 0000:04:05.0[A] -> GSI 18 (level, low) -> IRQ 18
mptbase: Initiating ioc0 bringup
ioc0: 53C1030: Capabilities={Initiator,Target}
ACPI: PCI Interrupt 0000:04:05.1[B] -> GSI 19 (level, low) -> IRQ 19
mptbase: Initiating ioc1 bringup
ioc1: 53C1030: Capabilities={Initiator,Target}
Loading mptscsih.ko module
Fusion MPT SCSI Host driver 3.01.20
scsi0 : ioc0: LSI53C1030, FwRev=01032300h, Ports=1, MaxQ=255, IRQ=18
   Vendor: FUJITSU   Model: MAP3735NC         Rev: 5608
   Type:   Direct-Access                      ANSI SCSI revision: 03
SCSI device sda: 143374650 512-byte hdwr sectors (73408 MB)
SCSI device sda: drive cache: write through
SCSI device sda: 143374650 512-byte hdwr sectors (73408 MB)
SCSI device sda: drive cache: write through
  sda: sda1 sda2 sda3 sda4 < sda5 >
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
   Vendor: FUJITSU   Model: MAP3735NC         Rev: 5608
   Type:   Direct-Access                      ANSI SCSI revision: 03
SCSI device sdb: 143374650 512-byte hdwr sectors (73408 MB)
SCSI device sdb: drive cache: write through
SCSI device sdb: 143374650 512-byte hdwr sectors (73408 MB)
SCSI device sdb: drive cache: write through
  sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 >
Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
   Vendor: FUJITSU   Model: MAP3735NC         Rev: 5608
   Type:   Direct-Access                      ANSI SCSI revision: 03
SCSI device sdc: 143374650 512-byte hdwr sectors (73408 MB)
SCSI device sdc: drive cache: write through
SCSI device sdc: 143374650 512-byte hdwr sectors (73408 MB)
SCSI device sdc: drive cache: write through
  sdc: sdc1
Attached scsi disk sdc at scsi0, channel 0, id 2, lun 0
   Vendor: PE/PV     Model: 1x3 SCSI BP       Rev: 1.1
   Type:   Processor                          ANSI SCSI revision: 02
scsi1 : ioc1: LSI53C1030, FwRev=01032300h, Ports=1, MaxQ=255, IRQ=19
Loading dm-mod.ko module
device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
Loading md.ko module
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
Loading raid1.ko module
md: raid1 personality registered as nr 3
Loading jbd.ko module
Loading ext3.ko module
raidautorun: RAID_AUTORUN failed: 19
raidautorun: RAID_AUTORUN failed: 19
raidautorun: RAID_AUTORUN failed: 19
Creating root device
Mounting root filesystem
EXT3-fs: unable to read superblock
mount: error 22 mounting ext3
mount: error 2 mounting none
Switching to new root
switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!
  (XEN) Domain 0 shutdown: rebooting machine. 



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Michael Montgomery

2006-Mar-01 21:39 UTC

head link

Re: [Xen-users] Re: Dom0 lvm/software raid rhel4.1 booting issues.

http://lists.xensource.com/archives/html/xen-users/2006-02/msg00053.html

I believe the above answers the question.  Sorry for the multiple posts.

Michael Montgomery wrote:> Well I reinstalled only making root a software raid, and now I get this 
> kernel panic, which basically states
> 
> raidautorun: RAID_AUTORUN failed: 19
> raidautorun: RAID_AUTORUN failed: 19
> raidautorun: RAID_AUTORUN failed: 19
> 
> Does anyone have any ideas why it would do this?
> 
> ----------------------------------------
> 
> Red Hat nash version 4.2.1.6 starting
> Mounted /proc filesystem
> Mounting sysfs
> Creating /dev
> Starting udev
> Loading scsi_mod.ko module
> scsi_mod: no version for "struct_module" found: kernel tainted.
> SCSI subsystem initialized
> Loading sd_mod.ko module
> Loading mptbase.ko module
> Fusion MPT base driver 3.01.20
> Copyright (c) 1999-2004 LSI Logic Corporation
> ACPI: PCI Interrupt 0000:04:05.0[A] -> GSI 18 (level, low) -> IRQ 18
> mptbase: Initiating ioc0 bringup
> ioc0: 53C1030: Capabilities={Initiator,Target}
> ACPI: PCI Interrupt 0000:04:05.1[B] -> GSI 19 (level, low) -> IRQ 19
> mptbase: Initiating ioc1 bringup
> ioc1: 53C1030: Capabilities={Initiator,Target}
> Loading mptscsih.ko module
> Fusion MPT SCSI Host driver 3.01.20
> scsi0 : ioc0: LSI53C1030, FwRev=01032300h, Ports=1, MaxQ=255, IRQ=18
>   Vendor: FUJITSU   Model: MAP3735NC         Rev: 5608
>   Type:   Direct-Access                      ANSI SCSI revision: 03
> SCSI device sda: 143374650 512-byte hdwr sectors (73408 MB)
> SCSI device sda: drive cache: write through
> SCSI device sda: 143374650 512-byte hdwr sectors (73408 MB)
> SCSI device sda: drive cache: write through
>  sda: sda1 sda2 sda3 sda4 < sda5 >
> Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
>   Vendor: FUJITSU   Model: MAP3735NC         Rev: 5608
>   Type:   Direct-Access                      ANSI SCSI revision: 03
> SCSI device sdb: 143374650 512-byte hdwr sectors (73408 MB)
> SCSI device sdb: drive cache: write through
> SCSI device sdb: 143374650 512-byte hdwr sectors (73408 MB)
> SCSI device sdb: drive cache: write through
>  sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 >
> Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
>   Vendor: FUJITSU   Model: MAP3735NC         Rev: 5608
>   Type:   Direct-Access                      ANSI SCSI revision: 03
> SCSI device sdc: 143374650 512-byte hdwr sectors (73408 MB)
> SCSI device sdc: drive cache: write through
> SCSI device sdc: 143374650 512-byte hdwr sectors (73408 MB)
> SCSI device sdc: drive cache: write through
>  sdc: sdc1
> Attached scsi disk sdc at scsi0, channel 0, id 2, lun 0
>   Vendor: PE/PV     Model: 1x3 SCSI BP       Rev: 1.1
>   Type:   Processor                          ANSI SCSI revision: 02
> scsi1 : ioc1: LSI53C1030, FwRev=01032300h, Ports=1, MaxQ=255, IRQ=19
> Loading dm-mod.ko module
> device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
> Loading md.ko module
> md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
> Loading raid1.ko module
> md: raid1 personality registered as nr 3
> Loading jbd.ko module
> Loading ext3.ko module
> raidautorun: RAID_AUTORUN failed: 19
> raidautorun: RAID_AUTORUN failed: 19
> raidautorun: RAID_AUTORUN failed: 19
> Creating root device
> Mounting root filesystem
> EXT3-fs: unable to read superblock
> mount: error 22 mounting ext3
> mount: error 2 mounting none
> Switching to new root
> switchroot: mount failed: 22
> umount /initrd/dev failed: 2
> Kernel panic - not syncing: Attempted to kill init!
>  (XEN) Domain 0 shutdown: rebooting machine.
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
-- 
Michael Montgomery
Systems Administrator
http://theplanet.com

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Reasonably Related Threads

Search for more reasonably related threads

Xen users - Feb 2006 - Dom0 lvm/software raid rhel4.1 booting issues.

[Xen-users] Dom0 lvm/software raid rhel4.1 booting issues.

[Xen-users] Re: Dom0 lvm/software raid rhel4.1 booting issues.

Re: [Xen-users] Re: Dom0 lvm/software raid rhel4.1 booting issues.

Re: [Xen-users] Re: Dom0 lvm/software raid rhel4.1 booting issues.

Reasonably Related Threads