Unable to enable iSCSI

    • OMV 1.0
    • Resolved

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Unable to enable iSCSI

      New OMV user here. I've been searching around and hoping to find a different NAS solution that I've never used.

      Anyway, I've come across OMV and am really liking it so far. My question here is obviously regarding the iSCSI plugin. I've installed the plugin, but I'm unable to even enable the service.

      Mind you..this is a fresh install. So, I've wiped a 500GB drive that I can use as testing for iSCSI storage. Before even configuring Incoming/Outgoing, shouldn't I be able to at least enable the service? I can configure a target just fine, selecting the device as the 500GB drive, users, etc.

      When I go to enable service and apply the settings, I keep getting this error message:
      Failed to execute command 'export LANG=C; invoke-rc.d 'iscsitarget' start 2>&1': Starting iSCSI enterprise target service:FATAL: Module iscsi_trgt not found. failed! invoke-rc.d: initscript iscsitarget, action "start" failed.


      Details:
      Error #4000:
      exception 'OMVException' with message 'Failed to execute command 'export LANG=C; invoke-rc.d 'iscsitarget' start 2>&1': Starting iSCSI enterprise target service:FATAL: Module iscsi_trgt not found.
      failed!
      invoke-rc.d: initscript iscsitarget, action "start" failed.' in /usr/share/php/openmediavault/initscript.inc:176
      Stack trace:
      #0 /usr/share/php/openmediavault/initscript.inc(141): OMVSysVInitScript->invoke('start')
      #1 /usr/share/php/openmediavault/initscript.inc(61): OMVSysVInitScript->start()
      #2 /usr/share/openmediavault/engined/module/iscsitarget.inc(91): OMVSysVInitScript->exec()
      #3 /usr/share/openmediavault/engined/rpc/config.inc(206): OMVModuleIscsiTarget->startService()
      #4 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
      #5 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
      #6 /usr/share/php/openmediavault/rpcservice.inc(158): OMVRpcServiceAbstract->callMethod('applyChanges', Array, Array)
      #7 /usr/share/openmediavault/engined/rpc/config.inc(224): OMVRpcServiceAbstract->callMethodBg('applyChanges', Array, Array)
      #8 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
      #9 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
      #10 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('applyChangesBg', Array, Array)
      #11 /usr/sbin/omv-engined(500): OMVRpc::exec('Config', 'applyChangesBg', Array, Array, 1)
      #12 {main}


      And I get this same error whether anything is configured in iSCSI or not.

      Any suggestions?
    • Nope. iscsi doesn't work with the 3.16 last time I tried. I would install the build-essential package and linux headers for the 3.2 kernel. Then purge the plugin and try reinstalling.
      omv 4.1.12 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • I removed the plugin, installed build-essential & linux headers for my kernel, and I'm now receiving this when trying to install the plugin. Wth (i did reboot the PC)?

      It's not a big deal as I can just reinstall from scratch...but still think that's odd those 2 groups of packages borked the iSCSI plugin, ya know.

      Reading package lists...
      Building dependency tree...
      Reading state information...
      The following extra packages will be installed:
      dkms iscsitarget-dkms
      Recommended packages:
      fakeroot
      The following NEW packages will be installed:
      dkms iscsitarget-dkms openmediavault-iscsitarget
      0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
      1 not fully installed or removed.
      Need to get 0 B/196 kB of archives.
      After this operation, 930 kB of additional disk space will be used.
      WARNING: The following packages cannot be authenticated!
      dkms iscsitarget-dkms openmediavault-iscsitarget
      Authentication warning overridden.
      Selecting previously unselected package dkms.
      (Reading database ... 37523 files and directories currently installed.)
      Unpacking dkms (from .../dkms_2.2.0.3-1.2_all.deb) ...
      Selecting previously unselected package iscsitarget-dkms.
      Unpacking iscsitarget-dkms (from .../iscsitarget-dkms_1.4.20.2-10.1_all.deb) ...
      Selecting previously unselected package openmediavault-iscsitarget.
      Unpacking openmediavault-iscsitarget (from .../openmediavault-iscsitarget_1.1_all.deb) ...
      Processing triggers for man-db ...
      Processing triggers for openmediavault ...
      Restarting engine daemon ...
      Setting up iscsitarget (1.4.20.2-10.1) ...
      Starting iSCSI enterprise target service:FATAL: Module iscsi_trgt not found.
      failed!
      invoke-rc.d: initscript iscsitarget, action "start" failed.
      dpkg: error processing iscsitarget (--configure):
      subprocess installed post-installation script returned error exit status 1
      Setting up dkms (2.2.0.3-1.2) ...
      Setting up iscsitarget-dkms (1.4.20.2-10.1) ...

      Creating symlink /var/lib/dkms/iscsitarget/1.4.20.2/source ->
      /usr/src/iscsitarget-1.4.20.2

      DKMS: add completed.

      Kernel preparation unnecessary for this kernel. Skipping...

      Building module:
      cleaning build area....
      make KERNELRELEASE=3.2.0-4-amd64 -C /lib/modules/3.2.0-4-amd64/build M=/var/lib/dkms/iscsitarget/1.4.20.2/build.......
      cleaning build area....

      DKMS: build completed.

      iscsi_trgt:
      Running module version sanity check.
      - Original module
      - No original module exists within this kernel
      - Installation
      - Installing to /lib/modules/3.2.0-4-amd64/kernel/drivers/iscsi//

      depmod.......

      DKMS: install completed.
      dpkg: dependency problems prevent configuration of openmediavault-iscsitarget:
      openmediavault-iscsitarget depends on iscsitarget; however:
      Package iscsitarget is not configured yet.

      dpkg: error processing openmediavault-iscsitarget (--configure):
      dependency problems - leaving unconfigured
      Errors were encountered while processing:
      iscsitarget
      openmediavault-iscsitarget
    • Let me setup a VM tomorrow morning to see if I can figure something out. I know I have got it working before.
      omv 4.1.12 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • I got it working on a fresh VM. Try this:

      apt-get purge iscsitarget
      apt-get autoremove
      apt-get clean
      apt-get install linux-headers-$(uname -r) build-essential
      apt-get install openmediavault-iscsitarget

      Then enable the plugin. Check to see if the iscsi_trgt module is loaded with: lsmod | grep iscsi
      omv 4.1.12 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Tried that too, but I believe that this plugin is actually not ready for production. This morning I started to install iscsi on my testlab, I have a virtualized OMV box running and can go back to a snapshot in seconds.
      At first I run into the same error (FATAL: Module iscsi_trgt not found. failed!) and after looking into the error protocol I saw that it complained about missing kernel headers.
      So I installed them with the same command, but only without build-essentials. I could start the service, but couldn't connect to the target from an ESXi host.
      Now I tried it again after reading aaron's post with build-essentials and can start the service again. Build a target and let the ESXi host connect. While connecting the kernel and syslogd were spitting out a lo of messages:

      Brainfuck Source Code

      1. Message from syslogd@pronas5 at Dec 10 12:14:09 ...
      2. kernel:[ 102.226431] ------------[ cut here ]------------
      3. Message from syslogd@pronas5 at Dec 10 12:14:09 ...
      4. kernel:[ 102.226573] invalid opcode: 0000 [#1] SMP
      5. Message from syslogd@pronas5 at Dec 10 12:14:09 ...
      6. kernel:[ 102.230741] Stack:
      7. Message from syslogd@pronas5 at Dec 10 12:14:09 ...
      8. kernel:[ 102.231431] Call Trace:
      9. Message from syslogd@pronas5 at Dec 10 12:14:09 ...
      10. kernel:[ 102.232348] Code: 48 85 ed 75 28 48 c7 c1 38 1d 35 a0 ba 88 01 00 00 48 c7 c6 a7 19 35 a0 48 c7 c7 df 19 35 a0 31 c0 e8 45 2d 00 e1 e8 6a 12 00 e1 <0f> 0b 48 89 df e8 d0 fa ff ff 8b 55 14 39 d0 0f 46 d0 85 d2 0f
      11. Message from syslogd@pronas5 at Dec 10 12:14:49 ...
      12. kernel:[ 142.237978] ------------[ cut here ]------------
      13. Message from syslogd@pronas5 at Dec 10 12:14:49 ...
      14. kernel:[ 142.238161] invalid opcode: 0000 [#2] SMP
      15. Message from syslogd@pronas5 at Dec 10 12:14:49 ...
      16. kernel:[ 142.242204] Stack:
      17. Message from syslogd@pronas5 at Dec 10 12:14:49 ...
      18. kernel:[ 142.242894] Call Trace:
      19. Message from syslogd@pronas5 at Dec 10 12:14:49 ...
      20. kernel:[ 142.245186] Code: 48 85 ed 75 28 48 c7 c1 38 1d 35 a0 ba 88 01 00 00 48 c7 c6 a7 19 35 a0 48 c7 c7 df 19 35 a0 31 c0 e8 45 2d 00 e1 e8 6a 12 00 e1 <0f> 0b 48 89 df e8 d0 fa ff ff 8b 55 14 39 d0 0f 46 d0 85 d2 0f
      21. Message from syslogd@pronas5 at Dec 10 12:15:29 ...
      22. kernel:[ 182.233659] Oops: 0011 [#3] SMP
      23. Message from syslogd@pronas5 at Dec 10 12:15:29 ...
      24. kernel:[ 182.237587] Stack:
      25. Message from syslogd@pronas5 at Dec 10 12:15:29 ...
      26. kernel:[ 182.238281] Call Trace:
      27. Message from syslogd@pronas5 at Dec 10 12:15:29 ...
      28. kernel:[ 182.239556] Code: ff ff ff 00 00 00 00 00 00 00 00 b0 c7 56 37 01 88 ff ff e0 cc 56 37 01 88 ff ff c8 c9 56 37 01 88 ff ff 08 76 e2 37 01 88 ff ff <f0> 9e 87 37 01 88 ff ff f0 9e 87 37 01 88 ff ff 58 ca 56 37 01
      29. Message from syslogd@pronas5 at Dec 10 12:15:29 ...
      30. kernel:[ 182.241495] CR2: ffff880137879ef0
      Display All


      Hm. The target was detected, but unavailable. So I restarted the OMV box and got a hanging boot screen, see the screenshot attached (boot error).

      Than I did a hard reset in the vSphere Client and to my surprise, after the machine came back the iscsi target was available on the ESXi host.
      But while I tried to mount this iscsi lun the vsphere client gut totally stuck and after a while an error message appeared on the OMV system screen (Attached, systemerror).

      After that I tried to shut down the OMV box, but it is hanging again with the message "Removing iSCSI enterprise taget devices: :" and nothing happens.
      So there's no success in connecting to an iscsi device. Sorry.
      Images
      • booterror.jpg

        123.6 kB, 737×433, viewed 949 times
      • systemerror.jpg

        146.76 kB, 719×393, viewed 1,001 times
      Homebox: Bitfenix Prodigy Case, ASUS E45M1-I DELUXE ITX, 8GB RAM, 5x 4TB HGST Raid-5 Data, 1x 320GB 2,5" WD Bootdrive via eSATA from the backside
      Companybox 1: Standard Midi-Tower, Intel S3420 MoBo, Xeon 3450 CPU, 16GB RAM, 5x 2TB Seagate Data, 1x 80GB Samsung Bootdrive - testing for iSCSI to ESXi-Hosts
      Companybox 2: 19" Rackservercase 4HE, Intel S975XBX2 MoBo, C2D@2200MHz, 8GB RAM, HP P212 Raidcontroller, 4x 1TB WD Raid-0 Data, 80GB Samsung Bootdrive, Intel 1000Pro DualPort (Bonded in a VLAN) - Temp-NFS-storage for ESXi-Hosts
    • Nice! That worked great! I honestly think manually installing it with 'apt-get install openmediavault-iscsitarget' solved the problem. Maybe there were dependencies that weren't getting installed when invoking the plugin install via WebUI? *shrug*

      Note: running 'apt-get install linux-headers-$(uname -r) build-essential' again only did a minor upgrade to my existing packages installed from the other day.

      Either way, it's working perfectly now. Thank you for taking the time to resolve this for me, ryecoaaron. I heard the community for this project has great support, and I can definitely see why.
    • From which device or OS do you connect to the iscsi lun?
      Homebox: Bitfenix Prodigy Case, ASUS E45M1-I DELUXE ITX, 8GB RAM, 5x 4TB HGST Raid-5 Data, 1x 320GB 2,5" WD Bootdrive via eSATA from the backside
      Companybox 1: Standard Midi-Tower, Intel S3420 MoBo, Xeon 3450 CPU, 16GB RAM, 5x 2TB Seagate Data, 1x 80GB Samsung Bootdrive - testing for iSCSI to ESXi-Hosts
      Companybox 2: 19" Rackservercase 4HE, Intel S975XBX2 MoBo, C2D@2200MHz, 8GB RAM, HP P212 Raidcontroller, 4x 1TB WD Raid-0 Data, 80GB Samsung Bootdrive, Intel 1000Pro DualPort (Bonded in a VLAN) - Temp-NFS-storage for ESXi-Hosts
    • Some insights..... the kernel and syslogd messages from my post above appear only if I try to connect to the virtualized OMV box from the ESXi host the box is running on. It looks like this is not possible, although the box simply exposes it's iscsi services to the network, but the host cannot connect.
      Then I started the box with a former snapshot, installed it like aaron has posted and voila, I can connect to the iscsi share from a W2012R2 server and use the iscsi lun like any other iscsi device I am running here. That's good.

      But when I try to connect from another ESXi host to this lun after disconnecting the win server, I do not get the iscsi lun. I can connect, it finds the correct iqn of the OMV box, but it doesn't get the iscsi lun, no path is available. That's weird.
      Homebox: Bitfenix Prodigy Case, ASUS E45M1-I DELUXE ITX, 8GB RAM, 5x 4TB HGST Raid-5 Data, 1x 320GB 2,5" WD Bootdrive via eSATA from the backside
      Companybox 1: Standard Midi-Tower, Intel S3420 MoBo, Xeon 3450 CPU, 16GB RAM, 5x 2TB Seagate Data, 1x 80GB Samsung Bootdrive - testing for iSCSI to ESXi-Hosts
      Companybox 2: 19" Rackservercase 4HE, Intel S975XBX2 MoBo, C2D@2200MHz, 8GB RAM, HP P212 Raidcontroller, 4x 1TB WD Raid-0 Data, 80GB Samsung Bootdrive, Intel 1000Pro DualPort (Bonded in a VLAN) - Temp-NFS-storage for ESXi-Hosts
    • Yeeehaa, i made it. 8o

      What a fight. It seems to be that the iscsitarget version which will be downloaded via apt-get still has a somehow persistant bug as described here:
      vaspects.com/2013/11/01/esxi-5-5-crashes-linux-iscsi_trgt/
      But the ESXi versions 5.0 and 5.1 I have tested run into this bug, too. Forget my thoughts from my last postings, these kernel and syslogd messages will appear too while trying to connect from another ESXi host. I got two versions of errors: Either it doesn't find any iscsi target on the OMV box or it takes a long time until it times out and then the kernel messages appear on the screen.

      Remember: Going the way like aaron has described above it is possible to connect to a iscsi target using the initiator on a Windows server. That works well.
      But it doesn't work if you try to connect from an ESXi host.

      I found the solution here:
      ubuntuforums.org/showthread.php?t=1877348

      What I did to make it possible to connect from ESXi:

      apt-get install devscripts equivs build-essential
      apt-get install iscsitarget
      apt-get install iscsitarget-dkms

      These next two steps are possibly not needed if there's another way to get the sources on the box, but
      I found it pretty convenient ;)
      apt-get install subversion
      svn co https://svn.code.sf.net/p/iscsitarget/code iscsitarget
      (Attention: This command puts the sources into a subdirectory named iscsitarget whereever you have started the command from. So it is a good idea to run that from a place like /home)

      cd to iscsitarget/trunk
      make
      make install

      configure the iscsi target as described here:
      howtoforge.com/using-iscsi-on-…eeze-initiator-and-target
      reboot the box and try to connect from an ESXi host. I just did it and it was finished in a few seconds. I can mount the target as a data storage in the vSphere Client, put VMFS5 file system on it and use it like any other storage on this host.

      This describes the manual way how to install iscsitarget on the OMV box, there's no tab in the web-gui. If you want to use it that way, you have to configure the iscsi targets manually from the CLI (Hint: That's easy if you use mc).
      But that's no hard work for the IT pros, there are basically two files to configure and this is not that much.
      Homebox: Bitfenix Prodigy Case, ASUS E45M1-I DELUXE ITX, 8GB RAM, 5x 4TB HGST Raid-5 Data, 1x 320GB 2,5" WD Bootdrive via eSATA from the backside
      Companybox 1: Standard Midi-Tower, Intel S3420 MoBo, Xeon 3450 CPU, 16GB RAM, 5x 2TB Seagate Data, 1x 80GB Samsung Bootdrive - testing for iSCSI to ESXi-Hosts
      Companybox 2: 19" Rackservercase 4HE, Intel S975XBX2 MoBo, C2D@2200MHz, 8GB RAM, HP P212 Raidcontroller, 4x 1TB WD Raid-0 Data, 80GB Samsung Bootdrive, Intel 1000Pro DualPort (Bonded in a VLAN) - Temp-NFS-storage for ESXi-Hosts
    • In the next step I will try to add this patch with an installed OMV plugin to have full advantage of the web-gui configuration.

      ./edit: It looks like it is not possible to add the patch to an installed OMV plugin, it throws a lot of errors when I try to activate the plugin:

      Source Code

      1. rror
      2. #4000:
      3. exception 'OMVException' with message 'Failed to execute command 'export
      4. LANG=C; update-rc.d 'iscsitarget' disable 2>&1': update-rc.d:
      5. using dependency based boot sequencing
      6. insserv: warning: current start runlevel(s) (empty) of script
      7. `iscsitarget' overrides LSB defaults (2 3 4 5).
      8. insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script
      9. `iscsitarget' overrides LSB defaults (0 1 6).
      10. insserv: warning: script 'iscsi-target' missing LSB tags and overrides
      11. insserv: There is a loop between service monit and iscsi-target if
      12. stopped
      13. insserv: loop involving service iscsi-target at depth 2
      14. insserv: loop involving service monit at depth 1
      15. insserv: Stopping iscsi-target depends on monit and therefore on system
      16. facility `$all' which can not be true!
      17. insserv: exiting now without changing boot order!
      18. update-rc.d: error: insserv rejected the script header' in
      19. /usr/share/php/openmediavault/initscript.inc:90
      20. Stack trace:
      21. #0 /usr/share/php/openmediavault/initscript.inc(56):
      22. OMVSysVInitScript->update(true)
      23. #1 /usr/share/openmediavault/engined/module/iscsitarget.inc(72):
      24. OMVSysVInitScript->exec()
      25. #2 /usr/share/openmediavault/engined/rpc/config.inc(164):
      26. OMVModuleIscsiTarget->stopService()
      27. #3 [internal function]: OMVRpcServiceConfig->applyChanges(Array,
      28. Array)
      29. #4 /usr/share/php/openmediavault/rpcservice.inc(125):
      30. call_user_func_array(Array, Array)
      31. #5 /usr/share/php/openmediavault/rpcservice.inc(158):
      32. OMVRpcServiceAbstract->callMethod('applyChanges', Array, Array)
      33. #6 /usr/share/openmediavault/engined/rpc/config.inc(224):
      34. OMVRpcServiceAbstract->callMethodBg('applyChanges', Array, Array)
      35. #7 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array,
      36. Array)
      37. #8 /usr/share/php/openmediavault/rpcservice.inc(125):
      38. call_user_func_array(Array, Array)
      39. #9 /usr/share/php/openmediavault/rpc.inc(79):
      40. OMVRpcServiceAbstract->callMethod('applyChangesBg', Array, Array)
      41. #10 /usr/sbin/omv-engined(500): OMVRpc::exec('Config', 'applyChangesBg',
      42. Array, Array, 1)
      43. #11 {main}
      Display All


      Ok. Was worth a try, aaron can possibly solve that.
      Homebox: Bitfenix Prodigy Case, ASUS E45M1-I DELUXE ITX, 8GB RAM, 5x 4TB HGST Raid-5 Data, 1x 320GB 2,5" WD Bootdrive via eSATA from the backside
      Companybox 1: Standard Midi-Tower, Intel S3420 MoBo, Xeon 3450 CPU, 16GB RAM, 5x 2TB Seagate Data, 1x 80GB Samsung Bootdrive - testing for iSCSI to ESXi-Hosts
      Companybox 2: 19" Rackservercase 4HE, Intel S975XBX2 MoBo, C2D@2200MHz, 8GB RAM, HP P212 Raidcontroller, 4x 1TB WD Raid-0 Data, 80GB Samsung Bootdrive, Intel 1000Pro DualPort (Bonded in a VLAN) - Temp-NFS-storage for ESXi-Hosts

      The post was edited 1 time, last by datadigger ().

    • ryecoaaron wrote:

      What did you patch in the plugin?

      I am not programmer enough to tell if this patches the plugin or the kernel....
      These are the sources for make and make install:
      svn.code.sf.net/p/iscsitarget/code/trunk/
      Homebox: Bitfenix Prodigy Case, ASUS E45M1-I DELUXE ITX, 8GB RAM, 5x 4TB HGST Raid-5 Data, 1x 320GB 2,5" WD Bootdrive via eSATA from the backside
      Companybox 1: Standard Midi-Tower, Intel S3420 MoBo, Xeon 3450 CPU, 16GB RAM, 5x 2TB Seagate Data, 1x 80GB Samsung Bootdrive - testing for iSCSI to ESXi-Hosts
      Companybox 2: 19" Rackservercase 4HE, Intel S975XBX2 MoBo, C2D@2200MHz, 8GB RAM, HP P212 Raidcontroller, 4x 1TB WD Raid-0 Data, 80GB Samsung Bootdrive, Intel 1000Pro DualPort (Bonded in a VLAN) - Temp-NFS-storage for ESXi-Hosts
    • Oh, you just compiled a newer kernel module. The plugin must have code that doesn't work with the newer version. I've never used iscsi so I can't really help on this one.
      omv 4.1.12 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Aha. Thanks for the info. Although I can read source code and compose programs in VB I'm not that much of a programmer, I am some kind of a guy from the hands-on trenches. ;)

      I wouldn't say that a iscsi plugin to which you can only connect from one OS world is useless, but I would call it incomplete. I don't know anything about future plans where OMV will go, but if it ever wants to leave the home NAS league a fully compatible iscsi plugin is somehow mandatory.
      Homebox: Bitfenix Prodigy Case, ASUS E45M1-I DELUXE ITX, 8GB RAM, 5x 4TB HGST Raid-5 Data, 1x 320GB 2,5" WD Bootdrive via eSATA from the backside
      Companybox 1: Standard Midi-Tower, Intel S3420 MoBo, Xeon 3450 CPU, 16GB RAM, 5x 2TB Seagate Data, 1x 80GB Samsung Bootdrive - testing for iSCSI to ESXi-Hosts
      Companybox 2: 19" Rackservercase 4HE, Intel S975XBX2 MoBo, C2D@2200MHz, 8GB RAM, HP P212 Raidcontroller, 4x 1TB WD Raid-0 Data, 80GB Samsung Bootdrive, Intel 1000Pro DualPort (Bonded in a VLAN) - Temp-NFS-storage for ESXi-Hosts

      The post was edited 1 time, last by datadigger ().