Dell PERC H310 - Driver issue?

Hardware Support
,
1

Looking for assistance with possibly a driver issue?
Have a Dell PERC H310 RAID controller, had access to it when 17.1 was installed but lost access to it after some update and I finally had some time to test it.
Tested using boot usb, can connect to controller with Zorin 15, 16 and 17.1
-The boot usb Zorin 17.1r2 is using Megaraid_sas 07.725.01.00-rc1 and connects and I call see the contents of the array.
-The installed internal boot disk is using version 07.727.03.00-rc1 and won’t connect
How do I remove and install the older version? Is there a way to stop it from updating once it’s rolled back?

IMG_5831
IMG_58313067×481 922 KB

IMG_5854
IMG_58542489×441 555 KB

2

Hi and welcome. I couldn't find a solution on roll back unless you have Timeshift installed, but did find solution on how to prevent updates with Brave A.I. search engine via mojeek:

"To prevent updates from occurring, you can pin your packages to a specific version using apt . For example, you can use the apt-mark command to hold packages from being updated:

sudo apt-mark hold <package_name>

Replace <package_name> with the name of the package you want to prevent from updating. To unhold a package, you can use:

sudo apt-mark unhold <package_name>

For the MegaRAID driver, you would need to find the specific package name and pin it to the version you want to keep. However, this method does not prevent system-wide updates, only specific packages.

To manage the MegaRAID driver specifically, you can also download and install the specific version of the driver you need from the manufacturer's website or a trusted repository, ensuring it remains unchanged during system updates."

1 Like
3

I originally posted in hardware support about a driver issue with the PERC H310 raid controller having issues after update from 17.1r2 to 17.3, and now after an update last night when asked to restart, I can no longer see a boot screen or login screen. So I’m thinking this might be a larger issue with Zorin 17.3?
The system starts as normal and when it gets to where I should see the Zorin boot logo it’s just black, after a while the monitor goes to sleep. But what’s odd is when I move the mouse the monitor comes back on but still displays black.
I’m using the onboard display.
The other note is the fans don’t idle down now and are running at full.
I have no issues when I boot from usb thumb drive using “try Zorin” 16.3 or 17.1r2.
Is there a suggested way to see what the issues are and possibly fix them? Or at the least send the information to someone that may be able to fix this so others might not have the same issues?
I’m suspecting I’ll need to format and install 16.3. Rebuild and block updates. :frowning:

4

I already answered your question. When you reinstall be sure to install Timeshift together with the advice I gave here;

5

Hey, thanks for the information for the PERC driver issue and stopping its updates, but my other post was to do with a new issue where Zorin now will not boot after a recent update in the last 48 hours. I can appreciate the suggestion for installing “timeshift” as a future prevention, but was hoping to understand why now Zorin won’t boot and see if there was a conflict with zorin or maybe a firmware issue? I’d like to understand what issue is causing this now and hopefully help having a post for anyone that may have the same Dell Poweredge T320 and wants to use Zorin if this becomes a common problem.
I was able to test out a straight Ubuntu boot disk and it has no issue other then the latest Megaraid driver version not cooperating, but I was at least able to boot. But I’ll ignore that driver issue in this instance.
Is there a method to get a boot error report, or a “repair” method from usb? Or is it just a straight up, it toasted itself, restart?
I’m desperately trying to not go back to Microsoft

6

You could try it with this method. Use your USB boot stick with Zorin OS:

1 Like
7

You could also use the live media to search for logs giving clues as to what might be the issue. Fron Brave A.I. search engine via mojeek:

"Where to Find Crash Logs

To find crash logs in Ubuntu 22.04, you can check several locations:

  • /var/log/syslog and /var/log/kern.log: These files contain detailed information about system errors and crashes. You can use commands like journalctl -p err -b -1 to view logs from the previous boot, which can help identify errors or crash reports.
  • /var/crash/: This directory contains detailed crash reports generated by Apport, a crash reporting tool.
  • dmesg : Use the dmesg command to view kernel-related errors and messages.
  • journalctl : Use journalctl -b -1 -e to show the last logs of the previous boot, which can be useful for identifying the cause of a crash.

These logs can provide valuable information to help diagnose and resolve system crashes."

1 Like
8

Thanks for the information! It unfortunately didn’t work, gave a “error NVram is locked”.
But good news is I disabled the on board display and hooked up a graphics card and I was able to get logged in! :smiley:
So it appears right now that the recent update took out the onboard display as well. :frowning:
So I was now able to install Timeshift for issues moving forward, but will now have to learn how to downgrade the display and the megaraid drivers.
Any assistance with that would be greatly appreciated.
And maybe a suggestion as to what driver might be causing the fan to run at high speed? The fan would idle down after boot before the latest update.

9

Unfortunately, I can't help you with the graphics and raid drivers as I'm not familiar with them. You could only try to go back to the previous kernel if you have updated to a newer kernel version. You can set this when booting Zorin by clicking on "advanced options". Here you can select an older kernel. But it is no solution for your problem.