Can't access SSD in Cloudshell on Ubuntu 18.04

Post Reply
RayBe
Posts: 7
Joined: Wed Nov 27, 2019 9:48 pm
languages_spoken: english
ODROIDs: Odroid XU4 in Cloudshell
Has thanked: 0
Been thanked: 0
Contact:

Can't access SSD in Cloudshell on Ubuntu 18.04

Unread post by RayBe » Wed Nov 27, 2019 10:05 pm

Hi All,

I have been using my XU4 board inside the Cloudshell1 for many years now.
Working perfectly when running Ubuntu 14.04.
Since Ubuntu no longer supports 14.04 i thought it was a good idea to make the switch to 18.04 (ubuntu-18.04.3-4.14-minimal-odroid-xu4-20190910.img.xz)

Inside de Cloudshell1 i have installed a 120GB intel 330 SSD which worked perfectly under ubuntu 14.04.
I wrote the 18.04 image to a new SD card using Etcher. The system boots perfectly.

My problem:
I can't access the SSD.
When i try the commands fdisk or blkid on that drive the terminal window just freezes, nothing happens.

lsblk shows:

Code: Select all

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda           8:0    0 917.2G  0 disk 
└─sda1        8:1    0 111.8G  0 part 
The size of sda is wrong it should be 120G

lsusb -t shows:

Code: Select all

/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 5000M
        |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 5000M
            |__ Port 1: Dev 4, If 0, Class=Hub, Driver=hub/4p, 5000M
                |__ Port 3: Dev 6, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
            |__ Port 4: Dev 5, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 480M
        |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
            |__ Port 1: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M
            |__ Port 2: Dev 5, If 0, Class=Vendor Specific Class, Driver=cp210x, 12M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=exynos-ohci/3p, 12M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=exynos-ehci/3p, 480M
dmesg | grep usb shows:

Code: Select all

