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)
or
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
or
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 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…
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
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.
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…
Summary
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…
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.
