This was all working before, but its now not sharing my USB hard drive, nothing has changed apart from latest update
The SMB still works for the MMC (kodi folders)
but not for this hard drive
Any ideas what to check or add to get this back working
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 twice(!)
-
reproduce the issue
-
upload the log set (all configs and logs!) either using the
Log Uploadermethod within the My OSMC menu in the GUI or thesshmethod invoking commandgrab-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:
Whats the filesystem of the drive? Provide logs as @darwindesign asked or the output of
lsblk -f
and also
mount
I cant remember tbh, I bought the drive and plugged it in years ago
Cant get logs at minute as im not at home, but if its any thing to run on SSH i can do it
Yes just execute grab-logs -A via SSH and share the URL.
It looks like your harddisk failed and is not mounted.
Its failed to upload
Might have been to big, can try grab-logs -J -K -f -a -b
As expected there is an issue with your external drive
Oct 16 19:55:58 osmcFrontRoom ntfs-3g[2955]: Failed to read of MFT, mft=495422 count=1 br=-1: Input/output error
Oct 16 19:55:58 osmcFrontRoom kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Oct 16 19:55:58 osmcFrontRoom kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x2 [current]
Oct 16 19:55:58 osmcFrontRoom kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x4 ASCQ=0x1
Oct 16 19:55:58 osmcFrontRoom kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 73 26 78 00 00 00 08 00 00
Oct 16 19:55:58 osmcFrontRoom kernel: blk_update_request: I/O error, dev sda, sector 7546488
Oct 16 19:55:58 osmcFrontRoom kernel: Buffer I/O error on dev sda2, logical block 910287, async page read
2094.141971] blk_update_request: I/O error, dev sda, sector 3
[ 2094.141977] Buffer I/O error on dev sda, logical block 3, async page read
[ 2254.832040] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 2254.832051] sd 0:0:0:0: [sda] tag#0 Sense Key : 0x2 [current]
[ 2254.832056] sd 0:0:0:0: [sda] tag#0 ASC=0x4 ASCQ=0x1
[ 2254.832065] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 04 00 00 00 01 00 00
Either the disk failed or your have a power issue. How is the drive powered?
On the sideline you can remove this line from your sources.list.
deb http://apt.osmc.tv videoimprovevero49 main
Its a 3.5" external drive, It has its own PSU, i`ll have it checked once im home.
Its rarely used compare to other drives on network, so hope its not failed
Cheers
Turns out the HD is faulty so replaced with another drive
In the share it shows as “886e0e906e0e776a” Is there any way to name this a bit better?
You can rename it on a Windows PC if it’s recognised. That’ll probably be the easiest way.
Its mapped to a network drive so shows like this, if it can be changed then fine
Before it did display a more logical name like Seagate Expansion Drive
Unplug the drive from the Vero, plug it into a PC. On the PC in Windows Explorer rename the drive to whatever you want. Plug it back into the Vero and then it should auto-mount using the name of the drive as the mount point and samba should also automatically use that as the name of the share.
Cheers will give it a try tomorrow
Renamed the drive in windows as it was previously blank
But when you plug it back into the device it shows as the same
how would you change it in SSH?
Unplug the drive from the Vero and power off the device. Unplug the power from the Vero for a few seconds and then plug it back in. After Kodi has been up for a minute plug the drive back in and see if that fixes the issue.
There is the option to manually mount the drive using autofs and then manually configuring samba to share the mount, and you can find info for both by searching the forum, but that should really not be required just to change the share name.
First do the restart as indicated by @darwindesign if that doesn’t work we do it via SSH.
You can label it via SSH, but for that we would need to see current status to give you right command.
lsblk -f
and
grab-logs -A
Cheers, I tried rebooting it last night, but done it again this morning, USB unplugged first, below
Seems your rename in Windows didn’t worked.
via SSH do
sudo ntfslabel /dev/sda2 NAMEYOUWANT
And reboot
1 Like