raptorz

Members
  • Content Count

    3
  • Joined

  • Last visited

  1. Thank you very very much. iSCSI is work fine for me.
  2. Thank you very much. I have installed this version and check the open-iscsi: apt install is OK, but service iscsid still fail: ● iscsid.service - iSCSI initiator daemon (iscsid) Loaded: loaded (/lib/systemd/system/iscsid.service; disabled; vendor preset: enabled) Active: activating (start) since Fri 2018-11-16 12:52:51 UTC; 27s ago Docs: man:iscsid(8) Process: 8838 ExecStart=/sbin/iscsid (code=exited, status=0/SUCCESS) Process: 8835 ExecStartPre=/lib/open-iscsi/startup-checks.sh (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 1895) CGroup: /system.slice/iscsid.service Nov 16 12:52:51 aml systemd[1]: Starting iSCSI initiator daemon (iscsid)... Nov 16 12:52:52 aml iscsid[8838]: iSCSI logger with pid=8839 started! Nov 16 12:52:52 aml systemd[1]: iscsid.service: Failed to parse PID from file /run/iscsid.pid: Invalid argument Nov 16 12:52:52 aml iscsid[8839]: iSCSI daemon with pid=8840 started! Nov 16 12:52:52 aml iscsid[8839]: can not create NETLINK_ISCSI socket I found a commit of armbian/build that comments 'Enable iSCSI kernel options for mvebu-next', is it any help for this problem? thanks again.
  3. Hello, I'm using the newest version armbian for amlogic 5.64 on S905D, but when installing open-iscsi, there are some error messages: ... Job for iscsid.service failed because of unavailable resources or another system error. See "systemctl status iscsid.service" and "journalctl -xe" for details. invoke-rc.d: initscript iscsid, action "start" failed. ● iscsid.service - iSCSI initiator daemon (iscsid) Loaded: loaded (/lib/systemd/system/iscsid.service; enabled; vendor preset: e nabled) Active: failed (Result: resources) since Sat 2018-10-13 13:44:05 UTC; 21ms ag o Docs: man:iscsid(8) Process: 6965 ExecStart=/sbin/iscsid (code=exited, status=0/SUCCESS) Process: 6960 ExecStartPre=/lib/open-iscsi/startup-checks.sh (code=exited, sta tus=0/SUCCESS) Oct 13 13:44:05 aml systemd[1]: Starting iSCSI initiator daemon (iscsid)... Oct 13 13:44:05 aml iscsid[6965]: iSCSI logger with pid=6966 started! Oct 13 13:44:05 aml systemd[1]: iscsid.service: Failed to read PID from fil…ment Oct 13 13:44:05 aml systemd[1]: iscsid.service: Daemon never wrote its PID …ing. Oct 13 13:44:05 aml systemd[1]: Failed to start iSCSI initiator daemon (iscsid). Oct 13 13:44:05 aml systemd[1]: iscsid.service: Unit entered failed state. Oct 13 13:44:05 aml systemd[1]: iscsid.service: Failed with result 'resources'. Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package open-iscsi (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for libc-bin (2.24-11+deb9u3) ... Processing triggers for systemd (232-25+deb9u4) ... Processing triggers for man-db (2.7.6.1-2) ... Processing triggers for initramfs-tools (0.130) ... ln: failed to create hard link '/boot/initrd.img-4.18.7-aml-s9xxx.dpkg-bak' => ' /boot/initrd.img-4.18.7-aml-s9xxx': Operation not permitted update-initramfs: Generating /boot/initrd.img-4.18.7-aml-s9xxx W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. update-initramfs: Converting to u-boot format Errors were encountered while processing: open-iscsi E: Sub-process /usr/bin/dpkg returned an error code (1) I tried to start the iscsid service manually, but get error: can not bind NETLINK_ISCSI socket perhaps the kernel not support iSCSI. could you please fix it?