[    0.000000] Kernel command line: usb-storage.quirks=05e3:0735,05e3:0616,05e3:0610,0x05e3:0x0735,0x05e3:0x0616,0x05e3:0x0610:u console=tty1 console=ttySAC2,115200n8 root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro fsck.repair=yes net.ifnames=0  HPD=true vout=hdmi usbhid.quirks=0x0eef:0x0005:0x0004 smsc95xx.macaddr=00:1e:06:61:7a:39 false s5p_mfc.mem=16M
[    0.297805] usbcore: registered new interface driver usbfs
[    0.297871] usbcore: registered new interface driver hub
[    0.298041] usbcore: registered new device driver usb
[    0.853629] samsung-usb2-phy 12130000.phy: 12130000.phy supply vbus not found, using dummy regulator
[    0.854676] exynos5_usb3drd_phy 12100000.phy: 12100000.phy supply vbus not found, using dummy regulator
[    0.854761] exynos5_usb3drd_phy 12100000.phy: 12100000.phy supply vbus-boost not found, using dummy regulator
[    0.855137] exynos5_usb3drd_phy 12500000.phy: 12500000.phy supply vbus not found, using dummy regulator
[    0.855223] exynos5_usb3drd_phy 12500000.phy: 12500000.phy supply vbus-boost not found, using dummy regulator
[    2.014674] usbcore: registered new interface driver r8152
[    2.019806] usbcore: registered new interface driver cdc_ether
[    2.025610] usbcore: registered new interface driver cdc_subset
[    2.043161] exynos-ehci 12110000.usb: EHCI Host Controller
[    2.048305] exynos-ehci 12110000.usb: new USB bus registered, assigned bus number 1
[    2.056210] exynos-ehci 12110000.usb: irq 80, io mem 0x12110000
[    2.074465] exynos-ehci 12110000.usb: USB 2.0 started, EHCI 1.00
[    2.079314] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.085794] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.092982] usb usb1: Product: EHCI Host Controller
[    2.097829] usb usb1: Manufacturer: Linux 4.14.150-170 ehci_hcd
[    2.103753] usb usb1: SerialNumber: 12110000.usb
[    2.126577] exynos-ohci 12120000.usb: USB Host Controller
[    2.131735] exynos-ohci 12120000.usb: new USB bus registered, assigned bus number 2
[    2.139445] exynos-ohci 12120000.usb: irq 80, io mem 0x12120000
[    2.206701] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[    2.212049] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.219834] usb usb2: Product: USB Host Controller
[    2.224001] usb usb2: Manufacturer: Linux 4.14.150-170 ohci_hcd
[    2.229891] usb usb2: SerialNumber: 12120000.usb
[    4.013491] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[    4.020113] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.027306] usb usb3: Product: xHCI Host Controller
[    4.032156] usb usb3: Manufacturer: Linux 4.14.150-170 xhci-hcd
[    4.038048] usb usb3: SerialNumber: xhci-hcd.3.auto
[    4.070253] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[    4.078355] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[    4.085016] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.092210] usb usb4: Product: xHCI Host Controller
[    4.097060] usb usb4: Manufacturer: Linux 4.14.150-170 xhci-hcd
[    4.102964] usb usb4: SerialNumber: xhci-hcd.3.auto
[    4.167727] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
[    4.174362] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.181552] usb usb5: Product: xHCI Host Controller
[    4.186421] usb usb5: Manufacturer: Linux 4.14.150-170 xhci-hcd
[    4.192295] usb usb5: SerialNumber: xhci-hcd.6.auto
[    4.224496] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
[    4.232597] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003
[    4.239262] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.246454] usb usb6: Product: xHCI Host Controller
[    4.251304] usb usb6: Manufacturer: Linux 4.14.150-170 xhci-hcd
[    4.257197] usb usb6: SerialNumber: xhci-hcd.6.auto
[    4.574505] usb 3-1: new high-speed USB device number 2 using xhci-hcd
[    4.770115] usb 3-1: New USB device found, idVendor=05e3, idProduct=0610
[    4.775370] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    4.782477] usb 3-1: Product: USB2.0 Hub
[    4.786338] usb 3-1: Manufacturer: GenesysLogic
[    4.894595] usb 4-1: new SuperSpeed USB device number 2 using xhci-hcd
[    4.921899] usb 4-1: New USB device found, idVendor=05e3, idProduct=0616
[    4.927177] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    4.934258] usb 4-1: Product: USB3.0 Hub
[    4.938163] usb 4-1: Manufacturer: GenesysLogic
[    5.134498] usb 3-1.2: new high-speed USB device number 3 using xhci-hcd
[    5.240388] usb 3-1.2: New USB device found, idVendor=2109, idProduct=2812
[    5.245809] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    5.253088] usb 3-1.2: Product: USB2.0 Hub             
[    5.258282] usb 3-1.2: Manufacturer: VIA Labs, Inc.         
[    5.322642] usb 4-1.2: new SuperSpeed USB device number 3 using xhci-hcd
[    5.434542] usb 6-1: new SuperSpeed USB device number 2 using xhci-hcd
[    5.459350] usb 6-1: New USB device found, idVendor=0bda, idProduct=8153
[    5.464603] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[    5.471723] usb 6-1: Product: USB 10/100/1000 LAN
[    5.476385] usb 6-1: Manufacturer: Realtek
[    5.480451] usb 6-1: SerialNumber: 000001000000
[    5.592399] usb 4-1.2: New USB device found, idVendor=2109, idProduct=0812
[    5.597820] usb 4-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    5.605104] usb 4-1.2: Product: USB3.0 Hub             
[    5.610289] usb 4-1.2: Manufacturer: VIA Labs, Inc.         
[    5.648595] usb 6-1: reset SuperSpeed USB device number 2 using xhci-hcd
[    5.682440] usb 3-1.2.1: new high-speed USB device number 4 using xhci-hcd
[    5.799963] usb 3-1.2.1: New USB device found, idVendor=2109, idProduct=2812
[    5.806552] usb 3-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    5.813987] usb 3-1.2.1: Product: USB2.0 Hub             
[    5.819362] usb 3-1.2.1: Manufacturer: VIA Labs, Inc.         
[    5.938449] usb 3-1.2.2: new full-speed USB device number 5 using xhci-hcd
[    6.056192] usb 3-1.2.2: New USB device found, idVendor=10c4, idProduct=ea60
[    6.061798] usb 3-1.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    6.069238] usb 3-1.2.2: Product: CP2102 USB to UART Bridge Controller
[    6.075753] usb 3-1.2.2: Manufacturer: Silicon Labs
[    6.080608] usb 3-1.2.2: SerialNumber: 0001
[    6.142687] usb 4-1.2.1: new SuperSpeed USB device number 4 using xhci-hcd
[    6.405840] usb 4-1.2.1: New USB device found, idVendor=2109, idProduct=0812
[    6.411440] usb 4-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    6.418892] usb 4-1.2.1: Product: USB3.0 Hub             
[    6.424257] usb 4-1.2.1: Manufacturer: VIA Labs, Inc.         
[    6.526657] usb 4-1.2.4: new SuperSpeed USB device number 5 using xhci-hcd
[    6.553398] usb 4-1.2.4: New USB device found, idVendor=05e3, idProduct=0735
[    6.559002] usb 4-1.2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    6.566446] usb 4-1.2.4: Product: USB3.0 SATA Bridge
[    6.571376] usb 4-1.2.4: Manufacturer: USB Storage
[    6.576145] usb 4-1.2.4: SerialNumber: 0000000000000033
[    6.591179] usb-storage 4-1.2.4:1.0: USB Mass Storage device detected
[    6.598664] scsi host0: usb-storage 4-1.2.4:1.0
[    6.601933] usbcore: registered new interface driver usb-storage
[    6.608216] usbcore: registered new interface driver uas
[    6.834522] usb 4-1.2.1.3: new SuperSpeed USB device number 6 using xhci-hcd
[    6.859570] usb 4-1.2.1.3: New USB device found, idVendor=1058, idProduct=107c
[    6.865337] usb 4-1.2.1.3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[    6.872958] usb 4-1.2.1.3: Product: Elements 107C
[    6.877638] usb 4-1.2.1.3: Manufacturer: Western Digital
[    6.882919] usb 4-1.2.1.3: SerialNumber: 5758373144413441304A5236
[    6.889917] usb-storage 4-1.2.1.3:1.0: USB Mass Storage device detected
[    6.900015] scsi host1: usb-storage 4-1.2.1.3:1.0
[   37.950715] usb 4-1.2.4: reset SuperSpeed USB device number 5 using xhci-hcd
[   42.979617] usbcore: registered new interface driver usbserial
[   42.979732] usbcore: registered new interface driver usbserial_generic
[   42.979795] usbserial: USB Serial support registered for generic
[   42.982932] usbcore: registered new interface driver cp210x
[   42.982995] usbserial: USB Serial support registered for cp210x
[   42.985382] usb 3-1.2.2: cp210x converter now attached to ttyUSB0
First i thought it was a gas driver problem, but the driver doesn't seem to be loaded for the drive.

