External HDD mount

Hi, I’m trying to access an external HDD USB3.0 from osmc latest version. I can’t see it. In terminal I launched :

osmc@osmc:/$ lsblk
sda 8:0 0 7.3T 0 disk
|-sda1 8:1 0 16M 0 part
`-sda2 8:2 0 7.3T 0 part

mmcblk0 179:0 0 14.9G 0 disk
|-mmcblk0p1 179:1 0 63M 0 part /media/RECOVERY
|-mmcblk0p2 179:2 0 1K 0 part
|-mmcblk0p5 179:5 0 32M 0 part /media/SETTINGS
|-mmcblk0p6 179:6 0 80M 0 part /boot
`-mmcblk0p7 179:7 0 14.7G 0 part /

One is my sd card the 7.3T is my external HDD. I can’t access because isn’t mounted. Why is it unmounted? Can I access it?

I tried to report also

sudo fdisk -l

but I think this freeze my shell… without sudo:

cannot open /dev/sda: Permission denied

HDD works fine with Windows.


Does it have its own power supply? Otherwise I suggest to use a powered hub

Yes, it has an external power supply .

Please post some logs

[ 21.284965] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[ 21.285365] sd 0:0:0:0: [sda] 15628052480 512-byte logical blocks: (8.00 TB/7.28 TiB)
[ 21.285377] sd 0:0:0:0: [sda] 4096-byte physical blocks
[ 21.285907] sd 0:0:0:0: [sda] Write Protect is off
[ 21.285916] sd 0:0:0:0: [sda] Mode Sense: 47 00 10 08
[ 21.286493] sd 0:0:0:0: [sda] No Caching mode page found
[ 21.286505] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 21.289859] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[ 22.266122] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 22.266148] sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current]
[ 22.266155] sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0
[ 22.266167] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x88 88 00 00 00 00 03 a3 81 27 d8 00 00 00 08 00 00
[ 22.266179] print_req_error: critical medium error, dev sda, sector 15628052440
[ 22.266187] Buffer I/O error on dev sda, logical block 1953506555, async page read
[ 22.266244] Alternate GPT is invalid, using primary GPT.
[ 22.266313] sda: sda1 sda2
[ 22.271089] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[ 22.272678] sd 0:0:0:0: [sda] Attached SCSI disk

This is the only information I found in my log…

Obviously this device has a problem at least in the last area of its sectors. You need to first check your HDD … which will be a painful longish process with that size:

  • try chkdsk /r on Windows (I’m not too convinced about that but it is a present onboard tool with Windows)
  • might be better: Go to the HDD’s vendor support page and search for a vendor specific tool to do this scan job detecting and repairing bad sectors
  • try smartmontools which runs on OSMC and Windows and do a long test smartctl -t long .... You need to prevent the specific OS to hibernate the USB HDD by running any IO activity in loop every 60 seconds or so. So, a simple script doing a periodic smartctl -i or smartctl -aor creating’N deleting a file on the HDD’s file system is doing this. smartctl only helps to detect a defect sector and typically stops on first found, it does not repair anything. So, if you find pendingor uncorrectable sectors afterwards or see a lot of reallocated sectors you’ve to take a decision.

Imho, I personally see HDDs as untrustworthy once the first defect sectors occur.

I tried to launch chkdsk /r but it’s a long process I think today I haven’t time to do it. The HDD is in exFAT, could be this the issue? Thanks

I don’t think so. Your posted info more suggests at least one bad sector on the disk, see also this link.

Don’t know whether the fuse module cannot handle this error in the alternate GUID Partition Table at the end of the hdd’s sectors … but just for tests I formatted a 1TB hdd using GPT and exFAT and all works as expected connecting it to an OSMC device (Pi3 B+).

Thanks for test. So windows have no issue to works with this disk, I used crystaldiskinfo to have a green test to continue to use it… I don’t understand why osmc can’t use it…

Hi, did you resolved this problem?

I have similar with a new external HDD USB3.0 2Tb with a a powered hub, Vero don´t mount when mounting other older HDD, and the new I can see in windows

I have chage format but nothing

Upload logs then we can help.
Did you give the disk/parition a proper label?

1 Like

Sorry, I don´t know how to make and upload a log.

Which is a proper label to the HD?
With other HD I have no problem. Maybe to be USB 3.0 is a problem?

thank you and MC

To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.

Depending on the used skin you have to set the settings-level to standard or higher, in summary:

  • enable debug logging at settings->system->logging

  • reboot the OSMC device

  • reproduce the issue

  • upload the log set either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A

  • publish the provided URL from the log set upload, here

Thanks for your understanding. We hope that we can help you get up and running again shortly.

OSMC skin screenshot:

Some USB 3 cable have issues in a USB 2 port but logs will tell us

the log is in https://paste.osmc.tv/etememonol
that´s correct?

That is correct. I think your hard drive enclosure is using a chipset that is problematic with Linux. I take it this is a drive that you put into a 3rd party case?

On an unrelated note…


We recommend people with 4K TV’s set their user interface (UI) to 1080p. Kodi’s UI is not optimized for 4K yet and this can put unnecessary demands on your device and can lead to a suboptimal picture quality, as well as potentially cause other issues.

The settings we recommend are as follows…

Settings>System>Display>Resolution> 1920x1080p
Settings>System>Display>Whitelist> (empty)
Settings>Player>Videos>Adjust display refresh rate> On start/stop

Some televisions may also need, or benefit from, the following being set…

System>Display>Force 4:2:2 colour subsampling> (enable)

With the above settings your UI will be output in Full HD and your 4K content will be output in 4K. If you have any doubt, feel free to upload some logs so we can verify that your settings are indeed correct.

If you have another USB cable on hand try that.
Otherwise maybe it is a USB3 incompatibility that may be different when the Kernel on the Vero will be upgraded, maybe you can try then again.

If you want to investigate further your could try to boot a Linux LiveUSB on your PC and see how the disk behave there.

thanks, when will this be done? (the upgrade)

In the coming future

Not long now.