Hi,
I’ve connected VERBATIM Store ´n´ Go Portable SSD 240GB to Turris MOX F module, but no new device file was created. Therfore Forris, LuCi nor blkid see the new device.
Disk model is: HFS512G3
On connection, there is only one new line i messages:
kernel: [ 2020.288122] usb 3-4: new SuperSpeed USB device number 4 using xhci_hcd
I’ve connected the disk to a windows box and it found it including factory pre-created FAT32 system with some vendor files, like product manual, so I assume the disk itself to be OK.
lsusb lists the device bus 3 device 4:
root@pozitron:~# lsusb
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 0781:5583 SanDisk Corp. Ultra Fit
Bus 005 Device 002: ID 1058:25a2 Western Digital Technologies, Inc. Elements 25A2
Bus 003 Device 004: ID 18a5:0422 Verbatim, Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
but there is no device file for it, I can see only /dev/sda and /dev/sdb which belongs to SanDisk and WD disk.
Should I install some drivers to get the disk working?
Thanks for any advice.
Ales
I would try fdisk or cfdisk or/and hdparam to check that usb dongle … if you see it in fdisk/cfdisk just format it from scratch as GPT with some decent filesystem. If you do not see it, use windows disk management console to do the same.
… any factory partition and very possibly as MBR cause sometimes that you do not see it correctly in “turris” . I have similar issues with my “kingston” some time ago.
1 Like
There is no device file (whereas on my notebook with Fedora30 it works like a charm), so no [c]fdisk. I’ll try to drop partition table usnig Fedora and create new GPT and I’ll see it it helps.
Thanks for your inputs!
After some testing, the issue has nothing to do with partition table type, I’ve plugged the drive into my Omnia and it was immediatelly detected, device file for the drive was created, so blkid, lsdev worked like a charm. I was able to create GPT table and format the drive using ext4 without any issue - so the disk is ok.
I’ve compared kmod-usb* modules on omnia (Turris OS 3 ) and on MOX and (Turris OS 4) and added USB disk support modules to have as much as possible same setup ad on Omnia and now on MOX device file is created:
Oct 12 20:29:32 pozitron kernel: [91244.764281] usb 3-4: new SuperSpeed USB device number 4 using xhci_hcd
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0781:5583 SanDisk Corp. Ultra Fit
Bus 005 Device 002: ID 1058:25a2 Western Digital Technologies, Inc. Elements 25A2
Bus 003 Device 004: ID 18a5:0422 Verbatim, Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
ct 12 21:21:24 pozitron kernel: [ 166.821213] usb 3-4: new SuperSpeed USB device number 3 using xhci_hcd
Oct 12 21:21:24 pozitron kernel: [ 166.880637] scsi host2: uas
Oct 12 21:21:24 pozitron kernel: [ 166.889271] scsi 2:0:0:0: Direct-Access Verbatim Portable SSD 0 PQ: 0 ANSI: 6
Oct 12 21:21:24 pozitron kernel: [ 166.900540] sd 2:0:0:0: [sdc] 468862128 512-byte logical blocks: (240 GB/224 GiB)
Oct 12 21:21:24 pozitron kernel: [ 166.908821] sd 2:0:0:0: [sdc] Write Protect is off
Oct 12 21:21:24 pozitron kernel: [ 166.913929] sd 2:0:0:0: [sdc] Mode Sense: 43 00 00 00
Oct 12 21:21:24 pozitron kernel: [ 166.919634] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Oct 12 21:21:24 pozitron kernel: [ 166.930906] sd 2:0:0:0: [sdc] Optimal transfer size 33553920 bytes
Oct 12 21:21:24 pozitron kernel: [ 166.943178] sd 2:0:0:0: [sdc] Attached SCSI disk
Unfortnuatelly MOX did not boot whlie the disk is connected. I can run fsck on /dev/sdc on the disk filesystem, but blkid stuck and did not return prompt (it dispaly mmcblk, sda, sdb as expected).
Manually, if I connect the disk after MOX is running, I can even smoothly mount /dev/sdc.
I have no clue why MOX is not able to boot with SSD USB3 drive connected, but it makes the disk impossible to use with MOX.