When I try to remove a link in Link2SD I will have the message
Remove link failure
rm failed for /data/sdext2..... Read-only file system
All files I can se have RW. Can it be a problem with the SD-card?
Is is not possible to make any new links either.
beani45 said:
When I try to remove a link in Link2SD I will have the message
Remove link failure
rm failed for /data/sdext2..... Read-only file system
All files I can se have RW. Can it be a problem with the SD-card?
Is is not possible to make any new links either.
Click to expand...
Click to collapse
It sounds like the partition got mounted to /data/sdext2 as read-only somehow. It doesn't matter what the actual file permissions are if the partition is not mounted as read/write. Try one of the following commands to see how it is mounted:
Code:
#If using a terminal emulator on your phone
mount
#If using adb on your computer
adb shell mount
#Here's the output I get:
rootfs on / type rootfs (ro)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /mnt/asec type tmpfs (rw,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,mode=755,gid=1000)
/dev/block/mtdblock3 on /system type yaffs2 (ro)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev)
/dev/block/mmcblk0p2 on /sd-ext type ext2 (rw,noatime,nodiratime,errors=continue)
/dev/block/mtdblock4 on /data/dalvik-cache type yaffs2 (rw,nosuid,nodev)
/dev/block/mmcblk0p2 on [B][COLOR="Red"]/data/sdext2[/COLOR][/B] type ext2 ([B][COLOR="Red"]rw[/COLOR][/B],noatime,nodiratime,errors=continue)
/dev/block/vold/179:4 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:4 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,size=0k,mode=000)
If yours says "ro" instead of "rw", you might have to modify the link2sd mounting script in /etc/init.d/
I would also suggest posting this in the Link2SD thread so more people, including the dev, can help you figure it out.
I too am having a similar problem, except when trying to create a link. The message i get is:
"Create Link Failure
: cannot create /data/sdext2/sampleapp.apk: read-only file system"
I checked to see if my sdext2 partition is RO - and it is. How do I fix this? I found the link2sd mounting script in the init.d directory, but I have no clue as to how to edit it in order to get things working. I checked in the link2sd thread u posted above, but found no answer to this problem after reading thru 94+ pages.
Help...please...
Bling_Diggity said:
The message i get is:
"Create Link Failure
: cannot create /data/sdext2/sampleapp.apk: read-only file system"
I checked to see if my sdext2 partition is RO - and it is. How do I fix this? I found the link2sd mounting script in the init.d directory, but I have no clue as to how to edit it in order to get things working.
Click to expand...
Click to collapse
Please post the output from the mount command so it will help us figure out how the link2sd script needs to be modified if that is the problem. It would be good if you could attach or post the contents of the link2sd script also. The easiest way might be to just open up either a terminal emulator or use an adb shell through your computer for two commands(filling in the appropriate script name):
Code:
su
cat /etc/init.d/LINK2SD_SCRIPT_NAME
Copy that output and post it here. If you get a read-only error, look below on how to remount /system as r/w and try again.
The script's mount command might use /dev/block/mmcblk0p2 instead of /dev/block/vold/179:2 as well as -o options and/or -t type possibly being specified but it should be similar to the following:
Code:
mount /dev/block/vold/179:2 /data/sdext2
#Only guessing until I get more info but you could try one of these:
mount -o rw /dev/block/vold/179:2 /data/sdext2
mount -o rw -t TYPE /dev/block/vold/179:2 /data/sdext2
#TYPE will be the format of your 2nd partition: ext2 or ext3 or ext4 or vfat(if fat32)
To edit the link2sd script, Root Explorer would work if you have it. If so, you can navigate to /system/etc/init.d/, click on the "mount rw" button at the top right, then long click on the link2sd script, choose "open in text editor" and make your changes. Another option is using adb. You can pull a copy of the script to your computer, edit it, then push it back. From a terminal/cmd prompt on your computer with adb set up:
Code:
#pull script to your current directory
adb pull /etc/init.d/LINK2SD_SCRIPT_NAME
#now edit the script then push it back and give correct permissions
adb push ./LINK2SD_SCRIPT_NAME /etc/init.d/
adb shell
su
chown 0:2000 /etc/init.d/LINK2SD_SCRIPT_NAME
chmod 750 /etc/init.d/LINK2SD_SCRIPT_NAME
Another option would be to use a terminal emulator on your phone:
Code:
su
cp /etc/init.d/LINK2SD_SCRIPT_NAME /sdcard/
#access the sdcard using a usb cable with your computer, edit the script, and disconnect from the computer
cp /sdcard/LINK2SD_SCRIPT_NAME /etc/init.d/
chown 0:2000 /etc/init.d/LINK2SD_SCRIPT_NAME
chmod 750 /etc/init.d/LINK2SD_SCRIPT_NAME
If you get read-only errors while trying to do any of the steps, you'll need to remount the /system partition as read/write. From terminal emulator or in adb shell:
Code:
su
mount -o remount,rw /system
Problem solved. Apparently something happened that caused Clockworkmod to create my partition in Read-Only mode. Couldn't figure out how to change that to R/W, so I did a complete wipe of everything (including SD card), changed over to Amon Ra, repartioned using it, reloaded everything back on to the SD card, re-flashed CM7/gapps, then booted and reinstalled L2SD. Works perfectly now. Not sure why CWM created my partition in read-only mode...but Amon Ra didn't have that issue...so I guess I'll be sticking with it from now on.
MongooseHelix said:
The script's mount command might use /dev/block/mmcblk0p2 instead of /dev/block/vold/179:2 as well as -o options and/or -t type possibly being specified but it should be similar to the following:
Code:
mount /dev/block/vold/179:2 /data/sdext2
#Only guessing until I get more info but you could try one of these:
mount -o rw /dev/block/vold/179:2 /data/sdext2
mount -o rw -t TYPE /dev/block/vold/179:2 /data/sdext2
#TYPE will be the format of your 2nd partition: ext2 or ext3 or ext4 or vfat(if fat32)
Click to expand...
Click to collapse
i seem to be getting closer with this solution but in terminal emul i'm entering
#mount -o rw -t vfat /dev/block/vold/179:2 /data/sdext2
and i'm getting failed device or resource busy
blkwhk said:
#mount -o rw -t vfat /dev/block/vold/179:2 /data/sdext2
and i'm getting failed device or resource busy
Click to expand...
Click to collapse
vfat? Obviously wrong, isn't it?
Getting a read-only mount probably means that the filesystem is corrupted (which would exactly match my experience regarding the partitioning/formatting capabilities of CWM... has nothing but trouble with that one).
doktornotor said:
vfat? Obviously wrong, isn't it?
Getting a read-only mount probably means that the filesystem is corrupted (which would exactly match my experience regarding the partitioning/formatting capabilities of CWM... has nothing but trouble with that one).
Click to expand...
Click to collapse
vfat because i used minitools to create a 2nd fat32 partition. the ext2,3,etc didn't work for me in link2sd
blkwhk said:
vfat because i used minitools to create a 2nd fat32 partition. the ext2,3,etc didn't work for me in link2sd
Click to expand...
Click to collapse
Well, FAT32 is extremely bad choice. They did not work for you pretty much for the reason stated above - you are using a broken tool to partition/format them. Forget about CWM, simply do it on PC or use AmonRA.
doktornotor said:
Well, FAT32 is extremely bad choice. They did not work for you pretty much for the reason stated above - you are using a broken tool to partition/format them. Forget about CWM, simply do it on PC or use AmonRA.
Click to expand...
Click to collapse
didn't use CWM, used minitools on PC
FYI
mount -t vfat -o rw,remount /dev/block/vold/179:2 /data/sdext2
worked for me
blkwhk said:
didn't use CWM, used minitools on PC
Click to expand...
Click to collapse
Never heard about minitools. Try something better next time. In case you wonder why FAT32 sucks then, first of all, it has no concept of permissions at all, so any process can write and delete the files there, and second, the filesystem gets corrupted all the time on unclean unmount.
blkwhk said:
didn't use CWM, used minitools on PC
FYI
mount -t vfat -o rw,remount /dev/block/vold/179:2 /data/sdext2
worked for me
Click to expand...
Click to collapse
I used minitools as well to create a FAT32, but still keep getting I/O mount-script-creation error when trying to load up link2sd.
I will say it again - do NOT use the fricking FAT32.
Same for me
Well, i just had the same problem.
To solve it, i just rebooted my cellphone (cuz i'm a lazy boy who doesn't like code lines^^).
I had the same problem and found the folder in /data/sdext2 listed as RO on my phone. I set it on RW and the problem was solved for me.
Hopefully it'll work for you guys too.
link2sd failure
Erikdeperik said:
I had the same problem and found the folder in /data/sdext2 listed as RO on my phone. I set it on RW and the problem was solved for me.
Hopefully it'll work for you guys too.
Click to expand...
Click to collapse
still failure when create link manually or automatic,...
......................................................................
any other sollution???
Uppppppppp. SAME problem.
I also noticed my error says /data/sdext2, but my partition type if ext4. Should that be a red flag?
I was getting an error specific to the dalvik-cache (/data/sdext2/dalvik-cache) claiming that it was read only. I used root explorer to try and change permissions for the folder, but root explorer was unable to (on a side note I WAS able to change permissions for the /data/sdext2 folder). I ended up using root explorer to edit the link2sd script..
MongooseHelix said:
To edit the link2sd script, Root Explorer would work if you have it. If so, you can navigate to /system/etc/init.d/, click on the "mount rw" button at the top right, then long click on the link2sd script, choose "open in text editor" and make your changes.
Click to expand...
Click to collapse
turns out my script included the /dev/block/vold/179:2 line AS WELL AS the /dev/block/mmcblk0p2 line.. however both were showing "rw". I removed the /dev/block/mmcblk0p2 line and added mount -t vfat -o rw /dev/block/vold/179:2 /data/sdext2/dalvik-cache
works like a charm now =D
Thank you MongooseHelix and everyone else for your help!
blkwhk said:
didn't use CWM, used minitools on PC
FYI
mount -t vfat -o rw,remount /dev/block/vold/179:2 /data/sdext2
worked for me
Click to expand...
Click to collapse
Worked for me too...No formats no nothing...thanks!
Solved ! Failure Link2SD package invalid
For friends who are having problems with the "Create Link" in Link2SD, here I will try to help resolve the problem, because some days I also mess around with "Failure Link2SD package invalid" on my phone. And here's how:
previously, ROM I use is miniROM with Stock Kernel, and Sandisk 8Gb MicroSD Class10
1. Create Partition as follows:
• FAT32 = 6.50 Gb *create as primary
• Ext2 = 600MB *create as primary
• Linux Swap = 200MB *create as primary
#Put MiniTool to create partitions, search on google for a tutorial
2. Link2SD *can use whatever version, I use the latest version V3.7.3
Download Link2SD only from Playstore, do not use version Link2SD Cracked / Mod, remember only from Playstore. If you are using a version of Crack / Mod then bound to fail in the Create Link in Link2SD, and it is based on my experience these days.
If you want Link2SD full version, try using Lucky Patcher. But I do not use it that way, because this is enough for me.
Sorry for my bad english, i used Google Translate to translate my language, (Indonesia to English) :silly:
#Screenshot on Attachment
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
I've been trying to swap sdcard on kitkat, but no avail. any Ideas about how to swap or even remove the internal sdcard?
been trying to remount with this script but it's black screen with force closes, maybe theres something wrong with it?
Code:
LOG=/data/swap.log
umount /storage/sdcard0
umount /storage/sdcard1
umount /mnt/secure/asec
umount /storage/emulated/legacy
umount /mnt/shell/emulated
umount /mnt/media_rw/sdcard1
mount -t vfat -o umask=0000,uid=1023,gid=1023 /dev/block/vold/179:33 /mnt/shell/emulated 1>>$LOG 2>>$LOG
mount -t vfat -o umask=0000,uid=1023,gid=1023 /dev/block/vold/179:33 /storage/emulated/legacy 1>>$LOG 2>>$LOG
mount -t vfat -o umask=0000,uid=1023,gid=1023 /dev/block/vold/179:33 /storage/sdcard0 1>>$LOG 2>>$LOG
mount -t vfat -o umask=0000,uid=1023,gid=1023 /dev/block/vold/179:33 /mnt/media_rw/sdcard1 1>>$LOG 2>>$LOG
mount -t vfat -o umask=0000,uid=1023,gid=1023 /dev/block/vold/179:33 /storage/sdcard1 1>>$LOG 2>>$LOG
mount -t vfat -o umask=0000,uid=1023,gid=1023 /dev/block/vold/179:33 /mnt/secure/asec 1>>$LOG 2>>$LOG
I saw some build.prop tweak to swap them(without init.d or any other modification),try to find it in google.
P.S.-I found a way to mount sdcard(ye,4gb partition used in 4.2.2 ) partition throw ADB,but i need help to make init.d script... For now its work correct,no problems with Googleplay(installing apps),camera(save pictures without problems)...
hmm
siankatabg said:
I saw some build.prop tweak to swap them(without init.d or any other modification),try to find it in google.
P.S.-I found a way to mount sdcard(ye,4gb partition used in 4.2.2 ) partition throw ADB,but i need help to make init.d script... For now its work correct,no problems with Googleplay(installing apps),camera(save pictures without problems)...
Click to expand...
Click to collapse
I can help you with init.d script just PM me
siankatabg said:
I saw some build.prop tweak to swap them(without init.d or any other modification),try to find it in google.
P.S.-I found a way to mount sdcard(ye,4gb partition used in 4.2.2 ) partition throw ADB,but i need help to make init.d script... For now its work correct,no problems with Googleplay(installing apps),camera(save pictures without problems)...
Click to expand...
Click to collapse
Make it public pls, system and data filled that emulated storage thing and now i can't store a thing :/
lybxlpsv said:
Make it public pls, system and data filled that emulated storage thing and now i can't store a thing :/
Click to expand...
Click to collapse
Its public
Just go here and read or wait for permanent fix.
http://forum.xda-developers.com/xperia-l/general/help-solution-sd-card-mount-cm11-t2683432
not to bring up an old tread
But would this method work with any phone or tablet with kitkat on it? Because I'm trying to do the same thing
Back in 5.1.1, I was able to mount the system partition.
Now in 7.0, I couldn't mount it anymore without making my phone crash
I've tried different methods...
Code:
mount -o rw,remount -t ext4 /system
This crashes my phone
Code:
mount -o rw,remount,rw -t ext4 /system
This reports back "...Device or Resource busy"
So then I was thinking that something might be using that directory so I tried to make a system mount point in /mnt, thinking as processes depend on /system, I must make another mount point
So I did, this time, "mount" says system is mounted with "ro,seclabel,relatime,norecovery" as it's option. so when I changed it to "rw,seclabel,relatime,norecovery", it doesn't mount, with no errors
So I tried, with system mounted on /mnt/system,
Code:
# mount -o rw,remount -t ext4 /dev/block/sda18 /mnt/system
(don't worry I know you can do ".../platform/xxxxxxxx.ufs/by-name")
This ALSO crashes my phone
So I pretty much gave up, and looked online, and all I found was the same process, but nothing on "this crashes my phone" or any other.
Agreed
I had the same problem. Hard lock up of phone.
how did u get root via adb??
DDwhite said:
how did u get root via adb??
Click to expand...
Click to collapse
https://forum.xda-developers.com/verizon-galaxy-s6/general/unlock-bootloader-t3688594