Install Tools advanced edition :) (tarball only no deb will be coming) - Page 5 - maemo.org

penguinbait | # 41 | 2008-09-23, 20:42 | Report

Originally Posted by pmeng View Post

Hi,

I installed the advanced Install Tools and used them as described on my n810 with Diablo.
But i encounter a strange issue:
When entering bootmenu and selecting to boot from SD Card, it tries a minute to do so, and then suddenly reboots using the OS in flash.
I have not yet been able to boot into the SD card a single time - so i don't know how to debug it. Does someone had a similar issue and some advice for me to fix it?

Thanks a lot penguinbait for this AWESOME software!

Thanks,

Philipp

So you get your menu, but it fails to boot.

Is this the internal card? or external SD?

What does your txt file look like?

You can also run it like so

sh -x clone.sh 1> out.txt 2> err.txt

Then send me both out.txt and err.txt

Last edited by penguinbait; 2008-09-23 at 20:47.

douwen | # 42 | 2008-09-24, 02:35 | Report

I use Install-tools-ad.tgz to clone my Diabo to mmc2 successfully, and my N800 could boot from mmc2 in most case. but sometimes, the booting always failed, with message "Boot form mmc2 failed, booting from flash", i have to re-clone my OS to mmc2, and it work again, after some days, the above situation appear again.
My 8G SDHC card is brand new, and when i use it as a pure data card, it work well with no problem.
i am a newb to linux , just want to know if it is the problem of my Card or the clone procedure?
thanks.

gemniii42 | # 43 | 2008-09-24, 03:39 | Report

What brand card? Some are prone to failure.

douwen | # 44 | 2008-09-24, 04:06 | Report

Kingmax 6 class 8G SDHC..

pmeng | # 45 | 2008-09-25, 14:45 | Report

My txt file is:

Code:

FAT      256
SWAP  192
1         ext3
TIMEOUT 6

err.txt:

Code:

Checking that no-one is using this disk right now ...
OK
Warning: no primary partition is marked bootable (active)
This does not matter for LILO, but the DOS MBR will not boot this disk.
BLKRRPART: Device or resource busy
The command to re-read the partition table failed
Reboot your system now, before using mkfs
If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
to zero the first 512 bytes:  dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)
/root/install-tools/tar: ./var/lib/gps/gps_driver_ctrl: socket ignored
/root/install-tools/tar: ./home/user/.gpe-calendar-rendezvous: socket ignored

out.txt:

Code:

0
STARTING PARTITIONING NOW
STARTING PARTITIONING NOW
STARTING PARTITIONING NOW

Disk /dev/mmcblk1: 125440 cylinders, 4 heads, 16 sectors/track
Old situation:
Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start   End    MiB    #blocks   Id  System
/dev/mmcblk1p1         0+   255    256-    262143+   6  FAT16
/dev/mmcblk1p2       256   3727   3472    3555328   83  Linux
/dev/mmcblk1p3      3728   3919    192     196608   82  Linux swap / Solaris
/dev/mmcblk1p4         0      -      0          0    0  Empty
New situation:
Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start   End    MiB    #blocks   Id  System
/dev/mmcblk1p1         0+   255    256-    262143+   6  FAT16
/dev/mmcblk1p2       256   3727   3472    3555328   83  Linux
/dev/mmcblk1p3      3728   3919    192     196608   82  Linux swap / Solaris
/dev/mmcblk1p4         0      -      0          0    0  Empty
Successfully wrote the new partition table

Re-reading the partition table ...

mkfs.vfat 2.11 (12 Mar 2005)
Setting up swapspace version 1, size = 201322496 bytes
Dateisystem-Label=
OS-Typ: Linux
Blockgröße=4096 (log=2)
Fragmentgröße=4096 (log=2)
444416 Inodes, 888832 Blöcke
44441 Blöcke (5.00%) reserviert für den Superuser
erster Datenblock=0
28 Blockgruppen
32768 Blöcke pro Gruppe, 32768 Fragmente pro Gruppe
15872 Inodes pro Gruppe
Superblock-Sicherungskopien gespeichert in den Blöcken: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736

Schreibe Inode-Tabellen:  0/28 1/28 2/28 3/28 4/28 5/28 6/28 7/28 8/28 9/2810/2811/2812/2813/2814/2815/2816/2817/2818/2819/2820/2821/2822/2823/2824/2825/2826/2827/28erledigt                           
Erstelle Journal (8192 Blöcke): erledigt
Schreibe Superblöcke und Dateisystem-Accountinginformationen: erledigt

