sdcard - hardware or software limitation - Galaxy Note 8.0 (Tablet) Q&A, Help & Troubleshooti

Hello all
i have been reading this forum for a while and seen users discussing limitation of space/size. For that reason they use sd cards - 32 or 64 etc. I would like to know when they say device support upto 64 sdcard what does it mean? is it hardware limitation or software limitation?
I hope my question is not stupid. Just want to clarify.

both, methinks

The answer is it depends. I can't speak from the device side, since I'm not going to open up my tablet.
SD -> pre-formatted FAT.
SDHC -> pre-formatted FAT32
SDXC -> pre-formatted exFAT or FAT32.
Officially / legally to support exFAT, you must get a license from Microsoft.
Most devices support FAT32 but not exFAT.
Windows (at least XP) won't format things to FAT32 over a certain size, 32GB if I remember correctly.
exFAT has the advantage that it has higher limits, such as storing files over 4GB - 1 byte, which might be desirable for many 64GB / UHS-I card users as the emphasis is pretty much on recording a real time stream of full HD video and you don't always want to start a new file every couple gigs.
To further complicate matters the Android ROM (e.g. TouchWiz) does not support mounting all file systems the kernel is capable of supporting. So for example, most devices can mount FAT formatted cards but not ext4 formatted, despite the internal memory using ext4!
These are software issues.
In order to use certain "Newer" features of modern SD cards: you need to have hardware support for additional pins and signalling, including any 'reassigned' pins. Pins, as in those things on the end of the card that you plug in. An example of said newer hardware features are things like Ultra High Speed (UHS) for faster transfer rates. Some hardware may also be physically capable of these features but be loaded with firmware that does not support these features or is lacking some necessarily licensing data to enable the associated behaviour.
Our device supports the following file systems:
Code:
$ cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev binfmt_misc
nodev debugfs
nodev sockfs
nodev usbfs
nodev pipefs
nodev anon_inodefs
nodev devpts
ext2
ext3
ext4
nodev ramfs
vfat
msdos
nodev ecryptfs
nodev fuse
fuseblk
nodev fusectl
exfat
$
So all Microsoft FAT should work unless the ROM gets modded to reject!

What can you use to format a 64GB device to FAT32? I thought that wasn't possible.
Also, anyone know of an OTG cable that will actually support a 64GB SDXC device? Most of them max out at 32GB, but it sure would be nice to go higher with an OTG device.
mudge

I assume that the mounter code is the same for USB media as for card slots.
iCurmudgeon said:
What can you use to format a 64GB device to FAT32? I thought that wasn't possible.
Click to expand...
Click to collapse
Just stick it in a Linux or BSD machine and use mkfs with the right options for fat. Probably -t vfat -F32 or something like that.
Sent from my GT-N5110 using Tapatalk 4

Related

[Q] Problem with installing apps to SD

Hi ,
My phone is kaiser i have froyo 2.2.2 and i install it to flash not with haret method. I install system to nand and data to sd partition but apps doesn't go to my sd card they are installing on internal memory (even they downloading to internal memory ). When i go to applications and click move to sd card then i see information that sd card is removed.
I changed many times to data to ext2 and other options but same think.
Any ideas???
I downloaded my ROM from sourceforge
Sorry for my bad english.
kuba725 said:
Hi ,
My phone is kaiser i have froyo 2.2.2 and i install it to flash not with haret method. I install system to nand and data to sd partition but apps doesn't go to my sd card they are installing on internal memory (even they downloading to internal memory ). When i go to applications and click move to sd card then i see information that sd card is removed.
I changed many times to data to ext2 and other options but same think.
Any ideas???
I downloaded my ROM from sourceforge
Sorry for my bad english.
Click to expand...
Click to collapse
Your rom probably has Terminal installed, if not download it from market.
After you have it, open it, and run " mount " without the quotes. Paste the result or screenshot.
kuba725 said:
Hi ,
My phone is kaiser i have froyo 2.2.2 and i install it to flash not with haret method. I install system to nand and data to sd partition but apps doesn't go to my sd card they are installing on internal memory (even they downloading to internal memory ). When i go to applications and click move to sd card then i see information that sd card is removed.
I changed many times to data to ext2 and other options but same think.
Any ideas???
I downloaded my ROM from sourceforge
Sorry for my bad english.
Click to expand...
Click to collapse
You have data to sd partition. I don't know if anyone has ever gotten that configuration to work with the option to move apps to SD, and I don't know any advantage in doing so.
If, on the other hand, you had data on NAND, you would want to be able to move apps to SD. I think scooter got that to work once, but I have never had success. I have tried many times. Something about the way we mount /sdcard versus /mnt/sdcard, I think, but not sure.
daedric said:
Your rom probably has Terminal installed, if not download it from market.
After you have it, open it, and run " mount " without the quotes. Paste the result or screenshot.
Click to expand...
Click to collapse
I can't mount in terminal i have only this
$ export PATH =/data/local/bin:$PATH
$
SD card is in.
ohhh sory i must write mount .....
I have this in terminal :
$ export PATH=/data/local/bin: $PATH
$mount
rootfs on / type rootfs (rw)
proc on / proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
/dev/block/mmcb1k0p1 on /sdcard type vfat (rw,noatime,nodiratime, fmask=0000, dmask=0000,allow_utime=0022,codepage=cp437 , iocharset=iso8859-1,shortname=nixed,utf8,flush,errors=remount-ro)
/dev/block/mtdblock2 on /system type yaffs2 (ro,nodev,relatime)
/dev/block/mtdblock3 on /data type yaffs2 (rw,nodev,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
tmpfs on /sqlite_stmt_journalist type tmpfs (rw,relatime,size=4096k)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuct1 type cgroup (rw,relatime,cpu)
/dev/block/mtdblock2 on /bin/su type yaffs2 (ro,nodev,relatime)
$
n2rjt said:
You have data to sd partition. I don't know if anyone has ever gotten that configuration to work with the option to move apps to SD, and I don't know any advantage in doing so.
If, on the other hand, you had data on NAND, you would want to be able to move apps to SD. I think scooter got that to work once, but I have never had success. I have tried many times. Something about the way we mount /sdcard versus /mnt/sdcard, I think, but not sure.
Click to expand...
Click to collapse
You say that i will be able to move apps to SD when data will be on Nand but i have this same issue that when i go to aplications and i click move to SD then i see information "SD card removed" (this information not always show up) then when i go to my apps i dont see this application . One time this have succes to transport it on sd and one time dont have succes
kuba725 said:
I have this in terminal :
$ export PATH=/data/local/bin: $PATH
$mount
rootfs on / type rootfs (rw)
proc on / proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
/dev/block/mmcb1k0p1 on /sdcard type vfat (rw,noatime,nodiratime, fmask=0000, dmask=0000,allow_utime=0022,codepage=cp437 , iocharset=iso8859-1,shortname=nixed,utf8,flush,errors=remount-ro)
/dev/block/mtdblock2 on /system type yaffs2 (ro,nodev,relatime)
/dev/block/mtdblock3 on /data type yaffs2 (rw,nodev,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
tmpfs on /sqlite_stmt_journalist type tmpfs (rw,relatime,size=4096k)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuct1 type cgroup (rw,relatime,cpu)
/dev/block/mtdblock2 on /bin/su type yaffs2 (ro,nodev,relatime)
$
Click to expand...
Click to collapse
Okay, now you are running with data on yaffs (which is NAND). Now you have the problem that all or most of us have. When I try to move an app to SD, it sometimes appears to work. Then, I reboot, and the app is gone.
Can we pool our knowledge and figure out how to make this feature work?
I like kaiser but he is was not created for android and i think that i will buy new phone , mayby SAMSUNG I5700 he have android 2.1 and 800 mhz is good and he has a lot of support from XDA
Kaiser was not made for android. But then again, no device was. Take the HD2, made for Winmobile 6.5 IIRC, is running W7, Android, and probably Maemo and Ubuntu and what not.
The problem with porting Android to kaiser is, first we don't have the support of google or a major provider, like HTC or Motorola.
Second, we're working blind here, we're trying to guess or find/hack many things...
Still, to take a device Announced in July 2007, with 128mb RAM, 256 rom, MSM7200 400Mhz with a Adreno 130 GPU and make it work with android, it's a damn good achievement.
Don't be sad it doesn't work oh so well, be glad it works better than windows mobile.
daedric said:
Kaiser was not made for android. But then again, no device was. Take the HD2, made for Winmobile 6.5 IIRC, is running W7, Android, and probably Maemo and Ubuntu and what not.
The problem with porting Android to kaiser is, first we don't have the support of google or a major provider, like HTC or Motorola.
Second, we're working blind here, we're trying to guess or find/hack many things...
Still, to take a device Announced in July 2007, with 128mb RAM, 256 rom, MSM7200 400Mhz with a Adreno 130 GPU and make it work with android, it's a damn good achievement.
Don't be sad it doesn't work oh so well, be glad it works better than windows mobile.
Click to expand...
Click to collapse
I don't think that kaiser is bad phone is very good but i need some new stuff
I don't have too much money, for me HD2 is best phone ever but is too expensive.
Hmmm Maybe you know some cheap phone better than the Samsung I5700???

CWM can't mount SD

I just rooted my phone and installed CWM. When I try to install a zip from SD it says "E: can't mount SD" i've tried everything (manually mount SD card and format external card from CWM and phone and nothing happened!) does anybody now a solution? can I installa a ROM from internal memory? i guess i can't...
thanks a lot!
http://www.youtube.com/watch?v=JmvCpR45LKA
sswb27 said:
http://www.youtube.com/watch?v=JmvCpR45LKA
Click to expand...
Click to collapse
I checked other posts and no solution for me...
thanks anyway
Download rom manger from play store and use it to update CWM.
sswb27 said:
Download rom manger from play store and use it to update CWM.
Click to expand...
Click to collapse
Thanks. I have updated it but the problem persists
Have you tried twrp recovery? If nothing else use internal storage.
Your SD card is most likely formatted in exFAT filesystem. This is a MS proprietary format that requires licensed drivers to mount. As of now there are no custom recoveries that can mount exFAT.
There are a few options:
1) Re-format the card to FAT32 and do backup.
2) Get a smaller (8-16gb) card to use for backups and keep in FAT32 format.
3*) Partition larger card (32-64gb) with multiple partition types. ex. 40gb exFAT/24gb FAT32. *Please note that I have not tried this nor seen it done but just an idea I wanted to try out to see if it was feasible. I may have time to give it a shot later today and if so I'll update this post.
dasgh said:
Your SD card is most likely formatted in exFAT filesystem. This is a MS proprietary format that requires licensed drivers to mount. As of now there are no custom recoveries that can mount exFAT.
There are a few options:
1) Re-format the card to FAT32 and do backup.
2) Get a smaller (8-16gb) card to use for backups and keep in FAT32 format.
3*) Partition larger card (32-64gb) with multiple partition types. ex. 40gb exFAT/24gb FAT32. *Please note that I have not tried this nor seen it done but just an idea I wanted to try out to see if it was feasible. I may have time to give it a shot later today and if so I'll update this post.
Click to expand...
Click to collapse
Do not partition a 64 GB micro SD to FAT32. Performance will be awful because of the way the mem blocks are sized.
Also, your internal SD is exFAT... that is read by the recovery perfectly fine.
I would say save yourself some trouble and just find a ROM kernel combo that supports exFAT micro SD. Your 64 GB will work flawlessly and performance will not take a hit.
maybe post in correct forum for more replys, just sayin
Just for anyones future reference:
This is from stock JB GS3.
Below you can see the various partitions file system types. Mostly ext4 and various ramfs types. At the bottom you can see the external storage as exfat.
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,gid=1000,fmask=0006,dmask=0006,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/vold/179:97 /storage/extSdCard exfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=utf8,namecase=0,errors=remount-ro 0 0
I currently understand the recovery image to work as below. Someone please correct me if it's incorrect.
While the kernel does support exfat the "interpreter" (driver) and custom recovery image can not talk to each other. The exfat driver can only be called/read if you know which system calls to use and how to interpret its response. The custom recovery image does not know how to utilize the exfat driver.
Please read forum rules before posting
Development is ONLY for developers to post release threads
Questions go in Q&A
Thread moved

