Closed splatmat closed 11 years ago
Check size of image file, it should not exceed 4095 MB. Turn on debug mode (Settings -> Debug mode) and put error log here.
Alternatively you can mount it from an EXT2 part
thx to freeload101, this really worked good. After successfully setting up Kali with image size 900MB i tried it with 8000MB, needed more space for missing pentesting tools... Kali still running :+1:
Updating configuration file ... done Updating configuration file ... done
begin: install Checking mount points ... done Checking installation path ... done Making new disk image (7128 MB) ... dd: opening
/sd-ext/linux.img': Read-only file system dd: opening
/sd-ext/linux.img': Read-only file system done Making file system (ext2) ... ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /sd-ext/linux.img is mounted. mke2fs: No such file or directory while trying to determine filesystem size done Mounting partitions:
/ ... mount: mounting /sd-ext/linux.img on /data/data/ru.meefik.linuxdeploy/linux/mnt failed: No such file or directory fail <<< end: install
So I am a super noob but i managed to solve the problem. All i had to do is to change File System to ext2 ( or whatever works), image size = 900, installed busybox, and uncheck built- in shell. also if you want you can change the directory of the file.
I had to go to busybox and check all the commands at the bottom (all green) and install them. It seems as if busybox left out some important commands such as 'dd' 'mount' and 'unmount'.
I had the same issue, with the help of the debug option I found out that the su binary was missing from bin/ but it was present in /xbin and besides that xbin/ was set to be used instead of bin/ TL;DR: make sure your BusyBox installation is 100% correct and you're not missing any binaries from either folder.
I was having this issue after trying to use Directory installation instead of File installation. I think at some point a loop device got stuck associated and it wasn't able to associate with a new image. I rebooted the phone and it was all good from there. I assume the loop devices got disassociated and that's what fixed it for me.
For me this issue was happening because of SuperSU 'Mount namespace separation'. Go to SuperSu settings and disable this option (this is a security measure tho) and reboot.
u0_a194@android:/ $ u0_a194@android:/ $ cd /storage/emulated/0/Kalilinux u0_a194@android:/storage/emulated/0/Kalilinux $ su s.linuxonandroid/files/bootscript.sh /storage/emulated/0/Kalilinux/kalilinux.img < Checking loop device... MISSING Creating loop device... OK mount: mounting /storage on /data/local/mnt/external_sd failed: Invalid argument No user defined mount points net.ipv4.ip_forward = 1 chroot: can't execute '/root/init.sh': Permission denied Shutting down Linux ARM umount: can't umount /data/local/mnt/external_sd: Invalid argument umount: can't umount /data/local/mnt/dev: Invalid argument 1|root@android:/storage/emulated/0/Kalilinux # I got this problem while installing kali linux on my tab 3. Any help
Sorry to be touching on an old topic but i've been struggling with this issue, i'd really appreciate help tackling it.
[03:28:22] Updating configuration file ... done [03:28:22] >>> configure [03:28:22] Mounting partitions: [03:28:22] / ... fail [03:28:22] <<< configure [03:28:25] Updating configuration file ... done [03:28:25] >>> start [03:28:25] Mounting partitions: [03:28:25] / ... fail [03:28:25] <<< start
Same problem. After creatin d image. Bt i get mounting partition fail. I really need help here
Has there been a successful story on doing this? I currently have a 4gb loop file almost full. Would like to use GParted to split up the SD with lets say a 15gb ext4 partion and copy the loop to that partition and expand it. I still don't understand how to make Linux Deploy see that new partition on SD.
Any thoughts on this?
UPDATE: Actually , forgot but I have been using the full SD with exFAT partion format.. There should not be this limit.. will try and expand. Yay.. it works fine since SD is exFAT ;-) . Im at 7gb image loop file
Thanks
I've got an Odys Neo X7 running a rooted Android 4.0.3 Kernel Version 3.0.8+ and i tried to install Kali with Linux Deploy. I use an 8GB FAT32 sd card to install the linux.img file. Installation fails after making file system.
i get the following output:
Mounting partitions: / ... fail <<< end: install
What am i doing wrong? or is it a known issue? i really need help here...