Odroid HC1 does not see Sata drive

Installed on Odroid HC1. The sata drive does not show at all when running lsblk, no sda under /dev

Does the drive have to have a certain format prior to connection to be seen?

I’ve done searches but can’t find anyone having this trouble with a normal SSD. I’ve tried a couple of different drives each approx. 250GB.

What am I missing?

Plan to use it with dietpi running motioneye for security cameras.

Hi,

did you tried using a normal USB stick. Will this show up?

As well you could check kernel messages using dmesg | grep -i usb, to verify if you SSD is detected. If a drive is detected, you should see following

root@DietPi3:~# dmesg | grep -i usb
...
[    3.174821] usb 1-1.2: new high-speed USB device number 4 using dwc_otg
[    3.361806] usb 1-1.2: New USB device found, idVendor=8564, idProduct=1000, bcdDevice= 1.00
[    3.364078] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.366226] usb 1-1.2: Product: Mass Storage Device
[    3.368415] usb 1-1.2: Manufacturer: JetFlash
[    3.370527] usb 1-1.2: SerialNumber: LZV3THUY
[    3.379528] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[    3.390969] scsi host0: usb-storage 1-1.2:1.0
...

To check attached usb devices, use lsusb

root@DietPi3:~# lsusb
Bus 001 Device 004: ID 8564:1000 Transcend Information, Inc. JetFlash

I didn’t see any usb mass storage from the command.

I tested the power supply has the right voltage, but suspect it may not be providing enough amps… even though it is rated at 4. I’ve ordered a beefier one rated at 6 amps, it won’t be here until next week to try out.

Will wait until then to try again, unless someone spots something from the below code.

Thank you.

