-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with P812 after having it workin #37
Comments
I have since upgraded my P812 to 6.64 firmware, same deal, I even re-patched to make sure and rebooted.
|
Same issue here on a P410i with kernel 6.2. I guess it's not a board issue but rather something related to the kernel. |
cat contrib/dkms/patch.sh |
@Iv I'm using this one: https://github.com/fermino/hpsahba/blob/master/contrib/dkms/patch.sh The behavior I have identified is the following: when starting up, the drives and cage appear masked. If I unload and load the dkms module again (with the flag, of course), the connected drives do show up (unmasked), but any further disconnect/connect of drives is not detected by the kernel. After that, trying to unload/load the kernel module again does not work (it gets stuck on load). |
@LV I was using the exact same one also |
I had my P812 controller working for like 2 weeks, no issues. I ran the directions here:
https://github.com/im-0/hpsahba/tree/master/contrib/dkms
I am running Ubuntu 22 on kernel v 5.15.0-83. After editing
patch.sh
it worked with my 5.15 kernel. I added the linehpsa hpsa_use_nvram_hba_flag=1
to my modprobe file so it keeps after reboot. I rebooted multiple times in 2 weeks time period of it working, kept working, drives were there, I could access them, it worked.Then one day all drives on that adapter just disappeared. I have rebooted, still won't come back. The controller see's them, they are just masked. HBA mode is enabled according to the tool:
But yet, they are not there. I checked
dmesg
and this is what it gave me:So it seems they are there, it sees them, they are masked. If I check
ssacli
it gives me this:So I swapped the drives out and rebooted, thinking maybe something happened to the drives. Still the same thing, won't show up. So then I re-ran
modprobe
to see if I could get them to re-show:Still don't show up and below is what
dmesg
shows me:I know the drives are good, if I plug them into another computer they work fine.
Like I said, this worked for 2 whole weeks, then just stopped one day 2 or 3 weeks ago and I have not been able to get them back up since then. Nothing has changed in the server since it worked, I haven't upgraded anything, kernel still the same version.
The text was updated successfully, but these errors were encountered: