Trouble iSCSI setting device

James S

Explorer
Joined
Apr 14, 2014
Messages
91
I configured iSCSI to run under FN 11.1 to run with ESXI 6 and all worked fine until a bundle of simulatenous disk failures in the data pool. In rebuild I've taken advantage to upgrade to FN 11.2. WD were kind enough to replace 3TiB with 4TiB so I've moved the pools around too - recreating one pool as a stripped mirror (existing 2TiB) and the new disks as raidz2.

I'm trying to set up the extent but cannot get the device to stick in the settings. I can choose it (store-1) but

extent-chosen.PNG


after saving it dissapears
extent-not-applied.PNG


I'm assuming it should show up under "Device*" - third row?
On the exsi side it shows the drive mounted but does not show store-1 or the size.
I've rebuild the storage a number of times since it seems capital letters and perhaps underscores (?) are forbidden.

What am I doing wrong here?

Another issue is making sure the storage is actually configured as a stripped mirror (something I screwed up last time :( Under zpool status I'm seeing

zpool-status.PNG


Does this confirm a stripped mirror?

Thanks!
 
D

dlavigne

Guest
Which version of 11.2 (from the Dashboard)? Are you using a zvol for the device?
 

James S

Explorer
Joined
Apr 14, 2014
Messages
91
OS version is 11.2-U5
Yes, I'm using a zvol and for clarity:
zvol.PNG

store-1 shows up as an option to choose but after clicking 'save' it is not present.
The esxi shows reports it mounted by cannot, it seems (?) read the volume.
exxi-6.PNG

This is what it reports

Code:
Login to iSCSI target
iqn.2011-03.org.exam.istgt:iscsi-target on
vmhba36 @ vmk2 failed. The iSCSI initiator could
not establish a network connection to the target.
error
8/29/2019 5:36:03 PM
localhost.localdomain
 

James S

Explorer
Joined
Apr 14, 2014
Messages
91
Last edited:

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
Does this confirm a stripped mirror?
You have two mirror vdevs, yes.

This might be a regression from after the fix. File a new bug report and post the link here (note that the old Redmine bug tracker is not active anymore and you'll need to use Jira: https://jira.ixsystems.com/secure/Dashboard.jspa ).
 
Top