I have been trying to get this fixed for days now. Sadly nothing seems to help.
Any pointers or help is much appreciated.

Thanks upfront!

best regards,
Raymond

User avatar
odroid
Site Admin
Posts: 32690
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 212 times
Been thanked: 364 times
Contact:

Re: Can't access SSD in Cloudshell on Ubuntu 18.04

Unread post by odroid » Thu Nov 28, 2019 5:30 pm

Did you connect "WD Elements 107C" storage together?

Code: Select all

[    6.834522] usb 4-1.2.1.3: new SuperSpeed USB device number 6 using xhci-hcd
[    6.859570] usb 4-1.2.1.3: New USB device found, idVendor=1058, idProduct=107c
[    6.865337] usb 4-1.2.1.3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[    6.872958] usb 4-1.2.1.3: Product: Elements 107C
[    6.877638] usb 4-1.2.1.3: Manufacturer: Western Digital
[    6.882919] usb 4-1.2.1.3: SerialNumber: 5758373144413441304A5236
[    6.889917] usb-storage 4-1.2.1.3:1.0: USB Mass Storage device detected
The original CloudShell had a GL3321G2 controller which had VID:PID = 05E3:0735.

RayBe
Posts: 7
Joined: Wed Nov 27, 2019 9:48 pm
languages_spoken: english
ODROIDs: Odroid XU4 in Cloudshell
Has thanked: 0
Been thanked: 0
Contact:

Re: Can't access SSD in Cloudshell on Ubuntu 18.04

Unread post by RayBe » Thu Nov 28, 2019 11:32 pm

Hi,

@Odroid, thanks for your reply.
odroid wrote:
Thu Nov 28, 2019 5:30 pm
Did you connect "WD Elements 107C" storage together?
Yes i did.
Using it together with my intel 330 SSD in the CloudShell with ubuntu 14.04 it worked like a charm.
odroid wrote:
Thu Nov 28, 2019 5:30 pm
The original CloudShell had a GL3321G2 controller which had VID:PID = 05E3:0735.
I have the original CloudShell, the dmesg output i posted also shows the VID:PID = 05E3:0735.
I also added the following in to my boot.ini:

Code: Select all

usb-storage.quirks=05e3:0735,05e3:0616,05e3:0610,0x05e3:0x0735,0x05e3:0x0616,0x05e3:0x0610:u
Just to make sure that UAS isn't being used for any device connected to the Genesys bridge.

thanks for helping,
br,

Raymond

User avatar
odroid
Site Admin
Posts: 32690
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 212 times
Been thanked: 364 times
Contact:

Re: Can't access SSD in Cloudshell on Ubuntu 18.04

Unread post by odroid » Fri Nov 29, 2019 10:14 am

There are two USB 3.0 storage devices in your lsusb -t output obviously.

Code: Select all

/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 5000M
        |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 5000M
            |__ Port 1: Dev 4, If 0, Class=Hub, Driver=hub/4p, 5000M
                |__ Port 3: Dev 6, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
            |__ Port 4: Dev 5, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
But you might not be able to find any clue in the dmesg like me.
Remove other USB devices and connect "GL3321G2" board only and capture the dmesg output again for easier trace.
"lsusb", "lsusb -t" and "dmesg" outputs will be helpful.

RayBe
Posts: 7
Joined: Wed Nov 27, 2019 9:48 pm
languages_spoken: english
ODROIDs: Odroid XU4 in Cloudshell
Has thanked: 0
Been thanked: 0
Contact:

Re: Can't access SSD in Cloudshell on Ubuntu 18.04

Unread post by RayBe » Fri Nov 29, 2019 9:44 pm

Hi odroid,

The only things connected to the USB3 ports of my Odroid XU4 is a TP-Link UH720 powered USB3 hub and the CloudShell USB-SATA-Bridge controller.
With that setup i got the output as shown below.
(Today i found out that if i _only_ connect the devices as described above, the system does not boot, i have to add the WD-USB-HDD to boot the system, after that i disconnect the WD-USB-HDD and got the output as shown below)

Maybe you wonder why i connect a powered USB-hub, let me explain.
Because the power supply to the XU4 (4A iirc) is not strong enough to power the Odroid XU4 and the USB-SATA-Bridge controller at the same time, i came up with the following solution:
The _only_ thing connected to the Odroid XU4's USB3 port is the TP-Link UH720 powered USB3 hub. To that hub i connected the USB3 cable that is connected to the CloudShell USB-SATA-Bridge controller board, that way it gets its power from the USB-hub ;) .
All other USB-devices (a Z-wave controller and the WD-HDD) are normally also connected to the USB-hub.
That setup has been working for a couple of years when using Ubuntu 14.04.

Sorry I didn't mention the USB-hub before, i didn't think it matters to the setup.
I do mention it now to be verbose :)

lsusb shows:

Code: Select all

Bus 006 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. 
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 005: ID 05e3:0735 Genesys Logic, Inc. 
Bus 004 Device 004: ID 2109:0812 VIA Labs, Inc. VL812 Hub
Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
Bus 004 Device 002: ID 05e3:0616 Genesys Logic, Inc. hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 003 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
lsusb -t shows:

Code: Select all

/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 5000M
        |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 5000M
            |__ Port 1: Dev 4, If 0, Class=Hub, Driver=hub/4p, 5000M
            |__ Port 4: Dev 5, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 480M
        |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
            |__ Port 1: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=exynos-ohci/3p, 12M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=exynos-ehci/3p, 480M
