[Q] Debian AlternativeOS fails in Uruk 1.5 - Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting

I plug my Archos 101 into my laptop and copy an unarchived Debian rootfs image to rootfs.img, unmount, unplug and reboot. In the alternative OS menu, I choose Debian and stock Android boots. When I mount the image, it looks fine.
Is AlterntativeOS working in 1.5? If so, where might I be going wrong?

---

pengyo said:
I plug my Archos 101 into my laptop and copy an unarchived Debian rootfs image to rootfs.img, unmount, unplug and reboot. In the alternative OS menu, I choose Debian and stock Android boots. When I mount the image, it looks fine.
Is AlterntativeOS working in 1.5? If so, where might I be going wrong?
Click to expand...
Click to collapse
Here is howto for Debian in AlternativeOS - i'll prepare Video later.
http://code.google.com/p/urukdroid/wiki/RM_AlternativeOS_Debian

---

Thank you!
I used your updated script with the name deb.boot.
It came up in the boot screen, but the behavior was the same.
No log output was generated in the AlternativeOS directory.
I also tried creating /mnt/card, which did not exist, and
changing the device name to /dev/block/vold/179:9 which is
what 'mount' reports for the partition mounted on /mnt/storage that
contains the image.

---

Here is (crappy I know - sorry ) video how bootup looks like

---

The video helps, thank you. When I take the same steps, my
system passes through the 'booting' screen much faster and
goes to Android.
Here is something from dmesg that may be related:
Code:
EXT4-fs: mmcblk2p1: Filesystem with huge files cannot be mounted read-write without CONFIG_LBD.
I am running Urukdroid 1.5 upgraded in the default ways from 1.0 that
was installed without incident using simple install. My SD card is a 16G PNY type 4 card,
which has been dreadfully slow and on which iobench hangs at 52%. This also
causes many aplications to trigger the 'kill or wait' dialogue (the applications
generally respond if I wait).
EDIT:
I flashed the 1.5 kernel and initramfs.
I tried the following from the post on booting Urukdroid from openAOS BootMenu:
"you may have to disable huge_file on your ext4 partition/file using tune2fs -O ^huge_file yourfile.img or /dev/yourpartition"
and I tried preceeding my device name with
/dev , /dev/block, and /dev/block/vold
Still no success, and no log output.

---

pengyo said:
The video helps, thank you. When I take the same steps, my
system passes through the 'booting' screen much faster and
goes to Android.
Here is something from dmesg that may be related:
Code:
EXT4-fs: mmcblk2p1: Filesystem with huge files cannot be mounted read-write without CONFIG_LBD.
Click to expand...
Click to collapse
Probably you have formatted this partition manually - with huge_files options, do it again without it.

---

Debian AlterntiveOS fails in Uruk 1.5
Hello at all,
my Archos device is a Archos 70 IT with 250GB hard drive, without SD card.
Have according to instructions from $aur0n repartitioned the hdd, extra partition created for the image files.
According to fdisk it is /dev/sda4, but I can not mount.
mount /dev/sda4 /mnt/card
(mount: special device /dev/sda4 does not exist)
When I mount the device with mount /dev/block/sda4 /mnt/card, I can access it.
ls -l says:
-rwxrwxrwx 1 1000 1015 4026531840 Jul 26 09:48 rootfs.img
the debian.boot is this:
*************************************************************************************************************
#!/bin/sh
#
# Script to boot alternative OS: Debian
#
# OS_Name: Debian
# OS_Desc: Debian armel
#
# Ver: 1.2 (17.08.2011) Adrian (Sauron) Siemieniak
#
set -xv
# Device where debian image reside (storagefs on sdcard in example)
debian_dev="/dev/block/sda4"
debian_dev_mountp="/mnt/card"
# Debian image file
debian_img="rootfs.img"
debian_mountp="/AlternativeOS"
# Mounting device where image file reside
$MOUNT $debian_dev $debian_dev_mountp || log "Failed to mount device with debian file"
# Creating loop device
$LOSETUP /dev/loop0 $debian_dev_mountp"/"$debian_img || log "Mounting system partition failed"
# Mounting debian rootfs disk
$MOUNT /dev/loop0 $debian_mountp
# Switching to debian
exec /sbin/switch_root $debian_mountp /sbin/init
# IF it fails - we can do some clean ups
$UMOUNT $debian_mountp
$UMOUNT $debian_dev_mountp
*************************************************************************************************************
The Folder, /mnt/card, have i created manually.
When boot to AlternativeOS - debian, debian does not start.
Android Froyo starts.
When i reboot to Developer Edition, UrukDroid starts normaly.
When i boot the Image under Standard Froyo as Developer Edition it's OK.
What is wrong?
Can anyone help me?
Sorry for my bad english.
best regards
kwalter

