similar to: passthrough PCI SCSI device

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

Hi! I am trying to export a PCI device (an AVM Fritzcard PCI ISDN card...) to a domU but when starting my domU I am getting this error: "pciback pci-4-0: 22 Couldn''t locate PCI device (0000:00:06.0)! perhaps already in-use?" My system is running both debian etch in dom0 and domU... Below you can find (hopefully) all important information... Sincerely, Gaubatz Patrick

Hello all, I have a problem with Xen and FibreChannel. The Dom0 can''t export a Disk on a FibreChannel SAN-Box to the DomU''s. In the DomU configuration I try: disk = [ ''phy:/dev/sdb1,/dev/sda1,w'' ] or disk = [ ''file:/mnt/sambashare.img,sda1,w'' ] sambashare.img is a 512MB great Diskimage on a Partition on the FC-SAN-Box, the Dom0 mount this

Hello I do have problem using Linux with an external HP tape drive. The server platform is also an HP Server; the server is an HP ML350 G4, and the Tape drive is a HP Storage Works Ultrium 448 - 1U Rack-mountable. HP Ultrium documentation says two drivers should be automatically up, sym53c8xx for LSI SCSI interface "st" for tape and /proc/scsi/scsi should contain information about

I am currently testing an Overland Tape storage unit with a LTO-3 drive on CentOS 4.4. After a random amount of time but usually when we have backed up about 0.5-1TB we get scsi errors which cause the backup to fail. I have rebuilt the box with Solaris 10 x86 and Windoze to prove the hardware and have successfully backed up over 3TB on each OS without error. Can anyone offer advice on how to find

So yesterday I got was able to get a domU successfully using a PCI SCSI card. This morning I restarted the host server. When I try to start up the same domU I get this error: Error: pci: improper device assignment specified: pci: 0000:0e:04.0 must be co-assigned to the same guest with 0000:0e:04.0, but it is not owned by pciback. How do I make this card owned by pciback on reboot. Do I need to

I have a CentOS 5 machine in which I'm trying to remove lvm. I dd'ed the file system to another partition, then dd'ed it back overwriting the lvm partition. I then modified menu.lst and fstab and replaced the paths to point to the correct device. When the system boots it's still looking for lvm. I can restore the system back to where it was with lvm, but I'm not sure what

Hi all, I have a problem during the lauching of my first virtual image. First thing : domain 0 is on fedora core 6 (probably a xen package made in fedora :-S, sorry ...) Second thing : the error is really traditional (i already had it with uml) but there i am blocking. here my config file (for image on logical volume, swap too) root = "/dev/sda1 ro" [root@p-virtvip8 xen]# cat p-virtser9

Hi List, Any ideas what is wrong with controller? It is running latest 5.x series of centos and driver spills out following warnings at random times: mptbase: ioc0: WARNING - IOC is in FAULT state (1600h)!!! mptbase: ioc0: WARNING - Issuing HardReset from mpt_fault_reset_work!! mptbase: ioc0: Initiating recovery mptbase: ioc0: WARNING - IOC is in FAULT state!!! mptbase: ioc0: WARNING -

I've got a fully updated Fedora Core 4 server crashing hard every week or two. I use Samba via smbmount and autofs to read & delete log files on 17 XP boxs and 6 NT4SP6 boxes as well as a couple other Windows files servers every 5 minutes. The first indication of a problem I get is smbmount stops working, then the server becomes unresponsive to the point where only a power slam will fix

Hi, all! I want to change current RHEL 4.0 ES into CentOS 4.2 on Sun X4100 server. The server has SAS SCSI based two 2.5" hard disks. I could only install RHEL 4.0 Update 1 because the server is equipped with RHEL 4.0 Update 1's device driver only. I've included below the boot process messages concerned with SCSI controller. If it's possible for me to install CentOS 4.0 on my

I''m tracking performance on the machine I installed yesterday. mutt running on one Xen instance, accessing via imap to another instance, accessing via nfs the maildir in another instances, seems little laggy when moving up and down the message index list. Network latency seems low < 30ms on average. So I was tracking vmstat. On the mutt instances is seems reasonable: [nic@shell:~]

NOTE: this is happening on Centos 6 x86_64, 2.6.32-504.3.3.el6.x86_64 not Centos 5 Dell PowerEdge 2970, Seagate SATA drive, non-raid. I have this server which has been dying randomly, with no logs. I had a tail -f over ssh for a week, when this just happened. Feb 8 00:10:21 thirteen-230 kernel: mptscsih: ioc0: attempting task abort! (sc=ffff880057a0a080) Feb 8 00:10:21 thirteen-230 kernel:

Hi, I''m running OpenSuse 12.2 with kernel 3.5.3 HBA= LSI 1068e using the MPTSAS driver (patched) (https://patchwork.kernel.org/patch/1379181/) SANOS1:/media # uname -a Linux SANOS1 3.5.3 #3 SMP Sun Sep 2 18:44:37 CEST 2012 x86_64 x86_64 x86_64 GNU/Linux I''ve tried to simulate a disk replacement but it seems that now /dev/sdg is stuck in the btrfs pool (RAID10) SANOS1:/media #

All, I am running xen3.0.2 and xen unstable on RHEL 4, and get this error when trying to boot Xen kernel(domain0) ...... Creating root device Mounting root filesystem mount: error 6 mounting ext3 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempting to kill init! Then system reboot.In grub.conf,I have

All, I am running xen3.0.2 and xen unstable on RHEL 4, and get this error when trying to boot Xen kernel(domain0) ...... Creating root device Mounting root filesystem mount: error 6 mounting ext3 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempting to kill init! Then system reboot.In grub.conf,I have

> -----Original Message----- > From: Jason Pyeron > Sent: Sunday, February 08, 2015 0:00 > > > -----Original Message----- > > From: Jason Pyeron > > Sent: Saturday, February 07, 2015 22:54 > > > > NOTE: this is happening on Centos 6 x86_64, > > 2.6.32-504.3.3.el6.x86_64 not Centos 5 > > > > Dell PowerEdge 2970, Seagate SATA drive,

I've got an i386 server running centos 4.2 with 3 3ware controllers in it -- an 8006-2 for the system disks and 2 7500-8s. On the 7500s, I'm running an all software RAID50. This morning I came in to find the system hung. Turns out a disk went overnight on one of the 7500s, and rather than a graceful failover I got this: Jan 6 01:03:58 $SERVER kernel: 3w-xxxx: scsi2: Command

Hi , I am ruuning Senmail with MailScanner on CentOS 4.4. It has updated to kernel 2.6.9-42.0.8.EL from its past kernel 2.6.9-42.0.3.EL. Now the Server can not boot up and gives the below error. mkrootdev: label / not found Mounting root filesystem mount: error 2 mouting ext3 switchroot: mount failed: 22 Kernel panic - not syncing: Attempted to kill init! But I can boot up from its

Hi, I just came across this box [0] (McKay Creek). Seems to be exceptional building material for ZFS based NAS/iSCSI unit. I especially liked the two extra system disks hidden inside the box ! Any one have an experience with these ? [0] http://www.intel.com/design/servers/storage/ssr212mc2 -- Regards, Cyril