dmesg | grep usb shows:

Code: Select all

[    0.000000] Kernel command line: usb-storage.quirks=05e3:0735,05e3:0616,05e3:0610,0x05e3:0x0735,0x05e3:0x0616,0x05e3:0x0610:u console=tty1 console=ttySAC2,115200n8 root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro fsck.repair=yes net.ifnames=0  HPD=true vout=hdmi usbhid.quirks=0x0eef:0x0005:0x0004 smsc95xx.macaddr=00:1e:06:61:7a:39 false s5p_mfc.mem=16M
[    0.299347] usbcore: registered new interface driver usbfs
[    0.299417] usbcore: registered new interface driver hub
[    0.299566] usbcore: registered new device driver usb
[    0.854954] samsung-usb2-phy 12130000.phy: 12130000.phy supply vbus not found, using dummy regulator
[    0.855997] exynos5_usb3drd_phy 12100000.phy: 12100000.phy supply vbus not found, using dummy regulator
[    0.856083] exynos5_usb3drd_phy 12100000.phy: 12100000.phy supply vbus-boost not found, using dummy regulator
[    0.856479] exynos5_usb3drd_phy 12500000.phy: 12500000.phy supply vbus not found, using dummy regulator
[    0.856566] exynos5_usb3drd_phy 12500000.phy: 12500000.phy supply vbus-boost not found, using dummy regulator
[    2.014145] usbcore: registered new interface driver r8152
[    2.019294] usbcore: registered new interface driver cdc_ether
[    2.025097] usbcore: registered new interface driver cdc_subset
[    2.042711] exynos-ehci 12110000.usb: EHCI Host Controller
[    2.047853] exynos-ehci 12110000.usb: new USB bus registered, assigned bus number 1
[    2.055732] exynos-ehci 12110000.usb: irq 80, io mem 0x12110000
[    2.075964] exynos-ehci 12110000.usb: USB 2.0 started, EHCI 1.00
[    2.080797] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.087294] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.094481] usb usb1: Product: EHCI Host Controller
[    2.099358] usb usb1: Manufacturer: Linux 4.14.150-170 ehci_hcd
[    2.105224] usb usb1: SerialNumber: 12110000.usb
[    2.128072] exynos-ohci 12120000.usb: USB Host Controller
[    2.133233] exynos-ohci 12120000.usb: new USB bus registered, assigned bus number 2
[    2.140943] exynos-ohci 12120000.usb: irq 80, io mem 0x12120000
[    2.208202] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[    2.213556] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.221383] usb usb2: Product: USB Host Controller
[    2.225510] usb usb2: Manufacturer: Linux 4.14.150-170 ohci_hcd
[    2.231399] usb usb2: SerialNumber: 12120000.usb
[    4.012961] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[    4.019586] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.026778] usb usb3: Product: xHCI Host Controller
[    4.031625] usb usb3: Manufacturer: Linux 4.14.150-170 xhci-hcd
[    4.037521] usb usb3: SerialNumber: xhci-hcd.3.auto
[    4.069782] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[    4.077828] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[    4.084489] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.091681] usb usb4: Product: xHCI Host Controller
[    4.096530] usb usb4: Manufacturer: Linux 4.14.150-170 xhci-hcd
[    4.102422] usb usb4: SerialNumber: xhci-hcd.3.auto
[    4.167204] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
[    4.173831] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.181021] usb usb5: Product: xHCI Host Controller
[    4.185872] usb usb5: Manufacturer: Linux 4.14.150-170 xhci-hcd
[    4.191764] usb usb5: SerialNumber: xhci-hcd.6.auto
[    4.223970] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
[    4.232070] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003
[    4.238734] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.245925] usb usb6: Product: xHCI Host Controller
[    4.250776] usb usb6: Manufacturer: Linux 4.14.150-170 xhci-hcd
[    4.256669] usb usb6: SerialNumber: xhci-hcd.6.auto
[    4.579995] usb 3-1: new high-speed USB device number 2 using xhci-hcd
[    4.769302] usb 3-1: New USB device found, idVendor=05e3, idProduct=0610
[    4.774556] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    4.781660] usb 3-1: Product: USB2.0 Hub
[    4.785547] usb 3-1: Manufacturer: GenesysLogic
[    4.892083] usb 4-1: new SuperSpeed USB device number 2 using xhci-hcd
[    4.918852] usb 4-1: New USB device found, idVendor=05e3, idProduct=0616
[    4.924114] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    4.931449] usb 4-1: Product: USB3.0 Hub
[    4.935156] usb 4-1: Manufacturer: GenesysLogic
[    5.127977] usb 3-1.2: new high-speed USB device number 3 using xhci-hcd
[    5.233382] usb 3-1.2: New USB device found, idVendor=2109, idProduct=2812
[    5.238796] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    5.246076] usb 3-1.2: Product: USB2.0 Hub             
[    5.251271] usb 3-1.2: Manufacturer: VIA Labs, Inc.         
[    5.316070] usb 4-1.2: new SuperSpeed USB device number 3 using xhci-hcd
[    5.448037] usb 6-1: new SuperSpeed USB device number 2 using xhci-hcd
[    5.472846] usb 6-1: New USB device found, idVendor=0bda, idProduct=8153
[    5.478105] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[    5.485203] usb 6-1: Product: USB 10/100/1000 LAN
[    5.489886] usb 6-1: Manufacturer: Realtek
[    5.493952] usb 6-1: SerialNumber: 000001000000
[    5.579399] usb 4-1.2: New USB device found, idVendor=2109, idProduct=0812
[    5.584823] usb 4-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    5.592110] usb 4-1.2: Product: USB3.0 Hub             
[    5.597290] usb 4-1.2: Manufacturer: VIA Labs, Inc.         
[    5.671935] usb 3-1.2.1: new high-speed USB device number 4 using xhci-hcd
[    5.680081] usb 6-1: reset SuperSpeed USB device number 2 using xhci-hcd
[    5.793402] usb 3-1.2.1: New USB device found, idVendor=2109, idProduct=2812
[    5.799010] usb 3-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    5.806456] usb 3-1.2.1: Product: USB2.0 Hub             
[    5.811819] usb 3-1.2.1: Manufacturer: VIA Labs, Inc.         
[    6.000081] usb 4-1.2.1: new SuperSpeed USB device number 4 using xhci-hcd
[    6.263439] usb 4-1.2.1: New USB device found, idVendor=2109, idProduct=0812
[    6.269034] usb 4-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    6.276482] usb 4-1.2.1: Product: USB3.0 Hub             
[    6.281849] usb 4-1.2.1: Manufacturer: VIA Labs, Inc.         
[    6.380156] usb 4-1.2.4: new SuperSpeed USB device number 5 using xhci-hcd
[    6.406881] usb 4-1.2.4: New USB device found, idVendor=05e3, idProduct=0735
[    6.412480] usb 4-1.2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    6.419930] usb 4-1.2.4: Product: USB3.0 SATA Bridge
[    6.424862] usb 4-1.2.4: Manufacturer: USB Storage
[    6.429629] usb 4-1.2.4: SerialNumber: 0000000000000033
[    6.444775] usb-storage 4-1.2.4:1.0: USB Mass Storage device detected
[    6.463851] scsi host0: usb-storage 4-1.2.4:1.0
[    6.467203] usbcore: registered new interface driver usb-storage
[    6.473453] usbcore: registered new interface driver uas
[    6.692004] usb 4-1.2.1.3: new SuperSpeed USB device number 6 using xhci-hcd
[    6.717091] usb 4-1.2.1.3: New USB device found, idVendor=1058, idProduct=107c
[    6.722859] usb 4-1.2.1.3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[    6.730478] usb 4-1.2.1.3: Product: Elements 107C
[    6.735153] usb 4-1.2.1.3: Manufacturer: Western Digital
[    6.740439] usb 4-1.2.1.3: SerialNumber: 5758373144413441304A5236
[    6.747264] usb-storage 4-1.2.1.3:1.0: USB Mass Storage device detected
[    6.753553] scsi host1: usb-storage 4-1.2.1.3:1.0
[   37.952211] usb 4-1.2.4: reset SuperSpeed USB device number 5 using xhci-hcd
[  394.342251] usb 4-1.2.1.3: USB disconnect, device number 6
Thanks for helping and looking into my problem,

