 
	
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] Re: xen 2.0/3.0 pb with SW-RAID
 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: 
 .. 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.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@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. 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@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users 
 
 
 | 
|  | Lists.xenproject.org is hosted with RackSpace, monitoring our |