5.0.4 is in the repo. https://github.com/OpenMediaVa…a9ccf18dee8139edcc78fa252
VMWare and iSCSI
-
- OMV 5.x
- rjones1229
-
-
Hey,
I get this error in "systemctl status tgt.service":
Codetgt_target_create(2145) Target name iqn.2020-2.box.fritz.0E_13_CC_65_2E_FD:mactest has invalid characters
content is:Code<target iqn.2020-2.box.fritz.0E_13_CC_65_2E_FD:mactest> device-type pt bs-type sg backing-store /dev/sg3 initiator-address 192.168.1.129 </target>
I try to mount my BRDVD drive. Worked yesterday when I setup iscsi und tgt in console without your plugin. As I see, your plugin will the same do within OMV.Edit: I killed the MAC address out of the target name and now the services gets started. Maybe the insertion of MAC address is a bug?
Any suggestions?
-
Hi,
> 5.0.4 is in the repo. github.com/OpenMediaVault-Plug…a9ccf18dee8139edcc78fa252
You did a better job than I would have done, thank you.
Do you have a plan to use LIO/targetcli in place of TGT ?
Best regards.
Francis
-
Any suggestions?
Your system seems to be resolving it hostname as a mac address. what is the output of: hostname -f
Do you have a plan to use LIO/targetcli in place of TGT ?
Wouldn't it be strange for the tgt plugin to use something other than TGT? I wrote this plugin because there was a need for an iscsi plugin. targetcli is not ideal for a plugin since it has an interactive setup instead of just creating config files. If there is a way to configure it with config files, I'm not against making another plugin. Why do you want targetcli/LIO instead of TGT?
-
output is
I had made 2 Targets (one for CDROM and one for a hardfile) and get 2 different target names (with 2 different MAC addresses)
-
Hello,
> Wouldn't it be strange for the tgt plugin to use something other than TGT?
Yes but a LIO plugin to use targetcli ?> I wrote this plugin because there was a need for an iscsi plugin.
Thank You for your good job.> If there is a way to configure it with config files
cat configfile | targetcliconfigfile look like:
cd /backstores/...
create lun ...
cd /iscsi
create ...
...> Why do you want targetcli/LIO instead of TGT?
I do not want LIO instead TGT I want ISCSI for OMV > 3 (to replace OMV 3 iscsitarget).
But from the OMV 5 FAQ:
Why there is no iscsitarget plugin in openmediavault 4 ?
The intention is to migrate core underlaying software from iscsitarget to LIO targetcliThere is more implementation of SCSI target framework for Linux STGT, SCST but I understand that LIO is the "default" (?)
Best regards.
Francis
-
I had made 2 Targets (one for CDROM and one for a hardfile) and get 2 different target names (with 2 different MAC addresses)
I guess I will have to improve my code for hostname retrieval but it shouldn't be getting a mac address ever - https://github.com/OpenMediaVa…/engined/rpc/tgt.inc#L112
-
Yes but a LIO plugin to use targetcli ?
That is a plugin that doesn't exist and I have very little time to write plugins.
cat configfile | targetcli
configfile look like:
cd /backstores/...
create lun ...
cd /iscsi
create ......
No. I will never create automation that pipes values to an interactive prompt (or uses expect).
I do not want LIO instead TGT I want ISCSI for OMV > 3 (to replace OMV 3 iscsitarget).
TGT is iscsi. What am I missing?
Why there is no iscsitarget plugin in openmediavault 4 ?
The intention is to migrate core underlaying software from iscsitarget to LIO targetcliThere is more implementation of SCSI target framework for Linux STGT, SCST but I understand that LIO is the "default" (?)
I don't understand the question here. The iscsitarget plugin was not ported to OMV 4.x because it doesn't work with the backports kernel. Volker (author of OMV) was going to write one but never had time. He didn't have time for it for OMV 5.x either. So, I wrote the tgt plugin. If that doesn't work for you, not sure what to say.
-
Hello,
Sorry my english is bad and I think am not clear.
I am very happy with the TGT plugin (how many time waiting for an iscsi plugin). I do not say I am not happy with it.
I just ask you if you have a plan to use LIO like Volker say, if not this is not a problem.
Francis
-
Is it possible to set a network range for the initiator and not only single IP addresses? This is because I want to use the CDROM not only for my Mac. I've diffenrent VMs from time to time.
-
Is it possible to set a network range for the initiator and not only single IP addresses?
Sure. Just add 192.168.1.0/24 for the entire 192.168.1.0 range.
-
I guess I will have to improve my code for hostname retrieval but it shouldn't be getting a mac address ever - https://github.com/OpenMediaVa…/engined/rpc/tgt.inc#L112
I've checked this again and tried to search for the MAC addresses. No network adapter, neither physical or virtual, have these MAC address(es)...
Code
Alles anzeigenroot@plex-jens:~# ifconfig br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.10 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 2a02:810a:143f:cdbc:7da1:2fa9:97f1:f56a prefixlen 64 scopeid 0x0<global> inet6 2a02:810a:143f:cdbc:997b:3322:66a3:9cb0 prefixlen 64 scopeid 0x0<global> inet6 2a02:810a:143f:cdbc:2cd2:3494:b2f0:ec54 prefixlen 64 scopeid 0x0<global> inet6 fe80::2b85:dd5b:a340:22df prefixlen 64 scopeid 0x20<link> inet6 2a02:810a:143f:cdbc:8a3e:c841:d61a:2fe8 prefixlen 64 scopeid 0x0<global> ether 14:da:e9:e0:ae:6d txqueuelen 1000 (Ethernet) RX packets 30289285 bytes 23448908041 (21.8 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 12270269 bytes 22835268767 (21.2 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255 ether 02:42:f7:57:97:52 txqueuelen 0 (Ethernet) RX packets 46560 bytes 6840543 (6.5 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 83383 bytes 6998175 (6.6 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 enp5s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 14:da:e9:e0:ae:6d txqueuelen 1000 (Ethernet) RX packets 31543556 bytes 23957132556 (22.3 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 12415833 bytes 22844194704 (21.2 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 41395632 bytes 4390093201 (4.0 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 41395632 bytes 4390093201 (4.0 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 192.168.10.1 netmask 255.255.255.0 destination 192.168.10.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 100 (UNSPEC) RX packets 2320 bytes 123782 (120.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1564 bytes 338234 (330.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth41f4bea: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether fa:4c:db:30:eb:94 txqueuelen 0 (Ethernet) RX packets 237 bytes 17375 (16.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 39151 bytes 3201299 (3.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth5c26a00: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether b6:cb:04:49:ce:c6 txqueuelen 0 (Ethernet) RX packets 12985 bytes 4773807 (4.5 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 53570 bytes 3508726 (3.3 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth84e90b1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 36:d4:63:94:a7:95 txqueuelen 0 (Ethernet) RX packets 23 bytes 2502 (2.4 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 38739 bytes 2457083 (2.3 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethb20b890: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 76:a4:e5:9d:4f:20 txqueuelen 0 (Ethernet) RX packets 33315 bytes 2698699 (2.5 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 68072 bytes 5171695 (4.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:0a:cd:21 txqueuelen 1000 (Ethernet) RX packets 22737 bytes 108511269 (103.4 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 60570 bytes 88666490 (84.5 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
-
've checked this again and tried to search for the MAC addresses. No network adapter, neither physical or virtual, have these MAC address(es)...
Can you run php in interactive mode (php -a) and post the output of:
aaron@omv5dev:~$ php -a
Interactive mode enabledphp > echo gethostname();
omv5dev.domain.com
php > echo gethostbyname(gethostname());
192.168.1.131
php > echo gethostbyaddr(gethostbyname(gethostname()));
omv5dev.domain.comAnd the output of: hostname -f
-
-
I just updated the plugin to use hostname from the command line instead of the php functions. I know that will never return a random mac address. 5.0.5 is in the repo now.
-
Thanks! this works great!
-
Super! tgt läuft bei mir jetzt produktiv. Habe mir ein Target für eine TimeMachine-Platte als mitwachsendes Hardfile erstellt. Läuft hervorragend! Bisher hatte ich mit TimeMachine über eine AFP/SMB-Freigabe irgendwann wiederkehrende Berechtigungsprobleme. Das ist nun mit dem iSCSI-Target erledigt
Super Sache!!
-
Hi,
I having some problems with this plugin.
At least no Windows Hosts (Windows 10 + Windows Server 2019) can connect to the iscsi target.
They are getting the error message: "the target name is not found or is marked as hidden from login"For testing supposes i created a VM with debian 10, installed tgt manually and configured a target.
The Windows hosts connected immediatly .Do you have any idea, why the Windows hosts can not connect the iSCSI target on OMV?
-
Do you have any idea, why the Windows hosts can not connect the iSCSI target on OMV?
Since I don't know how either was configured, no. Did you compare the /etc/tgt/targets.conf and /etc/tgt/conf.d/* created by the plugin with what you created manually? If you find something that needs to be changed in the plugin, I can do that.
-
Both configs are simple and looks good.
Even a "tgtadm --mode target --op show" looks good (is online) on OMV, but i can't connect to the iscsi target on OMV.Any ideas how to troubleshoot this error on OMV ?
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!