Das Dateisystem wird automatisch alle 25 Mounts bzw. alle 180 Tage überprüft,
je nachdem, was zuerst eintritt. Veränderbar mit tune2fs -c oder -t .
STARTING FILESYSTEM CLONE - MAY TAKE A FEW MINUTES - PLEASE WAIT
STARTING FILESYSTEM CLONE - MAY TAKE A FEW MINUTES - PLEASE WAIT
STARTING FILESYSTEM CLONE - MAY TAKE A FEW MINUTES - PLEASE WAIT

 === Flasher for initfs with onscreen bootmenu ===

For safe flashing please do the following:

- close all aplications (to free available RAM and prevent system crash)
- disconnect from wi-fi network (to prevent random system crash with N770)
- make sure you have at least 5MB free disk space in flasher directory
- make sure you know how to reflash device in usual way if this fails

 *** creating initfs.orig.jffs2 ...
-rw-r--r--    1 user     users     1882336 Sep 25 16:37 initfs.orig.jffs2
Part 1 - Preparing initfs.bootmenu.jffs2 image
 *** copying current initfs ... done.
 *** removing extra stuff ...
 *** extracting boot menu files for initfs version 2008-24 ...
./
./dev/
./dev/mmcblk0p3
./dev/mmcblk0p4
./dev/mmcblk1p3
./dev/mmcblk1p4
./usr/
./usr/bin/
./usr/bin/evkey
./usr/bin/fb_update_mode
./linuxrc
 *** copying bootmenu.sh
./
./dev/
./dev/pts/
./dev/ptmx
./usr/
./usr/sbin/
./usr/sbin/utelnetd
 *** OK, utelnetd added
 *** searching for optional bootmenu.conf in current directory ...
 *** OK, bootmenu.conf added
 *** creating initfs.bootmenu.jffs2 ...
-rw-r--r--    1 user     users     1882336 Sep 25 16:39 initfs.bootmenu.jffs2

 *** remounting initfs read only ... OK
 *** caching old initfs to memory (for crash prevention)
 *** erasing initfs partition (/dev/mtd3) ...

Erasing 128 Kibyte @ 0 --  0 % complete. Cleanmarker written at 0.
Erasing 128 Kibyte @ 20000 --  3 % complete. Cleanmarker written at 20000.
Erasing 128 Kibyte @ 40000 --  6 % complete. Cleanmarker written at 40000.
Erasing 128 Kibyte @ 60000 --  9 % complete. Cleanmarker written at 60000.
Erasing 128 Kibyte @ 80000 -- 12 % complete. Cleanmarker written at 80000.
Erasing 128 Kibyte @ a0000 -- 15 % complete. Cleanmarker written at a0000.
Erasing 128 Kibyte @ c0000 -- 18 % complete. Cleanmarker written at c0000.
Erasing 128 Kibyte @ e0000 -- 21 % complete. Cleanmarker written at e0000.
Erasing 128 Kibyte @ 100000 -- 25 % complete. Cleanmarker written at 100000.
Erasing 128 Kibyte @ 120000 -- 28 % complete. Cleanmarker written at 120000.
Erasing 128 Kibyte @ 140000 -- 31 % complete. Cleanmarker written at 140000.
Erasing 128 Kibyte @ 160000 -- 34 % complete. Cleanmarker written at 160000.
Erasing 128 Kibyte @ 180000 -- 37 % complete. Cleanmarker written at 180000.
Erasing 128 Kibyte @ 1a0000 -- 40 % complete. Cleanmarker written at 1a0000.
Erasing 128 Kibyte @ 1c0000 -- 43 % complete. Cleanmarker written at 1c0000.
Erasing 128 Kibyte @ 1e0000 -- 46 % complete. Cleanmarker written at 1e0000.
Erasing 128 Kibyte @ 200000 -- 50 % complete. Cleanmarker written at 200000.
Erasing 128 Kibyte @ 220000 -- 53 % complete. Cleanmarker written at 220000.
Erasing 128 Kibyte @ 240000 -- 56 % complete. Cleanmarker written at 240000.
Erasing 128 Kibyte @ 260000 -- 59 % complete. Cleanmarker written at 260000.
Erasing 128 Kibyte @ 280000 -- 62 % complete. Cleanmarker written at 280000.
Erasing 128 Kibyte @ 2a0000 -- 65 % complete. Cleanmarker written at 2a0000.
Erasing 128 Kibyte @ 2c0000 -- 68 % complete. Cleanmarker written at 2c0000.
Erasing 128 Kibyte @ 2e0000 -- 71 % complete. Cleanmarker written at 2e0000.
Erasing 128 Kibyte @ 300000 -- 75 % complete. Cleanmarker written at 300000.
Erasing 128 Kibyte @ 320000 -- 78 % complete. Cleanmarker written at 320000.
Erasing 128 Kibyte @ 340000 -- 81 % complete. Cleanmarker written at 340000.
Erasing 128 Kibyte @ 360000 -- 84 % complete. Cleanmarker written at 360000.
Erasing 128 Kibyte @ 380000 -- 87 % complete. Cleanmarker written at 380000.
Erasing 128 Kibyte @ 3a0000 -- 90 % complete. Cleanmarker written at 3a0000.
Erasing 128 Kibyte @ 3c0000 -- 93 % complete. Cleanmarker written at 3c0000.
Erasing 128 Kibyte @ 3e0000 -- 96 % complete. Cleanmarker written at 3e0000.
 *** flashing initfs.bootmenu.jffs2 image ...
