I'm not aware of this being an issue for just updating the driver. I've updated mine at least 3-4 times in the few years I've had them in two different MacPros, and always just updated the driver with no issues at all. Of course, it's always a good plan to be sure you have a backup, so hopefully you do.....
Thanks. I do have backups, I was more just trying to save myself some time and avoid doing the wrong thing first (one of my talents!) So in that spirit, instead of waiting for a response from their support, I did some more reading in the threads here and saw someone else claiming Highpoint told him to remove the controllers before uninstalling and installing the new drivers (for Big Sur IIRC.)
*I reasoned all of this may have something to do with the change from 10.15 > 11 being more dramatic than 11 > 12 or 13.
I followed the procedure as stated by Highpoint in the video
NVMe Driver update from macOS10.15 to macOS 11.x and later and physically removed the controllers from the machine before disabling secure boot and SIP and uninstalling the old driver (1.1.25) through the terminal command line using the command
Code:
sudo rm -rf /Library/Extensions/HighPoint*
. I then verified the drivers were removed successfully by examining the extensions plane in System Report. I then installed the new driver (1.1.30) and after restart verified that it was showing in the extensions plane in System Report. I proceeded to install the webGUI. I then shut down the machine and physically re-installed the controllers.
Upon rebooting they still did not appear. Checking the diagnostic pane of the RAID Management WebGUI, bizarrely, it still displays the driver version as "1.1.25". Also curiously, when I attempted to shutdown, I had an issue where the system restarted on its own and described in an error message that it had encountered an error (see below).
Code:
panic(cpu 0 caller Oxffffff8015fe761c): PowerOff timed out in phase 'Notifying priority clients'. Total 30000 ms:
proc_shutdown: 10001 ms vs unmountall: 13625 ms vis unmountall: 1678 ms
Blocked on priority client: 55836 ms @ Ox<ptr>, com.highpoint-tech.kext. HighPointNVMe (1. 1. 25) (F4DC71BD-AEA1-3EFA-B59F-0970A4C995AD @0x<ptr>->0xsptr
@IOPMrootDomain. cpp:5868
Panicked task Oxffffff9ba2da38b8: 358 threads: pid 0: kernel_task
Backtrace
(CPU 0) ,
thread: Oxffffff9ba3f44598, Frame: Return Address
Oxffffffad31687af0
Oxffffff80158705fd
Oxffffffad31687b40
Oxffffff80159c4b84
Oxffffffad31687b80 : 0xffffff80159b4619
•Ox 16+5£F8015819951
Oxffffffad31687c99
Oxffffff80158708dd
oxtritttad31687Ct6
Ox†tit+18615861187
охтттттта05108/050
Oxffffffad31687e40
Oxffffff8015fe761c
Oxffffffad3168770
Oxffffff8015f37a3d
Oxtritttad31687ea6
Oxtitit†86158c6C68
Oxffffffad31687 e00
Oxffffff80158c7cb8
Oxffffffad31687fa0
: Oxffffff801581019e
Frocess name corresponding co current thread (Oxffffff9ba3f44598): kernel_task
Mac Os version:
Kernel version:
Darwin Kernel Version 22.4.0: Mon Mar 6 21:00:17 PST 2023; root:xnu-8796.101.5~3/RELEASE_X86_64
Kernel
CF2A42DA-3F7C-30C6-9433-6F2076FF1F94
roots installed: B
KernelCache slide: 0x0000000015400000
kerne ccache Dases exffffff8015600000
KELTELES lide:
0x00000000154dc000
Kernel text base:
Oxffffff80156dc008
text base: Oxffffff8015500000
System
mode name
MacPro7, 1 (Mac-27AD2F918AE68F61
System shutdown begun: YES
Hibernation exit count:
I replied to the the autogenerated reply from Highpoint to add the above context but if anyone here has any insight, it would be much appreciated!