similar to: USB Drive is detected and but the device "/dev/sda1" is not initialized

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, 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'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

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 am getting the following error on boot on a new install Centos 51: #/bin/sh ro no such file or directory then a kernel panic I have traced it to the call ''switchroot'' in the init script in the initrd. the exact same build without zen has no problems. the boot messages look like: Attaching to iSCSI storage iscsistart: transport class version 2.0-724. iscsid version 2.0-865

Hi people, I installed a via SATA controller in a CentOS release 3.8 (Final) - I needed additional disk space. After the first boot, the kudzu service, added the following line to /etc/modules.conf: alias scsi_hostadapter sata_via and I rebooted. After reboot in dmesg one can see: scsi0 : sata_via scsi1 : sata_via Vendor: ATA Model: SAMSUNG HD080HJ Rev: WT10 Type: Direct-Access

I managed to install RHEL3 onto a 1GB USB key. I had to forgo using grub to get it to but, but am now using extlinux. It actually boots, but ends up panicking. Here's the console messages that should be of interest: usb.c: registered new driver hub Loading ehci-hcd.o module ehci-hcd 00:1d.7: Intel Corp. 82801EB USB2 ehci-hcd 00:1d.7: irq 23, pci mem f882b000 usb.c: new USB bus

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

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:

-----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 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

> > Well, i''m using here the qla2340 on several boxes. It works > > with Xen 2.0 but noch with Xen 3.0. as part of SUSE Linux 10.0: > > Interesting. If the driver really doews work flawlessly in > Xen 2, then I think the culprit has to be interrupt routeing. > > Under Xen 3, does /proc/interrupts show you''re receiving interrupts? I cannot boot with

> > Well, i''m using here the qla2340 on several boxes. It works > > with Xen 2.0 but noch with Xen 3.0. as part of SUSE Linux 10.0: > > Interesting. If the driver really doews work flawlessly in > Xen 2, then I think the culprit has to be interrupt routeing. > > Under Xen 3, does /proc/interrupts show you''re receiving interrupts? I cannot boot with

I''ve been attempting to update my dom0 kernel by using the 2.6.27 git tree from the xenclient repo and also to 2.6.30 using opensuse patches rebased by Andrew Lyon. In both cases there''s a problem with the 3ware 3w_9xxx driver incorrectly detecting the LUNs on the device or some other issue, which ultimately prevents partition table detection. In my testing I applied the

Dear list, I have inherited a CentOS-5 box with a LSI Sata Raid controller. It is configured as a RAID5 w/hot-standby. My concern is that I have no present means of determining the RAID status w/o downing the system and going into the bios to get status. If a disk has failed and brought the standby disk online, I would like to know about it, the day it happens by seeing it in syslog or getting

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 just tried this with CentOS 5.3 as well, and got exactly the same symptoms and dmesg output. (As a point of comparison, Ubunu 8.04 on my work laptop is able to access the drive.) Obviously "not detected" is a misapprehension, though I'm puzzled why "lsusb" doesn't show it. The device is there even though the partition table can't be read. ---------- Forwarded

hdwr HPQ DC7700S ix86 Core Duo I have just updated this CentOS-5.3 box to 5.4. This process was not satisfactory. While the update packages all downloaded without problem the update process itself stalled at several points. By stalled I mean that at some point the entire process stopped for hours. The packages at which it stalled included evince, evolution, totem and vinfo. There may have

I really hope someone has a clue on this one.... :) I've got a 2.2TB array mounted on a 3ware 9500 controller. I installed it last week ensuring that LBA was enabled and using gpt with parted to get the full size available on one array. I also think I chose reiserfs for the array. We then moved ALOT of data to the array. Problem now is that after a reboot LBA doesn't seem to be in