Writing data to block 0
Writing data to block 20000
Writing data to block 40000
Writing data to block 60000
Writing data to block 80000
Writing data to block a0000
Writing data to block c0000
Writing data to block e0000
Writing data to block 100000
Writing data to block 120000
Writing data to block 140000
Writing data to block 160000
Writing data to block 180000
Writing data to block 1a0000
Writing data to block 1c0000
 *** done
Press enter to reboot device (or ctrl+c to quit, not recommended)
Rebooting ...

By the way: It's a bit strange that i always have to run "export PATH=/sbin:/usr/sbin:/usr/local/sbin:$PATH" before doing anything as root, because it won't find the commands then... Does this only occur on my n810?

Thanks a lot

Philipp

penguinbait | # 46 | 2008-09-26, 20:49 | Report

Originally Posted by pmeng View Post

My txt file is:

Code:

FAT      256
SWAP  192
1         ext3
TIMEOUT 6

By the way: It's a bit strange that i always have to run "export PATH=/sbin:/usr/sbin:/usr/local/sbin:$PATH" before doing anything as root, because it won't find the commands then... Does this only occur on my n810?

Philipp

PATH
Well, not strange as /usr/local/bin is not in your path. My question would be though, what resides in /usr/local that your trying to access?

The logs all look good, did it boot after installing? Also to be clear, what version of OS are you running. I noticed if I installed old version and then did and upgrade through APP manager it hosed my build and I could not boot. Do all upgrades prior to cloning.

I have the same card as you and have no problems. I am wondering if when it stops booting from SD can you boot to flash and access the data or is the whole card corrupt?

Here is a link to fdisk or parted if you want to try manually. I am just not sure what this problem is?
http://tablethacker.com/wp/?p=56

pmeng | # 47 | 2008-09-26, 21:54 | Report

Originally Posted by penguinbait View Post

PATH
My question would be though, what resides in /usr/local that your trying to access?

I always export the paths, after i got root.
If i don't do this, i get a "Command not found" error... Why i am exporting /usr/local is a good question - never thought of if i would need it or not ^^

The System did show the bootmenu after flashing, and i can select to boot from SD Card, but it hangs up while booting, and after some time, reboots and boots into flash.
The System in flash is usable, and i can access the storage card without problems....

I am running Diablo, all updates are installed
(Version says: 4.2008.30-2)

It's all really strange...
Is there a possibility for looking into logfiles or something like this?

Thanks

Philipp

penguinbait | # 48 | 2008-09-26, 22:08 | Report

Originally Posted by pmeng View Post

I always export the paths, after i got root.
If i don't do this, i get a "Command not found" error... Why i am exporting /usr/local is a good question - never thought of if i would need it or not ^^

The System did show the bootmenu after flashing, and i can select to boot from SD Card, but it hangs up while booting, and after some time, reboots and boots into flash.
The System in flash is usable, and i can access the storage card without problems....

I am running Diablo, all updates are installed
(Version says: 4.2008.30-2)

It's all really strange...
Is there a possibility for looking into logfiles or something like this?

Thanks

Philipp

So your saying, its working, then it just reboots itself and you can no longer boot to it?

Or your saying you just turn off one day and it wont boot anymore?

pmeng | # 49 | 2008-09-26, 22:11 | Report

I mean, after using clone.sh i can use the bootmenu.

I can boot into flash without problems, but i can't boot into SD card.

really strange

penguinbait | # 50 | 2008-09-27, 00:23 | Report

This will happen occasionally, you should just reinstall it again. If you have run it 5 times and your getting a menu and it still wont work, I am not sure what the problem is?

Note there should not be any usb connections and not have any virtual memory enabled.

Its possible there is something else wrong with your OS that preventing it from working, but I am not sure what that is.

You could try the DEB and see if there is any better luck? No ext3 though.