Not related to the USB Hub but the Enclosure. Try the -d option with either auto or test or one of the USB profiles.
-d TYPE, --device=TYPE Specify device type to one of: ata, scsi, nvme[,NSID], sat[,auto][,N][+TYPE], usbcypress[,X], usbjmicron[,p][,x][,N], usbprolific, usbsunplus, marvell, areca,N/E, 3ware,N, hpt,L/M/N, megaraid,N, aacraid,H,L,ID, cciss,N, auto, test
It’s a 2.5" so I’ll just plug it straight in to the Vero.
Seagate5TB contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
fsck: Warning... fsck.ext4 for device /dev/sda1 exited with signal 9.
It just says that SMART is disabled.
osmc@osmc:~$ sudo smartctl -i /dev/sda1
smartctl 6.6 2016-05-31 r4324 [aarch64-linux-3.14.29-152-osmc] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: Seagate
Product: BUP BK
Revision: 0304
Compliance: SPC-4
User Capacity: 5,000,981,077,504 bytes [5.00 TB]
Logical block size: 512 bytes
Physical block size: 4096 bytes
Logical Unit id: 0x5000000000000001
Serial number: NA9W6CCJ
Device type: disk
Local Time is: Wed Sep 25 20:53:26 2019 MST
SMART support is: Available - device has SMART capability.
SMART support is: Disabled
Temperature Warning: Disabled or Not Supported
osmc@osmc:~$ sudo smartctl -t short -C /dev/sda1
smartctl 6.6 2016-05-31 r4324 [aarch64-linux-3.14.29-152-osmc] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
Short foreground self test failed [unsupported field in scsi command]Wouldn’t enabling SMART have to be done on a BIOS level?
Did you try with one of the -d opetions?
Also you run it with /dev/sda (the disk) not /dev/sda1 (the partition).
Also what does smartctl -a /dev/sda say?
What does smartctl -t short /dev/sda say?
Doing comands with just sda instead of sda1 gave me no output.
So that’s why I was doing sda1.
That’s odd. Did you try with sudo smartclt -a /dev/sda?
Also because of the enclosure I guess you still have to play with the -d type option.
osmc@osmc:~$ sudo smartctl -a /dev/sda
smartctl 6.6 2016-05-31 r4324 [aarch64-linux-3.14.29-152-osmc] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/sda: Unknown USB bridge [0x0bc2:0xab28 (0x100)]
Please specify device type with the -d option.
Use smartctl -h to get a usage summary
So I check it out but have no idea what to use.
-d TYPE, --device=TYPE
Specify device type to one of: ata, scsi, nvme[,NSID], sat[,auto][,N][+TYPE], usbcypress[,X], usbjmicron[,p][,x][,N], usbprolific, usbsunplus, marvell, areca,N/E, 3ware,N, hpt,L/M/N, megaraid,N, aacraid,H,L,ID, cciss,N, auto, testAs written earlier try different ones (each at a time):
-d auto
-d test
-d usbcypress
-d usbprolific
....
Just use the process of elimination?
Okay, I guess I have nothing to lose…
osmc@osmc:~$ sudo smartctl -d test -t short -C /dev/sda1
smartctl 6.6 2016-05-31 r4324 [aarch64-linux-3.14.29-152-osmc] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/sda1: Device of type 'scsi' [SCSI] detected
/dev/sda1: Device of type 'scsi' [SCSI] openedEvery usb* option gave me:
Read Device Identity failed: scsi error unsupported scsi opcode
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
Only -d test gave anything worth while, but that just says it’s SCSI.
Surely nothing too lose.
Still would suggest stop using sda1 but sda.
Seems that -d scsi should work.
So what does sudo smartctl -d scsi -a /dev/sda gives you?
osmc@osmc:~$ sudo smartctl -d scsi -t short -C /dev/sda
smartctl 6.6 2016-05-31 r4324 [aarch64-linux-3.14.29-152-osmc] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
Short foreground self test failed [unsupported field in scsi command]
osmc@osmc:~$ sudo smartctl -d test -t short -C /dev/sda
smartctl 6.6 2016-05-31 r4324 [aarch64-linux-3.14.29-152-osmc] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/sda: Unknown USB bridge [0x0bc2:0xab28 (0x100)]
Please specify device type with the -d option.
Use smartctl -h to get a usage summaryOk, let me do some test with my own enclosure to check what might work.
osmc@osmc:~$ sudo smartctl -d auto -t short -C /dev/sda
smartctl 6.6 2016-05-31 r4324 [aarch64-linux-3.14.29-152-osmc] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/sda: Unknown USB bridge [0x0bc2:0xab28 (0x100)]
Please specify device type with the -d option.
Use smartctl -h to get a usage summary
osmc@osmc:~$ sudo smartctl -d usbcypress -t short -C /dev/sda
smartctl 6.6 2016-05-31 r4324 [aarch64-linux-3.14.29-152-osmc] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
Read Device Identity failed: Unknown error
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
osmc@osmc:~$ sudo smartctl -d usbprolific -t short -C /dev/sda
smartctl 6.6 2016-05-31 r4324 [aarch64-linux-3.14.29-152-osmc] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
Read Device Identity failed: scsi error unsupported scsi opcode
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
osmc@osmc:~$ sudo smartctl -d usbjmicron -t short -C /dev/sda
smartctl 6.6 2016-05-31 r4324 [aarch64-linux-3.14.29-152-osmc] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
Smartctl open device: /dev/sda [USB JMicron] failed: scsi error unsupported scsi opcode
osmc@osmc:~$ sudo smartctl -d usbsunplus -t short -C /dev/sda
smartctl 6.6 2016-05-31 r4324 [aarch64-linux-3.14.29-152-osmc] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
Read Device Identity failed: scsi error unsupported scsi opcode
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
I don’t think anything is going to work because SMART is not enabled.
Is there a way outside of BIOS to enable SMART?
osmc@osmc:~$ sudo hdparm -I /dev/sda
/dev/sda:
ATA device, with non-removable media
Model Number: ST5000LM000-2AN170
Serial Number: WCJ1L927
Firmware Revision: 0001
Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
Standards:
Used: unknown (minor revision code 0x006d)
Supported: 10 9 8 7 6 5
Likely used: 10
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 268435455
LBA48 user addressable sectors: 9767541168
Logical Sector size: 512 bytes
Physical Sector size: 4096 bytes
Logical Sector-0 offset: 0 bytes
device size with M = 1024*1024: 4769307 MBytes
device size with M = 1000*1000: 5000981 MBytes (5000 GB)
cache/buffer size = unknown
Form Factor: 2.5 inch
Nominal Media Rotation Rate: 5526
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 1 Current = ?
Advanced power management level: 128
Recommended acoustic management value: 208, current value: 208
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* DOWNLOAD_MICROCODE
* Advanced Power Management feature set
Power-Up In Standby feature set
* SET_FEATURES required to spinup after power up
SET_MAX security extension
* 48-bit Address feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* General Purpose Logging feature set
* WRITE_{DMA|MULTIPLE}_FUA_EXT
* 64-bit World wide name
* WRITE_UNCORRECTABLE_EXT command
* {READ,WRITE}_DMA_EXT_GPL commands
* Segmented DOWNLOAD_MICROCODE
unknown 119[6]
* Gen1 signaling speed (1.5Gb/s)
* Gen2 signaling speed (3.0Gb/s)
* Gen3 signaling speed (6.0Gb/s)
* Native Command Queueing (NCQ)
* Phy event counters
* READ_LOG_DMA_EXT equivalent to READ_LOG_EXT
DMA Setup Auto-Activate optimization
Device-initiated interface power management
* Software settings preservation
unknown 78[7]
* SMART Command Transport (SCT) feature set
* SCT Write Same (AC2)
* SCT Data Tables (AC5)
unknown 206[7]
unknown 206[12] (vendor specific)
unknown 206[13] (vendor specific)
* reserved 69[4]
* reserved 69[7]
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
supported: enhanced erase
826min for SECURITY ERASE UNIT. 2min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 5000c500b5b5e2d8
NAA : 5
IEEE OUI : 000c50
Unique ID : 0b5b5e2d8
Checksum: correctosmc@osmc:~$ sudo smartctl --smart=on /dev/sda
smartctl 6.6 2016-05-31 r4324 [aarch64-linux-3.14.29-152-osmc] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/sda: Unknown USB bridge [0x0bc2:0xab28 (0x100)]
Please specify device type with the -d option.
Use smartctl -h to get a usage summaryWhat do you get if you run
sudo smartctl --all /dev/sdaosmc@osmc:~$ sudo smartctl --all /dev/sda
smartctl 6.6 2016-05-31 r4324 [aarch64-linux-3.14.29-152-osmc] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/sda: Unknown USB bridge [0x0bc2:0xab28 (0x100)]
Please specify device type with the -d option.
Use smartctl -h to get a usage summaryI still believe it is an issue with the USB enclosure and the missing type.
I just checked with the single enclosure that I currently have connected and it worked fine without any type definition. But I have to search I think I had one enclosure where I also needed to give the type in the past.
Maybe, but I tried every usb* listed in -h so…