Closed vially closed 7 years ago
Can you do sfdisk dump (and equivalent for GPT)?
This is the output of sfdisk --dump
:
label: dos
label-id: 0x0f475a66
device: /dev/sdb
unit: sectors
/dev/sdb1 : start= 2048, size= 976771072, type=7
It seems the disk gets recognized after setting the partition table to MBR and formatting it as a single NTFS partition as listed above.
Now when I plug it in, an Android popup appears (I'm using the TV image) asking me how I would like to use the disk: "internal storage"/"removable device". So I select removable device and it asks me to format it which I confirm. So after letting Android format it the sfdisk --dump
looks like this (which seems to be MBR with one big FAT32 partition with the boot
and lba
flags set):
label: dos
label-id: 0x00000000
device: /dev/sdb
unit: sectors
/dev/sdb1 : start= 2048, size= 976771120, type=c, bootable
So now the disk gets recognized correctly and I can browse files in ES File Manager, however, I can't find the device in Kodi. Any idea why that might happen?
Also, what is the default mount point for USB devices? Is it /storage/PARTITION-ID
?
I have heard about Kodi problem, not recognising USB drives. Can you write more? Maybe you could look in Kodi source code to see what happens there and how they do discover external drives?
I'm looking further into it. I'll update this issue with the progress if I find anything.
This is fixed in latest build.
Setup
I'm using an external 500 GB external USB 3.0 drive plugged in a USB hub (the USB hub has external power source).
Steps to reproduce:
I've tried formatting the drive as ext3, ext4, fat32, ntfs and all of them have the same issue. I've tried both MBR and GPT partition tables with no success. Also, I've tried opening the device in Kodi but it's not listed there either.
The exact same setup was working fine with your Android TV 5.1 image.
Logs
These are some logs taken from adb although they seem pretty generic and I don't think they'll offer much help.
logcat
dmesg