I’m expecting to free up an NVMe SSD soon, and my Pi 5 is currently
making do with an SD card, so I’ve been looking into options for putting the two together.
Has anyone used this case?
https://shop.pimoroni.com/products/argon-neo-5-m-2-nvme-pcie-case-for-raspberry-pi-5
Another easily discoverable option is:
https://shop.pimoroni.com/products/nvme-base
...but I think I’d need a new case and I’ve not yet managed to find one that’s likely to fit.
Are there any other good options out there?
I’m expecting to free up an NVMe SSD soon, and my Pi 5 is currently
making do with an SD card, so I’ve been looking into options for putting the two together.
Has anyone used this case?
https://shop.pimoroni.com/products/argon-neo-5-m-2-nvme-pcie-case-for-raspberry-pi-5
Another easily discoverable option is:
https://shop.pimoroni.com/products/nvme-base
...but I think I’d need a new case and I’ve not yet managed to find one that’s likely to fit.
Are there any other good options out there?
I got rid of my desire for an nvme with my opi5. Due to being PCIe 1
lane, it wasn't that much faster,
and there was significant additional
effort installing the OS, compared to a micro SD. Obviously, you may
have a different use-case.
On 21/02/2024 17:42, Pancho wrote:
I got rid of my desire for an nvme with my opi5. Due to being PCIe 1
lane, it wasn't that much faster,
That surprises me, could anyone with an NVMe base run this script
which measures the maximum sequential and random access read/write
speeds. You'll need to install the fio package and be in a directory
on the disc under test.
#!/bin/bash
TESTFILE=fio-tempfile.dat
fio --name SeqRead --eta-newline=5s --filename=$TESTFILE --rw=read\
--size=500m --io_size=10g --blocksize=1024k --ioengine=libaio\
--fsync=10000 --iodepth=32 --direct=1 --numjobs=1 --runtime=30\
--group_reporting | grep bw=
fio --name SeqWrite --eta-newline=5s --filename=$TESTFILE --rw=write\
--size=500m --io_size=10g --blocksize=1024k --ioengine=libaio\
--fsync=10000 --iodepth=32 --direct=1 --numjobs=1 --runtime=30\
--group_reporting | grep bw=
fio --name RndRead --eta-newline=5s --filename=$TESTFILE
--rw=randread\ --size=500m --io_size=10g --blocksize=4k
--ioengine=libaio --fsync=1\ --iodepth=1 --direct=1 --numjobs=1 --runtime=30 --group_reporting\ | grep bw= fio --name RndWrite --eta-newline=5s --filename=$TESTFILE--rw=randwrite\ --size=500m --io_size=10g --blocksize=4k --ioengine=libaio --fsync=1\ --iodepth=1 --direct=1 --numjobs=1 --runtime=30 --group_reporting\ | grep bw= rm $TESTFILE
and there was significant additional
effort installing the OS, compared to a micro SD. Obviously, you may
have a different use-case.
More than dd'ing the SD card image on to the NVMe, using gparted to
expand the linux partition, and then changing the boot device in /boot/cmdline.txt and /etc/fstab ?
---druck
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
I posted some stats back in December ( hdparm -Ttv), on the opi5 the
nvme was only giving 186 MB/s seq read, not that much more than a USB3
SSD at 137 MB/s.
I think, like the oPi5, the rPi5 also has the handicap that it only
allocates PCIe 3.0 x 1 to nvme.
So yes, nvme is faster in benchmarks, but nowhere near the 3000MB/s you
might see on a PC.
Pancho wrote:
I posted some stats back in December ( hdparm -Ttv), on the opi5 the
nvme was only giving 186 MB/s seq read, not that much more than a USB3
SSD at 137 MB/s.
I think, like the oPi5, the rPi5 also has the handicap that it only
allocates PCIe 3.0 x 1 to nvme.
So yes, nvme is faster in benchmarks, but nowhere near the 3000MB/s
you might see on a PC.
I think Jeff Geerling saw 900MB/s ?
fio --name SeqRead --eta-newline=5s --filename=$TESTFILE --rw=read\
--size=500m
On 22/02/2024 00:17, Andy Burns wrote:
Pancho wrote:
I posted some stats back in December ( hdparm -Ttv), on the opi5 the
nvme was only giving 186 MB/s seq read, not that much more than a
USB3 SSD at 137 MB/s.
I think, like the oPi5, the rPi5 also has the handicap that it only
allocates PCIe 3.0 x 1 to nvme.
So yes, nvme is faster in benchmarks, but nowhere near the 3000MB/s
you might see on a PC.
I think Jeff Geerling saw 900MB/s ?
Remember, I'm testing nvme on an Orange Pi 5 not a Raspberry Pi 5, but,
I feel quite inadequate. However, it is what I get.
Here are the results from druck's script:
READ: bw=200MiB/s (209MB/s), 200MiB/s-200MiB/s (209MB/s-209MB/s), io=6000MiB (6291MB), run=30060-30060msec
WRITE: bw=199MiB/s (209MB/s), 199MiB/s-199MiB/s (209MB/s-209MB/s), io=6000MiB (6291MB), run=30085-30085msec
READ: bw=36.0MiB/s (37.8MB/s), 36.0MiB/s-36.0MiB/s
(37.8MB/s-37.8MB/s), io=1081MiB (1133MB), run=30001-30001msec
READ: bw=48.1MiB/s (50.4MB/s), 48.1MiB/s-48.1MiB/s
(50.4MB/s-50.4MB/s), io=1443MiB (1513MB), run=30001-30001msec
Maybe my result is so bad because I'm only using a KingSpec nvme drive?
It's supposed to do 3500MB/s, but I've never tested it in anything that
could handle that.
I'm not going to use a top range drive on a Pi. The Orange Pi isn't
doing anything else, isn't busy.
I was curious, so I did a bit of digging, it appears my nvme drive is
running as PCIe gen 1. The oPi5 should be gen 3, The nvme drive should
be gen 3.
Pancho wrote:
I was curious, so I did a bit of digging, it appears my nvme drive is
running as PCIe gen 1. The oPi5 should be gen 3, The nvme drive should
be gen 3.
I don't have an rpi5, but they also default to gen1, a config.txt option
can force gen3
dtparam=pciex1_gen=3
does an opi5 have similar?
I looked, I tried, I failed!
I tried adding the following line to /boot/armbianEnv.txt
'''
dtoverlay=pcie-gen2
'''
I also tried editing the dtb overlay: /boot/dtb/rockchip/rk3588s-orangepi-5.dtb
which was already configured for gen 2
Seriously, the oPi5 looks like a brilliant device, it feels like a
brilliant device, but nothing quite works properly, my advice is to buy
the rPi5, every time.
Here's the output of your script tested on my Pi5 with NVMe SSD:
READ: bw=850MiB/s (891MB/s), 850MiB/s-850MiB/s (891MB/s-891MB/s), io=10.0GiB
(10.7GB), run=12046-12046msec
WRITE: bw=746MiB/s (782MB/s), 746MiB/s-746MiB/s (782MB/s-782MB/s), io=10.0GiB
(10.7GB), run=13727-13727msec
READ: bw=64.6MiB/s (67.7MB/s), 64.6MiB/s-64.6MiB/s (67.7MB/s-67.7MB/s), io=1937MiB (2031MB), run=30000-30000msec
READ: bw=223MiB/s (234MB/s), 223MiB/s-223MiB/s (234MB/s-234MB/s), io=6684MiB
(7008MB), run=30000-30000msec
On Wed, 21 Feb 2024 20:51:31 +0000
druck <news@druck.org.uk> wrote:
fio --name SeqRead --eta-newline=5s --filename=$TESTFILE --rw=read\
--size=500m
Shouldn't that file size be much larger to prevent it from being
cached ? I get ridiculous numbers trying that script on a PC.
On 22/02/2024 10:00, Pancho wrote:
Here are the results from druck's script:
READ: bw=200MiB/s (209MB/s), 200MiB/s-200MiB/s (209MB/s-209MB/s),
io=6000MiB (6291MB), run=30060-30060msec
WRITE: bw=199MiB/s (209MB/s), 199MiB/s-199MiB/s (209MB/s-209MB/s),
io=6000MiB (6291MB), run=30085-30085msec
READ: bw=36.0MiB/s (37.8MB/s), 36.0MiB/s-36.0MiB/s
(37.8MB/s-37.8MB/s), io=1081MiB (1133MB), run=30001-30001msec
READ: bw=48.1MiB/s (50.4MB/s), 48.1MiB/s-48.1MiB/s
(50.4MB/s-50.4MB/s), io=1443MiB (1513MB), run=30001-30001msec
Check the line breaks didn't get messed up, as the last line should be
WRITE.
---druck
That's my general feeling. I think Armbian are trying to increase their
level of support for various board, but they are just volunteers with no
help from vendors.
I’m expecting to free up an NVMe SSD soon, and my Pi 5 is currently
making do with an SD card, so I’ve been looking into options for
putting the two together.
Has anyone used this case?
https://shop.pimoroni.com/products/argon-neo-5-m-2-nvme-pcie-case-for-raspberry-pi-5
In February I mentioned getting an Argon NEO 5 NVMe case for my Pi 5.
It was slightly fiddly to put it all together, but not really outside expectations. Linux was able to see my SSD without any trouble.
However I have not been able to get the Pi to boot directly from the
SSD. It can see there’s something there but can’t interpret it properly; the diagnostic output (copy-typed) is:
NVME on 0
Trying partition: 0
Unable to read partition as FAT
type: 32 lba: 0 '' ' ' clusters 0 (0)
Trying partition: 0
Unable to read partition as FAT
type: 32 lba: 0 '' ' ' clusters 0 (0)
NVME off
Timeout 00000000 3c303020 00000000 00000000
nvme: error 8
Failed to open device: 'nvme'
(Why is there ASCII ‘ 00<’ in the timeout message?)
My solution was to boot from the SD card but to configure it (via
cmdline.txt and /etc/fstab) to mount the root system from the SSD. This
works (and it’s not like the performance & capacity of the firmware partition is very important) though there are now two points of failure.
My interpretation of all this is that the hardware is connecting the SSD perfectly well, and the Linux kernel talks to it correctly, but the boot loader is failing to communicate properly with the SSD.
Based on forum posts there are many compatibility issues between the Pi
5 and NVMe devices, so anyone planning to buy one should do their
research first.
In my case the SSD is a Crucial CT1000P5SSD8; I had it left over from a decommissioned PC.
In this case it looks like it (the bootloader) cant find the FAT
partition.
Now that could be that it is making some unwarranted assumptions about
where on the disk that actually is.
And the disk has it either elsewhere, or mapped internally to elsewhere.
I note that it is trying partition 0..
is that actually where the FAT volume resides?
The Natural Philosopher <tnp@invalid.invalid> writes:
No problems with wimpy power supplies? apparently pi's and ssds take a
lot of current at boot time
It’s the official PSU.
In February I mentioned getting an Argon NEO 5 NVMe case for my Pi 5.
It was slightly fiddly to put it all together, but not really outside expectations. Linux was able to see my SSD without any trouble.
However I have not been able to get the Pi to boot directly from the
SSD. It can see there’s something there but can’t interpret it properly; the diagnostic output (copy-typed) is:
In my case the SSD is a Crucial CT1000P5SSD8; I had it left over from a decommissioned PC.
The Natural Philosopher <tnp@invalid.invalid> writes:
No problems with wimpy power supplies? apparently pi's and ssds take a
lot of current at boot time
It’s the official PSU.
On 23/05/2024 09:03, Richard Kettlewell wrote:There is an entry in config.txt that 'tells' the pi that it has a high
The Natural Philosopher <tnp@invalid.invalid> writes:
No problems with wimpy power supplies? apparently pi's and ssds take a
lot of current at boot time
It’s the official PSU.
I bought a Pi5 without the official PSU, or even a Pi4 official PSU. It
would run for a minute or two and then crash. Completely unusable. It is
now fine with the official PSU.
On 23/05/2024 09:44, Pancho wrote:
On 23/05/2024 09:03, Richard Kettlewell wrote:There is an entry in config.txt that 'tells' the pi that it has a high
The Natural Philosopher <tnp@invalid.invalid> writes:
No problems with wimpy power supplies? apparently pi's and ssds take a >>>> lot of current at boot time
It’s the official PSU.
I bought a Pi5 without the official PSU, or even a Pi4 official PSU.
It would run for a minute or two and then crash. Completely unusable.
It is now fine with the official PSU.
power power supply.
Otherwise it has to do an appl-ish sort of negotiation with its PSU to
see if it is.
On 23/05/2024 10:58, The Natural Philosopher wrote:
On 23/05/2024 09:44, Pancho wrote:
On 23/05/2024 09:03, Richard Kettlewell wrote:There is an entry in config.txt that 'tells' the pi that it has a high
The Natural Philosopher <tnp@invalid.invalid> writes:
No problems with wimpy power supplies? apparently pi's and ssds take a >>>>> lot of current at boot time
It’s the official PSU.
I bought a Pi5 without the official PSU, or even a Pi4 official PSU.
It would run for a minute or two and then crash. Completely unusable.
It is now fine with the official PSU.
power power supply.
Otherwise it has to do an appl-ish sort of negotiation with its PSU to
see if it is.
No, I was talking about the USB standard. This is from memory, so take
with a pinch of salt.
I have high wattage USB C chargers for mobiles, pads etc. They quote 20
or 25 watts. Given I wasn't using any USB power draining devices, I
assumed this would be OK for the Pi 5.
However, it wasn't OK, Pi 5 crashed. When I looked at the USB small
print, the charger achieved a high wattage by boosting the voltage from
5v to 20v, still using a relatively low amps. AIUI, this is USB standard.
However, the Pi requires 5v (maybe even 5.1v) and a high 5 amps. Which
is totally non-standard and makes the Pi 5 USB PSU effectively bespoke.
I suppose, but haven't tested, the Pi 5 PSU is also no good to fast
charge your mobile.
Presumably there is some good cost justification, but I don't like it.
The Orange Pi 5 is fine on a standard USB fast charger, but it is
generally lower power than the Raspberry Pi 5.
high wattage
On 23/05/2024 11:50, Pancho wrote:
high wattage
For God's sake it's high power or high current. Saying high wattage
makes you look ignorant.
Like all the left pondians who say "it's
negative 15 today" when they mean "minus 15".
On 23/05/2024 11:50, Pancho wrote:
high wattage
For God's sake it's high power or high current. Saying high wattage
makes you look ignorant. Like all the left pondians who say "it's
negative 15 today" when they mean "minus 15".
Richard Kettlewell <invalid@invalid.invalid> writes:
In February I mentioned getting an Argon NEO 5 NVMe case for my Pi 5.
It was slightly fiddly to put it all together, but not really outside
expectations. Linux was able to see my SSD without any trouble.
However I have not been able to get the Pi to boot directly from the
SSD. It can see there’s something there but can’t interpret it properly; >> the diagnostic output (copy-typed) is:
Did you configure your Pi to boot from the SSD?
On 23 May 2024 at 16:18:59 BST, "mm0fmf" <none@invalid.com> wrote:
On 23/05/2024 11:50, Pancho wrote:
high wattage
For God's sake it's high power or high current. Saying high wattage
makes you look ignorant. Like all the left pondians who say "it's
negative 15 today" when they mean "minus 15".
High wattage *is* high power. Power is measured in watts.
Only for DC or when the PF is 1.
I have high wattage USB C chargers for mobiles, pads etc. They quote 20
or 25 watts. Given I wasn't using any USB power draining devices, I
assumed this would be OK for the Pi 5.
However, it wasn't OK, Pi 5 crashed. When I looked at the USB small
print, the charger achieved a high wattage by boosting the voltage from
5v to 20v, still using a relatively low amps. AIUI, this is USB standard.
However, the Pi requires 5v (maybe even 5.1v) and a high 5 amps. Which
is totally non-standard and makes the Pi 5 USB PSU effectively bespoke.
I suppose, but haven't tested, the Pi 5 PSU is also no good to fast
charge your mobile.
On 23/05/2024 11:50, Pancho wrote:
high wattage
For God's sake it's high power or high current. Saying high wattage
makes you look ignorant. Like all the left pondians who say "it's
negative 15 today" when they mean "minus 15".
5 Volts at 5 amps is within the USB power spec, albeit less commonly used.
On 23/05/2024 12:28, Chris Townley wrote:
5 Volts at 5 amps is within the USB power spec, albeit less commonly used.
It would be unusual to come across a USB-PD power supply that did 5V 5A.
5A is a relatively recent addition to the USB-PD spec. Previously it
stopped at 3A. My 45W Samsung USB-PD charger gets 45W by doing 15V 3A.
My USB-PD laptop charger gets 60W by doing 20V 3A.
It would be unusual to come across a USB-PD power supply that did 5V 5A.
5A is a relatively recent addition to the USB-PD spec. Previously it
stopped at 3A. My 45W Samsung USB-PD charger gets 45W by doing 15V
3A. My USB-PD laptop charger gets 60W by doing 20V 3A.
I was curious, so I did a bit of digging, it appears my nvme drive is
running as PCIe gen 1. The oPi5 should be gen 3, The nvme drive should
be gen 3.
looks like a brilliant device, it feels like a brilliant device, but nothing quite works properly
| Sysop: | Coz |
|---|---|
| Location: | Anoka, MN |
| Users: | 2 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 140:15:09 |
| Calls: | 166 |
| Files: | 5,389 |
| Messages: | 223,236 |