-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/05/2011 09:08 AM, Frantisek Hanzlik wrote: > Xiao Peng Wang wrote: >> Hi, >> >> I made a diskless image against Fedora15, during the boot I found >> it displayed the following error message and went into emergency >> mode. >> >> The error message: Starting Relabel all filesystems, if necessary >> ^[[1;31maborted^[[0m because a dependency failed. [ 107.607155] >> systemd[1]: Job fedora-autorelabel.service/start failed with >> result 'dependency'. Starting Mark the need to relabel after >> reboot ^[[1;31maborted^[[0m because a dependency failed. [ >> 107.625156] systemd[1]: Job >> fedora-autorelabel-mark.service/start failed with result >> 'dependency'. [ 107.634580] systemd[1]: Job local-fs.target/start >> failed with result 'dependency'. [ 107.642615] systemd[1]: >> Triggering OnFailure= dependencies of local-fs.target. [ >> 107.650738] systemd[1]: Job var-tmp.mount/start failed with >> result 'dependency'. [ 107.658580] systemd[1]: Job >> fsck@tmpfs.service/start failed with result 'dependency'. [ >> 107.666876] systemd[1]: Job tmpfs.device/start failed with >> result 'timeout'. Welcome to emergency mode. Use "systemctl >> default" or ^D to activate default mode. >> >> And when I run the command 'service sshd start' to start the >> sshd, it displayed the following error message: [ 8545.884404] >> udev[2872]: starting version 167 [ 8635.560123] systemd[1]: Job >> tmpfs.device/start timed out. [ 8635.565867] systemd[1]: Job >> fedora-autorelabel.service/start failed with result >> 'dependency'. [ 8635.574812] systemd[1]: Job >> fedora-autorelabel-mark.service/start failed with result >> 'dependency'. [ 8635.584217] systemd[1]: Job >> local-fs.target/start failed with result 'dependency'. [ >> 8635.592203] systemd[1]: Triggering OnFailure= dependencies of >> local-fs.target. [ 8635.600311] systemd[1]: Job >> var-tmp.mount/start failed with result 'dependency'. [ >> 8635.608102] systemd[1]: Job fsck@tmpfs.service/start failed >> with result 'dependency'. [ 8635.616355] systemd[1]: Job >> tmpfs.device/start failed with result 'timeout'. Welcome to >> emergency mode. Use "systemctl default" or ^D to activate default >> mode. Then I tried to start the tmpfs.device # systemctl start >> tmpfs.device [432039.543362] systemd[1]: Job tmpfs.device/start >> timed out. [432039.549335] systemdJob timed out. Looks like the >> tmpfs.device was not installed. Did I miss something that >> depended by system? Any comments are appreciated. >> >> >> >> Thanks Best Regards >> ---------------------------------------------------------------------- >> >> Wang Xiaopeng (王晓朋) >> IBM China System Technology Laboratory Tel: 86-10-82453455 Email: >> wxp@xxxxxxxxxx Address: 28,ZhongGuanCun Software Park,No.8 Dong >> Bei Wang West Road, Haidian District Beijing P.R.China 100193 >> !DSPAM:4e6497a4108619485919262! > > Emergency mode systemd target is equivalent to runlevel 1 > singleuser mode at SysV init system, thus probably network isn't > active and sshd refuses to run. > > I'm not sure, but tmpfs (shm fs) need active swap, which probably > isn't on diskless station. > > Another question is, when SELinux is appropriate to run on > diskless station (you may try disable it). > > I also saw problem, when dracut was not able start diskless PXE > F14 station when LAN default router was down (but it isn't this > case). > > Or there is just reciprocal proportion principle: when systemd > consumes 10x more RAM then SysV init, then he can 10x fewer. > (narrowly, i686 F15 system comsumes 9x more RAM compared to i686 > F7 SysVinit on my systems) > > > Franta Hanzlik Yes since we do not support labeling on NFS, SELinux most likely will not work in this environment. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5mLGcACgkQrlYvE4MpobOexQCgzPZmNZLa2FroQ38EbhPCYHqX 1dIAn1FrBWgJSXUWRO9++e4sNgKRiNQA =n91G -----END PGP SIGNATURE----- -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