root@DietPi:~# dmesg | grep -i usb
[    0.307253] usbcore: registered new interface driver usbfs
[    0.307333] usbcore: registered new interface driver hub
[    0.307504] usbcore: registered new device driver usb
[    0.812844] samsung-usb2-phy 12130000.phy: 12130000.phy supply vbus not found, using dummy regulator
[    0.813845] exynos5_usb3drd_phy 12100000.phy: 12100000.phy supply vbus not found, using dummy regulator
[    0.813945] exynos5_usb3drd_phy 12100000.phy: 12100000.phy supply vbus-boost not found, using dummy regulator
[    0.814311] exynos5_usb3drd_phy 12500000.phy: 12500000.phy supply vbus not found, using dummy regulator
[    0.814393] exynos5_usb3drd_phy 12500000.phy: 12500000.phy supply vbus-boost not found, using dummy regulator
[    1.977382] usbcore: registered new interface driver r8152
[    1.982540] usbcore: registered new interface driver cdc_ether
[    1.988325] usbcore: registered new interface driver cdc_subset
[    1.996342] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.005926] exynos-ehci 12110000.usb: EHCI Host Controller
[    2.011064] exynos-ehci 12110000.usb: new USB bus registered, assigned bus number 1
[    2.018954] exynos-ehci 12110000.usb: irq 80, io mem 0x12110000
[    2.040120] exynos-ehci 12110000.usb: USB 2.0 started, EHCI 1.00
[    2.044956] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.051450] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.058637] usb usb1: Product: EHCI Host Controller
[    2.063515] usb usb1: Manufacturer: Linux 4.14.180+ ehci_hcd
[    2.069118] usb usb1: SerialNumber: 12110000.usb
[    2.074267] hub 1-0:1.0: USB hub found
[    2.082370] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    2.091933] exynos-ohci 12120000.usb: USB Host Controller
[    2.097129] exynos-ohci 12120000.usb: new USB bus registered, assigned bus number 2
[    2.104848] exynos-ohci 12120000.usb: irq 80, io mem 0x12120000
[    2.172349] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[    2.177704] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.185595] usb usb2: Product: USB Host Controller
[    2.189655] usb usb2: Manufacturer: Linux 4.14.180+ ohci_hcd
[    2.195285] usb usb2: SerialNumber: 12120000.usb
[    2.200437] hub 2-0:1.0: USB hub found
[   15.600258] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 3
[   15.623347] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[   15.629970] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   15.637161] usb usb3: Product: xHCI Host Controller
[   15.642012] usb usb3: Manufacturer: Linux 4.14.180+ xhci-hcd
[   15.647644] usb usb3: SerialNumber: xhci-hcd.3.auto
[   15.652810] hub 3-0:1.0: USB hub found
[   15.665590] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 4
[   15.673218] xhci-hcd xhci-hcd.3.auto: Host supports USB 3.0  SuperSpeed
[   15.679846] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[   15.687953] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[   15.694625] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   15.708395] usb usb4: Product: xHCI Host Controller
[   15.708402] usb usb4: Manufacturer: Linux 4.14.180+ xhci-hcd
[   15.717666] usb usb4: SerialNumber: xhci-hcd.3.auto
[   15.718388] hub 4-0:1.0: USB hub found
[   15.744717] xhci-hcd xhci-hcd.6.auto: new USB bus registered, assigned bus number 5
[   15.767795] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
[   15.774431] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   15.781623] usb usb5: Product: xHCI Host Controller
[   15.786471] usb usb5: Manufacturer: Linux 4.14.180+ xhci-hcd
[   15.792106] usb usb5: SerialNumber: xhci-hcd.6.auto
[   15.797258] hub 5-0:1.0: USB hub found
[   15.810052] xhci-hcd xhci-hcd.6.auto: new USB bus registered, assigned bus number 6
[   15.817676] xhci-hcd xhci-hcd.6.auto: Host supports USB 3.0  SuperSpeed
[   15.824308] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
[   15.832410] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003
[   15.839074] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   15.846267] usb usb6: Product: xHCI Host Controller
[   15.851117] usb usb6: Manufacturer: Linux 4.14.180+ xhci-hcd
[   15.856750] usb usb6: SerialNumber: xhci-hcd.6.auto
[   15.861926] hub 6-0:1.0: USB hub found
[   17.040196] usb 6-1: new SuperSpeed USB device number 2 using xhci-hcd
[   17.065031] usb 6-1: New USB device found, idVendor=0bda, idProduct=8153
[   17.070290] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[   17.077389] usb 6-1: Product: USB 10/100/1000 LAN
[   17.082072] usb 6-1: Manufacturer: Realtek
[   17.086138] usb 6-1: SerialNumber: 000001000000
[   17.280423] usb 6-1: reset SuperSpeed USB device number 2 using xhci-hcd
root@DietPi:~# lsblk
NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk1     179:0    0 29.6G  0 disk 
├─mmcblk1p1 179:1    0  257M  0 part /boot
└─mmcblk1p2 179:2    0 29.3G  0 part /

hmm your system is not detecting the drive at all. No chance for DietPi at this stage to get it mounted. Could be an issue with the USB port or the drive themselves. Hard to say. Did you test with an usb stick? is this working?

Sorry I forgot to answer about using a usb thumb drive, it did show/work. I did find a few references online where the odroid HC1 didn’t see the sata drive due to not enough current from the power supply, so i ordered a beefier one just in case that is the cause. I have also tried an ubuntu server install and it didn’t show on it either… so must either be a weak power supply or a bad HC1… I’m hoping it’s the power supply. I’ll update next week when I get the new one in to test it out. It does not appear to be a DietPi issue, but want to follow up in case anyone else in the future has the same trouble.

usually we recommend to use external drives with own power supply to avoid issues if the usb port is not able to provide enough power.

The HC1 is defective. After getting a second one I quickly noticed it has a Sata indicator led… comes on when power is applied to the new one, never comes on on the defective one. So if anyone is wondering, the led is near the sata connector between the power and data portions of the connector. It should come on anytime power is applied to the board, regardless of whether a sata drive is attached or not. It stays on solid green on my new board with the drive connected.

thx for sharing. To bad that your board had some issues,.