Hey @davinci,
Drive identified: Crucial P3 4TB (CT4000P3SSD8E), Gen3 x4, DRAM-less, firmware P9CR30D. P9CR30D is shared firmware across the P3 family - the 1TB sibling carries the same string - so it is not a 4TB-specific firmware oddity.
Now the real point.
The boot-from-NVMe path on Volumio Pi was validated against drives whose capacity is much smaller than yours. There is no public record of a 4TB Crucial P3 booting Volumio cleanly on a Pi 5. Beyond about 2TB, you are in self-validation territory - not a path the project has signed off on. Two factors compound at this size on this drive class:
- The P3 is DRAM-less and relies on Host Memory Buffer for caching. The Pi kernel command line explicitly disables HMB (nvme.max_host_mem_size_mb=0). The install log captured the kernel rejecting the drive’s HMB request. The drive is operating without its expected cache backing.
- The Volumio data partition (p3) was sized at 3.6T to fill the drive. The combination of that volume size, this drive class and HMB-disabled is what we are seeing fall over.
So we constrain the Volumio data partition to a size well inside known-good territory, and use the rest of the drive as a separate partition for music storage. The burden of doing this manual work is on you - the project does not validate or support it - but it puts the boot/data path back on stable ground.
Procedure, all run while booted from SD card with the NVMe attached.
-
Run Install to disk again so you have a clean GPT layout on the NVMe. Wait for it to complete fully.
-
Do NOT reboot into NVMe. Verify the layout:
sudo lsblk -f /dev/nvme0n1 -
Shrink p3 from 3.6T down to 512G. Filesystem first, then partition:
sudo e2fsck -fy /dev/nvme0n1p3 sudo resize2fs /dev/nvme0n1p3 512G sudo parted /dev/nvme0n1 ---pretend-input-tty resizepart 3 512GiBConfirm:
sudo parted /dev/nvme0n1 unit GiB print -
Power down, remove the SD card, boot from NVMe. Watch the screen and do not connect to the WebUI for at least five minutes. We need to know whether it stays up under its own weight before we trust it with anything else.
-
If the system stays up, report back. We can then deal with creating an additional partition in the freed space for music, mounted from inside Volumio’s network sources.
If the failure repeats with p3 at 512G, the working hypothesis (drive size + HMB) is wrong and we look at other angles - drive carrier, ribbon, PCIe gen, or the drive itself. But constrain p3 first and let me know the result.
One question on the PSU: the install log shows a 4-second undervoltage event at 08:58:32 during the install. You mentioned you had previously been on a Pi 4 supply and switched to the LinearPi Pro. Was the LinearPi Pro the one in use during the install where the undervoltage was logged, or were you still on the Pi 4 supply at that point?
Kind Regards,
