similar to: AW: Re: xen 3.0 boot problem

I''ve compiled the 3.0-devel version on SUSE Linux 9.3. The ony problem is the qla2300 driver, which will not start all correctly on boot. So i cannot see other partitions than sda. --------------------------------------------------------------------------------- QLogic Fibre Channel HBA Driver ACPI: PCI Interrupt 0000:04:02.0[A] -> GSI 24 (level, low) -> IRQ 185 qla2300

I wanted to post this in case there is a real bug here. The system this is on is running Debian Etch with the Xen packages from Debian Unstable (currently 3.0.2+hg9697-1). I am running all packaged software so this is probably slightly out of date. This is on an HP DL320 G4 with a Pentium D 930 processor. I tried unloading and reloading the qla2xxx module, but rmmod reported it in use, however

> I wanted to post this in case there is a real bug here. > > The system this is on is running Debian Etch with the Xen packages from > Debian Unstable (currently 3.0.2+hg9697-1). I am running all packaged > software so this is probably slightly out of date. It would be interesting to see if this can be repro''ed on a tree built from a recent xen-unstable.hg.

I''ve compiled xen without any problems. but now i have to create an initrd file. When i use the command mkinitrd (without any options) the i''ve got some errors: # mkinitrd Root device: /dev/sda3 (mounted on / as reiserfs) Module list: ata_piix mptbase mptscsih qla2300 reiserfs Kernel image: /boot/vmlinuz-2.6.11.12-xen0 Initrd image: /boot/initrd-2.6.11.12-xen0 Shared

This is a really long email...my apologies. Hardware platform: Dell Poweredge 1855 (blade), Dual Xeon 2.8 GHz; 12 MB RAM; PERC 4/IM; mirrored 73 GB U320 SCSI; qLogic 2312 PCI Fibre Channel HBAs. OS: (currently) CentOS 4.3, gcc 3.4.5 Software: Xen 3.0.2-2 Attempting to boot off local SCSI RAID (mirror)...not the SAN. I am more of a Solaris person, so forgive me if I don''t know all

I may have asked about this before, but I can't find any records of so doing in my saved mail (which includes almost everything I ever read or write): All of a sudden, I am not getting flash drives automatically mounted in CentOS 5.3 with GNOME - they are recognized by the hardware, but there seems to be a (new?) problem with the maps. Here's the tail end of dmesg: usb 1-10: new high

I apologize in advance as this is not really at CentOS specific issue, but I don't know where else to turn. We are configuring some Dell 1850s for a customer, and they have all been configured with a QLogic dual channel HBA. But no storage has been (or will be in the near future) attached to these HBAs. During the boot process (both for the kickstart and after the OS has been

I''m trying to get Xen 3.0.2 working on an IBM Bladecenter with a qlogic 2300 fiber channel device and booting on a SAN. I have compiled several version of the xen kernel and I''m unable to have an initrd with the qla2300 or qla2xxx discovering any drive. I have tried several options when compiling xen. But the result is always the same: the initrd loads the driver but each

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

Hello, I have a weird problem after adding new PV do LMV volume group. It seems the error comes out only during boot time. Please read the story. I have couple of 1U machines. They all have two, four or more Fujitsu-Siemens SAS 2,5" disks, which are bounded in Raid1 pairs with Linux mdadm. First pair of disks has always two arrays (md0, md1). Small md0 is used for booting and the rest - md1

I just installed CentOS 5 on a computer. On boot, I get the a error message, related to 2 SATA disks. These errors did NOT appear on version 4.4 with the EXACT same hardware. Could someone please tell me what these error are and if there is some known way to prevent them? My configuration: - 2 Hitachi SATA 120 GB Harddisks - Intel P4 3GHz - Tyan Tomcat i875p motherboard - 1 GB ECC RAM - 2

Hello, I have a Promise EX 12-port RAID controller in my box, connected to 8 750GB disks. I have set up 2 RAID-5 devices and joined these using LVM. This is working fine. However, there is something that seems wrong.. (4-1) * 750 = 2250, but df reports the LVM volume as a mere 4.0T; /dev/mapper/storage_volume-stor 4.0T 3.6T 507G 88% /storage Shouldn't this be 4.5TB? Relevant bit of

I just installed CentOS 5 on a computer. On boot, I get the a error message, related to 2 SATA disks. These errors did NOT appear on version 4.4 with the EXACT same hardware. Despite the error messages, the disks seem to be working with no problems. Could someone please tell me what these error are and if there is some known way to prevent them? I searched the Net for these errors and they seem

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This seems to be an old problem, but I haven't found much about it. SuSE mentions "hwprobe=-pci" but, as far as I know, CentOS doesn't use it. This does stop the machine from booting (mounting /) quite a few times. Logs: SCSI subsystem initialized sym0: <895> rev 0x2 at pci 0000:00:13.0 irq 177 sym0: Symbios NVRAM, ID 7,

I've been having an extremely hard time using the on board SATA controller on my nvidia based board. I have two 160gig Maxtor SATA drives attached to the on board controller, setup as software raid0. The problem is the array is extremely unreliable, where I'm getting constant I/O errors like: sd 0:0:0:0: SCSI error: return code = 0x00040000 end_request: I/O error, dev sda, sector

So I'm working with the iSCSI Initiator and an EqualLogic SAN. I'm not sure when this might have happened, but it appears that the /dev/sdc device is missing, yet the /dev/sdc1 partition exists AND is mountable. Is there a method to re-create the /dev/sdc device? I cannot dd or fdisk it, obviously, but I can mount the /dev/sdc1 partition and it works just fine. Not having the /dev/sdc

Fresh install of CentOS 4.4. uname -a, lspci, & lsusb output at bottom. I insert my 256MB USB key, light goes on, then off. Never mounts. Here's the end of dmesg: usb 1-1: new full speed USB device using address 11 scsi7 : SCSI emulation for USB Mass Storage devices Vendor: Generic Model: STORAGE DEVICE Rev: 1.02 Type: Direct-Access ANSI SCSI revision:

Hello List, I'm hoping someone else out there has an Asus DSBF-DE server board, and can tell me if anything special needs to be done to get ports 5 and 6 of the onboard SATA to work under Centos 5.1 x64. I have drives on 1 through 4 that are detected and working properly, however, a drive on 5 is not detected, from what i can tell, the kernel doesn't even see phy's for ports 5 and 6.

Dear All, I have using CentOS 4.4 and My PC USB Drive is detected and but the device "/dev/sda1" is not initialized and i have executed the dmesg command and I am getting the following messages usb 1-6: new high speed USB device using address 2 SCSI subsystem initialized Initializing USB Mass Storage driver... scsi0 : SCSI emulation for USB Mass Storage

I have a perc5i (and perc5e) raid controller in my poweredge 2970 running centos 5.5. The RAID controller config is set for write-back policy, which I can confirm by checking in OpenManage. I also called Dell and ran their reporting application and had them double check to make sure everything looks OK hardware wise and they confirm that it does Yet when CentOS boots is appears to use the