[ N810 , diablo 43-7 , also cloned ]

Just in case someone can guess ...

Running from flash,
I guess I must have accidentally messed the file system up.

I used emelfm2 to edit and install a startup script in /etc/init.d/ .
OK after REBOOT,
and the thus as /mnt/storage mounted ext2-partition
was visible in the File Manager.
Then I linked: ln -s /mnt/storage/seq /home/user/.seqretary ,
and tried to make Seqretary work from there.

>> The result :
After a REBOOT the tablet shows the Nokia hands,
and then hangs looking like the photo.
The menu from the power button is accessible.

From there :
Switching off by the power button menu and powering on
brings the hung system up again.
or :
Powering off by a long press of the power button and powering on again
brings the flash system up looking OK.

Again, from OK system,
any of these or a reboot (through the boot menu)
brings up the (same) hung system.


Is this possible to diagnose?
( Just trying to learn something.)


The startup script in /etc/init.d/ :
insmod /mnt/initfs/lib/modules/2.6.21-omap1/mbcache.ko
insmod /mnt/initfs/lib/modules/2.6.21-omap1/ext2.ko
mount /dev/mmcblk0p4 /mnt/storage

Initiated by :
ln -s /etc/init.d/my_script /etc/rc2.d/S15my_script

( following the wiki http://wiki.maemo.org/Moving_system_...o_a_flash_card ,
and having found in the forum that rc2.d (?) would suffice )



EDIT :

I managed to recreate the same-looking hung system in a simpler way,
now running from a clone in int. mmc.

1) In X Terminal as user :
mkdir /mnt/storage ,
2) as root :
mount /dev/mmcblk0p4 /mnt/storage .
3) Moved /home/user/.seqretary to /mnt/storage (with emelfm2) .
4) In X Terminal as user :
/bin/ln -s /dev/mmcblk0p4/.seqretary /mnt/storage/.seqretary .
>> Seqretary worked.

5) Rebooted, and so broke the mount and the link.
>> Same-looking hung system with the same symptoms.


Is this a maemo or a Seqretary problem ?
It seems a bit weird, that a broken link in an application should have such consequences ?