Can't read sd card after upgraded to MM

After upgrade can't identify sd card WTF all my file pics are in my sd card .any way can't fix that?sorry for my English
I'd eject the card and hook up to a PC to see if you can recover.
My personal experience with SD Cards is they are OK as an extender to store stuff that is expendable such as spotify cache.
They are pretty flaky and would only store photos if they are in synch with Google Drive or some other cloud service.
Good Luck.
Dredd73 said:
I'd eject the card and hook up to a PC to see if you can recover.
My personal experience with SD Cards is they are OK as an extender to store stuff that is expendable such as spotify cache.
They are pretty flaky and would only store photos if they are in synch with Google Drive or some other cloud service.
Good Luck.
Click to expand...
Click to collapse
I did put my sd card to check all files are still there but when i put it back to phone can't identify again
paullu said:
I did put my sd card to check all files are still there but when i put it back to phone can't identify again
Click to expand...
Click to collapse
I've had similar situations and found only formatting fixes it. Which is why I only put expendable items now on SD.
Is your card encrypted?
the_brad said:
Is your card encrypted?
Click to expand...
Click to collapse
No
paullu said:
No
Click to expand...
Click to collapse
Which file manager do you use? Maybe try a different one?
---------- Post added at 12:36 PM ---------- Previous post was at 12:33 PM ----------
If that makes no difference I've had this problem before and the solution I found was to copy/backup card to pc, reformat card, then copy files back onto card. Phone would then read card again.
E5823 said:
Which file manager do you use? Maybe try a different one?
---------- Post added at 12:36 PM ---------- Previous post was at 12:33 PM ----------
If that makes no difference I've had this problem before and the solution I found was to copy/backup card to pc, reformat card, then copy files back onto card. Phone would then read card again.
Click to expand...
Click to collapse
I don't think so it is file manager issue I have like 10g pictures on my 128gb if phone can recognize your sd card you can see all your pictures from album which I can't .
I even format my 128gb sd card but still can't recognize. strange!! no issue when I try on my computer
but when I use my 64gb card it fine
paullu said:
I don't think so it is file manager issue I have like 10g pictures on my 128gb if phone can recognize your sd card you can see all your pictures from album which I can't .
I even format my 128gb sd card but still can't recognize. strange!! no issue when I try on my computer
but when I use my 64gb card it fine
Click to expand...
Click to collapse
It seems like your phone, most likely the card reader, has compromised your sd card. It's strange that a re-format did not work. Did you re-format on pc or in the phone? If you did it on pc perhaps try in phone, if possible...
E5823 said:
It seems like your phone, most likely the card reader, has compromised your sd card. It's strange that a re-format did not work. Did you re-format on pc or in the phone? If you did it on pc perhaps try in phone, if possible...
Click to expand...
Click to collapse
I format two times on pc.
As what i said phone can't recognized my 128gb card so I can't do format on my phone
Just an update. I have now also upgrade my Z4 Tablet to marshmallow and this now also does not read my 200gb micro sd. Both my Z4 Tablet and Z5 Premium are on the generic Nordic marshmallow rom. Those who cant read their micro sd, which rom are you on?
Sent from my SGP771 using Tapatalk
thats happened to me and i tried all methods but only one thing that make it works that u have to format he sd cad from ur phone using this cable hope u have it included with ur z5p and it will work fine after
karimgalal89 said:
thats happened to me and i tried all methods but only one thing that make it works that u have to format he sd cad from ur phone using this cable hope u have it included with ur z5p and it will work fine after
Click to expand...
Click to collapse
I don't have this cable.what is name of this cable?
paullu said:
I don't have this cable.what is name of this cable?
Click to expand...
Click to collapse
p,
i deleted the following file and directories on from pc card reader then reinserted sd card [exfat 128gb] and it reads now.
.android
Android
customized_capability.xml
Also it doesn't appear that the kernel has ntfs support, i did a kernel build with all sorts of fiesystem support crammed in
and so far it seems to be running, i haven't tested ntfs yet, but your current kernel should support exfat
in terminal run
cat /proc/filesystems
this is my output with current build
Code:
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev debugfs
nodev securityfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev configfs
nodev devpts
ext3
ext2
ext4
nodev ramfs
vfat
exfat
iso9660
nodev cifs
ntfs
fuseblk
nodev fuse
nodev fusectl
udf
nodev selinuxfs
nodev functionfs
nodev ecryptfs
[COLOR="Red"] texfat[/COLOR]
texfat is from the "stock" offering meaning no changes to defconfig during compile - so your card should be supprted.
exfat,ntfs after crammed kernel build
m
moonbutt74 said:
p,
i deleted the following file and directories on from pc card reader then reinserted sd card [exfat 128gb] and it reads now.
.android
Android
customized_capability.xml
Also it doesn't appear that the kernel has ntfs support, i did a kernel build with all sorts of fiesystem support crammed in
and so far it seems to be running, i haven't tested ntfs yet, but your current kernel should support exfat
in terminal run
cat /proc/filesystems
this is my output with current build
Code:
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev debugfs
nodev securityfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev configfs
nodev devpts
ext3
ext2
ext4
nodev ramfs
vfat
exfat
iso9660
nodev cifs
ntfs
fuseblk
nodev fuse
nodev fusectl
udf
nodev selinuxfs
nodev functionfs
nodev ecryptfs
[COLOR="Red"] texfat[/COLOR]
texfat is from the "stock" offering meaning no changes to defconfig during compile - so your card should be supprted.
exfat,ntfs after crammed kernel build
m
Click to expand...
Click to collapse
Thanks for reply but how to delete these files?sorry because i am not good at computer
paullu said:
Thanks for reply but how to delete these files?sorry because i am not good at computer
Click to expand...
Click to collapse
p,
just put your sdcard in the reader that should have come with it, then put the reader with you sdcard into your pc
open the directory like normal, and delete thos files, i am thinking that just deleting the xml file might be sufficient.
m
moonbutt74 said:
p,
just put your sdcard in the reader that should have come with it, then put the reader with you sdcard into your pc
open the directory like normal, and delete thos files, i am thinking that just deleting the xml file might be sufficient.
m
Click to expand...
Click to collapse
But i am already did format
Right now my sd card is empty
Did you try with TWRP?
Sent from my E6653 using Tapatalk
c,
TWRP currently doesnt seem to mount/read my external sdcard [exfat]
TRY AndroPlus build
m
The cable name is otg cable

