[Android Software Development] Dav_Edward:
***EDIT***

Hang on.. something is amiss here. Although Busybox installer said it was successful, after I did a reboot of the system I found that it now states 'more than one version of busybox is installed' for some reason on boot up Siyah keeps messing around with busy box. Each time I reboot with busybox cleanly installed I see a message that 'Android is upgrading' then find a new xbin folder appears in /system/

On top of that there's a /sbin/ folder too. I think Siyah keeps messing with busybox...

*********

Edit 2:

Okay.. this is kinda screwed up. Apparently CF-Root and Siyah don't get along. If you have CF-Root installed, and then install the new kernel Siyah. CF-Root installs it's own busybox which is typical, but then when you install Siyah, it ignores the busybox CF-Root made and tries to make it's won busybox and the two conflict.

Trying to use the busybox installer to cleanly install a fresh one instead results in making a THIRD busybox that then messes up the whole system completely.

*********

Edit 3:

This issue seems to have become a Siyah issue at this point.

I did a factory restore wipe, installed Siyah, and did *not* install Busybox and got the exact same error log.

Installing Busybox still gives the same result, but after a reboot Busybox will then warn that 'multiple versions of busybox are installed' then an other reboot later it says it can't detect busybox.

Siyah is causing way too many issues for me at this point. Think I should try a different kernel.

*********

Original post:

As recommended earlier, I tried reflashing my phone and I installed both Siyah kernel and removed the old busybox and instead installed the newest version of busybox to /system/bin

However my results seem to be a whole lot worse.

If I restore my system back to using CF-Root with it's pre-installed busybox, my error log is still what I posted earlier.

But with the new busybox and kernel this is my error log now:

app_178@android:/ $ su
app_178@android:/ # cd /sdcard/external_sd/ubuntu
ubuntu.sh <
Loop device exists
mount: mounting /dev/block/loop255 on /data/local/mnt failed: Invalid argument
mount: mounting devpts on /data/local/mnt/dev/pts failed: No such file or directory
mount: mounting proc on /data/local/mnt/proc failed: No such file or directory
mount: mounting sysfs on /data/local/mnt/sys failed: No such file or directory
mount: mounting /sdcard on /data/local/mnt/sdcard failed: No such file or directory
mount: mounting /sdcard/external_sd on /data/local/mnt/external_sd failed: No such file or directory
net.ipv4.ip_forward = 1
ubuntu.sh[58]: cannot create /data/local/mnt/etc/resolv.conf: No such file or directory
ubuntu.sh[59]: cannot create /data/local/mnt/etc/resolv.conf: No such file or directory
ubuntu.sh[60]: cannot create /data/local/mnt/etc/hosts: No such file or directory
Ubuntu is configured with SSH and VNC servers that can be accessed from the IP:
eth0: No such device

chroot: can't execute '/root/init.sh': No such file or directory
Shutting down Ubuntu ARM
failed: No such file or directory
failed: No such file or directory
failed: No such file or directory
failed: No such file or directory
failed: No such file or directory
failed: Invalid argument
app_178@android:/sdcard/external_sd/ubuntu #

Any clue what's going on here?