Hello,
in the meantime I found out, that installer hangs if one ext2 file
system is used for installation, i.e. / on ext2 file system with /boot
as a normal subdirectory. Don't know why.
With a separate /boot ext2 file system installation works fine.
Best regards
/Ulrich Kleynmans/
Am 14.01.2015 um 17:22 schrieb Martin Michlmayr:
* Ulrich Kleynmans <[email protected]> [2015-01-09 19:29]:
Installation is done with uImage und uInitrd from
ftp.debian.org/debian/dists/stable/main/installer-armel/current/images/kirkwood/netboot/marvell/sheevaplug/.
Installation can be started and works as expected until 'Making the
system bootable' at 33%. Last successfull operation was 'Installed
u-boot-tools '. After this the install hangs without error message. I
waited for serveral hours.
When this happens, please make another SSH connection to the installer
and open a shell (when you connect with SSH, it will ask if you want
to run the installer or a shell). Then take a look at /var/log/syslog
to see what's going on, or possibly use "ps aux" to see what commands
are running/stuck.
But new uImage and uInitrd are not generated, I searched the whole
device for it.
This is related to the problem above. The uImage/uInitrd files are
generated after the step that hung in your installation.