[6.3.3] mtip32xx Drives Don't Show

9 posts in this topic Last Reply

Recommended Posts

Description: The module for the Micron RealSSD P420m loads, but presents the drives as rssda, rssdb, etc

How to reproduce: Boot machine with a Micron RealSSD inserted and UnRAID 6.3.3.

Expected results: The drive should show up as a drive usable as a cache drive or other drive device.

Actual results: The drive isn't visible in the list.

Other information:



Link to post
  • 2 weeks later...

tried again with 6.3.3, the mtip32xx driver exists, however its unable to detect the drive correctly


I have loaded Microns RealSSD Manager (RSSDM)  which gives the below:


root@Tower:~# rssdm -L

DiscoverDrives operation failed
CMD_STATUS   : Unable to find any P320/P420 drives connected

Copyright (C) 2014 Micron Technology, Inc.


lspci -v

02:00.0 Mass storage controller: Micron Technology Inc RealSSD P320h (rev 03)
        Subsystem: Micron Technology Inc RealSSD P320h
        Flags: bus master, fast devsel, latency 0, IRQ 28
        Memory at f7c07000 (32-bit, non-prefetchable)
        Memory at f7c06000 (32-bit, non-prefetchable)
        I/O ports at e000
        Memory at f7c04000 (32-bit, non-prefetchable)
        Expansion ROM at f7c00000 [disabled]
        Capabilities: [40] Express Endpoint, MSI 00
        Capabilities: [c0] Power Management version 3
        Capabilities: [d0] MSI: Enable+ Count=1/8 Maskable+ 64bit+
        Capabilities: [100] Advanced Error Reporting
        Kernel driver in use: mtip32xx
        Kernel modules: mtip32xx



Edited by miniwalks
Link to post

For someone with this controller, please attach some drives and then post the output of these two commands:


v /sys/dev/block
v /dev/disk/by-id

Then, for one of the devices, please post output of:

smartctl -A /dev/rssda  [or use whichever rssdX device you have]


Link to post
  • 3 weeks later...
  • 3 weeks later...

Bad new is there is no udev support for this device type, meaning unRaid can't easily get the device model/serial number in order to assign it.  Also looks like the device is not supported by smartctl, though it's possible one of the -d options (device type) might work.  The smartctl issue you could live with.  The udev issue is a showstopper.

Link to post
  • 2 weeks later...
  • 3 years later...

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.

Reply to this topic...

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