Mount usb sooner?

Help and Support
1

Is there a way to get the usb drive to mount sooner? Right now it finally mounts about a minute or 2 after boot.
It is an externally powered drive that is pretty much always connected.

2

A USB drive should finish mounting about 10-12 seconds from the beginning of boot, (just before the Kodi screen appears) it definitely does not take 1-2 minutes unless you have a hardware issue.

What type of USB drive is it and what is is powered from ?

Can you please use the My OSMC log uploader to upload all debug logs (after the system has fully booted and the drive has appeared) so we can have a look.

3

The usb drive is a WD Elements and has it’s own power supply.
Here are the logs: http://paste.osmc.io/ehozosovec

4

You have un-readable sectors on the disk:

Sep 27 14:00:54 osmc kernel: sd 0:0:0:0: [sda] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Sep 27 14:00:54 osmc kernel: sd 0:0:0:0: [sda] Sense Key : 0x3 [current] 
Sep 27 14:00:54 osmc kernel: sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x0 
Sep 27 14:00:54 osmc kernel: sd 0:0:0:0: [sda] CDB: opcode=0x28 28 00 00 5f 74 88 00 00 f0 00
Sep 27 14:00:54 osmc kernel: blk_update_request: critical medium error, dev sda, sector 6255752

Sep 27 14:00:57 osmc kernel: sd 0:0:0:0: [sda] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Sep 27 14:00:57 osmc kernel: sd 0:0:0:0: [sda] Sense Key : 0x3 [current] 
Sep 27 14:00:57 osmc kernel: sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x0 
Sep 27 14:00:57 osmc kernel: sd 0:0:0:0: [sda] CDB: opcode=0x28 28 00 00 5f 75 88 00 00 f0 00
Sep 27 14:00:57 osmc kernel: blk_update_request: critical medium error, dev sda, sector 6256008

Sep 27 14:00:59 osmc kernel: sd 0:0:0:0: [sda] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Sep 27 14:00:59 osmc kernel: sd 0:0:0:0: [sda] Sense Key : 0x3 [current] 
Sep 27 14:00:59 osmc kernel: sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x0 
Sep 27 14:00:59 osmc kernel: sd 0:0:0:0: [sda] CDB: opcode=0x28 28 00 00 5f 76 78 00 00 f0 00
Sep 27 14:00:59 osmc kernel: blk_update_request: critical medium error, dev sda, sector 6256248

critical medium error means just what it says - parts of the disk cannot be read properly, if you listen very closely to the drive during boot you may hear it clicking.

Sometimes un-readable sectors can be “fixed” by re-formatting the disk with a full format as overwriting the bad sectors allows the drive to relocate the bad sectors and map in spare sectors. Of course this would wipe all data on the drive.

Or these errors could be a sign that the drive is failing in a more serious way. Either way your drive is not healthy.

5

Yeah, I had an issue where it just disconnected, so ended up doing a repair with fdisk, but I think I am gonna need to replace the drive soon.

Thanks!

6

If I copy the contents to another disk and plug it in, what is the best way to change the library reference? Do I just change it in sources.xml, or rescan everything?

Also, is there a way to run fsck to fix these errors? I tried it on /dev/sda1 but just kicked me back to a terminal prompt.