Hello all I am having issues mounting my partitions residing on my sw raid5.. I have tried with the stable version of xen (2.0.7) and yesterday''s hg. Same issue. Attached is the dmesg I could get while at the maintenance prompt. I am running sles9, with no service pack. The server is a relion320, with 6 HDD UltraATA. Any help appreciated. Thanks. fred _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
No one? :''( On 10/11/05, Fred Blaise <chapeaurouge@gmail.com> wrote:> Hello all > > I am having issues mounting my partitions residing on my sw raid5.. > I have tried with the stable version of xen (2.0.7) and yesterday''s > hg. Same issue. > > Attached is the dmesg I could get while at the maintenance prompt. > > I am running sles9, with no service pack. The server is a relion320, > with 6 HDD UltraATA. > > Any help appreciated. > > Thanks. > > fred > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fred Blaise wrote:> No one? :''(OK, I''ll have a go. Fred Blaise wrote:> I am running sles9, with no service pack. The server is a relion320, > with 6 HDD UltraATA.I am not familiar with your hardware or disk layout. In your original email you posted the dmesg output for the broken xen boot. Good. But it might also be helpfull to seen the dmesg output when you boot the machine with a non Xen kernel. That way we can see how it behaves when it is booting correctly. Find the difference between the two cases, and maybe we find the fix... Looking through the dmesg output I can see you have... Fred Blaise''s dmesg:>> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 >> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx >> ICH3: IDE controller at PCI slot 0000:00:1f.1 >> PCI: Enabling device 0000:00:1f.1 (0005 -> 0007) >> PCI: Obtained IRQ 18 for device 0000:00:1f.1 >> ICH3: chipset revision 2 >> ICH3: not 100% native mode: will probe irqs later >> ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio >> ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:DMA >> Probing IDE interface ide0... >> hda: ST3120026A, ATA DISK drive >> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 >> Probing IDE interface ide1... >> hdc: ST3120026A, ATA DISK drive >> hdd: SAMSUNG CD-R/RW DRIVE SW-252F, ATAPI CD/DVD-ROM drive >> ide1 at 0x170-0x177,0x376 on irq 15 >> Probing IDE interface ide2... >> Probing IDE interface ide3... >> Probing IDE interface ide4... >> Probing IDE interface ide5... >> hda: max request size: 1024KiB >> hda: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63, UDMA(100) >> hda: cache flushes supported >> hda: hda1 hda2 hda3 < hda5 > >> hdc: max request size: 1024KiB >> hdc: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63, UDMA(33) >> hdc: cache flushes supported >> hdc: hdc1 >> hdd: ATAPI 1X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33) >> Uniform CD-ROM driver Revision: 3.20.. what looks like three IDE devices, hda (ST3120026A), hdc (another ST3120026A), hdd (CD-ROM drive). What are the 6 HDD ultra ATA ? Do you mean the interfaces ide0 through ide5? or are there 6 addition disk drives that have not been recognised?>> Red Hat/Adaptec aacraid driver (1.1.2-lk2 Aug 4 2005) >> 3ware Storage Controller device driver for Linux v1.26.02.000. >> libata version 1.10 loaded. >> Fusion MPT base driver 3.01.18 >> Copyright (c) 1999-2004 LSI Logic Corporation >> Fusion MPT SCSI Host driver 3.01.18Hmm, these are drivers for other disk interface cards aren''t they? Which of these, if any, are actually being used? If we are using aacraid driver (hardware RAID) then we probably don''t want to bother with the md (software RAID) drivers.>> md: raid0 personality registered as nr 2 >> md: raid1 personality registered as nr 3 >> md: raid5 personality registered as nr 4 >> raid5: automatically using best checksumming function: pIII_sse >> pIII_sse : 2697.200 MB/sec >> raid5: using function: pIII_sse (2697.200 MB/sec) >> md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27 >> device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.comYou have the sofware raid5 module loaded, good.>> ReiserFS: hdc1: found reiserfs format "3.6" with standard journal >> ReiserFS: hdc1: using ordered data mode >> ReiserFS: hdc1: journal params: device hdc1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 >> ReiserFS: hdc1: checking transaction log (hdc1) >> ReiserFS: hdc1: Using r5 hash to sort names >> VFS: Mounted root (reiserfs filesystem).so /dev/hdc1 is your root partition and it has been mounted correctly.>> Adding 1052248k swap on /dev/hda2. Priority:42 extents:1And you have swap too, good.>> md: could not open unknown-block(33,1). >> md: autostart failed! >> md: Autodetecting RAID arrays. >> md: autorun ... >> md: ... autorun DONE.robbie@adler:~> ls -l /dev/hde1 brw-rw---- 1 root disk 33, 1 2005-03-19 19:36 /dev/hde1 robbie@adler:~> so block device 33,1 is /dev/hde1 I didn''t see /dev/hde appear in your dmesg, so we need to try to get the dom0 kernel to find that device and possibly others too. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 10/13/05, Robbie Dinn <robbie@microbus.com> wrote:> Fred Blaise wrote: > > No one? :''( > > OK, I''ll have a go.Hi, thanks for taking a shot at this.> > Fred Blaise wrote: > > I am running sles9, with no service pack. The server is a relion320, > > with 6 HDD UltraATA. > > I am not familiar with your hardware or disk layout. > In your original email you posted the dmesg output for > the broken xen boot. Good. But it might also be > helpfull to seen the dmesg output when you boot the > machine with a non Xen kernel. That way we can see how > it behaves when it is booting correctly. Find the difference > between the two cases, and maybe we find the fix...I have attached a dmesg of the regular sles9 boot.> > Looking through the dmesg output I can see you have... > > Fred Blaise''s dmesg: > >> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > >> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx > >> ICH3: IDE controller at PCI slot 0000:00:1f.1 > >> PCI: Enabling device 0000:00:1f.1 (0005 -> 0007) > >> PCI: Obtained IRQ 18 for device 0000:00:1f.1 > >> ICH3: chipset revision 2 > >> ICH3: not 100% native mode: will probe irqs later > >> ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio > >> ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:DMA > >> Probing IDE interface ide0... > >> hda: ST3120026A, ATA DISK drive > >> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 > >> Probing IDE interface ide1... > >> hdc: ST3120026A, ATA DISK drive > >> hdd: SAMSUNG CD-R/RW DRIVE SW-252F, ATAPI CD/DVD-ROM drive > >> ide1 at 0x170-0x177,0x376 on irq 15 > >> Probing IDE interface ide2... > >> Probing IDE interface ide3... > >> Probing IDE interface ide4... > >> Probing IDE interface ide5... > >> hda: max request size: 1024KiB > >> hda: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63, UDMA(100) > >> hda: cache flushes supported > >> hda: hda1 hda2 hda3 < hda5 > > >> hdc: max request size: 1024KiB > >> hdc: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63, UDMA(33) > >> hdc: cache flushes supported > >> hdc: hdc1 > >> hdd: ATAPI 1X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33) > >> Uniform CD-ROM driver Revision: 3.20 > > .. what looks like three IDE devices, hda (ST3120026A), > hdc (another ST3120026A), hdd (CD-ROM drive). > > What are the 6 HDD ultra ATA ? Do you mean the interfaces ide0 through > ide5? or are there 6 addition disk drives that have not been recognised?no... it seems, somehow, that hda and hdc are being recognized differently than the other 4 maybe? At boot-up time (BIOS level), there''s a screen that detects the 4 last drives. Doesn''t do this for the 2 first.> > >> Red Hat/Adaptec aacraid driver (1.1.2-lk2 Aug 4 2005) > >> 3ware Storage Controller device driver for Linux v1.26.02.000. > >> libata version 1.10 loaded. > >> Fusion MPT base driver 3.01.18 > >> Copyright (c) 1999-2004 LSI Logic Corporation > >> Fusion MPT SCSI Host driver 3.01.18 > > Hmm, these are drivers for other disk interface cards aren''t they? > Which of these, if any, are actually being used? > If we are using aacraid driver (hardware RAID) then we probably > don''t want to bother with the md (software RAID) drivers.I don''t think I have this storage controller in there. Maybe these conflict with the md module?> > >> md: raid0 personality registered as nr 2 > >> md: raid1 personality registered as nr 3 > >> md: raid5 personality registered as nr 4 > >> raid5: automatically using best checksumming function: pIII_sse > >> pIII_sse : 2697.200 MB/sec > >> raid5: using function: pIII_sse (2697.200 MB/sec) > >> md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27 > >> device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com > > You have the sofware raid5 module loaded, good. > > >> ReiserFS: hdc1: found reiserfs format "3.6" with standard journal > >> ReiserFS: hdc1: using ordered data mode > >> ReiserFS: hdc1: journal params: device hdc1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 > >> ReiserFS: hdc1: checking transaction log (hdc1) > >> ReiserFS: hdc1: Using r5 hash to sort names > >> VFS: Mounted root (reiserfs filesystem). > > so /dev/hdc1 is your root partition and it has been mounted correctly.This has changed as of a few days. It is now a sw-raid1, on /dev/hda1 and /dev/hdc1. And it still mounts ok...> > >> Adding 1052248k swap on /dev/hda2. Priority:42 extents:1 > > And you have swap too, good.Yes. Now also a swraid1, on /dev/hda2 and /dev/hdc2.> > >> md: could not open unknown-block(33,1). > >> md: autostart failed! > >> md: Autodetecting RAID arrays. > >> md: autorun ... > >> md: ... autorun DONE. > > robbie@adler:~> ls -l /dev/hde1 > brw-rw---- 1 root disk 33, 1 2005-03-19 19:36 /dev/hde1 > robbie@adler:~> > > so block device 33,1 is /dev/hde1 > > I didn''t see /dev/hde appear in your dmesg, so we need > to try to get the dom0 kernel to find that device and > possibly others too.Indeed.>Thanks a lot for your time. fred _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 10/13/05, Robbie Dinn <robbie@microbus.com> wrote:> Fred Blaise wrote: > > No one? :''( > > OK, I''ll have a go.Hey again> > Fred Blaise wrote: > > I am running sles9, with no service pack. The server is a relion320, > > with 6 HDD UltraATA. > > I am not familiar with your hardware or disk layout. > In your original email you posted the dmesg output for > the broken xen boot. Good. But it might also be > helpfull to seen the dmesg output when you boot the > machine with a non Xen kernel. That way we can see how > it behaves when it is booting correctly. Find the difference > between the two cases, and maybe we find the fix... > > Looking through the dmesg output I can see you have... > > Fred Blaise''s dmesg: > >> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > >> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx > >> ICH3: IDE controller at PCI slot 0000:00:1f.1 > >> PCI: Enabling device 0000:00:1f.1 (0005 -> 0007) > >> PCI: Obtained IRQ 18 for device 0000:00:1f.1 > >> ICH3: chipset revision 2 > >> ICH3: not 100% native mode: will probe irqs later > >> ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio > >> ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:DMA > >> Probing IDE interface ide0... > >> hda: ST3120026A, ATA DISK drive > >> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 > >> Probing IDE interface ide1... > >> hdc: ST3120026A, ATA DISK drive > >> hdd: SAMSUNG CD-R/RW DRIVE SW-252F, ATAPI CD/DVD-ROM drive > >> ide1 at 0x170-0x177,0x376 on irq 15 > >> Probing IDE interface ide2... > >> Probing IDE interface ide3... > >> Probing IDE interface ide4... > >> Probing IDE interface ide5... > >> hda: max request size: 1024KiB > >> hda: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63, UDMA(100) > >> hda: cache flushes supported > >> hda: hda1 hda2 hda3 < hda5 > > >> hdc: max request size: 1024KiB > >> hdc: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63, UDMA(33) > >> hdc: cache flushes supported > >> hdc: hdc1 > >> hdd: ATAPI 1X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33) > >> Uniform CD-ROM driver Revision: 3.20 > > .. what looks like three IDE devices, hda (ST3120026A), > hdc (another ST3120026A), hdd (CD-ROM drive). > > What are the 6 HDD ultra ATA ? Do you mean the interfaces ide0 through > ide5? or are there 6 addition disk drives that have not been recognised?Thought I would copy-paste some info from /proc/ide in here too. This is taken from the working sles9 system. bicolor:/proc/ide # ls -l total 7 -r--r--r-- 1 root root 0 2005-10-14 10:11 drivers lrwxrwxrwx 1 root root 8 2005-10-14 10:11 hda -> ide0/hda/ lrwxrwxrwx 1 root root 8 2005-10-14 10:11 hdc -> ide1/hdc/ lrwxrwxrwx 1 root root 8 2005-10-14 10:11 hdd -> ide1/hdd/ lrwxrwxrwx 1 root root 8 2005-10-14 10:11 hde -> ide2/hde/ lrwxrwxrwx 1 root root 8 2005-10-14 10:11 hdf -> ide2/hdf/ lrwxrwxrwx 1 root root 8 2005-10-14 10:11 hdg -> ide3/hdg/ lrwxrwxrwx 1 root root 8 2005-10-14 10:11 hdh -> ide3/hdh/ dr-xr-xr-x 3 root root 0 2005-10-14 10:11 ide0/ dr-xr-xr-x 4 root root 0 2005-10-14 10:11 ide1/ dr-xr-xr-x 4 root root 0 2005-10-14 10:11 ide2/ dr-xr-xr-x 4 root root 0 2005-10-14 10:11 ide3/ -r--r--r-- 1 root root 0 2005-10-14 10:11 pdcnew -r--r--r-- 1 root root 0 2005-10-14 10:11 piix bicolor:/proc/ide # cat drivers ide-cdrom version 4.61 ide-floppy version 0.99.newide ide-disk version 1.18 bicolor:/proc/ide # cat piix Controller: 0 Intel PIIX4 Ultra 100 Chipset. --------------- Primary Channel ---------------- Secondary Channel ------------- enabled enabled --------------- drive0 --------- drive1 -------- drive0 ---------- drive1 ------ DMA enabled: yes no yes no UDMA enabled: yes no yes yes UDMA enabled: 5 X 2 2 UDMA DMA PIO> > >> Red Hat/Adaptec aacraid driver (1.1.2-lk2 Aug 4 2005) > >> 3ware Storage Controller device driver for Linux v1.26.02.000. > >> libata version 1.10 loaded. > >> Fusion MPT base driver 3.01.18 > >> Copyright (c) 1999-2004 LSI Logic Corporation > >> Fusion MPT SCSI Host driver 3.01.18 > > Hmm, these are drivers for other disk interface cards aren''t they? > Which of these, if any, are actually being used? > If we are using aacraid driver (hardware RAID) then we probably > don''t want to bother with the md (software RAID) drivers. > > >> md: raid0 personality registered as nr 2 > >> md: raid1 personality registered as nr 3 > >> md: raid5 personality registered as nr 4 > >> raid5: automatically using best checksumming function: pIII_sse > >> pIII_sse : 2697.200 MB/sec > >> raid5: using function: pIII_sse (2697.200 MB/sec) > >> md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27 > >> device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com > > You have the sofware raid5 module loaded, good. > > >> ReiserFS: hdc1: found reiserfs format "3.6" with standard journal > >> ReiserFS: hdc1: using ordered data mode > >> ReiserFS: hdc1: journal params: device hdc1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 > >> ReiserFS: hdc1: checking transaction log (hdc1) > >> ReiserFS: hdc1: Using r5 hash to sort names > >> VFS: Mounted root (reiserfs filesystem). > > so /dev/hdc1 is your root partition and it has been mounted correctly. > > >> Adding 1052248k swap on /dev/hda2. Priority:42 extents:1 > > And you have swap too, good. > > >> md: could not open unknown-block(33,1). > >> md: autostart failed! > >> md: Autodetecting RAID arrays. > >> md: autorun ... > >> md: ... autorun DONE. > > robbie@adler:~> ls -l /dev/hde1 > brw-rw---- 1 root disk 33, 1 2005-03-19 19:36 /dev/hde1 > robbie@adler:~> > > so block device 33,1 is /dev/hde1 > > I didn''t see /dev/hde appear in your dmesg, so we need > to try to get the dom0 kernel to find that device and > possibly others too. >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 10/14/05, Marcus Brown <marcusbrutus@internode.on.net> wrote:> Hi Fred, > > I''m not familiar with your hardware or distro, so hopefully I won''t > be adding to your problems! > > To me, these stand out: > > > md: hdXn has different UUID to hdYm > > I''d have a look at making sure you have a valid mdadm.conf, > then create a new initrd and see if things improve. > I assume that the major difference between the two kernels (apart > from one being xen-patched!) is that with the xen-patched one > you''ve had to create your own initrd. > AFAIK some mkinitrd methods need mdadm.conf so that mdadm > (and others) are loaded properly. > eg: > # cat /etc/mdadm/mdadm.conf > DEVICE partitions > ARRAY /dev/md0 level=raid0 num-devices=2 UUID=72c1f448:2d5f8521:431d286d:3de5be1d > devices=/dev/hda3,/dev/hdc3 > ARRAY /dev/md1 level=raid0 num-devices=2 UUID=f739cdb1:7cfb3f92:605674de:969a9c53 > devices=/dev/hda6,/dev/hdc6 > ARRAY /dev/md2 level=raid0 num-devices=2 UUID=0b81ec82:8cd3167c:8192ec98:f749babc > devices=/dev/hda7,/dev/hdc7 > # mdadm --examine /dev/hda3 | grep UUID > UUID : 72c1f448:2d5f8521:431d286d:3de5be1d > # mdadm --examine /dev/hdc3 | grep UUID > UUID : 72c1f448:2d5f8521:431d286d:3de5be1dI am using /etc/raidtab and the raidtools2, but I had noticed these warnings as well. Will investigate.> > > Also, to simplify things a little, you don''t need to put your > swap on a raid device, just give the two swap partitions the > same priority. This will actually be faster too. > eg: > # grep swap /etc/fstab > /dev/hda2 none swap sw,pri=1 0 0 > /dev/hdc2 none swap sw,pri=1 0 0But if one of your disk crash, the swap on the good remaining disk will not have the same info as the failed disk, right?> > > The other msg that seems out of place is this: > { DriveReady SeekComplete Error } > and unless something really is wrong perhaps check DMA settings in > your kernel config. > grep DMA /mnt/kernels/config-2.6.11.12-xen0 > CONFIG_GENERIC_ISA_DMA=y > CONFIG_BLK_DEV_IDEDMA_PCI=y > # CONFIG_BLK_DEV_IDEDMA_FORCED is not set > CONFIG_IDEDMA_PCI_AUTO=y > # CONFIG_IDEDMA_ONLYDISK is not set > CONFIG_BLK_DEV_IDEDMA=y > # CONFIG_IDEDMA_IVB is not set > CONFIG_IDEDMA_AUTO=y >To add more information on the hdd configuration I have, here is what ''raiddetect'' says: bicolor:/home/fblaise # raiddetect The following disks hang off a HPT IDE controller: The following disks hang off a PDC IDE controller: name: /sys/block/hde, /dev name: /dev/hde, major: 33, minor: 0, size: 234441648, attached to: 0000:06:05.0, controller: 2, vendorid: 0x105a, deviceid: 0x4d68, subsystem_vendorid: 0x105a, subsystem_deviceid: 0x4d68, controllertype: 2, hasraidmagic: 0 name: /sys/block/hdf, /dev name: /dev/hdf, major: 33, minor: 64, size: 234441648, attached to: 0000:06:05.0, controller: 2, vendorid: 0x105a, deviceid: 0x4d68, subsystem_vendorid: 0x105a, subsystem_deviceid: 0x4d68, controllertype: 2, hasraidmagic: 0 name: /sys/block/hdg, /dev name: /dev/hdg, major: 34, minor: 0, size: 234441648, attached to: 0000:06:05.0, controller: 2, vendorid: 0x105a, deviceid: 0x4d68, subsystem_vendorid: 0x105a, subsystem_deviceid: 0x4d68, controllertype: 2, hasraidmagic: 0 name: /sys/block/hdh, /dev name: /dev/hdh, major: 34, minor: 64, size: 234441648, attached to: 0000:06:05.0, controller: 2, vendorid: 0x105a, deviceid: 0x4d68, subsystem_vendorid: 0x105a, subsystem_deviceid: 0x4d68, controllertype: 2, hasraidmagic: 0 The following disks hang off a SIL IDE controller: The following disks are unclassified: name: /sys/block/hda, /dev name: /dev/hda, major: 3, minor: 0, size: 234441648, attached to: 0000:00:1f.1, controller: 1, vendorid: 0x8086, deviceid: 0x248b, subsystem_vendorid: 0x8086, subsystem_deviceid: 0x2480, controllertype: 0, hasraidmagic: 0 name: /sys/block/hdc, /dev name: /dev/hdc, major: 22, minor: 0, size: 234441648, attached to: 0000:00:1f.1, controller: 1, vendorid: 0x8086, deviceid: 0x248b, subsystem_vendorid: 0x8086, subsystem_deviceid: 0x2480, controllertype: 0, hasraidmagic: 0 name: /sys/block/hdd, /dev name: /dev/hdd, major: 22, minor: 64, size: 8388604, attached to: 0000:00:1f.1, controller: 1, vendorid: 0x8086, deviceid: 0x248b, subsystem_vendorid: 0x8086, subsystem_deviceid: 0x2480, controllertype: 0, hasraidmagic: 0 Thanks.> > Marcus.fred>_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello Fred, I have looked at your two dmesg outputs, from kernel-xen and kernel-smp. There are two things that struck me. from the kernel-smp dmesg: > PDC20268: IDE controller at PCI slot 0000:06:05.0 > PDC20268: chipset revision 2 > PDC20268: ROM enabled at 0xfe8f8000 > PDC20268: 100% native mode on irq 26 > ide2: BM-DMA at 0xc400-0xc407, BIOS settings: hde:pio, hdf:pio > ide3: BM-DMA at 0xc408-0xc40f, BIOS settings: hdg:pio, hdh:pio > hde: ST3120026A, ATA DISK drive > hdf: ST3120026A, ATA DISK drive > ide2 at 0xcc00-0xcc07,0xc882 on irq 26 > hdg: ST3120026A, ATA DISK drive > hdh: ST3120026A, ATA DISK drive This didn''t seem to be in the kernel-xen dmesg output. I wonder if you are missing the kernel module for the PDC20268 harware? Looking in /lib/modules/2.6.11.4-21.9-xen/kernel/drivers/ide/pci on my machine, I see two candidates, pdc202xx_new.ko and pdc202xx_old.ko I don''t know which one of those would work. Do you have either of these loaded (lsmod)? You might need to put one of these modules in your initrd maybe. The other thing that struck me was the interrupts. The kernel-smp seems to be using both ACPI and the IOAPIC hardware. The kernel-xen doesn''t seem to be doing that. Maybe the interrupt routing is broken in the kernel-xen case. I am only speculating and I would not know how to fix it in any case. Hope that helps. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Fred,
I''m not familiar with your hardware or distro, so hopefully I
won''t
be adding to your problems!
To me, these stand out:
md: hdXn has different UUID to hdYm
I''d have a look at making sure you have a valid mdadm.conf,
then create a new initrd and see if things improve.
I assume that the major difference between the two kernels (apart
from one being xen-patched!) is that with the xen-patched one
you''ve had to create your own initrd.
AFAIK some mkinitrd methods need mdadm.conf so that mdadm
(and others) are loaded properly.
eg:
# cat /etc/mdadm/mdadm.conf
DEVICE partitions
ARRAY /dev/md0 level=raid0 num-devices=2
UUID=72c1f448:2d5f8521:431d286d:3de5be1d
devices=/dev/hda3,/dev/hdc3
ARRAY /dev/md1 level=raid0 num-devices=2
UUID=f739cdb1:7cfb3f92:605674de:969a9c53
devices=/dev/hda6,/dev/hdc6
ARRAY /dev/md2 level=raid0 num-devices=2
UUID=0b81ec82:8cd3167c:8192ec98:f749babc
devices=/dev/hda7,/dev/hdc7
# mdadm --examine /dev/hda3 | grep UUID
UUID : 72c1f448:2d5f8521:431d286d:3de5be1d
# mdadm --examine /dev/hdc3 | grep UUID
UUID : 72c1f448:2d5f8521:431d286d:3de5be1d
Also, to simplify things a little, you don''t need to put your
swap on a raid device, just give the two swap partitions the
same priority. This will actually be faster too.
eg:
# grep swap /etc/fstab
/dev/hda2 none swap sw,pri=1 0
0
/dev/hdc2 none swap sw,pri=1 0
0
The other msg that seems out of place is this:
{ DriveReady SeekComplete Error }
and unless something really is wrong perhaps check DMA settings in
your kernel config.
grep DMA /mnt/kernels/config-2.6.11.12-xen0
CONFIG_GENERIC_ISA_DMA=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
Marcus.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On 10/14/05, Robbie Dinn <robbie@microbus.com> wrote:> Hello Fred, > I have looked at your two dmesg outputs, from kernel-xen and kernel-smp. > There are two things that struck me. > > from the kernel-smp dmesg: > > PDC20268: IDE controller at PCI slot 0000:06:05.0 > > PDC20268: chipset revision 2 > > PDC20268: ROM enabled at 0xfe8f8000 > > PDC20268: 100% native mode on irq 26 > > ide2: BM-DMA at 0xc400-0xc407, BIOS settings: hde:pio, hdf:pio > > ide3: BM-DMA at 0xc408-0xc40f, BIOS settings: hdg:pio, hdh:pio > > hde: ST3120026A, ATA DISK drive > > hdf: ST3120026A, ATA DISK drive > > ide2 at 0xcc00-0xcc07,0xc882 on irq 26 > > hdg: ST3120026A, ATA DISK drive > > hdh: ST3120026A, ATA DISK drive > > This didn''t seem to be in the kernel-xen dmesg output. > I wonder if you are missing the kernel module for the > PDC20268 harware?It wasn''t configured. I recompiled the kernel with the pdc202xx_new built-in. I am waiting for a chance to reboot the server and test. Both old and new are enabled in my sles9 kernel config file.> > Looking in /lib/modules/2.6.11.4-21.9-xen/kernel/drivers/ide/pci > on my machine, I see two candidates, pdc202xx_new.ko and pdc202xx_old.ko > I don''t know which one of those would work. Do you have either of these > loaded (lsmod)? You might need to put one of these modules in your > initrd maybe. > > The other thing that struck me was the interrupts. The kernel-smp > seems to be using both ACPI and the IOAPIC hardware. The kernel-xen > doesn''t seem to be doing that. Maybe the interrupt routing is broken > in the kernel-xen case. I am only speculating and I would not know > how to fix it in any case. > > Hope that helps.It does. Thanks.>fred _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 10/14/05, Fred Blaise <chapeaurouge@gmail.com> wrote:> On 10/14/05, Robbie Dinn <robbie@microbus.com> wrote: > > Hello Fred, > > I have looked at your two dmesg outputs, from kernel-xen and kernel-smp. > > There are two things that struck me. > > > > from the kernel-smp dmesg: > > > PDC20268: IDE controller at PCI slot 0000:06:05.0 > > > PDC20268: chipset revision 2 > > > PDC20268: ROM enabled at 0xfe8f8000 > > > PDC20268: 100% native mode on irq 26 > > > ide2: BM-DMA at 0xc400-0xc407, BIOS settings: hde:pio, hdf:pio > > > ide3: BM-DMA at 0xc408-0xc40f, BIOS settings: hdg:pio, hdh:pio > > > hde: ST3120026A, ATA DISK drive > > > hdf: ST3120026A, ATA DISK drive > > > ide2 at 0xcc00-0xcc07,0xc882 on irq 26 > > > hdg: ST3120026A, ATA DISK drive > > > hdh: ST3120026A, ATA DISK drive > > > > This didn''t seem to be in the kernel-xen dmesg output. > > I wonder if you are missing the kernel module for the > > PDC20268 harware? > It wasn''t configured. I recompiled the kernel with the pdc202xx_new > built-in. I am waiting for a chance to reboot the server and test. > Both old and new are enabled in my sles9 kernel config file.That did the trick :-D> > > > Looking in /lib/modules/2.6.11.4-21.9-xen/kernel/drivers/ide/pci > > on my machine, I see two candidates, pdc202xx_new.ko and pdc202xx_old.ko > > I don''t know which one of those would work. Do you have either of these > > loaded (lsmod)? You might need to put one of these modules in your > > initrd maybe. > > > > The other thing that struck me was the interrupts. The kernel-smp > > seems to be using both ACPI and the IOAPIC hardware. The kernel-xen > > doesn''t seem to be doing that. Maybe the interrupt routing is broken > > in the kernel-xen case. I am only speculating and I would not know > > how to fix it in any case. > > > > Hope that helps. > It does. Thanks. > >Thanks all for your help.> fredfred> >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users