On Tuesday 14 July 2009 20:00:45 Heinz Diehl wrote:
On 14.07.2009, Bob Williams wrote:
Any suggestions as to what's preventing the drive from detected as an encrypted volume at boot time, and therefore invoking cryptsetup?
Another possibility: did you activate boot.crypto by doing a
"chkconfig boot.crypto on"
? This gives the same warning about a loop as in your previous message...
insserv: There is a loop between service boot.localfs and boot.crypto if started insserv: loop involving service boot.crypto at depth 3 insserv: loop involving service boot.localfs at depth 2 insserv: loop involving service boot.clock at depth 1 insserv: loop involving service boot.swap at depth 5 insserv: loop involving service boot.lvm at depth 4 insserv: loop involving service boot.dmraid at depth 5 insserv: loop involving service boot.sysctl at depth 9 insserv: exiting without changing boot order! Bob -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.1, Kernel 2.6.27.21-0.1-default, KDE 4.2.4 Intel Core2 Quad Q9400 2.66GHz, 4GB DDR RAM, nVidia GeForce 9200GS -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org