Samsung 970 EVO SSD 1TB - M.2 NVMe works on workstation but not Pinebook Pro
#1
I have a Samsung 970 EVO SSD 1TB - M.2 NVMe in a SSK Aluminum M.2 NVME external case, see here for the product on Amazon: https://www.amazon.com/gp/product/B07MNF...UTF8&psc=1

I installed the gnome-disks utility on the Pinebook Pro to assist me with this.

NVMe and enclosure work without problem on my workstation running Fedora 30. Format, partition, read, write, all good.


dmesg reports:
[341405.622922] usb 6-2: new SuperSpeed Gen 1 USB device number 6 using xhci_hcd
[341405.635207] usb 6-2: New USB device found, idVendor=152d, idProduct=0562, bcdDevice= 2.06
[341405.635211] usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[341405.635214] usb 6-2: Product: SSK Storage
[341405.635215] usb 6-2: Manufacturer: SSK
[341405.635217] usb 6-2: SerialNumber: DF56419883E5B
[341405.823661] usb 6-2: USB controller 0000:0c:00.0 does not support streams, which are required by the UAS driver.
[341405.823667] usb 6-2: Please try an other USB controller if you wish to use UAS.
[341405.823671] usb-storage 6-2:1.0: USB Mass Storage device detected
[341405.824043] scsi host15: usb-storage 6-2:1.0
[341406.842939] scsi 15:0:0:0: Direct-Access     SSK                       0206 PQ: 0 ANSI: 6
[341406.843583] sd 15:0:0:0: Attached scsi generic sg8 type 0
[341409.512535] sd 15:0:0:0: [sdg] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[341409.515399] sd 15:0:0:0: [sdg] Write Protect is off
[341409.515407] sd 15:0:0:0: [sdg] Mode Sense: 53 00 00 08
[341409.518240] sd 15:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[341409.528580]  sdg: sdg1
[341409.534874] sd 15:0:0:0: [sdg] Attached SCSI disk

However, the Pinebook Pro recognizes the enclosure when plugged in to a USB 3 port, assigning it the device file /dev/sda, but gnome-disks reports "No Media".  dmesg reports:

[ 1490.403480] usb 2-1.1: new high-speed USB device number 4 using ehci-platform
[ 1490.564908] usb 2-1.1: New USB device found, idVendor=152d, idProduct=0562, bcdDevice= 2.06
[ 1490.565662] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1490.566313] usb 2-1.1: Product: SSK Storage
[ 1490.566693] usb 2-1.1: Manufacturer: SSK
[ 1490.567050] usb 2-1.1: SerialNumber: DF56419883E5B
[ 1490.569695] scsi host0: uas
[ 1490.571524] scsi 0:0:0:0: Direct-Access     SSK                       0206 PQ: 0 ANSI: 6
[ 1490.573978] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 1499.433316] sd 0:0:0:0: [sda] Unit Not Ready
[ 1499.433767] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current]
[ 1499.434347] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81
[ 1499.435414] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1499.436252] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current]
[ 1499.436829] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81
[ 1499.437890] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1499.438720] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current]
[ 1499.439285] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81
[ 1499.440892] sd 0:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B)
[ 1499.441442] sd 0:0:0:0: [sda] 0-byte physical blocks
[ 1499.442261] sd 0:0:0:0: [sda] Test WP failed, assume Write Enabled
[ 1499.443012] sd 0:0:0:0: [sda] Asking for cache data failed
[ 1499.443537] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 1499.444514] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of physical block size (0 bytes)
[ 1499.485275] sd 0:0:0:0: [sda] Unit Not Ready
[ 1499.485675] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current]
[ 1499.486252] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81
[ 1499.487290] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1499.488131] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current]
[ 1499.488711] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81
[ 1499.489911] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1499.490756] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current]
[ 1499.491336] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81
[ 1499.494885] sd 0:0:0:0: [sda] Attached SCSI disk

I note that there is a package named nvme-cli, is this necessary?

Same problem with the default operating system, and with an install of the Mandriva KDE image.

Is this the problem: [ 1499.490756] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current], is the Pinebook Pro not capable of supplying sufficient current for this device?


Thanks for any ideas offered!


Messages In This Thread
Samsung 970 EVO SSD 1TB - M.2 NVMe works on workstation but not Pinebook Pro - by mgchristensen - 12-28-2019, 02:10 PM

Possibly Related Threads…
Thread Author Replies Views Last Post
  NVMe reukiodo 0 50 11-18-2024, 09:00 AM
Last Post: reukiodo
  NVMe drives not detected mattpenn 13 12,544 11-17-2024, 04:38 AM
Last Post: reukiodo
  New Working nVME gilwood 1 618 11-17-2024, 04:24 AM
Last Post: reukiodo
  Yet another new Pinebook keyboard problem MikoBob 3 503 09-11-2024, 07:05 AM
Last Post: MikoBob
  HDMI or VGA From Pinebook Pro via Pinebook Pro Docking Deck? segaloco 4 2,664 05-06-2024, 09:27 AM
Last Post: KC9UDX
  Pinebook Pro on Debian 12 Power Issue u974615 1 851 03-13-2024, 10:46 AM
Last Post: u974615
  Pinebook Pro Source for Trackpad Flex / Ribbon Cable rankharris 1 798 02-17-2024, 07:06 PM
Last Post: tllim
  Pinebook Pro charging issues tomekdev 1 1,119 01-05-2024, 08:40 PM
Last Post: tomekdev
  Replacement battery for PineBook Pro DrYak 3 2,044 11-07-2023, 10:09 AM
Last Post: DrYak
  Pinebook Pro Revised Keyboard Firmware jackhumbert 73 150,150 09-13-2023, 03:43 AM
Last Post: k3dAR

Forum Jump:


Users browsing this thread: 4 Guest(s)