M.2 ssd is not recognized

[krang]

Board + extra stuff is from innet. They replied quickly when I had a question about the Germany only weird U.LF adapter /w and w/o… And good prize, though.
SSD and case from Conrad, the only ones with a smaller kind of tested SSD. I really don’t need 250GB for network controller, maybe pfsense, pihole and openvpn.

[aaditya]

It looks to be similar problem reported here:

HP SSD EX900 M.2 250GB shown as 1GB only

Hi, a few days ago I got my first Rock Pi 4 Model A 2GB V1.4, together with a heat sink block and the M.2 Extend board v1.4. All works fine with booting the system from a 8GB µSD card, so I can use it. Today I got a HP SSD EX900 M.2 250GB, which is being recognized by the system as 1 GB only: # lsblk -o NAME,MODEL,SIZE,FSTYPE | grep nvme nvme0n1 SM2263 1024M Also parted and fdisk show 1GB only for that device. # parted /dev/nvme0n1 print Error: /dev/nvme0n1: unrecognised disk label Mode…

@krang and @Druid did you try the Radxa Debian image? The u-boot in that image is reported to work.

[krang]

Hey aaditya,

I don’t think, it is the same problem here. In my case it is absolutely not recognized. There is no /dev/nvme* entry, lspcie is empty, lsblk lists the sd as mmc* with the different partitions only.
And yes, I used the official Radxa images, both Ubuntu and Debian. Kernel Versions are 4.4, I think, for Armbian, I used 4.4 and 5.4 and for Manjaro 5.4 and 5.6. The latter says the also updated u-boot…

[aaditya]

Ok. For some users /dev/nvme* entries dont appear, as witnessed here:

M.2 NVMe Intel 1TB 660P Not reconized on Ubuntu Server

Here is a link to the item purchased: No /dev/nvme* device is created when booted. I tried directly connected to the board and also through the riser device. While looking at dmesg I see these errors: [ 3.875231] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout! [ 3.890425] rockchip-pcie: probe of f8000000.pcie failed with error -110 Any insight into why this m.2 nvme SSD wouldn’t be visible would be helpful. Thanks, digi

[krang]

This looks more familiar. Problem with the board?

[aaditya]

Cant say if its a problem with the board or with u-boot unable to set up the SSD while booting.
If I find anything relevant will post here.

[VKorenev]

[    2.178219] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!

I got this error with one of my nvme drives (Silicon Power 512GB p34a80) on the current Armbian buster with kernel 5.4. However it worked fine on the latest Manjaro.

[krang]

Hey @Druid
Where did you buy your Acer and it is working? I’m going to return the HP and try another one before thinking of returning the board (and probably go for something entirely different)…

[krang]

Which one is more likely to work and boot SPI/SSD only?

• Intel 760p Series SSD 128GB TLC PCIe NVMe 3.0 x4 - M.2 2280
• Gigabyte NVMe SSD 128 GB NVMe 1.3 M.2 2280

Maybe some comments before I order?

[jack]

@krang

The acer one is known working under u-boot:

https://shop.allnetchina.cn/products/acer-m-2-nvme-ssd-for-rock-pi-4?_pos=2&_sid=21fab7f62&_ss=r

[Druid]

@krang If you are from EU I bought it here.

[krang]

Thanks, the two of you!
And @Druid, can you please let me know if it works? So excited.

[Druid]

@krang Some delays with delivery. I only get it next week. I’ll let you know if Acer SSD works.

[PhoenixMage]

I have an intermitent issue with -110 on mainline 5.6.7, very strange. I have the HP EX900 above.

If I use the Rock Pi 4 Ubuntu 18.04 image then it works fine everytime.

[krang]

Funny, I didn’t get it to work with the same SSD and Ubuntu 18, amongst others.
Waiting for my Gigabyte SSD now, will order Acer if this fails as well…

[Druid]

Acer SSD is recognized. I was able to write image and boot from SSD only when SD is present. So it boots in a strange way.
Can anyone advise how to fix it (if it is possible).
In the logs I see

Scanning nvme 0:4…
Found /extlinux/extlinux.conf

But later I get

** Unable to read file /dtbs/4.4.154-59-rockchip-g5e70f14/rockchip/rk3399-rock-pi-4b.dtb **

Then it goes to sdcard and loads this

reading /dtbs/4.4.154-108-rockchip-ge9277b7e857a/rockchip/rk3399-rock-pi-4b.dtb

So it boots and when I check /boot directory I see that it is from SSD drive. And I don’t see rk3399-rock-pi-4b.dtb there I can only find rock-pi-4b.dtb.

[rua1]

/dtbs/4.4.154-59-rockchip-g5e70f14/rockchip/rk3399-rock-pi-4b.dtb

There was another name for the file with this kernel (rockpi-4b-linux.dtb) . The programmers in the latest version of Uboot set a different file name rk3399-rock-pi-4b.dtb and therefore new versions of Uboot do not work with old kernels from radxa. Therefore, you must either apply the old uboot, or copy boot 4.4.154-108 from microsd instead of 4.4.154-59 … or copy all rockpi-4b-linux.dtb to rk3399-rock-pi-4b.dtb.

[krang]

can confirm it works with the Gigabyte SSD as well, at least the OS recognizing it with correct size.
I’m currently on the write SPI step and will decide to try Armbian or Debian on the SSD. Let’s see

[rua1]

can confirm it works with the Gigabyte SSD as well

can’t confirm, I don’t have such a device
I reacted to the case when a new Uboot does not load old images.

To @radxa: the link from the official site still has an image of ubuntu without the correct dtb file names. Probably it was necessary to first lay out the correct images of the OS, and then already make changes to Uboot?

[Druid]

Thanks a lot. It helped. I renamed dts file and it helped. Then I wrote an old u-boot (from apt bionic main) but it still reads wrong file. I guess I need to rollback to really old version which I don’t want. I think I need to create a ticket somewhere for radxa team.