Jump to content

  • Power-on or device reset occurred on SAS drive with LSI HBA (unraid 6.12.10 and 6.12.11)

    Holaf

    By Holaf

      • Minor

    When there is a high activity on the server (eg parity check/rebuild) I get a lot of those errors :
      

    Jul 22 13:16:26 hlf-data3 kernel: mpt2sas_cm1: log_info(0x31120100): originator(PL), code(0x12), sub_code(0x0100)
Jul 22 13:16:26 hlf-data3 kernel: mpt2sas_cm1: log_info(0x31120100): originator(PL), code(0x12), sub_code(0x0100)
Jul 22 13:16:26 hlf-data3 kernel: sd 10:0:1:0: device_block, handle(0x000a)
Jul 22 13:16:28 hlf-data3 kernel: sd 10:0:1:0: device_unblock and setting to running, handle(0x000a)
Jul 22 13:16:28 hlf-data3 kernel: sd 10:0:1:0: Power-on or device reset occurred

     

    sometimes it is preceded by read errors : 

    Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241360
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241368
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241376
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241384
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241392
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241400
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241408
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241416
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241424
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241432
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241440
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241448
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241456
Jul 22 13:06:31 hlf-data3 kernel: sd 10:0:1:0: device_unblock and setting to running, handle(0x000a)
Jul 22 13:06:31 hlf-data3 kernel: sd 10:0:1:0: Power-on or device reset occurred

     

    I checked drives, cables, and SAS cards. It doesn't looks like it's hardware related.

    after searching on the net I found that someone had the same behavior on debian12 and it was related to the mpt3sas driver version 43.100.00.00 :

     

    It's the exact same version unraid uses (even on the v7 beta).

    Is there a way to have a kernel with a different version to see it if resolves the issue ? (at least 47.00.00.00)

    thanks 😊

    hlf-data3-diagnostics-20240722-1335.zip

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    JorgeB 
    Power-on or device reset occurred

     

    These are usually a power/connection problem, if it was a driver issue I would expect hundreds of reports, since these HBAs are probably the most used with Unraid, I have several myself.

    Link to comment
    Holaf

    As I said I already checked HHD, cables and HBA.
    I don't believe it's a power issue or else I would have more erratic behavior and the errors would certainly jump from disk to disk and not have a tendency to accumulate on the same one until the next reboot.

    And even if it's usually a power/connection problem that doesn't mean it is always the case.
    I allready spend a hundred euros on unnecessary hardware I will certainly not spend more 200 more to buy a new power supply since I believe it's not needed.

    having a test version version should'nt be that hard to produce 🤷‍♂️(unfortunately I can't do it myself), and it will be a quick way to test if it solves the problem (by testing with a recent driver and then going back to the 43.100.00.00)

    And if it is really a bug it's certainly better to fix it when it affects a very few people and not the whole wommunity :) (and before the release of the v7)
     

    Link to comment
    JorgeB
    1 hour ago, Holaf said:

    having a test version version should'nt be that hard to produce

    I cannot reproduce, and don't remember seeing any other similar reports, really doubt that the driver is the issue, but if you think that is really the problem, re-test once Unraid includes a new driver, Unraid always uses the in-tree driver, that means the driver that comes with the Linux kernel, once it's updated in the kernel, it will also be used by the next Unraid release with that or a newer kernel.

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.

    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.

×
×
  • Create New...