1830216 Members
1965 Online
109999 Solutions
New Discussion

Re: Kernel panic

 
MarkPrinsloo
Regular Visitor

Kernel panic

Good day,

I updated my HPE Proliant DL325 Gen 10 server firmware along with the raid controller and after the upgrade I get an error when tying to launch smart storage administrator (SSA).

[ 3.223887] Kernel panic - ot synching: VFS: Unable to mount root fs on unknown-block(0,0)

[ 3.224179] CPU: 0 PID: 1 Comm:swapper/0 Not tainted 5.3.18-57.3-default #1 SLE15-SP3 (unreleased)

[ 3.224524] Hardware name: HPE Proliant DL325 Gen10/Proliant DL325 Gen10, BIOS A41 11/13/2020

[ 3.224895] Call Trace:

[ 3.225002] dump_stack+0x66/0x8b

[ 3.225201] panic+0xfe/0x2d7

[ 3.225375] mount_block_root+0x277/0x2db

[ 3.225621] ? set_debug_rodata+0x11/0x11

[ 3.225804] prepare_namespace+0x130/0x166

[ 3.225986] kernel_init_freeable+0x23f/0x26b

[ 3.226183] ? rest_init+0xb0/0xb0

[ 3.226323] kernel_init+0xa/0x110

[ 3.226522] ret_from-fork+0x22/0x40

[ 3.226733] Kernel Offset: 0x2c00000 from 0xffffffff81000000 (relocationrange: 0xffffffff80000000-0xffffffffbffffffff)

[ 3.268936] ---[ end Kernel panic - not synching: VFS: unable to mount root fs on unknown-block(0,0) ]---

I reloaded the old firmware in hope resolve the issue but it did not help.

What can I try?

I cannot get into my SSA.

8 REPLIES 8
BPSingh
HPE Pro

Re: Kernel panic

Greetings!

Does the server operate properly if you refrain from trying to open ssacli?
Which controller model is currently installed?
Have you attempted to uninstall and reinstall ssacli?



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
MarkPrinsloo
Regular Visitor

Re: Kernel panic

Hi,

Yes, the server operates correctly it is only if I try to access the ssacli.

The Raid controller os a HPE Smart Array P816-a SR GEN 10

I have not tried to uninstall and re-install. I don't know how.

Regards,

BPSingh
HPE Pro

Re: Kernel panic

What is the OS version running on the server?

 


I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
MarkPrinsloo
Regular Visitor

Re: Kernel panic

Hi.

 

I am runnning Windows Server 2019 with Hyper-V

BPSingh
HPE Pro

Re: Kernel panic

Could you please re-confirm?

From the output shared above, it seems to be SLES15. 

For windows you can download from the below web-link:

https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-a1953c549aa145b2

 



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
support_s
System Recommended

Query: Kernel panic

Hello,

 

Let us know if you were able to resolve the issue.

 

If you have no further query, and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.

 

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

 

Thank you for being a HPE valuable community member.


Accept or Kudo

DrLloyd
Frequent Visitor

Re: Query: Kernel panic

I am getting the same issue on a ML350, but I am running VMware.  I get this screen when I try to run intelligent provisioning.  I have read that I may need to roll back an update but I am unsure what to roll back.

 

Mr_Techie
Trusted Contributor

Re: Query: Kernel panic


@DrLloyd wrote:

I am getting the same issue on a ML350, but I am running VMware.  I get this screen when I try to run intelligent provisioning.  I have read that I may need to roll back an update but I am unsure what to roll back.

 


Hi 

If you recently updated iLO firmware or system BIOS/UEFI, try rolling back to a previous version and see if that helps.