I've got a 3TB external drive drive hooked up to my Ouya running CM11 (Android 4.4)
I run Nzbget and Transmission in optware, and use CM primarily as a vehicle for XBMC so I need the space.
I had it in 2 ext4 partitions which needed a init script to mount under the stock OS.
I was hopping to get it working in a less hacky manner under CM.
I tried with the two parts, and no go so i redid it with one big partition with root as the UID and sdcard_rw as the GID.
Still no dice. I can access it in File Manager with elevated permissions, but no go in XBMC or other apps.
Also tried one big exFAT partioning with no luck.
I plugged in an 8g ntfs drive I had and it automounted it no problem.
Anyone know the right way to configure the drive? We're a Linux household so sticking with ext2/3/4 would be ideal. NTFS I would like to avoid.
Thanks
mounting manually for now
System logged this when it failed to automount
EXT4-fs (sdb1): Unrecognized mount option "context=ubject_r:sdcard_external:s0" or missing value
Anyone shed light on this?
Related
Hello,
My device didn't support exfat, so I compiled a kernel module and also the fuse modules, and I can successfully mount the device using terminal emulator, however I want the device to auto mount on the insertion of a exfat flash drive or sdcard like it would a fat32 drive, but for some reason it still won't auto mount when I plug in exfat device it just shows notification "damaged storage"
so does anyone have any idea how I can add this filesystem to the android list of supported partitions detection mechanism ?
I know there are programs on the playstore like stickmount ..etc but I want to integrate it into the main functionality of android if possible
I am rooted and have full access to the device, I am running android 4.2.2
any ideas would be great
So I bought an OTG cable for the first time yesterday, and I tested it with a pendrive. I could access the pen with Root Explorer, on /mnt/ntfs/sda1, but there was no option to mount/unmount the drive (the android system did ask me to erase the pen because it had a damaged filesystem, but I could access it with no problems with Root Explorer).
So what I want is to be able to unmount the device so I don't damage it over time, or properly mount it on a more logical path so I can use it with other apps.
I also tried an WD HDD of 1.5TB and the same thing happen, I could access it on the same path but no mount/unmount options anywhere. Not even "filesystem is damaged" warning this time.
I have tried with some Play Store apps (root required ones) but no luck.
Any suggestions?
Thanks in advance.
Also, I want to be able to mount FAT32 filesystems and to be able to write on NTFS ones. I have tried almost all of the Play Store apps but all of them crashed or didn't work. The only thing that works on my phone is the auto-mounting of NTFS filesystems in R/O, because of the SiyadKernel. No other filesystems or functions.
Is there any way of doing this?
Thanks.
Just for the heck of it I tried the Paragon NTFS/HFS download in the Play Store today to see if NTFS read/write would work. The app needs root, and of course we thankfully have that. I had a Seagate USB 3.0 drive formatted NTFS and connected it. Since Android auto mounts on the Mojo, it auto mounted as NTFS read only. I had to unmount it, and then re-mount it with the Paragon app and choose an alternate mount point (just created a folder called "NTFS" and mounted it) and I can confirm that I can read and write to the drive. Moving files, deleting files, and copying files all worked just fine. Just a heads up. I am sure there will be a better, more translucent way of doing this down the road, but for now there does exist the possibility. I wonder if anyone knows how to stop Android from auto mounting drives when plugged in?
I confirm that your method works, thanks!
Although I could have lived without the writing option enabled, it sure is nice being able to delete files I don't need on the fly.
I found that stock rom sucks in regards RW for external drives and doesnt allow it in exfat or NTFS the solution for me and others was installing CM12 rom instead of stock, now my drive has normal RW funtion without having to use an app to mount it
not I can use my 5TB drive
Hello there.
Recently I bought a "Sandisk Dual Ultra USB Drive" (32GB) since my smartphone only have 8GB of internal non-volatile memory and I could use some extra space. Sandisk says my device is supported but they won't help me if I don't update my Android, what I don't want to do because I did that before and some essential functions are broken (e.g.: no call recorder works). So I'm using Jelly Bean here.
I've formatted the USB device as FAT32 and it gets mounted automatically (with rw access) when I plug it, however, the permission is 075, and no matter what I do I can't change that... In fact, for some reason I can't change any permission of anything. In a shell (with root access of course) everything seems to work fine except for the fact chmod simply doesn't work, it doesn't matter the location of the object I'm trying to change the permission. The USB device gets mounted with rw access automatically, but even though I've tried to remount it a number of times, with and without write access and nothing changes. Root checker says everything is fine.
The only way I could write to the USB device is formatting it as NTFS and using the Paragon plugin for Total Commander. However, only Total Commander is able to access the device and I want to access it from other apps.
Any help?
Thank you in advance.
EDIT:
In fact I can chmod stuff in / and in /system
I solved the issue, here is what I did:
TIP-Forget about FAT32. I simply couldn't make it work.
I've installed the Paragon NTFS thing that adds support and mounts NTFS filesystems on Android devices. It works kinda okay, but ordinary apps won't be able to see the files outta the box. By default it mounts the device on /storage/emulated/legacy/ParagonNTFS, but for some reason the apps can only access the files there if the path is /data/media/0/ParagonNTFS, and most apps can't browse this folder.
To workaround that limitation, I've configured Paragon to mount the USB drive on /storage/sdcard1 and added a symlink on /storage/emulated/0/_USB, so every app will be able to access it from the 'home' folder through the symlink. It's working wonders. (NOTE to make a symlink just run "ln -s /storage/sdcard1 /storage/emulated/0/_USB").
In any case, I'm extremely tired of Android... only things that works correctly are games and unimportant stuff like social media stuff and 'entertainment' overall... the system feels extremely cheapo and it's full of idiotic things, stupid bugs and moronic limitations. I'm certainly not buying another Android device again. I'm gonna wait for something minimally decent, perhaps Tizen or something.
I didn't mean to offend anyone, it's just that Android is so bad that I was about to puke while trying to make a simple USD drive work. Too many dumb people working at Google I think.
My solution to NEXUS 5 can write to OTG USB pendrive
Ok, that's that I did, and it worked ( 4 or moure hours testing various things)
I used a Corsair Voyager GO 64 gb with NTFS filesystem.
My Nexus 5 is rooted.
I installed Chainfire "StickMount". So we can mount out USB pendrive to /sdcard/ubsStorage/sda1 No need to be PRO app.
I installed Paragon "paragon NTFS&HFS". Open it, and will ask to fix SELinux policies to Permisive. So Root Explorer can see now /Data/Media/ClockWorkmod/backup
I installed Jrummy Apps inc. "Root Explorer". I will copy, for example /Data/Media/ClockWorkmod/backup to /sdcard/ubsStorage/sda1 whithout any problems.
Don't forget to unmount USB drive before disconnecting it, go to StickMount and choose unmount
ES FILE EXPLORER WILL SAY "No space" "Error" or similar
Worked for me!
I'm happy with my investigation. I used Root Explorer in the past, and now it's useful again.
Sorry about my english, not perfect.
ENJOY!
I posted this on the Nexus7 pages, but I wonder if it might be better in a general android page .
I have a nexus 7 that i'm utilising in a car build.
It's running CM10.1 which I believe is based on 4.2.2, and Timurs custom Kernel.
I have a 175gb SSD dive, hooked up to a USB hub and OTG cable.
The SSD is recognised and mounts correctly on the Nexus via the kernel.
I'm looking to speed up the mount process.
When I connect the SSD, the led activity light on the SSD will start to blink rapidly, any media on the drive is inaccessible until the drive activity has ceased.
This process takes around 30 seconds or more.
The drive is formatted using exFat, with a single partition.
I've placed a number of .nomedia files inside the USBDISK folder, SDCARD folder, and in the root of the USB drive itself, but still mounting takes time.
Is there a way to speed up the mounting process.
Maybe moving the media folders inside a single folder, or some sort of file (like .nomedia) inside the folder structure to tell Android to not perform a file check and just mount it regardless.
Maybe a cache system.
The kernel is configured to have the drive in read only mode, so unless I manually add any files, then I have no need to scan for any file changes.
The drive could be in the car for months before I add any new media to it.
I noticed last night, when I connect the HDD to my Windows 7 PC, no such disk activity takes place.
The drive is mounted, and ready to access within seconds.
Thinking that the drive activity could be folder related, I created a new folder in the root named .files, and then moved all my data in to it.
However, the tablet is still performing some sort of laborious disk activity when the drive is connected.
This now has me thinking...
When a disk is mounted in Android, is it a real mount of a virtual one.
If it's a virtual one, then I guess the system needs to build the directory listing and populate this in a virtual folder ??
I guess no one else has experienced this, or I posted in the wrong forum, but i think i figured it out.
Just incase someone else has the same problem in the future, and in the vain hope that they stumble across this thread, I think it's only fair that I post my findings.
My SSD drive is formatted exFat for compatibilty between my PC, Tablet and S7 phone which is on Marshmallow.
I have 2 hard drives, I have a 2.5" SSD and a standard 2.5" Sata drive.
So something to experiment with.
I have 2 hard drives, I have a 2.5" SSD and a standard 2.5" Sata drive.
So something to experiment with.
Formatting the standard hard drive as NTFS and then copying a small number of my files on to it, i noticed that the mount time was instant, with hardly any drive activity.
All files are accessable.
It makes little sense, considering a standard mechanical drive is supposedly slower than SSD.
I then formatted it exFat, and copied roughly the same number of files, but now the mount time was about 5 seconds, with the drive light activity issue.
I reformatted my SSD as NTFS, copied my files back on to it, and the mount time is still almost instantaneous.
So it looks like whatever is causing the extended mount time is asscociated with exFat.
I've no idea why, so if anyone can explain, i'll be happy to learn.
somehow exfat formatted disk is checked for errors on android every time it mounts.