br,
Raymond

User avatar
odroid
Site Admin
Posts: 32690
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 212 times
Been thanked: 364 times
Contact:

Re: Can't access SSD in Cloudshell on Ubuntu 18.04

Unread post by odroid » Sun Dec 01, 2019 7:41 pm

Thank you for the detail explanation but still don't know what causes "USB reset".

Code: Select all

[   37.952211] usb 4-1.2.4: reset SuperSpeed USB device number 5 using xhci-hcd
[  394.342251] usb 4-1.2.1.3: USB disconnect, device number 6
Did you use Kernel 3.10 on Ubuntu 14.04?
What happens if you remove the usb-storage.quirks Kernel parameter?
Do you have a Linux PC which runs Kernel 4.14 or higher to test the USB storage?

Anyway, we will try to find the old Cloudshell in our office storage to check the issue.

RayBe
Posts: 7
Joined: Wed Nov 27, 2019 9:48 pm
languages_spoken: english
ODROIDs: Odroid XU4 in Cloudshell
Has thanked: 0
Been thanked: 0
Contact:

Re: Can't access SSD in Cloudshell on Ubuntu 18.04

Unread post by RayBe » Tue Dec 03, 2019 4:03 pm

odroid wrote:
Sun Dec 01, 2019 7:41 pm
Did you use Kernel 3.10 on Ubuntu 14.04?
I am using your default image:

