Thanks everyone for your replies.
I tried
- changing the entry in /boot/firmware/config.txt to dtparam=pciex1_gen=2
- Tried Gparted (it doesn't see the drive at all)
I bought an NVME -> USB external adaptor and when I plugged it in, Gparted could see the SDA drive. I was able to create the partition table (which was missing) and then a new volume. I then unplugged it and put it back in the Pineboard HAT and it can't be seen anymore - in Gparted or any other tool.
lsblk still gives
sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mmcblk0 179:0 0 29.7G 0 disk
ââmmcblk0p1 179:1 0 512M 0 part /boot/firmware
ââmmcblk0p2 179:2 0 29.2G 0 part /
nvme0n1 259:0 0 0B 0 disk
It can clearly be seen but not accessed. It still shows in SD Copier as a Samsung device, but can't be written to.
I feel that I am either missing something basic (haven't changed the config to read the card properly) or the HAT is faulty?
Any further thoughts would be much appreciated
I tried
- changing the entry in /boot/firmware/config.txt to dtparam=pciex1_gen=2
- Tried Gparted (it doesn't see the drive at all)
I bought an NVME -> USB external adaptor and when I plugged it in, Gparted could see the SDA drive. I was able to create the partition table (which was missing) and then a new volume. I then unplugged it and put it back in the Pineboard HAT and it can't be seen anymore - in Gparted or any other tool.
lsblk still gives
sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mmcblk0 179:0 0 29.7G 0 disk
ââmmcblk0p1 179:1 0 512M 0 part /boot/firmware
ââmmcblk0p2 179:2 0 29.2G 0 part /
nvme0n1 259:0 0 0B 0 disk
It can clearly be seen but not accessed. It still shows in SD Copier as a Samsung device, but can't be written to.
I feel that I am either missing something basic (haven't changed the config to read the card properly) or the HAT is faulty?
Any further thoughts would be much appreciated
Statistics: Posted by Cadgey — Thu Apr 03, 2025 11:08 pm