---

Check /AlternativeOS/debug.txt. It's certainly not /dev/block/xxx (this path is correct AFTER Uruk is booted, during initramfs its /dev/)

---

debug.txt is empty.
i have changed to: debian_dev="/dev/sda4"
The problem is the same.

---

kwalter said:
debug.txt is empty.
Click to expand...
Click to collapse
Make sure /AlternativeOS/debian.boot has +x for user (chmod u+x /AlternativeOS/debian.boot).

---

i have done chmod u+x /AlternativeOS/debian.boot
The Problem is the same.

---

k - i join in
tried the same with openAOS
used the script from http://code.google.com/p/urukdroid/wiki/RM_AlternativeOS_Debian (copy & paste) all I edited was rootfs.img -> openAOS.img
mkdir /mnt/card
rm /AlternativeOS/debug.txt
chmod 777 /AlternativeOS/openAOS.boot
openAOS.img is in root for SDCard -> mnt/storage/sdcard/openAOS.img
tried to boot (rescure menu -> select openAOS) -> short white bootup dialog of AlternativeOS (openAOS) -> blackscreen -> reboot (will boot stock FW) -> no debug.txt created
tried again with creating debug.txt again (with vi empty file :wq)
chmod 666 debug.txt
-> same as above nothing in debug.txt

---

FrEcP said:
k - i join in
mkdir /mnt/card
Click to expand...
Click to collapse
This is not required - since it's /mnt/card on initramfs (and there is this directory).
About debug.txt - I'll add more debug information and put new package.
edit: Your problem (lack of debug.txt) is because device reboot itself before it finish writing to disk... So either give "sync" after every command - or remove for a while "switch" - which cause device to reboot.
Anyway I'll modified initramfs and script to be more user friendly - I'll publish it soon...

---

@$auron
..... I would like to try debian ... but I don't understand at all the instructions to do it can you do a tread about this ... or maybe instructions on wiki ???

---

Ok,
So install this UD package
http://sauron.pourix.com/UrukDroid/UrukDroid-1.5/UrukDroid-1.5.1-kernel.tbz2
Use this boot script
Code:
#!/bin/sh
#
# Script to boot alternative OS: Debian
#
# OS_Name: Debian
# OS_Desc: Debian armel
#
# Ver: 1.2 (17.08.2011) Adrian (Sauron) Siemieniak
#
set -xv
# Device where debian image reside (storagefs on sdcard in example)
debian_dev="/dev/mmcblk2p1"
debian_dev_mountp="/mnt/card"
# Debian image file
debian_img="rootfs.img"
debian_mountp="/AlternativeOS"
# Mounting device where image file reside
$MOUNT $debian_dev $debian_dev_mountp || log_msg "Failed to mount device with debian file"
sync
# Creating loop device
$LOSETUP /dev/loop0 $debian_dev_mountp"/"$debian_img || log_msg "Mounting AlternativeOS partition failed"
sync
# Mounting debian rootfs disk
$MOUNT /dev/loop0 $debian_mountp
# It mount went ok
if [ $! -eq 0 ]; then
# Switching to debian
exec /sbin/switch_root $debian_mountp /sbin/init
fi
# IF it fails - we can do some clean ups
$UMOUNT $debian_mountp
$UMOUNT $debian_dev_mountp
This is how debug.txt will look like (this bootup failed because rootfs.img is missing)
Code:
Fri Aug 19 07:48:21 MDT 2011
Booting up Alternative OS: debian
Bootup file is: /new-root/AlternativeOS/debian.boot
# Device where debian image reside (storagefs on sdcard in example)
debian_dev="/dev/mmcblk2p1"
+ debian_dev=/dev/mmcblk2p1
debian_dev_mountp="/mnt/card"
+ debian_dev_mountp=/mnt/card
# Debian image file
debian_img="rootfs.img"
+ debian_img=rootfs.img
debian_mountp="/AlternativeOS"
+ debian_mountp=/AlternativeOS
# Mounting device where image file reside
$MOUNT $debian_dev $debian_dev_mountp || log_msg "Failed to mount device with debian file"
+ /bin/mount /dev/mmcblk2p1 /mnt/card
sync
+ sync
# Creating loop device
$LOSETUP /dev/loop0 $debian_dev_mountp"/"$debian_img || log_msg "Mounting AlternativeOS partition failed"
+ /sbin/losetup /dev/loop0 /mnt/card/rootfs.img
losetup: /dev/loop0: No such file or directory
+ log_msg Mounting AlternativeOS partition failed
+ /bin/aui -c message -t AlternativeOS: Mounting AlternativeOS partition failed
sync
+ sync
# Mounting debian rootfs disk
$MOUNT /dev/loop0 $debian_mountp
+ /bin/mount /dev/loop0 /AlternativeOS
mount: mounting /dev/loop0 on /AlternativeOS failed: Invalid argument
# It mount went ok
if [ $! -eq 0 ]; then
# Switching to debian
exec /sbin/switch_root $debian_mountp /sbin/init
fi
+ [ 575 -eq 0 ]
# IF it fails - we can do some clean ups
$UMOUNT $debian_mountp
+ /bin/umount /AlternativeOS
umount: can't umount /AlternativeOS: Invalid argument
$UMOUNT $debian_dev_mountp
+ /bin/umount /mnt/card
rplc790222 said:
@$auron
..... I would like to try debian ... but I don't understand at all the instructions to do it can you do a tread about this ... or maybe instructions on wiki ???
Click to expand...
Click to collapse
There IS instruction of wiki.