Code: Select all

ubuntu-14.04lts-server-odroid-xu3-20150725.img
odroid wrote:
Sun Dec 01, 2019 7:41 pm
What happens if you remove the usb-storage.quirks Kernel parameter?
If i remember correctly at first i didn't use it at all.
odroid wrote:
Sun Dec 01, 2019 7:41 pm
Do you have a Linux PC which runs Kernel 4.14 or higher to test the USB storage?
Sadly no, i only use ARM based machines :)
odroid wrote:
Sun Dec 01, 2019 7:41 pm
Anyway, we will try to find the old Cloudshell in our office storage to check the issue.
Awesome that you guys are willing to do so. I hope you still have one in your storage space.

Again, thank you very much for helping.
I have been using your products for a few years now, with great joy!

best regards,
Raymond

User avatar
rooted
Posts: 6899
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 270 times
Been thanked: 64 times
Contact:

Re: Can't access SSD in Cloudshell on Ubuntu 18.04

Unread post by rooted » Wed Dec 04, 2019 8:32 pm

If you have any device to test the SSD in that's what I would do, it could be a coincidence that you changed OS and the device stopped working properly. Perhaps it is a hardware fault with the drive or the USB to SATA controller on the cloudshell.

RayBe
Posts: 7
Joined: Wed Nov 27, 2019 9:48 pm
languages_spoken: english
ODROIDs: Odroid XU4 in Cloudshell
Has thanked: 0
Been thanked: 0
Contact:

Re: Can't access SSD in Cloudshell on Ubuntu 18.04

Unread post by RayBe » Wed Dec 04, 2019 11:13 pm

Thanks for your input rooted.

I changed back to the 14.04 image with a different sd card several times. Every time with 14.04 the drive and controller works just fine.
And every time I use 18.04 the drive doesn’t work anymore.

Br
Raymond

User avatar
rooted
Posts: 6899
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 270 times
Been thanked: 64 times
Contact:

Re: Can't access SSD in Cloudshell on Ubuntu 18.04

Unread post by rooted » Thu Dec 05, 2019 1:13 am

That rules out a hardware fault, I don't understand what's causing the issue since I've been running a cloudshell 1 on the latest Odroid kernel for years.

The only difference is I'm running Debian instead of Ubuntu but the kernel which drives the hardware is the same on both OS.

Do you have a mechanical 2.5" drive you can test to see if it's some strange quirk with the SSD and the 4.14.y kernel? I don't have an SSD to test in the cloudshell, mine runs a 500gb mechanical drive.

