Guide: use Intel Optane Memory H10 with Rock5B / pcie splitting

Is there anyone who could help?

Bumping this again. Please help me make the 16 GB optane module work. It would be ideal for keeping a Linux rootfs on.

For god sake, just buy 256gb ssd, like pm4a1.

不听不听,王八念经,所以这就是开源的魅力所在

Of course I considered this, but optane has advantages that normal SSDs don’t have, like incredibly low latency. Anyway, I don’t think I need to explain why I want to use something that should work out of the box.

Strange because I’m using a very similar drive (an 16GB optane memory) and it does works out of the box. :neutral_face:

You can see the neofetch of this post: Arch Linux ARM bootable using latest BSP

I literally booted from that drive with an OS that is not even officially supported, and that was 3 months ago.

I really don’t know what is the problem with yours that causing the nvme driver not recognizing it as a drive.

Mine has a model number of MEMPEK1J016GA, which has a label that appears to be a retail drive. (It’s the M10 optane drive). Yours appears to be an OEM drive. But there should not be much difference unless the OEM firmware is working weirdly.

1 Like

Thank you!! Can you share what lsblk and lspci shows for you?

I’m not with my board currently but the lspci is included in the screenshot in that post.

lsblk should not be too special and you should see an nvme drive in lsblk.

Could you check dmesg and see what happened?

Is your ssd broken/bricked?
Try ls /dev/nvme*
If it shows nvme0 without nvme0n1p1 it is probably broken.

1 Like

also try to check with the nvme command

I will try this at home, but from what I remember there isn’t anything that starts with nvme in /dev/. It would show up in lsblk too I suppose. But there is nothing there at all.

@gnattu have you ever tried your optane in a USB NVME enclosure? Does any system detect the drive when it’s in one?

In the meantime, I found this: https://community.intel.com/t5/Intel-Optane-Memory/problem-with-intel-optane-memory/m-p/606138/highlight/true#M2974 - can it be related?

Yes I did. I even flashed one image this way. If it is missing even with an enclosure, then probably your drive has some problem.

Yes, I checked and indeed it shows nvme0 but nothing else. But wouldn’t be the case as well if it was just not partitioned?
Output of dmesg|grep nvme:

[    9.118642] nvme nvme0: pci function 0000:01:00.0
[    9.118707] nvme 0000:01:00.0: enabling device (0000 -> 0002)
[    9.123662] nvme nvme0: could not set timestamp (16390)
[    9.123720] nvme nvme0: Could not set queue count (16390)
[    9.123728] nvme nvme0: IO queues not created

Output of dmesg|grep 0000:01:00

[    8.813923] pci 0000:01:00.0: [8086:2522] type 00 class 0x010802
[    8.813986] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
[    8.814061] pci 0000:01:00.0: reg 0x20: [mem 0x00000000-0x0000ffff 64bit]
[    8.814104] pci 0000:01:00.0: enabling Extended Tags
[    8.826516] pci 0000:01:00.0: BAR 4: assigned [mem 0xf0200000-0xf020ffff 64bit]
[    8.826570] pci 0000:01:00.0: BAR 0: assigned [mem 0xf0210000-0xf0213fff 64bit]
[    9.118642] nvme nvme0: pci function 0000:01:00.0
[    9.118707] nvme 0000:01:00.0: enabling device (0000 -> 0002)

You dont have namespace on it. Create it

I don’t know what a namespace is or how to create it.

Try nvme create-ns /dev/nvme0 with root.

Your ssd is very likely to be bricked.
Better check on a windows pc using the Intel MAS tool.

This resulted in:

FLBAS corresponding to block size 0 not found
Please correct block size, or specify FLBAS directly

Okay, try with nvme create-ns /dev/nvme0 --block-size 512 again. If even that does not work I probably don’t know what to do next.

Then please open google and read. Or just use pm9a1