OK, it is a good sign. (But it seems that "mr0" version doesn't have bug 10994).

Now, please do

./M32GBboot.sh

copy an attached files to /bootmenu.sh and /sbin/preinit :

cp bootmenu.sh.txt /bootmenu.sh
cp preinit.txt /sbin/preinit

and reboot with open KBD.

Your N900 would NOT BOOT with this files but you should see a console output which would freeze for 10 secs at message

**************** CHROOT RUN LEVEL=XXX

After that freeze a watchdog will enforce a new reboot. Please immediately close KBD, go to a regular boot and run ./M32GBrm.sh to restore both files. You should do it because there is a potentially a boot loop which can be interrupted by closing KBD. Just remember that N900 has a failed reboot counter and if it exceed 15 or 20 failed reboots in line some Nokia software will enforce a permanent shutdown and the only battery disconnection + rootFS + kernel reflash can help in this case.

And I am interesting in numeric value in place of XXX.

Thanks at this point for your help and your patience.

chroot run level 2 was the output of the boot with open KBD.

OK, good, then -

Please install klogd and sysklogd applications, do again
./M32GBrm.sh
./M32GBinit.sh
./M32GBboot.sh
and reboot with open KBD. If it still boots an old system - please send me files /home/var/log/syslog and /home/var/log/maemo-optify-boottime.log

Thank you.

ok, i booted again after running the three scripts but ended up in the old system.
the two log files are attached. the ones with the home prefix are from /home/var/log and those without are from /var/log

Do you think we will find a way to get this working until tuesday? if not, i would now install some applications for my vacations and could reflash my device afterwards when i come back to go on and try to get some more space at my rootfs to install ,any applications, even non-optified (using rootfs) ones.

I am not sure about Tuesday.

You have some very non-standard environment and I am looking into it trying to determine that is going on.

For a moment I don't see a couple of processes in /home syslog, Moreover, the /home syslog is duplicated in standard syslog but that should be a different run and it can be duplicated only if copied or so and DSME never starts during /home boot.

BTW, you have some FS errors in one of VFAT (eMMC or uSD)... but that should be not a problem.

Ok, so i will set up the device for my trip and come back afterwards.

What confuses me is, i reflashed the device, so this should be the very standard environment. I've got a N900 with global image flashed.

The syslog files where copied during M23GBinit.sh i think.

The FS errors come from my uSD card, which i reparted before inserting it. But this should have gone away now, because i set it to teh defaults this morning.

JanMalte - I would like to ask you all list of modifications which you did after re-flashing. And please send me your files

/etc/init.d/rcS
/etc/event.d/rcS-late
/sbin/preinit
/bootmenu.sh

I see the mount of uSD partition 3 as a swap before mounting eMMC partition 2 which should happen in /bootmenu.sh
Taking into account that swap mounts may happen in 2 scripts (rcS and rcS-late) which never run before /bootmenu.sh (it mounts EXT3!), I can't explain that.

It is a biggest issue for now. In normal boot it shows in log in regular place.

Can you check that your /var, /var/log are not symlinked to some place in /home? It can be a way how the same piece of log is duplicated in both logs. It is also very difficult to explain.

Can you also run EXT3 FS check? -

/sbin/fsck -n /dev/mmcblk0p2

Yet another question -

Can you try without uSD card?

EDIT: if you have on uSD file /sbin/preinit then startup process will definitely attempt using this as new root and it may fails if system doesn't respond in 15secs to watchdog. And that can explain all problems...

Ok, now i reflashed my device again. Now i did the following changes:

• add extras-devel as repository
• install rootsh

then i copied the files you want to /root/ and compressed them to upload here.

Now i run your Scripts again and copy the files again to /root/, compress them and upload them here.

The uSD card was removed since reflashing this time, so this should make any problems now.
/var/logs is not symlinked to any directory under /home/