mount usbstick with ext or anything other than fat

Hi. How can I mount on a rooted aftv an usbstick that is formated in ext3/ext4 or anything else than ntfs and fat32?
It's so f.... annoying.
I've tried with stickmount, but the symlink it creates is empty. I imagine that is 'cos the aftv software immediately takes over and asks to format the usbstick to fat32?
An usb stick with fat gets auto-mounted like this:
Code:
#mount
/dev/block/vold/8:1 /mnt/media_rw/usbdisk vfat
rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/usbdisk fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Now, if I want to mount my usb stick with ext4 to be accessable by kodi etc, where would I mount it to?
Code:
toolbox mount -t ext4 -o rw,nosuid,nodev /dev/block/sda1 /data/media/0/usbStorage/sda1
That location /data/media/0.... is only readable by root. Hey, anyone?

Invalid argument error when mounting /dev/block/sda1

I'm trying to follow this post: https://forum.xda-developers.com/showpost.php?p=59166089&postcount=124 to try to get link2sd up and running, I've followed the instructions until I encountered an issue:
mount -t ext4 /dev/block/sda1 /storage/usb
mount: '/dev/block/sda1'->'/storage/usb': Invalid argument
Click to expand...
Click to collapse
The device's name is valid, I've even tried umounting the usb drive in /storage, but it still gives me that error. Have I missed something? The post is quite old and some things might have changed since then.
/system/bin/mount -t ext4 /dev/block/sda1 /storage/usb
Child's Play said:
/system/bin/mount -t ext4 /dev/block/sda1 /storage/usb
Click to expand...
Click to collapse
same thing. I've run fsck on the usb drive, just to be sure, but it seems to work perfectly well.
dictorclef said:
same thing. I've run fsck on the usb drive, just to be sure, but it seems to work perfectly well.
Click to expand...
Click to collapse
Do
ls -l /dev/block/sda1
ls -l /storage/usb
to make sure both exist.
dcarvil said:
Do
ls -l /dev/block/sda1
ls -l /storage/usb
to make sure both exist.
Click to expand...
Click to collapse
they do
ls -l /dev/block/sda1
brw------- 1 root root 8, 1 1969-12-31 19:00 /dev/block/sda1
ls -l /storage/usb
total 0
Click to expand...
Click to collapse
Should have tried this already:
/system/bin/mount -vt ext4 /dev/block/sda1 /storage/usb
mount: '/dev/block/sda1'->'/storage/usb': Invalid argument
try '/dev/block/sda1' type 'ext4' on '/storage/usb'
Click to expand...
Click to collapse
It's as if it doesn't see ext4 in the command. I wonder if it could be a bug with this magisk module? https://forum.xda-developers.com/fire-tv/development/magisk-amazon-firetv4k-ntfs-f2fs-ext4-t3991981
dictorclef said:
Should have tried this already:
It's as if it doesn't see ext4 in the command. I wonder if it could be a bug with this magisk module? https://forum.xda-developers.com/fire-tv/development/magisk-amazon-firetv4k-ntfs-f2fs-ext4-t3991981
Click to expand...
Click to collapse
Did you read note 3 at that link?
"Note 3: Some EXT4 drives may fail to mount,most likely this is because e2fsck it's failing to check for errors. In the next version i will try to add a newer version of e2fsck.However, formatting to EXT4 directly on the device will fix the issue."
You can do "cat /proc/filesystems" to make sure you have ext4 support (should NOT have "nodev" before ext4), but you still may need to format the USB drive on your firestick.
dcarvil said:
Did you read note 3 at that link?
"Note 3: Some EXT4 drives may fail to mount,most likely this is because e2fsck it's failing to check for errors. In the next version i will try to add a newer version of e2fsck.However, formatting to EXT4 directly on the device will fix the issue."
You can do "cat /proc/filesystems" to make sure you have ext4 support (should NOT have "nodev" before ext4), but you still may need to format the USB drive on your firestick.
Click to expand...
Click to collapse
Device does have ext4 support:
cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev ramfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev configfs
nodev debugfs
nodev tracefs
nodev sockfs
nodev pipefs
nodev devpts
ext3
ext2
ext4
vfat
msdos
iso9660
fuseblk
nodev fuse
nodev fusectl
nodev selinuxfs
nodev functionfs
Click to expand...
Click to collapse
And I did try to format the drive using aparted on my firestick, still no luck.
I think I might actually be an idiot, /dev/block/sda1 was already mounted to /mnt/media_rw/[a bunch of numbers and letters]. Unmounted it and it will now mount where I want. Link2sd detects the partition just fine.

Categories

Resources