Page 1 of 1

DietPI + Odroid HC1 + Samsung 860 EVO doesn't work

Posted: Thu Aug 01, 2019 12:45 am
by SteveNZ
I am trying to set up a music server using an Odroid HC1. It works fine if I use a Sandisk Ultra II SSD, but won't work at all with a Samsung 860 EVO SSD. I have tried two different Samsung 860 EVO SSDs, one 512 GB and one 2TB with the same problem.

Linux DietPi 4.14.66+ #1 SMP PREEMPT Thu Aug 23 05:59:33 UTC 2018 armv7l GNU/Linux

Here's what happens when the Samsung SSD is inserted.

[ 738.819930] usb 4-1: new SuperSpeed USB device number 3 using xhci-hcd
[ 738.840999] usb 4-1: New USB device found, idVendor=152d, idProduct=0579
[ 738.841006] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 738.841012] usb 4-1: Product: JMS579
[ 738.841017] usb 4-1: Manufacturer: JMICRON
[ 738.841022] usb 4-1: SerialNumber: 3393E20D6002215
[ 738.841686] usb-storage 4-1:1.0: USB Mass Storage device detected
[ 738.842037] scsi host0: usb-storage 4-1:1.0
[ 739.844417] scsi 0:0:0:0: Direct-Access Samsung SSD 860 EVO 2TB 3101 PQ: 0 ANSI: 6
[ 739.845230] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 739.845443] sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[ 739.845792] sd 0:0:0:0: [sda] Write Protect is off
[ 739.845802] sd 0:0:0:0: [sda] Mode Sense: 47 00 00 08
[ 739.846136] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 739.867989] sda: sda1
[ 739.869488] sd 0:0:0:0: [sda] Attached SCSI disk

<< long delay here when the system is unresponsive and the drive light flashes continually >>

[ 756.336366] usb 4-1: reset SuperSpeed USB device number 3 using xhci-hcd

<< another long delay here when the system is unresponsive and the drive light flashes continually >>

[ 937.745151] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 937.745206] sd 0:0:0:0: [sda] tag#0 Sense Key : 0x2 [current]
[ 937.745250] sd 0:0:0:0: [sda] tag#0 ASC=0x4 ASCQ=0x1
[ 937.745299] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 e8 e0 87 80 00 00 08 00
[ 937.745339] print_req_error: I/O error, dev sda, sector 3907028864

Here's what happens for a Seagate SSD which does work properly:

[ 435.980178] usb 4-1: new SuperSpeed USB device number 2 using xhci-hcd
[ 436.001869] usb 4-1: New USB device found, idVendor=152d, idProduct=0579
[ 436.001901] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 436.001922] usb 4-1: Product: JMS579
[ 436.001942] usb 4-1: Manufacturer: JMICRON
[ 436.001962] usb 4-1: SerialNumber: 143635401249
[ 436.045758] SCSI subsystem initialized
[ 436.051173] usb-storage 4-1:1.0: USB Mass Storage device detected
[ 436.056493] scsi host0: usb-storage 4-1:1.0
[ 436.056764] usbcore: registered new interface driver usb-storage
[ 436.061458] usbcore: registered new interface driver uas
[ 437.060628] scsi 0:0:0:0: Direct-Access SanDisk SDSSDHII120G 3101 PQ: 0 ANSI: 6
[ 437.073580] scsi 0:0:0:0: Attached scsi generic sg0 type 0
[ 437.085197] sd 0:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/112 GiB)
[ 437.085656] sd 0:0:0:0: [sda] Write Protect is off
[ 437.085664] sd 0:0:0:0: [sda] Mode Sense: 47 00 00 08
[ 437.086078] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 437.098037] sda: sda1
[ 437.099997] sd 0:0:0:0: [sda] Attached SCSI disk

The smaller 860 EVO drive fails in the same manner:

Tried with a different Samsung SSD 512GB 860 EVO

[ 1105.680280] usb 4-1: new SuperSpeed USB device number 4 using xhci-hcd
[ 1105.702141] usb 4-1: New USB device found, idVendor=152d, idProduct=0579
[ 1105.702186] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1105.702217] usb 4-1: Product: JMS579
[ 1105.702247] usb 4-1: Manufacturer: JMICRON
[ 1105.702276] usb 4-1: SerialNumber: 3393E20D6002215
[ 1105.705174] usb-storage 4-1:1.0: USB Mass Storage device detected
[ 1105.706366] scsi host0: usb-storage 4-1:1.0
[ 1106.724444] scsi 0:0:0:0: Direct-Access Samsung SSD 860 EVO 2TB 3101 PQ: 0 ANSI: 6
[ 1106.725248] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 1106.725470] sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[ 1106.725824] sd 0:0:0:0: [sda] Write Protect is off
[ 1106.725836] sd 0:0:0:0: [sda] Mode Sense: 47 00 00 08
[ 1106.726174] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1106.748192] sda: sda1
[ 1106.749698] sd 0:0:0:0: [sda] Attached SCSI disk

<< long delay here when the system is unresponsive and the drive light flashes continually >>

[ 1122.160565] usb 4-1: reset SuperSpeed USB device number 4 using xhci-hcd

<< long delay here when the system is unresponsive and the drive light flashes continually >>

[ 1303.568481] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 1303.568490] sd 0:0:0:0: [sda] tag#0 Sense Key : 0x2 [current]
[ 1303.568496] sd 0:0:0:0: [sda] tag#0 ASC=0x4 ASCQ=0x1
[ 1303.568503] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 e8 e0 87 80 00 00 08 00
[ 1303.568510] print_req_error: I/O error, dev sda, sector 3907028864

There is another Odroid & Samsung EVO 860 user with a similar problem over here:

https://forum.odroid.com/viewtopic.php?t=32679

Has anyone had any joy with the Samsung 860 EVO SSDs? Is there anything I can do to get it to work?

Thanks, Steve

Re: DietPI + Odroid HC1 + Samsung 860 EVO doesn't work

Posted: Thu Aug 01, 2019 11:38 pm
by SteveNZ
I have just tested the HC1 with Armbian and the Samsung 860 EVO works fine.

uname -a shows

Linux odroidhc1 4.14.127-odroidxu4 #75 SMP PREEMPT Mon Jul 15 18:35:25 CEST 2019 armv7l GNU/Linux

There is a file /boot/armbianEnv.txt that has this in it.

board_name=hc1
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

Steve

Re: DietPI + Odroid HC1 + Samsung 860 EVO doesn't work

Posted: Wed Aug 07, 2019 11:03 pm
by SteveNZ
I received a 2TB Samsung 860 QVO and can confirm that it doesn't work with DitePi on the HC1.

[ 24.282357] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 40.047975] usb 4-1: reset SuperSpeed USB device number 2 using xhci-hcd
[ 205.219776] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 205.226500] sd 0:0:0:0: [sda] tag#0 Sense Key : 0x2 [current]
[ 205.232306] sd 0:0:0:0: [sda] tag#0 ASC=0x4 ASCQ=0x1
[ 205.237324] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 04 37 38 00 00 20 00
[ 205.244863] print_req_error: I/O error, dev sda, sector 276280
[ 284.397349] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 284.428183] r8152 6-1:1.0 eth0: carrier on
[ 284.430893] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 5691.143831] hrtimer: interrupt took 11973041 ns

I have also received two 2TB Seagate Barrcuda SSDs which do work properly. Happy to test some more if that helps.

Steve