Hi,
Has anyone else encounter the following;
While testing the new CentOS 6.5 kernel-2.6.32-431.1.2.el6.x86_64 on a Dell PowerEdge 2950 in the lab it kernel panics on boot up, complaining about the scsi_wait_scan Module signed with unknown public key.
The Dell Poweredge 2950 is running the latest 2.7.0 BIOS and BMC Firmware v2.50 with PERC5/i integrated (running latest firmware 5.2.2-0072, A09)
Error reported;
FATAL: Error inserting scsi_wait_scan (/lib/modules/2.6.32-431-1.2.el6.x84_64/kernel/drivers/scsi/scsi_wait_scan.ko) Required Key not available Module signed with unknown public key
Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tainted 2.6.32-431.1.2.el6.x86_64 #1
regards Tim
Hi,
Yes, while building a new machine this morning.
There's a bug report for it; info on the cause of the problem there (missing signing key):
http://bugs.centos.org/view.php?id=6831
Thanks, Paul
--
On 12/13/2013 12:18 PM, MeasureMyEnergy - Tim D'Cruz wrote:
Hi,
Has anyone else encounter the following;
While testing the new CentOS 6.5 kernel-2.6.32-431.1.2.el6.x86_64 on a Dell PowerEdge 2950 in the lab it kernel panics on boot up, complaining about the scsi_wait_scan Module signed with unknown public key.
The Dell Poweredge 2950 is running the latest 2.7.0 BIOS and BMC Firmware v2.50 with PERC5/i integrated (running latest firmware 5.2.2-0072, A09)
Error reported;
FATAL: Error inserting scsi_wait_scan (/lib/modules/2.6.32-431-1.2.el6.x84_64/kernel/drivers/scsi/scsi_wait_scan.ko) Required Key not available Module signed with unknown public key
Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tainted 2.6.32-431.1.2.el6.x86_64 #1
regards Tim
On 12/13/2013 12:21 PM, Paul Jones wrote:
Hi,
Yes, while building a new machine this morning.
There's a bug report for it; info on the cause of the problem there (missing signing key):
Thanks for the reply Paul.
regards Tim
On 12/13/2013 12:18 PM, MeasureMyEnergy - Tim D'Cruz wrote:
Hi,
Has anyone else encounter the following;
While testing the new CentOS 6.5 kernel-2.6.32-431.1.2.el6.x86_64 on a Dell PowerEdge 2950 in the lab it kernel panics on boot up, complaining about the scsi_wait_scan Module signed with unknown public key.
The Dell Poweredge 2950 is running the latest 2.7.0 BIOS and BMC Firmware v2.50 with PERC5/i integrated (running latest firmware 5.2.2-0072, A09)
Error reported;
FATAL: Error inserting scsi_wait_scan (/lib/modules/2.6.32-431-1.2.el6.x84_64/kernel/drivers/scsi/scsi_wait_scan.ko) Required Key not available Module signed with unknown public key
Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tainted 2.6.32-431.1.2.el6.x86_64 #1
regards Tim
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 13/12/13 13:21, Paul Jones wrote:
Hi,
Yes, while building a new machine this morning.
There's a bug report for it; info on the cause of the problem there (missing signing key):
http://bugs.centos.org/view.php?id=6831
Thanks, Paul
Yes, and because Murphy's in the way and because it's Friday 13th too, we have a sync issues between our mirrors. The faulty kernel package was removed earlier from the master mirror, and metadata was regenerated, but it's taking some time to propagate on all mirrors :-( We're waiting for the mirror network to reflect the bad package removal and a newer kernel package will be pushed anytime soon [TM].
In the meantime, don't update your machine, or don't reboot to the new kernel (for people having already updated it)
- -- Fabian Arrotin gpg key: 56BEC54E | twitter: @arrfab
In the meantime, don't update your machine, or don't reboot to the new kernel (for people having already updated it)
And for those who did the update, booted and got the panic, what do you suggest short of a total re-install?
This kind of update failure doesn't enhance the reliability reputation for CentOS, unfortunately.
David Kurn (Centos fanatic)
I got the panic on one machine. I solved this by boot again and selected the previous kernel and the system came back up.
I think CentOS defaults to keep the last 5 kernels.
M Morén
----- Ursprungligt meddelande -----
In the meantime, don't update your machine, or don't reboot to the new kernel (for people having already updated it)
And for those who did the update, booted and got the panic, what do you suggest short of a total re-install?
This kind of update failure doesn't enhance the reliability reputation for CentOS, unfortunately.
David Kurn (Centos fanatic)
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 13/12/13 16:50, david wrote:
In the meantime, don't update your machine, or don't reboot to the new kernel (for people having already updated it)
And for those who did the update, booted and got the panic, what do you suggest short of a total re-install?
Reboot and select the previous kernel.
This kind of update failure doesn't enhance the reliability reputation for CentOS, unfortunately.
David Kurn (Centos fanatic)
-
david -
Fabian Arrotin -
Magnus Morén -
MeasureMyEnergy - Tim D'Cruz -
Ned Slider -
Paul Jones