Napp-IT - Recovering iSCSI info after OmniOS Crash

Discussion in 'Solaris, Nexenta, OpenIndiana, and napp-it' started by coolrunnings82, Nov 21, 2017.

  1. coolrunnings82

    coolrunnings82 Active Member

    Joined:
    Mar 26, 2012
    Messages:
    395
    Likes Received:
    85
    I recently rebooted my OmniOS SAN due to some physical rack changes. I properly shut down the servers using iSCSI before shutting down the SAN. However upon booting back up, OmniOS went into some forced maintenance mode and I was unable to find a way to recover the info. I intended on moving the ZFS pool to a new server anyway so I pulled the drives, put them in a new system, and imported the ZFS volume into a fresh OmniOS VM (from the latest Napp-It Preconfigured Template). The pool imported just fine and I see everything I expect except the iSCSI configuration seems to be missing. I've never moved a pool containing an iSCSI target before. Previous pools using NFS and SMB had those settings automatically migrated with the pool.

    I looked at the ZFS file systems and I do see the used space and ZFS volume containing my data there but I don't know how to reconnect that so my existing volumes can be accessed over iSCSI. Any pointers would be helpful here! Thanks!
     
    #1
  2. audio catalyst

    Joined:
    Jan 4, 2014
    Messages:
    88
    Likes Received:
    12
    Did you make backup of you comstar config in nappit ?
    That would be the easiest, although not the only possibilities

    send from a mobile device, so typo's are to be expected :)
     
    #2
  3. coolrunnings82

    coolrunnings82 Active Member

    Joined:
    Mar 26, 2012
    Messages:
    395
    Likes Received:
    85
    Unfortunately I didn't do that and the old OS is totally hosed... I did see the setting when trying to figure things out though so I will certainly be making a backup when I get this up and going!
     
    #3
  4. audio catalyst

    Joined:
    Jan 4, 2014
    Messages:
    88
    Likes Received:
    12
    wel then you also don't know the GUID's anymore , so chances are you will have to rediscovery and add them to Esx, but at least you'll have your data : so here goes goed ol'manual


    sbdadm list-lu - to list you current LUNS
    stmfadm create-lu <PATH TO LUN ><FILENAME>

    then create your ISCSI target and views, and you should be able to detect them again :)
    make sure that you select "i copied" upon rescanning of the ISCSI volume, otherwise ESX will reformat !
     
    #4
    coolrunnings82 likes this.
  5. gea

    gea Well-Known Member

    Joined:
    Dec 31, 2010
    Messages:
    2,261
    Likes Received:
    750
    A iSCSI target is basically a zvol, file or a disk that is expected to be a blockdevice like a raw disk.

    To make a working iSCSI target from it you need a GUID as identifier. If you have a sudden crash and have lost this identifier, you can import this "raw device" via menu Comstar > LU > import. If you know the former identifier you can enter there otherwise select a random.

    This is why I added iSCSI as a ZFS filesystem property. When you create an iSCSI target via menu napp-it menu ZFS filesystems, the GUID will be part of the Zvol name what allows an activate via menu ZFS filesystems even after a crash.

    Anyway, no problem,
     
    #5
  6. coolrunnings82

    coolrunnings82 Active Member

    Joined:
    Mar 26, 2012
    Messages:
    395
    Likes Received:
    85
    Thanks for the info, guys! Will try this soon as I get back to the office!
     
    #6
    audio catalyst likes this.
  7. coolrunnings82

    coolrunnings82 Active Member

    Joined:
    Mar 26, 2012
    Messages:
    395
    Likes Received:
    85
    Update: sbdadm list-lu didn't list anything so I went to Comstar > Logical Units > Import LU in Napp-It and imported the file from there. Once I did that, I recreated my Target, Target Group, and View and I was off to the races. Thanks for your help, @gea and @audio catalyst. I appreciate the quick responses!
     
    #7
    audio catalyst likes this.
Similar Threads: Napp-IT Recovering
Forum Title Date
Solaris, Nexenta, OpenIndiana, and napp-it Napp-IT --> QNAP Migration Tuesday at 6:25 PM
Solaris, Nexenta, OpenIndiana, and napp-it How to install Napp-it on OI Hipster 2019.10 GUI + Must I really reset root password after install? Monday at 3:07 PM
Solaris, Nexenta, OpenIndiana, and napp-it Napp-It not scaling well ... - revisited ;) Nov 20, 2019
Solaris, Nexenta, OpenIndiana, and napp-it napp-it: some disks have same enclosure id, second disk vanishes when mapping the other Nov 17, 2019
Solaris, Nexenta, OpenIndiana, and napp-it Napp-it web gui issues Oct 5, 2019

Share This Page