I flashed one of these SN700 drives using a USB case and the RPI flash tool, and it isn’t being recognised by the OS. Is it supported?
Also the argon scripts sort of work, but there doesn’t seem to be any documentation that is current on the website for this case. It points to the blog page argon-resources, but this doesn’t have the RPI5 neo case on it.
Have you updated the EEPROM of your board with an SD card? I saw that a number of WD drives were unable to boot with other M.2 HATs as well and saw a line for WD NVME boot fix in the latest build.
The Argon ONE V3 and NEO 5 M.2 NVME-PCIe Boards followed the specifications of the Raspberry Pi Trading on its PCIe, which is similar to how Pimoroni implemented it also in their drive, unlike PineBerry Drive.
The only difference between the Argon V3 version vs the NEO 5 version is that the Argon ONE V3 version has 2 POGO PINS for additional power support for the M.2 board, which is not available for the NEO 5 version.
We will still need to do more validation of our own for the other drives but we would have the same compatibility with the Pimoroni Drives as well.
SOURCE PIMORONI WEBSITE Drive compatibility
AData Legend 700
AData Legend 800
AData XPG SX8200 Pro
Axe Memory Generic Drive
Crucial P2 M.2
Crucial P3 M.2
Crucial P3 Plus M.2
Inland PCIe NVMe SSD
Kingston KC3000
Kioxia Exceria NVMe SSD
Kioxia Exceria G2 NVMe SSD
Lexar NM620
Lexar NM710
Netac NV2000 NVMe SSD
Netac NV3000 NVMe SSD
Origin Inception TLC830 Pro NVMe
Patriot P300
Patriot P310
PNY CS1030
Sabrent Rocket 4.0
Sabrent Rocket Nano
Samsung 980
Samsung 980 Pro (500GB/1TB)
Team MP33
Western Digital Black SN750 SE (Phison Controller)
’ Maybe’ List. Works with quirks/not ideal.
These drives either needed extra power, were a bit quirky when we tested them or we’ve had reports of them being problematic. It may just be the drive we had, but they’re probably best avoided.
Kioxia BG4 2230. Performance very patchy. Runs at quite a high temp.
Samsung 970 EVO Plus. Runs at a higher temp. Some user reports of problems under heavy load or not showing up on boot.
Samsung 980 Pro (250GB). Reports of this size not working.
WD Blue SN550. Our fresh unit could be used as storage but could not be booted from.
WD Red SN700. Slow to boot first time, but worked and booted OK.
WD SN740. Our fresh unit worked well. YMMV.
WD Black SN770. Our fresh unit worked fine. YMMV.
‘Avoid’ List. We’ve had problems or reports of problems.
WD Green/Blue/Red/Black not in the above list. Variable results or not working because of quirks of a SanDisk controller/firmware. Our SN350 and SN570 prevented the RPi 5 from booting at all especially.
Could it be an idea that Argon provide an overview of which drives that actually aren’t compatible on your webpage (or better yet, if there is a subset of SSD sizes of a model that aren’t supported, how about listing those that are supported specifically)?
I ended up buying a Samsung 980 Pro 250GB because the webpage said 980 Pro is supported, but here I am sitting wasting time on trying to get the SSD to work as a boot device without knowing the device might not be supported at all.
Works fine to detect the drive when booting from microSD as a secondary disk, but that’s not the use case I had in mind when I ordered this. And as long as it doesn’t work setting the SSD as boot device, I have to say the information on the webpage is quite misleading.
Just an update to my previous post. After updating the fw of the Samsung 980 Pro 250GB from version 1B2QGXA7 to version 5B2QGXA7, booting from the ssd works just fine, so it could be an idea to add that information to the item page for the NVME board.