Hi,

Since last update, booting my ssd powered notebook takes quite a lot
of time (2-3min instead of 30s).
In /var/log/boot.log I found the following message:

Failed to start LSB: Starts and stops login and scanning of iSCSI devices.

Is this a known problem? Is there anything I can do to get a more
detailed error message?

Thank you in advance, Clemens
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Hmm, the more I think about it, the more I think its actually a systemd bug.
Updating to updates-testing didn't help unfourtunatly.

In /var/boot/boot.log the following problem is reported, which seems
to actually delay the boot:

Failed to start LSB: Starts and stops login and scanning of iSCSI
devices.
[FAILED]
See 'systemctl status iscsi.service' for details.


however, status tells me everything went fine, and iscsi is running:

$ systemctl status iscsi.service
iscsi.service - LSB: Starts and stops login and scanning of iSCSI devices.
Loaded: loaded (/etc/rc.d/init.d/iscsi)
Active: active (exited) since Sat, 11 Feb 2012 23:17:58 +0100; 18s ago
Process: 1731 ExecStart=/etc/rc.d/init.d/iscsi start (code=exited,
status=0/SUCCESS)
CGroup: name=systemd:/system/iscsi.service


Any idea what could be the problem?
Having to wait 2-5min for the machine to boot is more annoying than
one would expect

Thanks, Clemens
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Hi Tom,

> I see iscsi is still using a sysV init script. I just
> ran into this with an old init script:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=787366
>
> Perhaps something similar is going on? (Some recent
> change to systemd "improved" this - the exact same
> init script didn't have this problem till after
> I got updates).

Yes, I think its the same bug that causes troubles for you - I've left
a comment to re-open it.
What I find a bit alarming is, that the iscsi init-script was shipped by Fedora.
(Although for some reason nobody else seems to be affected)

As anaconda depends on the iscsi packages (... yeah ..), the only
solution I found was to just delete the script from /etc/initd/iscsi*
- now my system starts up fast again.

Thanks, Clemens
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 12Feb2012 11:16, Clemens Eisserer <linuxhippy@gmail.com> wrote:
| What I find a bit alarming is, that the iscsi init-script was shipped by Fedora.
| (Although for some reason nobody else seems to be affected)
|
| As anaconda depends on the iscsi packages (... yeah ..), the only
| solution I found was to just delete the script from /etc/initd/iscsi*
| - now my system starts up fast again.

You couldn't just turn it off with chkconfig? That avoids breaking the
packages.
--
Cameron Simpson <cs@zip.com.au> DoD#743
http://www.cskk.ezoshosting.com/cs/

If ye can say 'tis a brrraugh brrrrrit moonlicht nicht tonicht ye're
alrrright I ken.
An old Scotts drrrinkin song taught me by my Grandmother
- Ed Campbell, ed@Tekelec.com (maybe)
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org