Am 09.07.2015 14:38, schrieb Peter Nagel:
I'm thinking about to first install wheezy and than dist-upgrade to jessie ...Are there any other (better) solutions?
... a dist-upgrade from wheezy to jessie does not solve the problem.The problem might be that jessie comes with a new init system which has a stricter handling of failing "auto" mounts during boot. If it fails to mount an "auto" mount, systemd will drop to an emergency shell rather than continuing the boot - see release-notes (section 5.6.1):
https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#systemd-upgrade-default-init-system For example:If you have installed your system to a RAID1 device and the system is faced with a power failure which (might at the same time) cause a damage to one of your harddisks (out of this RAID1 device) your system will (during boot) drop to an emergency shell rather than boot from the remaining harddisk(s).
I found out that during boot (for some reason) the RAID device is not active anymore and therefore not available within /dev/disk/by-uuid (what causes the drop to the emergency shell).
A quickfix (to boot the system) would be to re-activate the RAID device (e.g. /dev/md0) from the emergency shell ...
mdadm --stop /dev/md0 mdadm --assemble /dev/md0 ... and to exit the shell.(Be careful: After 4 minutes the emergency shell is automatically rebooting)
-------Nevertheless, it would be nice if the system would boot automatically (and e.g. use the spare disk for data synchronization) as it is known to happend under wheezy.
Any ideas how to do that?
Description: S/MIME Cryptographic Signature