RayBe
Posts: 7
Joined: Wed Nov 27, 2019 9:48 pm
languages_spoken: english
ODROIDs: Odroid XU4 in Cloudshell
Has thanked: 0
Been thanked: 0
Contact:

Re: Can't access SSD in Cloudshell on Ubuntu 18.04

Unread post by RayBe » Fri Dec 06, 2019 4:10 pm

Hi root,

Sadly I don’t own a mechanical drive.
I hope Odroid wil find a cloudshell in their storage space.
Thanks for trying to help.

Br,
Raymond

User avatar
odroid
Site Admin
Posts: 32690
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 212 times
Been thanked: 364 times
Contact:

Re: Can't access SSD in Cloudshell on Ubuntu 18.04

Unread post by odroid » Sun Dec 08, 2019 6:36 pm

Finally, we found one and tested.
We installed our latest Ubuntu 18.04.3 minimal image and updated the Kernel to 4.14.157.
And connected a Samsung 860 EVO 250GB SSD. It worked fine out of the box.
We didn't edit boot.ini file.

Storage access performance looks fine.

Code: Select all

root@odroid:/media/ssd# dd if=/dev/zero of=test oflag=direct bs=8M count=128
128+0 records in
128+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 3.83589 s, 280 MB/s
root@odroid:/media/ssd# dd if=test of=/dev/null iflag=direct bs=8M
128+0 records in
128+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 4.48258 s, 240 MB/s

root@odroid:/media/ssd# lsusb -t
/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
   |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 5000M
       |__ Port 1: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 480M
       |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 12M
       |__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 12M
       |__ Port 2: Dev 3, If 2, Class=Human Interface Device, Driver=usbhid, 12M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=exynos-ohci/3p, 12M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=exynos-ehci/3p, 480M

root@odroid:/media/ssd# lsusb
Bus 006 Device 002: ID 0bda:8153 Realtek Semiconductor Corp.
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 003: ID 05e3:0735 Genesys Logic, Inc.
Bus 004 Device 002: ID 05e3:0616 Genesys Logic, Inc. hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
It is very hard to know why your CloudShell couldn't detect the storage with Kernel 4.14. :(

RayBe
Posts: 7
Joined: Wed Nov 27, 2019 9:48 pm
languages_spoken: english
ODROIDs: Odroid XU4 in Cloudshell
Has thanked: 0
Been thanked: 0
Contact:

Re: Can't access SSD in Cloudshell on Ubuntu 18.04

Unread post by RayBe » Sun Dec 08, 2019 9:57 pm

Odroid,

Thanks for investigating and even installing and looking for the cloudshell.
Very much appreciated!
odroid wrote:
Sun Dec 08, 2019 6:36 pm
We installed our latest Ubuntu 18.04.3 minimal image and updated the Kernel to 4.14.157
I also use that image:

Code: Select all

ubuntu-18.04.3-4.14-minimal-odroid-xu4-20190910.img
but i didn't update the Kernel to 4.14.157.
Maybe that will do the trick.
How did you perform the update and is it safe to do?
I am on Kernel 4.14.150-170.

If that doesn't help, i think its safe to say that my intel SSD isn't compatible with 18.04 and the cloudshell.
What do you think?

best regards,
Raymond

User avatar
rooted
Posts: 6899
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 270 times
Been thanked: 64 times
Contact:

Re: Can't access SSD in Cloudshell on Ubuntu 18.04

Unread post by rooted » Mon Dec 09, 2019 2:39 am

Login over SSH and

Code: Select all

sudo apt update
sudo apt dist-upgrade

User avatar
odroid
Site Admin
Posts: 32690
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 212 times
Been thanked: 364 times
Contact:

Re: Can't access SSD in Cloudshell on Ubuntu 18.04

Unread post by odroid » Mon Dec 09, 2019 1:38 pm

4.14.150-170 was okay too.

Since we don't have the same SSD, it is very hard to make a firm conclusion.
But I don't think the Intel SSD is a root cause. Your phenomenon is very weird and mysterious.

We also test the latest experimental Kernel 5.4 and it also worked fine.
viewtopic.php?f=184&t=36947

Post Reply

Return to “CloudShell”

Who is online

Users browsing this forum: No registered users and 0 guests