Working well for me, after installing the PCIE cable the wrong way round initially. Using an "SkHynix 256GB PCIe NVMe 2242 SSD (HFM256GD3HX015N) (OEM)" off Amazon. lspci says "0000:01:00.0 Non-Volatile memory controller: SK hynix Gold P31/PC711 NVMe Solid State Drive"
How do i activate the additional GPIO power supply in addition to FPC power supply that should be supported? I read that this could be the problem for some SSDs to not work properly.
Hi,X1003 does not have a 5V IN interface. If your board does not boot/recognize from SSD, please refer to the instructions in X1003#FAQ to troubleshoot the problem. Most non-recognition problems can be solved.
Any additional confirmed success with 2242 SSDs?
Is there a list?
Sadly also a lot of SSDs in the comments I can't order in my country. Like the Samsung or Micron
Looks like my KingSpec NXM-2242 256GB M.2 NVMe SSD is not working properly. (waiting for answer of support if there is a solution)
I tried with integral m2 NVMe gen3 x4 2230 and it does not work, but I do not know why. When the x1003 has the m2 connected no led is turned on. Only after I connect the PSU it blink a led from the m2 (not the x1003). If I disconnect the m2 and connect the PSU I can see 2 blue leds of the board. Then what is happening here? no led from the board means no power? I can't get the m2 recognized in the rpi5. Is the board fault? is the ssd? I need help with this.
Hi,Please refer here to test it X1003#FAQ and troubleshoot the problem. make sure the FPC cable is firmly and fully inserted into the PI 5, FPC cable direction is correct. Please be sure to upgrade to the latest version of firmware. If the problem is still not solved, please try to replace the FFC cable and test it.
I followed all the guides and there is no way to get it recognized by my rpi. Also the FPC is correctly connected. How is supposed that the FPC can be broken? and for me does not make sense to buy a new FPC
If it is a pre-update cable (yellow color), there may be a problem of not recognizing it. Please contact us by email [support@geekworm.com] and we will provide you with a new FPC cable.
Samsung PM991 does now work. You should update that in your page. I have a PM991 running right now. Key is you need to run rpi-eeprom-update -a and if you're running ubuntu you need to flash a sd drive with raspberry pi os and do the rpi-eeprom-update because ubuntu has not pushed the latest eeprom files. Once you do that you will be able to copy your ubuntu os or whatever you want. Works great.
You people are interesting GeekWorms. It would add .05 to 10 cents to add the ability to put the small nvme screw into eithe the 2242 or 2230 holes on the x 1003 device. Why not place the glued in washer in both holes. Just a thought since these tiny washers are hard to locate.
Hi,You can check the SSD controller through lspci, Not compatible with Phison controller. If the SSD is not recognized, please follow these steps to troubleshoot the problemNVMe SSD boot with the Raspberry Pi 5#FAQ
Hi,You can run "lspci" command to check the controller brand of the SSD, Not compatible with Phison controller. If the SSD is not recognized, please follow these steps to troubleshoot the problem NVMe SSD boot with the Raspberry Pi 5#FAQ Or contact us at email: support@geekworm.com
Using a solidigm P41 plus 2230 1TB drive. Typing this comment with it as the boot drive on my Raspberry Pi 5. Followed directions on the wiki here. Had to reboot twice before it worked. Very fast.
Got my X1003 working with my rpi5 using a "with a 512GB Inland TN436 NVMe M.2 Gen 4x4 SSD", and cloned the boot microSD to it using my Gerling's rpi-clone script.
The RPI5 doesn't want to boot from the NVMe even tho the 6 was added to the boot order line in the eeprom and the PCIE_PROBE=1 is in ther.
RETURNED the KINGSPEC nvme. It was making it so that the X1003 had NO LIGHTS illuminated.
Replaced it with a 512GB Inland TN436 NVMe M.2 Gen 4x4 SSD from amazon [WORKS even tho it has Phison E19 controller]. It arrived today, i put it in the X1003 and i had lights. I added the 6 to the end of the boot order in the eeprom. Device showed up. I ran the rpi-clone script (geerling's from his git). It went through all the glorious cloning motions.
Now i'm just working on getting the rpi5 to boot from it.
lspci
0000:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2712 (rev 21)
0000:01:00.0 Non-Volatile memory controller: Phison Electronics Corporation PS5019-E19 PCIe4 NVMe Controller (DRAM-less) (rev 01)
0001:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries
NOTICE the Phison controller WORKING with this NVMe! E19
Yo he probado con un KingSpec M.2 NVMe 512 GB 2242 y reconoce la unidad, las luces permanecen encendidas, copia la SD al SSD sin problemas, pero luego no arranca desde el PCIe.
Transcend MTE400S 1 TB NVMe PCIe Gen3 x4 M.2 2242 (TS1TMTE400S) seems not to be compatible. First installation tests succsessfully. Image copy worked, but lot of error messages while booting. Raspi freezes after boot.
Booting with an usb nvme-adapter was successfull. No errors.
Hi, I confirm that Transcend PCIe SSD Gen3 x4 with MTE400S controller (I have with the 256Gb version), didnt't work.
First of all, you have to push dtparam=pciex1_gen=3 in the config.txt configuration file. All other value (as dtparam=pciex1 or dtparam=pciex1_gen=2) can works, but with a very slow boot, a very slow login, and all commands are also very slow (it can takes several minutes !).
In second hand, if you can boot and play with your RPi5, I always experienced an I/O error with this SSD after 5', 1 hour, or 3 hours. It depends (of what ?) but at the end, the only way is to reboot your RPi5 to start again.
Also for me, this behavior is not acceptable with a system which is supposed to run 24/7....
Hello,@Anonymous user #17 ;please refer to NVMe SSD boot with the Raspberry Pi 5#FAQ and Try the following test it:
1/Run the lspci andlsblk command to check the NVMe SSD is recognized.
2/Add PCIE_PROBE=1 to the eeprom, (Run sudo rpi-eeprom-config --edit command, then add this line, then press CTRL+O to write change to file, press CTRL+X to exit, then reboot)
3/Update the bootloader firmware to the last verson, refer to How to update eeprom firmware, this is very important!!!And finally be sure to run the command vcgencmd bootloader_version to check if your upgrade was successful!
nvme0n1 showed up in my lsblk, but with a size of 1 MB. Doesn't appear to be compatible. I see now that it has a Phison E21T controller, along with almost every other SSD I can find.
I'll try the Lexar Play 1TB the other commenter successfully used.
Currently using with a Lexar Play M.2 2230 NVMe 1TB SSD. Works perfectly, boots Raspberry Pi OS with no issues. Running Gen 3 speed set in config.txt. Used 3M double-sided tape to hold SSD to X1003 adapter.
Hi, X1003's recommended drives , in general, are compatible, only some types of drives are not compatible, please refer to Important Notes , we are currently collecting feedback from buyers as well.
Enable comment auto-refresher
Anonymous user #21
Permalink |
Anonymous user #20
Permalink |
Anonymous user #20
Lisa
Anonymous user #20
Permalink |
Anonymous user #19
Permalink |
Lisa
Anonymous user #19
Lisa
Anonymous user #18
Permalink |
Anonymous user #17
Permalink |
Anonymous user #15
Permalink |
Anonymous user #14
Permalink |
Anonymous user #13
Permalink |
Lisa
Anonymous user #13
Permalink |
Lisa
Anonymous user #13
Permalink |
Lisa
Anonymous user #12
Permalink |
Anonymous user #3
Permalink |
Anonymous user #3
Permalink |
Anonymous user #11
Permalink |
Anonymous user #9
Permalink |
Anonymous user #3
Permalink |
Anonymous user #3
Permalink |
Anonymous user #10
Anonymous user #8
Permalink |
Anonymous user #16
Lisa
Anonymous user #7
Permalink |
Anonymous user #7
Permalink |
Anonymous user #6
Permalink |
Anonymous user #6
Permalink |
Walker
Anonymous user #5
Permalink |
Anonymous user #5
Anonymous user #2
Permalink |
Anonymous user #2
Anonymous user #4
Permalink |
Walker
Walker
Anonymous user #4
Anonymous user #4
Anonymous user #4
Anonymous user #3
Permalink |
Walker
Anonymous user #3
Permalink |
Walker
Anonymous user #2
Permalink |
Walker
Anonymous user #1
Permalink |
Walker