---

$aur0n said:
Ok,
So install this UD package
http://sauron.pourix.com/UrukDroid/UrukDroid-1.5/UrukDroid-1.5.1-kernel.tbz2
Use this boot script
Code:
#!/bin/sh
#
# Script to boot alternative OS: Debian
#
# OS_Name: Debian
# OS_Desc: Debian armel
#
# Ver: 1.2 (17.08.2011) Adrian (Sauron) Siemieniak
#
set -xv
# Device where debian image reside (storagefs on sdcard in example)
debian_dev="/dev/mmcblk2p1"
debian_dev_mountp="/mnt/card"
# Debian image file
debian_img="rootfs.img"
debian_mountp="/AlternativeOS"
# Mounting device where image file reside
$MOUNT $debian_dev $debian_dev_mountp || log_msg "Failed to mount device with debian file"
sync
# Creating loop device
$LOSETUP /dev/loop0 $debian_dev_mountp"/"$debian_img || log_msg "Mounting AlternativeOS partition failed"
sync
# Mounting debian rootfs disk
$MOUNT /dev/loop0 $debian_mountp
# It mount went ok
if [ $! -eq 0 ]; then
# Switching to debian
exec /sbin/switch_root $debian_mountp /sbin/init
fi
# IF it fails - we can do some clean ups
$UMOUNT $debian_mountp
$UMOUNT $debian_dev_mountp
This is how debug.txt will look like (this bootup failed because rootfs.img is missing)
Code:
Fri Aug 19 07:48:21 MDT 2011
Booting up Alternative OS: debian
Bootup file is: /new-root/AlternativeOS/debian.boot
# Device where debian image reside (storagefs on sdcard in example)
debian_dev="/dev/mmcblk2p1"
+ debian_dev=/dev/mmcblk2p1
debian_dev_mountp="/mnt/card"
+ debian_dev_mountp=/mnt/card
# Debian image file
debian_img="rootfs.img"
+ debian_img=rootfs.img
debian_mountp="/AlternativeOS"
+ debian_mountp=/AlternativeOS
# Mounting device where image file reside
$MOUNT $debian_dev $debian_dev_mountp || log_msg "Failed to mount device with debian file"
+ /bin/mount /dev/mmcblk2p1 /mnt/card
sync
+ sync
# Creating loop device
$LOSETUP /dev/loop0 $debian_dev_mountp"/"$debian_img || log_msg "Mounting AlternativeOS partition failed"
+ /sbin/losetup /dev/loop0 /mnt/card/rootfs.img
losetup: /dev/loop0: No such file or directory
+ log_msg Mounting AlternativeOS partition failed
+ /bin/aui -c message -t AlternativeOS: Mounting AlternativeOS partition failed
sync
+ sync
# Mounting debian rootfs disk
$MOUNT /dev/loop0 $debian_mountp
+ /bin/mount /dev/loop0 /AlternativeOS
mount: mounting /dev/loop0 on /AlternativeOS failed: Invalid argument
# It mount went ok
if [ $! -eq 0 ]; then
# Switching to debian
exec /sbin/switch_root $debian_mountp /sbin/init
fi
+ [ 575 -eq 0 ]
# IF it fails - we can do some clean ups
$UMOUNT $debian_mountp
+ /bin/umount /AlternativeOS
umount: can't umount /AlternativeOS: Invalid argument
$UMOUNT $debian_dev_mountp
+ /bin/umount /mnt/card
There IS instruction of wiki.
Click to expand...
Click to collapse
Jajajaja I missed the wiki instructions, my bad ... I will try later

