M.2 SSD "Crucial MX500 1TB CT1000MX500SSD4" not detected


tikey
 Share

3 3

Recommended Posts

I got the Helios64 and was running it from an external SD card so far since when I first installed it, the other options where not available, yet. I'm running openmediavault 5.5 (Armbian 20.11.6 Buster with Linux 5.9.14-rockchip64). Now, I wanted to move the system to a SSD and installed a "Crucial MX500 1TB CT1000MX500SSD4" according to https://wiki.kobol.io/helios64/m2/ Unfortunately, the SSD is not detected by the system, see output of dmesg below. For ata1, it only shows SATA link down.

 

Is there anything I can do to figure out what the problem is? Or is there any reason why this particular SSD would not work?

 

~$ dmesg | grep ata
[    0.000000] Memory: 3740032K/4061184K available (14464K kernel code, 2094K rwdata, 5980K rodata, 4224K init, 573K bss, 190080K reserved, 131072K cma-reserved)
[    0.016073] CPU features: detected: ARM errata 1165522, 1319367, or 1530923
[    1.394468] libata version 3.00 loaded.
[    3.019011] dwmmc_rockchip fe320000.mmc: DW MMC controller at irq 28,32 bit host data width,256 deep fifo
[    3.315946] ata1: SATA max UDMA/133 abar m8192@0xfa010000 port 0xfa010100 irq 240
[    3.315955] ata2: SATA max UDMA/133 abar m8192@0xfa010000 port 0xfa010180 irq 241
[    3.315964] ata3: SATA max UDMA/133 abar m8192@0xfa010000 port 0xfa010200 irq 242
[    3.315972] ata4: SATA max UDMA/133 abar m8192@0xfa010000 port 0xfa010280 irq 243
[    3.315979] ata5: SATA max UDMA/133 abar m8192@0xfa010000 port 0xfa010300 irq 244
[    3.628407] ata1: SATA link down (SStatus 0 SControl 300)
[   13.625910] ata2: softreset failed (1st FIS failed)
[   14.101801] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   14.121464] ata2.00: ATA-10: ST4000VN008-2DR166, SC60, max UDMA/133
[   14.121475] ata2.00: 7814037168 sectors, multi 0: LBA48 NCQ (depth 32), AA
[   14.123003] ata2.00: configured for UDMA/133
[   14.601788] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   14.615989] ata3.00: ATA-10: ST4000VN008-2DR166, SC60, max UDMA/133
[   14.616001] ata3.00: 7814037168 sectors, multi 0: LBA48 NCQ (depth 32), AA
[   14.617535] ata3.00: configured for UDMA/133
[   15.093805] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   15.113279] ata4.00: ATA-10: ST4000VN008-2DR166, SC60, max UDMA/133
[   15.113290] ata4.00: 7814037168 sectors, multi 0: LBA48 NCQ (depth 32), AA
[   15.114802] ata4.00: configured for UDMA/133
[   15.428239] ata5: SATA link down (SStatus 0 SControl 300)
[   17.307715] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null)
[   21.469500] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl

 

Link to post
Share on other sites

Armbian is a community driven open source project. Do you like to contribute your code?

Hi @tikey,

Did you make sure the SSD is making proper contact to the backplane connector? I also have some issues with the utmost left disk slot, when I remove/replace a disk in that slot, I have to open up the box and make sure that the connectors are tight and snug. If that does not help, you can try to insert the disk in another slot to rule out any connector or power rail issues. When box is open, make sure to also press down on the connectors in the main board, to make sure this is not related to loose cables or such.

Just FYI, I run a CT120BX500SSD1 in my box, although not the same model, but it works :-)

Groetjes,

Link to post
Share on other sites

Thanks for your answers and sorry for the late reply - unfortunately, I can only write 1 post/day in this forum so I can't even answer to your comments and questions.

So the SSD I'm using is a M2 which means that I couldn't just put it in another slot. But after @djurnys comment, I checked everything again and it turns out that I had the SSD the wrong way around. I didn't even think it would fit 2 ways but physically it does, it just doesn't work. I was first trying with a PCI SSD which is out of spec for the helios so I thought I overlooked some other compatibility issue. So thanks for your help and sorry about the noise. (But I can now confirm that the Crucial MX500 1TB is indeed working nicely also in the M2 version.

Link to post
Share on other sites

  • gprovost changed the title to M.2 SSD "Crucial MX500 1TB CT1000MX500SSD4" not detected
 Share

3 3