Jump to content

  • Disks attached to Rocket 750 not recognized

    JasonM

    By JasonM

      • Urgent

    I initially installed RC4 in place of 6.6.6 to address an issue I was having with the LSIO NVIDIA plugin. However, the issue seems to be related to unRAID itself. When I install the NVIDIA unRAID 6.6.6 build, disks connected to my Rocket 750 PCIe SATA controller are not recognized. This can be replicated even with no GPU installed, so the GPU isn’t the problem. If I revert back to vanilla unRAID 6.6.6, the disks come back. Even with a GPU installed, booting under vanilla, all drives come up. BIOS settings look good as far as I can tell and I've gone as far as to backup and nuke my USB to start from scratch. Same result.

     

    On recommendation from the NVIDIA support forum, I upgraded to RC4 (vanilla, not NVIDIA version,) but had the same issue. I nuked the USB again and installed RC3 with the USB Creator. It hung for a very long time while booting, so I dusted off a display, keyboard and mouse to see what was going on. The messages it hags on are all related to the 750. Once boot completes, it also take forever for emhttp to start. Between the two hangups, we're talking 5+ minutes to boot. The drives attached to the 750 did not show up. I upgraded in the unRAID web UI from RC3 to RC4 with the same result.

     

    I nuked the USB again, installed 6.6.6 via the USB Creator, booted normally with all drives recognized. Upgraded directly to RC4 from the web UI, and got the same result as above.

     

    None of these were the NVIDIA builds, and none of them had any config files carried over. They were all clean. So it seems the 750 is just not cooperating with 6.7 at the moment. I reverted to 6.6.6 and all is back to normal.

     

    I'm tagging this as urgent since the Rocket 750 is used in the 45Drives Storinator and user impact may be significant. If this is improper, mods please advise.

    Go to reports Prereleases

    User Feedback

    Recommended Comments

    JorgeB

    Please post the diagnostics: Tools -> Diagnostics, though the problem is likely the same as the already reported Marvell issue with v6.7:

     

     

    Edited by johnnie.black
    Link to comment
    JorgeB
    2 minutes ago, JasonM said:

    Shall I also reinstall 6.7 and post those diags as well?

    Diags from v6.7, when there's a problem, would be the ones needed.

    Link to comment
    JasonM

    After reading the other thread, I disabled Vt-d and achieved normal boot with all drives. I'll continue to monitor for updates. In the meantime, guess it's time to think about getting an LSI card.

    Link to comment
    dgreig

    I hope it doesn’t come down to getting a new HBA. Any word from limetech on this. Is it a kernel issue? Why would 6.6.6 work flawlessly and 6.7 not?

    Link to comment
    JorgeB
    29 minutes ago, dgreig said:

    Is it a kernel issue? Why would 6.6.6 work flawlessly and 6.7 not?

    It's a kernel issue, and it's not the first time with Marvell controllers.

    Link to comment
    dgreig

    Thanks for letting me know. Does that mean we need to wait for a fix upstream or will limetech go back to a previous kernel?

     

     

    Link to comment
    JorgeB
    6 hours ago, dgreig said:

    we need to wait for a fix upstream

    Likely this, though it might take a while, since this issues aren't new.

    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...