---

I re-formatted my microsd card, with huge_file option disabled on the first partition.
The debug output shows the script runs, echoing each command without errors until
#IF mount went ok
after that block, the output differs from yours slightly:
+[ 563 -eq 0]
Then the umount commands close with another line of different output:
+/bin/umount /mnt/card
umount: can't umount /mnt/card: Device or resource busy
The output in the alternative boot menu is something to the effect
'debian failed to boot' and goes back to boot options.

---

pengyo said:
I re-formatted my microsd card, with huge_file option disabled on the first partition.
The debug output shows the script runs, echoing each command without errors until
#IF mount went ok
after that block, the output differs from yours slightly:
+[ 563 -eq 0]
Then the umount commands close with another line of different output:
+/bin/umount /mnt/card
umount: can't umount /mnt/card: Device or resource busy
The output in the alternative boot menu is something to the effect
'debian failed to boot' and goes back to boot options.
Click to expand...
Click to collapse
same here - full debug.txt:
Fri Aug 19 17:55:21 MDT 2011
Booting up Alternative OS: openAOS
Bootup file is: /new-root/AlternativeOS/openAOS.boot
# Device where debian image reside (storagefs on sdcard in example)
debian_dev="/dev/mmcblk2p1"
+ debian_dev=/dev/mmcblk2p1
debian_dev_mountp="/mnt/card"
+ debian_dev_mountp=/mnt/card
# Debian image file
debian_img="openAOS.img"
+ debian_img=openAOS.img
debian_mountp="/AlternativeOS"
+ debian_mountp=/AlternativeOS
# Mounting device where image file reside
$MOUNT $debian_dev $debian_dev_mountp || log_msg "Failed to mount device with debian file"
+ /bin/mount /dev/mmcblk2p1 /mnt/card
sync
+ sync
# Creating loop device
$LOSETUP /dev/loop0 $debian_dev_mountp"/"$debian_img || log_msg "Mounting AlternativeOS partition failed"
+ /sbin/losetup /dev/loop0 /mnt/card/openAOS.img
sync
+ sync
# Mounting debian rootfs disk
$MOUNT /dev/loop0 $debian_mountp
+ /bin/mount /dev/loop0 /AlternativeOS
# It mount went ok
if [ $! -eq 0 ]; then
# Switching to debian
exec /sbin/switch_root $debian_mountp /sbin/init
fi
+ [ 563 -eq 0 ]
# IF it fails - we can do some clean ups
$UMOUNT $debian_mountp
+ /bin/umount /AlternativeOS
$UMOUNT $debian_dev_mountp
+ /bin/umount /mnt/card
umount: can't umount /mnt/card: Device or resource busy

---

Thanks for showing us how to get output into the log file $auron.
It seems the problem is at the switch_root command. It gives a usage
message as if it did not recognize one of its arguments- the mount point
or the init.

---

FrEcP said:
same here - full debug.txt:
$MOUNT /dev/loop0 $debian_mountp
+ /bin/mount /dev/loop0 /AlternativeOS
# It mount went ok
if [ $! -eq 0 ]; then
# Switching to debian
exec /sbin/switch_root $debian_mountp /sbin/init
fi
+ [ 563 -eq 0 ]
Click to expand...
Click to collapse
This is the problem (not switch root). Mount failed. Mount returned 563 output - and should 0. That's why switch_root is even not executed.