Re: [Xen-users] Re: xen 2.0/3.0 pb with SW-RAID

[Fred Blaise <chapeaurouge@xxxxxxxxx>]

On 10/13/05, Robbie Dinn <robbie@xxxxxxxxxxxx> 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@xxxxxxxxxx
>
> 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

Attachment: sles9_dmesg.txt
Description: Text document

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