Download | Devuan.org | Git | Bugs | Packages

The officially official Devuan Forum!

You are not logged in.

Pages: 1

#1 Re: Hardware & System Configuration » iSCSI autostart » 2025-10-02 12:28:16

deutschem

ok, runlevel was the tip of the day.
I am on Devuan and like Debian-way I think I am on runlevel 2 not 5. Based on that realization the login at boot works now. (sorry for the noise)

Last thing: it tries 2 times login at boot (first time 120 sec wait (ok,I can change that with node.session.initial_login_retry_max) second time login works immediately)

boot log:
.
.
Thu Oct  2 14:04:53 2025: Setting up iSCSI targets:
Thu Oct  2 14:04:53 2025: Logging in to [iface: default, target: iqn.2025-09.internal.testing.site1:11111, portal: 10.66.200.8,3260]
Thu Oct  2 14:05:09 2025: iscsiadm: Could not login to [iface: default, target: iqn.2025-09.internal.testing.site1:11111, portal: 10.66.99.8,3260].
Thu Oct  2 14:05:09 2025: iscsiadm: initiator reported error (8 - connection timed out)
Thu Oct  2 14:05:09 2025: iscsiadm:
Thu Oct  2 14:05:09 2025: Could not log into all portals
Thu Oct  2 14:05:09 2025: .
.
.
.
after entering runlevel 2
Thu Oct  2 14:05:15 2025: Setting up iSCSI targets:
Thu Oct  2 14:05:15 2025: Logging in to [iface: default, target: iqn.2025-09.internal.testing.site1:11111, portal: 10.66.200.8,3260]
Thu Oct  2 14:05:21 2025: Login to [iface: default, target: iqn.2025-09.internal.testing.site1:11111, portal: 10.66.200.8,3260] successful.
Thu Oct  2 14:05:21 2025: .

what am I missing ?

thank you

regards

#2 Re: Hardware & System Configuration » iSCSI autostart » 2025-10-02 08:09:29

deutschem

now it looks like:

lrwxrwxrwx 1 root root 20  2. Okt 09:36 /etc/rc3.d/S17open-iscsi -> ../init.d/open-iscsi
lrwxrwxrwx 1 root root 20  2. Okt 09:36 /etc/rc5.d/S17open-iscsi -> ../init.d/open-iscsi
lrwxrwxrwx 1 root root 20  2. Okt 09:57 /etc/rcS.d/S17open-iscsi -> ../init.d/open-iscsi

and

lrwxrwxrwx 1 root root 16  1. Okt 10:57 /etc/rc0.d/K01iscsid -> ../init.d/iscsid
lrwxrwxrwx 1 root root 16  1. Okt 10:57 /etc/rc1.d/K01iscsid -> ../init.d/iscsid
lrwxrwxrwx 1 root root 16  1. Okt 18:24 /etc/rc3.d/S16iscsid -> ../init.d/iscsid
lrwxrwxrwx 1 root root 16  1. Okt 18:16 /etc/rc5.d/S16iscsid -> ../init.d/iscsid
lrwxrwxrwx 1 root root 16  1. Okt 10:57 /etc/rc6.d/K01iscsid -> ../init.d/iscsid
lrwxrwxrwx 1 root root 16  2. Okt 09:22 /etc/rcS.d/S16iscsid -> ../init.d/iscsid

now I get again:

iscsiadm: initiator reported error (8 - connection timed out)

To keep coming, are the symlinks all correct now to principally, if the configs are all correct too, autostart iscsi and autologin ?

thanks

regards

#3 Re: Hardware & System Configuration » iSCSI autostart » 2025-10-01 16:43:38

deutschem

ok, now it looks like:
lrwxrwxrwx 1 root root 16  1. Okt 10:57 /etc/rc0.d/K01iscsid -> ../init.d/iscsid
lrwxrwxrwx 1 root root 16  1. Okt 10:57 /etc/rc1.d/K01iscsid -> ../init.d/iscsid
lrwxrwxrwx 1 root root 16  1. Okt 18:24 /etc/rc3.d/S16iscsid -> ../init.d/iscsid
lrwxrwxrwx 1 root root 16  1. Okt 18:16 /etc/rc5.d/S16iscsid -> ../init.d/iscsid
lrwxrwxrwx 1 root root 16  1. Okt 10:57 /etc/rc6.d/K01iscsid -> ../init.d/iscsid
lrwxrwxrwx 1 root root 16  1. Okt 16:05 /etc/rcS.d/K01iscsid -> ../init.d/iscsid

and no iscsid error entry in boot log.

but:

service iscsid status
iscsid is not running ... failed!

regards

#4 Re: Hardware & System Configuration » iSCSI autostart » 2025-10-01 14:11:49

deutschem

ok, this worked.
but now I get

