I also had the Grub lines on rebooting my HP3140 appliances. It turned to be the CD that I used to burn the image was at fault. I burned the image to a better quality CD and reimaged my HP from that and it worked fine. No more grubs and the interfaces behaved properly.
Curt
Curt McDaniel
Network Security
--------------------------
Sent from my BlackBerry Wireless Handheld
----- Original Message -----
From: Cisco Clean Access Users and Administrators <[log in to unmask]>
To: [log in to unmask] <[log in to unmask]>
Sent: Fri Jun 15 06:29:00 2007
Subject: Re: Installing v4.1.1 iso image on Dell 1850 fails after install with kernel panic
Ah, the NIC cards are listed, but these machines are using the BCM5721,
not BMC5702/03/04. There is mention of 57xx but for 3.6(2) and below, we
are running 4.0.4.
03:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721
Gigabit Ethernet PCI Express (rev 11)
Subsystem: Dell: Unknown device 01e6
Flags: bus master, fast devsel, latency 0, IRQ 5
Memory at fe7f0000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Capabilities: [58] Message Signalled Interrupts: 64bit+
Queue=0/3 Enable-
Capabilities: [d0] Express Endpoint IRQ 0
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
I also see GRUB running after a reboot? Once that prompt pops up, it
takes several minutes for the system to boot, even if I press the "any
key" to continue. Once the machine is up and running everything is fine.
I tried to get Dell PE 850's but they were not available.
I have two (HA Mode) running the CAS software and DHCP. Bottom line is
Disable integrated NICS (on board controllers 1 and 2) BEFORE software
install
Note: These can be enabled AFTER software install
Console Redirect set to OFF
Redirection after reboot is disabled
And they will work. Could it be done better, sure, but I don't know
enough about Linux to do it.
:-)
-----Original Message-----
From: Cisco Clean Access Users and Administrators
[mailto:[log in to unmask]] On Behalf Of Jackie Cheng
(jaccheng)
Sent: Thursday, June 14, 2007 21:58
To: [log in to unmask]
Subject: Re: Installing v4.1.1 iso image on Dell 1850 fails after
install with kernel panic
We are still working on supporting Dell PE 860. It's not on the
supported hardware list yet. Please refer to
http://www.cisco.com/en/US/products/ps6128/products_device_support_table
09186a00807600e1.html
Thanks,
--Jackie
-----Original Message-----
From: Cisco Clean Access Users and Administrators
[mailto:[log in to unmask]] On Behalf Of Speight, Howard
Sent: Thursday, June 14, 2007 9:14 AM
To: [log in to unmask]
Subject: Re: Installing v4.1.1 iso image on Dell 1850 fails after
install with kernel panic
Had a similar problem with Dell PE 860 and 4.0.4. Bios was not set
correctly.
Disable integrated Broadcom NICS
Serial Port Off
Console Redirection Off
After Reboot Disabled
my fault it was in the install notes, except the Broadcom NICS. I was
able to use the integrated Broadcom NICS after the install, but had
manually configure eth2. I set it through the management interface, but
after a reboot the settings were lost. I've had that problem before with
an older release and different hardware.
I was receiving "Kernel Panic - not syncing, Attempted to kill init!"
Also ICH7 not 100% compatible, but it's working...
From the anaconda.log
13:19:05 DEBUG : ignoring driverless device Intel Corporation 82801G
(ICH7 Family) SMBus Controller
13:19:05 DEBUG : ignoring driverless device Intel Corporation
82801GB/GR (ICH7 Family) LPC Interface Bridge
13:19:05 DEBUG : ignoring driverless device Intel Corporation 82801
PCI Bridge
13:19:05 DEBUG : ignoring driverless device Intel Corporation
82801GR/GH/GHM (ICH7 Family) PCI Express Port 6
13:19:05 DEBUG : ignoring driverless device Intel Corporation
82801GR/GH/GHM (ICH7 Family) PCI Express Port 5
13:19:05 DEBUG : ignoring driverless device Intel Corporation 82801G
(ICH7 Family) PCI Express Port 1
13:19:05 DEBUG : ignoring driverless device Intel Corporation PCI
Express Root Port
13:19:05 DEBUG : ignoring driverless device Intel Corporation Server
Memory Controller Hub
13:19:05 DEBUG : ignoring driverless device ATI Technologies Inc
Unknown device 515e
13:19:05 DEBUG : ignoring driverless device Intel Corporation 82801G
(ICH7 Family) IDE Controller
From the anaconda.syslog
<6>ata1: SATA max UDMA/133 cmd 0xCC98 ctl 0xCC92 bmdma 0xCC60 irq 20
<6>ata2: SATA max UDMA/133 cmd 0xCC80 ctl 0xCC7A bmdma 0xCC68 irq 20
<7>ata1: dev 0 cfg 49:2f00 82:746b 83:7f61 84:4163 85:7469 86:3c41
87:4163 88:207f
<6>ata1: dev 0 ATA-7, max UDMA/133, 156250000 sectors: LBA48
<6>ata1: dev 0 configured for UDMA/133
<6>scsi0 : ata_piix
<4>ATA: abnormal status 0x7F on port 0xCC87
<3>ata2: disabling port
<6>scsi1 : ata_piix
<5> Vendor: ATA Model: WDC WD800AAJS-18 Rev: 01.0
<5> Type: Direct-Access ANSI SCSI revision: 05
<5>SCSI device sda: 156250000 512-byte hdwr sectors (80000 MB)
<5>sda: Write Protect is off
<7>sda: Mode Sense: 00 3a 00 00
<5>SCSI device sda: drive cache: write back <5>SCSI device sda:
156250000 512-byte hdwr sectors (80000 MB)
<5>sda: Write Protect is off
<7>sda: Mode Sense: 00 3a 00 00
<5>SCSI device sda: drive cache: write back <6> sda: sda1 sda2 sda3
<5>sd 0:0:0:0: Attached scsi disk sda
Weird as it seems install worked fine with integrated NICS enabled, but
would not boot. I tried this several times just to make sure I was
seeing what I was seeing... The PE 860 is not listed as being supported,
so I'll take what I can get...
I'm not Linux savy, which is 95 percent of my problem...
-----Original Message-----
From: Cisco Clean Access Users and Administrators
[mailto:[log in to unmask]] On Behalf Of Bill Davis
Sent: Tuesday, June 12, 2007 17:10
To: [log in to unmask]
Subject: Installing v4.1.1 iso image on Dell 1850 fails after install
with kernel panic
I have just tried to reinstall CCA v4.1.1 on a Dell 1850 server that had
= a disk crash using the ISO image downloaded from the Cisco web site.
The install goes OK until the system is rebooted, at which point it
fails wit= h a kernel panic.
I can install using the ISO for v 4.0.3 and upgrade up to v4.1.1.
NOTE: The ISO for v4.0.4 causes the same error as the ISO for v4.1.1.
Has anyone else had this problem or know a solution? If not, I will
star= t up a TAC case.
-Bill
Colorado State University
|
