i have my new pi5 running but my ssd is not seen. I have seen cmd line instructions to wake this up and format it. I have ssh working can some one post?
Thank you
i have my new pi5 running but my ssd is not seen. I have seen cmd line instructions to wake this up and format it. I have ssh working can some one post?
Thank you
USB SSD drive mounted for extra storage or NVME device attached to the PCIe connector you want to boot from?
Mounted for storage but its on the pi hat and is m.2
hello
ist nur eine info
https://www.raspberrypi.com/documentation/computers/configuration.html
Example config.txt
Boot_Order options:
The BOOT_ORDER property defines the order for the different boot modes. It is read from right to left and up to 8 digits can be defined.
In the example set above “BOOT_ORDER=0xf416” this is 6-1-4-f:
6 = First boot attempt from NVME
1 = Second boot attempt from SD card
4 = Third boot attempt from USB
f = Loop – start again at the first boot attempt
############
BOOT_UART=1
POWER_OFF_ON_HALT=0
BOOT_ORDER=0xf146
PCIE_PROBE=1
dtparam=pciex1
dtparam=pciex1_gen=3
include distroconfig.txt
Display More
sparkplug have you added dtparam=pciex1 to /flash/config.txt?
No but i will now thanks!
Spotted this in Google results: https://wiki.geekworm.com/NVMe_SSD_boot_…_Raspberry_Pi_5 which states "We recommend avoiding the following NVMe SSD drives which is equipped with a Phison controller due to their proven incompatibility:" .. and the Corsair MP600 is listed. However there are notes on the same page and posts in RPi forums that hint some devices are then working with after RPi firmware updates (and with updates from early 2024, which is some time ago now).
So three things to do:
Do one thing at a time so you can see what made the difference, should it start working. If it doesn't, I'll be pointing fingers at the Phison controller and suspecting not-all issues are resolved.
EDIT: Also share the URL from "dmesg | paste" so we can see if there's something in the system log.
Thank you Chewitt for spending time on this!. I will test and report!
RPi5:~ # ls -l /dev/nvme*
crw------- 1 root root 243, 0 Dec 6 03:29 /dev/nvme0
brw-rw---- 1 root disk 259, 0 Dec 6 03:29 /dev/nvme0n1
brw-rw---- 1 root disk 259, 1 Dec 6 03:29 /dev/nvme0n1p1
brw-rw---- 1 root disk 259, 2 Dec 6 03:29 /dev/nvme0n1p2
If you do ^ that, do you see at least /dev/nvme0 listed? - I'm not really seeing any errors but there's no mention of any partitions being checked or mounted. The probable and logical explanation for that would simply be that none exist on the drive and you need to create one, e.g. (not 100% sure of the commands here, am working from memory):
parted -s /dev/nvme0n1 mklabel gpt
parted -s /dev/nvme0n1 mkpart primary ext4 40s 100%
parted -s /dev/nvme0n1 name 1 'MEDIA'
mkfs.ext4 -L "MEDIA" /dev/nvme0n1p1
fsck.ext4 -y /dev/nvme0n1p1
If that's not the issue I'm unsure what the actual issue is, so hard to advise.
We might be getting somewhere i see /dev/nvme0 and /dev/nvme0n1 the new ssd is 2 t in size if lable one how do i determine?
KodiJr:~ # ls -l /dev/nvme*
crw------- 1 root root 243, 0 Dec 5 22:02 /dev/nvme0
brw-rw---- 1 root disk 259, 0 Dec 5 22:02 /dev/nvme0n1
Yup, looks like the device is present but there are no paritions/filesystems - You need to create one. The commands I shared in the second code-block above should fix that.
~ # fsck.ext4 -y /dev/nvme0n1p1
e2fsck 1.47.1 (20-May-2024)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/nvme0n1p1
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
(hates me)
Show the output of all the commands, in sequence, or copy/paste to pastebin.com or similar.
question
why don't I read that he "flashed" or copied a (BS) Kodi on the NVMe and changed the config to NVMe!??
e.g. with https://www.raspberrypi.com/software/operating-systems/
on usb and then reboot to the NVMe (without sd card copy) only because of the config and boot order
unfortunately I only have instructions in german
frage (deutsch)
warum lese ich nicht das er ein (BS) Kodi auf der NVMe "geflasht" bzw. kopiert hat und die config auf NVMe umgestellt hat!?
zb. mit https://www.raspberrypi.com/software/operating-systems/
auf usb und dann mit reboot auf die NVMe zu kommen (ohne sd Card Copy) nur wegen der config und bootreienfolge
leider hab ich nur anleitungen auf deutsch
NVMe SSD boot with the Raspberry Pi 5 - Geekworm Wiki
I apologise if I have misunderstood