We couldn't find a replacement zero-channel SCSI RAID card (which would definitely work) to replace the Adaptec one, so we've decided to go with software RAID. So I deleted the RAID mirrors in the RAID card's setup utility, removed the old card, deleted everything Disk Druid tried to set up automatically so that I only had disks showing free space in Disk Druid, then set up software RAID and volume groups with logical volumes on top of it. Everything seems fine, but I get this when doing pvscan, vgscan, and lvscan, for example: # vgscan Reading all physical volumes. This may take a while... Found duplicate PV zyARq6fJKpfLSAGuF4zaHmlvvr6Kvv1E: using /dev/sdf not /dev/sdc Huge memory allocation (size 2028470292) rejected - metadata corruption? Out of memory. Requested 2028470292 bytes. Failed to read extents from /dev/sdf Found duplicate PV zyARq6fJKpfLSAGuF4zaHmlvvr6Kvv1E: using /dev/sdc not /dev/sdf Huge memory allocation (size 2028470292) rejected - metadata corruption? Out of memory. Requested 2028470292 bytes. Failed to read extents from /dev/sdc Found duplicate PV zyARq6fJKpfLSAGuF4zaHmlvvr6Kvv1E: using /dev/sdf not /dev/sdc Huge memory allocation (size 2028470292) rejected - metadata corruption? Out of memory. Requested 2028470292 bytes. Failed to read extents from /dev/sdf Found duplicate PV zyARq6fJKpfLSAGuF4zaHmlvvr6Kvv1E: using /dev/sdc not /dev/sdf Found duplicate PV zyARq6fJKpfLSAGuF4zaHmlvvr6Kvv1E: using /dev/sdf not /dev/sdc Huge memory allocation (size 2028470292) rejected - metadata corruption? Out of memory. Requested 2028470292 bytes. Failed to read extents from /dev/sdf Found duplicate PV zyARq6fJKpfLSAGuF4zaHmlvvr6Kvv1E: using /dev/sdc not /dev/sdf Huge memory allocation (size 2028470292) rejected - metadata corruption? Out of memory. Requested 2028470292 bytes. Failed to read extents from /dev/sdc Found duplicate PV zyARq6fJKpfLSAGuF4zaHmlvvr6Kvv1E: using /dev/sdf not /dev/sdc Huge memory allocation (size 2028470292) rejected - metadata corruption? Out of memory. Requested 2028470292 bytes. Failed to read extents from /dev/sdf Volume group "Volume02" not found Found volume group "VolGroup02" using metadata type lvm2 Found volume group "VolGroup01" using metadata type lvm2 Found volume group "VolGroup00" using metadata type lvm2 Anyone know why? Does the server somehow remember that from my previous installation? Can I fix it without having to reinstall the whole thing? I'm about to throw this server out the window or put Windows 98 on it!! :( Thanks. Johan -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Johan Booysen Sent: 24 October 2007 09:13 To: General Red Hat Linux discussion list Subject: RE: Adaptec SCSI RAID 2000S I don't think that recompiling the kernel will be an option over here either, for a number of reasons I don't think are worth going into. I've now also tried CentOS 5, but get exactly the same behaviour as with RHEL5. I did get a response from Red Hat support (after booting into rescue mode and generating an sosreport to send to them), which I'll try next: "It seems that anaconda fails to detect/install the second stage grub boot loader, In order to confirm this, could you please try the below method from grub> prompt, grub> root (hd0,0) -> Then hit Enter key grub> kernel /vmlinuz-2.6.18-8.el5 ro root=/dev/VolGroup00/root -> Then hit Enter key grub> initrd /initrd-2.6.18-8.el5.img -> Then hit Enter key grub> boot -> Then hit Enter key The above method would try to boot the system in to the default runlevel. Update us with your findings." Johan -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Geofrey Rainey Sent: 23 October 2007 21:35 To: General Red Hat Linux discussion list Subject: RE: Adaptec SCSI RAID 2000S Just a note, a kernel compilation sounds a lot scarier than it is. There are not too many steps involved and after you've done it once or twice, it's quite straight forward. Regards, Geoff. -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Johan Booysen Sent: Tuesday, 23 October 2007 8:50 p.m. To: General Red Hat Linux discussion list Subject: RE: Adaptec SCSI RAID 2000S My controller is an Adaptec SCSI RAID 2000S. I did try manually selecting the Aic79xx driver too, but that didn't work at all - was a bit of a desperate attempt, but hey... I've logged a support case with Red Hat, so will see if they can maybe help. Recompiling kernels...well, I'll have to look into that. That's way outside of my current knowledge/experience :) I see what you mean: It does appear as if the driver is present, but something is amiss somewhere. Thanks very much for your advice. Johan -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Geofrey Rainey Sent: 22 October 2007 22:08 To: General Red Hat Linux discussion list; sorin.srbu@xxxxxxxxxxxxx Subject: RE: Adaptec SCSI RAID 2000S Hello, I recently had a similar problem installing RHEL5.0 on a box with an Adaptec 7901x controller. To resolve I had to select "linux noprobe" during the install and explicitly select the required Drivers. In my case I needed the following drivers to get the kernel to recognize the scsi device: I2o_block Aic79xx (because my controller was a 7901x) And also the tg3 (network driver, but didn't work, see below) After this the kernel could see the scsi driver and enabled me to install onto the scsi device. However the same problem then emerged with the network driver and I couldn't seem to resolve This by explicitly specifying the tg3 driver during install, so I installed RHEL5 anyway minus network. To resolve this I downloaded the latest kernel source from kernel.org and recompiled it enabling both the Requisite drivers for the network card and the scsi device by compiling the drivers into the kernel Itself - as opposed to LKM's. So to summarise, the linux noprobe method allowed me to install the RHEL5 operating system onto The scsi device by explicitly selecting the requisite scsi drivers (but without network), and a kernel recompile of a generic kernel was necessary to get the network drivers to install as well as the scsi drivers. This was as interesting problem that despite logging a job with Redhat, the problem was unable to be Resolved using the Redhat kernel even though I also unpacked the initrd image and verified that All the drivers I needed were indeed contained in the image. Let me know how you get on, and if you need more help with anything above. Regards, Geofrey Rainey. -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Johan Booysen Sent: Monday, 22 October 2007 9:09 p.m. To: sorin.srbu@xxxxxxxxxxxxx; General Red Hat Linux discussion list Subject: RE: Adaptec SCSI RAID 2000S I don't think management over here will go for CentOS. Besides, if CentOS is the same as Red Hat, I assume that it too will not have the driver I need..? Thanks for the suggestion, though! Johan -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Sorin Srbu Sent: 22 October 2007 07:51 To: 'General Red Hat Linux discussion list' Subject: RE: Adaptec SCSI RAID 2000S Johan Booysen <> scribbled on Friday, October 19, 2007 6:28 PM: You should do fine with CentOS5 as a replacement for RHEL5. CentOS is binary compatible, a clone if you want, of RHEL. Only real difference (and the one I can care slightly about) is that CentOS has had all the RHEL-logos etc stripped and that it uses yum for updating instead of RHEL's up2date and the RHN. I use CentOS myself for trying out stuff before deploying to our RHEL3/4 machines. So far so good. I also like the fact that CentOS is supported as long as RHEL is. Redhat will support v5 until 2011?), and since CentOS is basically the same thing as RHEL, the same will be true for support and updates for CentOS. See this thread on the CentOS forums, it might help you decide: http://www.centos.org/modules/newbb/viewtopic.php?topic_id=3107&forum=35 . 8-) [off-track] I used Fedora before to try out stuff before, but thought the fast update-cycle was a bit too bleeding edge. I searched around a while and came across CentOS and haven't looked back since. [on-track] HTH. > Matt, > > Good question, and a very valid point. But anyway, this box is kind > of a test-lab Oracle server, and needs to be RHEL5 for that purpose. > I believe it will be pretty heavily used, so virtualizing it won't > happen > - I'll bet my last penny on that, and on the Springboks, by the way! > :) > > > I think the next thing to do is to perhaps flash the Adaptec adapter's > BIOS to a newer version, and then see if the driver will load...I'm > pretty certain that I've exhausted all other options for now. > > Will see what the boss says on Monday... > > Thanks very much for your reply. > > Johan > > -----Original Message----- > From: redhat-list-bounces@xxxxxxxxxx > [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Matt > Sent: 19 October 2007 17:18 > To: 'General Red Hat Linux discussion list' > Subject: RE: Adaptec SCSI RAID 2000S > > Perhaps this is not the answer you are looking for, but maybe you can > install another distro (Fedora or an older CENTOS) to get driver > support. > Also, could using a virtual server work? I am just wondering if you > can place something like CENT as the host OS then run VMWare and maybe > create a virtual machine with RHEL5? Perhaps this VM will not require > direct hardware support for the controller? You might be able to > virtualize part of your infrastructure as well and run a legacy OS > which supports your controller - then, include this box in the virtual > infrastructure. > > Maybe the real question is why is it that you need to run RHEL5 on a 4 > year old box? I am not saying there is a problem with it, but is it > essential that REHL5 is run on this one? > > Just some thoughts for you... > > -----Original Message----- > From: redhat-list-bounces@xxxxxxxxxx > [mailto:redhat-list-bounces@xxxxxxxxxx] > On Behalf Of Andrew Bacchi > Sent: Friday, October 19, 2007 11:41 AM > To: General Red Hat Linux discussion list > Subject: Re: Adaptec SCSI RAID 2000S > > I hope you've already solved this problem. Have you checked the > Adaptec web site for a Linux driver? If anyone has one, it would be the OEM. > > > Johan Booysen wrote: >> I urgently need advice on this: I need to install RHEL5 on a server >> that is probably about 4 years old. It contains an Adaptec SCSI RAID >> 2000S adapter, and there is no driver available that I can track down >> on short notice (and none included on the RHEL5 discs). Anaconda >> does not detect any disks on the server during installation. >> >> Anyone know what my best bet is to get around this, or where to find >> a driver that will work? >> >> Thanks very much. >> >> Johan > > -- > > veritatis simplex oratio est > -Seneca > > Andrew Bacchi > Systems Programmer > Rensselaer Polytechnic Institute > phone: 518.276.6415 fax: 518.276.2809 > > http://www.rpi.edu/~bacchi/ > > -- > > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list > > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.488 / Virus Database: 269.15.0/1077 - Release Date: > 10/18/2007 > 9:54 AM > > > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.5.488 / Virus Database: 269.15.0/1077 - Release Date: > 10/18/2007 > 9:54 AM > > > -- > > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list ========================================================== For more information on the Television New Zealand Group, visit us online at tvnz.co.nz ========================================================== CAUTION: This e-mail and any attachment(s) contain information that is intended to be read only by the named recipient(s). This information is not to be used or stored by any other person and/or organisation. -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list ========================================================== For more information on the Television New Zealand Group, visit us online at tvnz.co.nz ========================================================== CAUTION: This e-mail and any attachment(s) contain information that is intended to be read only by the named recipient(s). This information is not to be used or stored by any other person and/or organisation. -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