iscsiadm: initiator reported error (8 - connection timed out)
ls -l /etc/rc?.d/*iscsid

shows:
lrwxrwxrwx 1 root root 16  1. Okt 10:57 /etc/rc0.d/K01iscsid -> ../init.d/iscsid
lrwxrwxrwx 1 root root 16  1. Okt 10:57 /etc/rc1.d/K01iscsid -> ../init.d/iscsid
lrwxrwxrwx 1 root root 16  1. Okt 10:57 /etc/rc6.d/K01iscsid -> ../init.d/iscsid
lrwxrwxrwx 1 root root 16  1. Okt 16:05 /etc/rcS.d/K01iscsid -> ../init.d/iscsid

should it be in runlevel 5 ?

if yes:
should I do this in Devuan with update-rc or sysv-rc-conf ?

thank you

regards

#5 Hardware & System Configuration » iSCSI autostart » 2025-10-01 11:10:13

deutschem
Replies: 9

Hello,

i want to automatically lgoin to an iSCSI target on boot.

the manual way works without problems
(for example: 

iscsiadm -m node -T iqn.2025-09.internal.testing.site1:11111 -l

)

So ISCSI may be correct configured (yes, the option(s) node.startup is automatic)

I recognized that the iscsd deamon is not started after boot.
If I look into the /etc/iscsi/iscsid.conf I see

iscsid.startup = /bin/systemctl start iscsid.socket iscsiuio.socket

is uncommented, but we have no systemd ??...

Then I see 

iscsid.startup = /usr/bin/service start iscsid

but service is in /usr/sbin .... and should it not look like "...../service iscsid start" ?

I tried all changes but on boot.log I get:

iSCSI initiator daemon not started: not logging in to default targets ... failed!

and

startpar: service(s) returned failure: open-iscsi ... failed!

If I do a 

service iscsid start

and 

service open-iscsi start

the login works automatically and fine.

(tests on other systemd-distros worked)
any help ?

regards

#6 Hardware & System Configuration » pamu2fcfg not working on chimaera as user (nonroot), but ... » 2023-09-13 11:28:21

deutschem
Replies: 0

Hello,

... on Daedalus or Debian or Ubuntu it works with nonroot user.

(Want to use fido stick for 2fa with sudo)

therefore there are maybe wrong permissions (file/folder) in chimaera for oamu2fcg-system ? Where ?

thank yoou

#7 Re: Hardware & System Configuration » Luks decrypt home on boot with key and fallback password » 2023-08-15 14:04:48

deutschem

yes, seems that is also my way to use keyfile on stick and if the key is lost/damaged i fix it with the password slot and a live CD, not fancy. I feel I do not trust the keyscript-thing

fsmithred wrote:

This page might have the answer. It looks like you have to use a keyscript. https://stackoverflow.com/questions/197 … o-keyboard

I've never done that. I use a keyfile, and if the keyfile is doesn't work, I have a keyslot with a passphrase that I can use to fix it (make a new keyfile) after booting a live-CD or live-USB.

.

#8 Re: Hardware & System Configuration » Luks decrypt home on boot with key and fallback password » 2023-08-15 14:01:36

deutschem

yes, sorry I wrote it unclear, i want the fallback on boot (Boot->Stick is plugged->encrypt with keyfile (this works)), now if stick is not plugged in i want boot-> ask for password (in my case in slot 0)
If i do not plug in the stick, then the boot process runs fine to the end but of course without /home mounted....

rolfie wrote:

Ok, then you have your fallback option already. I am not 100% sure how that works in your case, I am used to use full disk encryption.

What happens in your case when the key stick isn't plugged in? Do you end up in the initramfs?

#9 Re: Hardware & System Configuration » Luks decrypt home on boot with key and fallback password » 2023-08-14 12:30:09

deutschem

in my LUKS volume i have 2 slots, one (slot 0) with a password and the second (with lukdAddKey) with the keyfile.

#10 Hardware & System Configuration » Luks decrypt home on boot with key and fallback password » 2023-08-14 06:06:25

deutschem
Replies: 7

Hi,

i 've configure successfully configured that my home partition was unlocked with a plugged in usb stick.
but i dont know how to configure the fallback (if stick is not pugged in use password).

the most hints are for systemd for ex:
https://forums.debian.net/viewtopic.php?t=152061

I use SysVinit

unplugged usb:
Sun Aug 13 21:44:58 2023: Starting remaining crypto disks...crypt_home (starting)...Invalid key path
Sun Aug 13 21:44:58 2023: Cannot seek to requested keyfile offset.
Sun Aug 13 21:44:58 2023: Invalid key path
Sun Aug 13 21:44:58 2023: Cannot seek to requested keyfile offset.
Sun Aug 13 21:44:58 2023: Invalid key path
Sun Aug 13 21:44:58 2023: Cannot seek to requested keyfile offset.
Sun Aug 13 21:44:58 2023: crypt_home (failed)...^[[31mfailed.^[[39;49m
Sun Aug 13 21:44:58 2023: done.

thank you

regards

Pages: 1

Board footer

Forum Software