when /flash or /storage is on non-persistent storage, it's not
yet available at the time fsck -a -p fires, so just skip
and force fsck only if ret=4
now, if /flash or /storage is non-persistent, users get
either non-recovered fs (just as it was before) or debug
shell if the fs is fubar (bad sb and so). nobody cares.
this makes no sense and may stop systemd-tmpfiles-setup,
journald-flush, sshd, irserver from starting
===
Jan 18 18:23:03 openelec systemd[1]: Found ordering cycle on systemd-tmpfiles-setup.service/start
Jan 18 18:23:03 openelec systemd[1]: Found dependency on systemd-journal-flush.service/start
Jan 18 18:23:03 openelec systemd[1]: Found dependency on var-log-debug.service/start
Jan 18 18:23:03 openelec systemd[1]: Found dependency on systemd-tmpfiles-setup.service/start
Jan 18 18:23:03 openelec systemd[1]: Breaking ordering cycle by deleting job systemd-journal-flush.service/start
===
units with DefaultDependencies=no should be always properly ordered.
