URGENT: Cannot boot after proxmox 3.4 upgrade to latest kernel

Paolo_Bernardoni

Renowned Member
Dec 27, 2013
13
0
66
Hi, today i've upgraded one of my cluster node (supermicro) from 2.6.32-41 to 2.6.32-47 kernel version.
This upgrade is needed to later upgrade to 4.x proxmox version, is'nt it ?

During reboot i get the following screen error.
kernel_accraid_error.gif

modinfo of aacraid with old working kernel 2.6.32-41-pve

root@proxmox13:/proc# modinfo aacraid
filename: /lib/modules/2.6.32-41-pve/kernel/drivers/scsi/aacraid/aacraid.ko
version: 1.2-1[40700]custom
license: GPL
description: Dell PERC2, 2/Si, 3/Si, 3/Di, Adaptec Advanced Raid Products, HP NetRAID-4M, IBM ServeRAID & ICP SCSI driver
author: Red Hat Inc and Adaptec
srcversion: 5F7A62278EA634057A3F177
alias: pci:v00009005d0000028Fsv*sd*bc*sc*i*
alias: pci:v00009005d0000028Dsv*sd*bc*sc*i*
alias: pci:v00009005d0000028Csv*sd*bc*sc*i*
alias: pci:v00009005d0000028Bsv*sd*bc*sc*i*
alias: pci:v00009005d00000288sv*sd*bc*sc*i*
alias: pci:v00009005d00000286sv*sd*bc*sc*i*
alias: pci:v00009005d00000285sv*sd*bc*sc*i*
alias: pci:v00009005d00000285sv000017AAsd*bc*sc*i*
alias: pci:v00009005d00000285sv00001028sd*bc*sc*i*
alias: pci:v00001011d00000046sv0000103Csd000010C2bc*sc*i*
alias: pci:v00001011d00000046sv00009005sd00001364bc*sc*i*
alias: pci:v00001011d00000046sv00009005sd00000364bc*sc*i*
alias: pci:v00001011d00000046sv00009005sd00000365bc*sc*i*
alias: pci:v00009005d00000285sv00001028sd00000287bc*sc*i*
alias: pci:v00009005d00000286sv00009005sd000002A2bc*sc*i*
alias: pci:v00009005d00000285sv00009005sd0000029Abc*sc*i*
alias: pci:v00009005d00000285sv00009005sd00000299bc*sc*i*
alias: pci:v00009005d00000285sv00009005sd00000298bc*sc*i*
alias: pci:v00009005d00000286sv00001014sd00009540bc*sc*i*
alias: pci:v00009005d00000286sv00001014sd00009580bc*sc*i*
alias: pci:v00009005d00000285sv00001014sd00000312bc*sc*i*
alias: pci:v00009005d00000285sv00001014sd000002F2bc*sc*i*
alias: pci:v00009005d00000285sv00009005sd00000297bc*sc*i*
alias: pci:v00009005d00000285sv00009005sd00000296bc*sc*i*
alias: pci:v00009005d00000285sv0000103Csd00003227bc*sc*i*
alias: pci:v00009005d00000285sv00009005sd00000294bc*sc*i*
alias: pci:v00009005d00000285sv00009005sd00000293bc*sc*i*
alias: pci:v00009005d00000285sv00009005sd00000292bc*sc*i*
alias: pci:v00009005d00000285sv00001028sd00000291bc*sc*i*
alias: pci:v00009005d00000285sv00009005sd00000290bc*sc*i*
alias: pci:v00009005d00000285sv00009005sd0000028Fbc*sc*i*
alias: pci:v00009005d00000285sv00009005sd0000028Ebc*sc*i*
alias: pci:v00009005d00000286sv00009005sd00000800bc*sc*i*
alias: pci:v00009005d00000200sv00009005sd00000200bc*sc*i*
alias: pci:v00009005d00000287sv00009005sd00000800bc*sc*i*
alias: pci:v00009005d00000286sv00009005sd000002A6bc*sc*i*
alias: pci:v00009005d00000285sv00009005sd000002A5bc*sc*i*
alias: pci:v00009005d00000285sv00009005sd000002A4bc*sc*i*
alias: pci:v00009005d00000286sv00009005sd000002A3bc*sc*i*
alias: pci:v00009005d00000286sv00009005sd000002A1bc*sc*i*
alias: pci:v00009005d00000286sv00009005sd000002A0bc*sc*i*
alias: pci:v00009005d00000286sv00009005sd0000029Fbc*sc*i*
alias: pci:v00009005d00000286sv00009005sd0000029Ebc*sc*i*
alias: pci:v00009005d00000286sv00009005sd0000029Dbc*sc*i*
alias: pci:v00009005d00000286sv00009005sd0000029Cbc*sc*i*
alias: pci:v00009005d00000286sv00009005sd0000029Bbc*sc*i*
alias: pci:v00009005d00000286sv00009005sd0000028Dbc*sc*i*
alias: pci:v00009005d00000286sv00009005sd0000028Cbc*sc*i*
alias: pci:v00009005d00000285sv00009005sd0000028Bbc*sc*i*
alias: pci:v00009005d00000285sv00009005sd0000028Abc*sc*i*
alias: pci:v00009005d00000285sv00009005sd00000289bc*sc*i*
alias: pci:v00009005d00000285sv00009005sd00000288bc*sc*i*
alias: pci:v00009005d00000285sv000017AAsd00000287bc*sc*i*
alias: pci:v00009005d00000285sv000017AAsd00000286bc*sc*i*
alias: pci:v00009005d00000285sv00009005sd00000287bc*sc*i*
alias: pci:v00009005d00000285sv00009005sd00000285bc*sc*i*
alias: pci:v00009005d00000285sv00009005sd00000286bc*sc*i*
alias: pci:v00009005d00000284sv00009005sd00000284bc*sc*i*
alias: pci:v00009005d00000283sv00009005sd00000283bc*sc*i*
alias: pci:v00001028d0000000Asv00001028sd00000121bc*sc*i*
alias: pci:v00001028d0000000Asv00001028sd0000011Bbc*sc*i*
alias: pci:v00001028d0000000Asv00001028sd00000106bc*sc*i*
alias: pci:v00001028d00000002sv00001028sd000000D9bc*sc*i*
alias: pci:v00001028d00000002sv00001028sd000000D1bc*sc*i*
alias: pci:v00001028d00000004sv00001028sd000000D0bc*sc*i*
alias: pci:v00001028d00000003sv00001028sd00000003bc*sc*i*
alias: pci:v00001028d00000002sv00001028sd00000002bc*sc*i*
alias: pci:v00001028d00000001sv00001028sd00000001bc*sc*i*
depends:
vermagic: 2.6.32-41-pve SMP mod_unload modversions
parm: firmware_debug:Enable Firmware print debugging.
0=off (default)
1=print to adapter diagnostic
2=print to syslog
3=adapter diagnostic to syslog (unsupported) (int)
parm: nondasd:Control scanning of hba for nondasd devices. 0=off, 1=on (int)
parm: cache:Disable Queue Flush commands:
bit 0 - Disable FUA in WRITE SCSI commands
bit 1 - Disable SYNCHRONIZE_CACHE SCSI command
bit 2 - Disable only if Battery is protecting Cache (int)
parm: dacmode:Control whether dma addressing is using 64 bit DAC. 0=off, 1=on (int)
parm: aac_sync_mode:Force sync. transfer mode 0=off, 1=on (int)
parm: aac_convert_sgl:Convert non-conformable s/g list 0=off, 1=on (int)
parm: commit:Control whether a COMMIT_CONFIG is issued to the adapter for foreign arrays.
This is typically needed in systems that do not have a BIOS. 0=off, 1=on (int)
parm: msi:IRQ handling. 0=PIC(default), 1=MSI, 2=MSI-X(unsupported, uses MSI) (int)
parm: startup_timeout:The duration of time in seconds to wait for adapter to have it's kernel up and
running. This is typically adjusted for large systems that do not have a BIOS. (int)
parm: aif_timeout:The duration of time in seconds to wait for applications to pick up AIFs before
deregistering them. This is typically adjusted for heavily burdened systems. (int)
parm: coalescethreshold:Control the maximum block size of sequential requests that are fed back to the scsi_merge layer for coalescing. 0=off, 16 block (8KB) default. (int)
parm: numacb:Request a limit to the number of adapter control blocks (FIB) allocated. Valid values are 512 and down. Default is to use suggestion from Firmware. (int)
parm: aac_remove_devnodes:Remove device nodes(/dev/sd* and /dev/sg*) permanently when the device goes to offline state. 0=off, 1=on(Default). (int)
parm: acbsize:Request a specific adapter control block (FIB) size. Valid values are 512, 2048, 4096 and 8192. Default is to use suggestion from Firmware. (int)
parm: update_interval:Interval in seconds between time sync updates issued to adapter. (int)
parm: check_interval:Interval in seconds between adapter health checks. (int)
parm: check_reset:If adapter fails health check, reset the adapter. a value of -1 forces the reset to adapters programmed to ignore it. (int)
parm: expose_physicals:Expose physical components of the arrays. -1=protect 0=off, 1=on (int)
parm: expose_hidden_space:Expose hidden space of the Array. -1=protect 0=off, 1=on (int)
parm: reset_devices:Force an adapter reset at initialization. (int)
parm: wwn:Select a WWN type for the arrays:
0 - Disable
1 - Array Meta Data Signature (default)
2 - Adapter Serial Number (int)
root@proxmox13:/proc#


Any help ?

Thank you in advance.
Paolo
 
Just use any older kernel for now from the grub menu when booting.
The latest kernel is not needed when updating to latest PVE.

I do not think so. I you do not use the latest kernel, you are not protected with latest security patches, even you use latest PVE.

If you use any kernel below 2.6.32-180 you are vulnerable to Dirty Cow.
 
No, is not needed to upgrade to 4.x proxmox version.
But i've installed my server from 4.3 proxmox cdrom, the controller run ok, the new kernel recognize it.
i've prefered to re-create a new cluster then migrate VM.
Paolo
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!