Results 1 to 4 of 4

Thread: No LUN for LIO iSCSI after reboot

  1. #1

    Default No LUN for LIO iSCSI after reboot

    I created an iSCSI LUN export on Leap 15.1 using LIO and an unformatted volume, and my clients had no problems scanning, mounting and formatting it. However, after a Leap server reboot, the client can no longer connect. It is seeing the iSCSI identifier just fine, but reports there is no LUN at that location. When I go into YaST, there is no LUN listed in the config, but if I try to readd it, I am told that it cannot create a LUN on that backstore. targetcli lists one target for iscsi, but no LUNs. How should I go about getting my storage back?

    Any help is appreciated.

  2. #2

    Default Re: No LUN for LIO iSCSI after reboot

    Quote Originally Posted by jcdick1 View Post
    I created an iSCSI LUN export on Leap 15.1 using LIO and an unformatted volume, and my clients had no problems scanning, mounting and formatting it. However, after a Leap server reboot, the client can no longer connect. It is seeing the iSCSI identifier just fine, but reports there is no LUN at that location. When I go into YaST, there is no LUN listed in the config, but if I try to readd it, I am told that it cannot create a LUN on that backstore. targetcli lists one target for iscsi, but no LUNs. How should I go about getting my storage back?

    Any help is appreciated.
    Are there any logs you could share from the server and/or the clients? Can you see the device on the server?
    I just created a virtual machine to reproduce this and I see that the service is disabled by default (in YaST). Maybe you need to go through the server settings again to ensure that your targets are active after reboot.

  3. #3

    Default Re: No LUN for LIO iSCSI after reboot

    The service is set to start on boot, and it was all going well until I rebooted. I used the yasat iscsi module to set the device to use as a target as /dev/sdc, so the base OS does see it, as it needs to for the service to see it. However, on reboot it "grabbed" the VGs:

    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
    sda 8:0 0 136.7G 0 disk
    ├─sda1 8:1 0 8M 0 part
    ├─sda2 8:2 0 134.7G 0 part /srv
    └─sda3 8:3 0 2G 0 part [SWAP]
    sdb 8:16 0 29.1T 0 disk
    └─sdb1 8:17 0 29.1T 0 part /mnt/media
    sdc 8:32 0 1.8T 0 disk
    └─sdc1 8:33 0 1.8T 0 part
    ├─VG_XenStorage--9a4774b3--9142--7df9--a7c4--d76d19a1ac67-MGT 254:0 0 4M 0 lvm
    ├─VG_XenStorage--9a4774b3--9142--7df9--a7c4--d76d19a1ac67-VHD--53ec9bd2--5242--46d9--aa75--b92949baf3a3
    │ 254:1 0 47.5G 1 lvm
    ├─VG_XenStorage--9a4774b3--9142--7df9--a7c4--d76d19a1ac67-VHD--d6ce9a47--3cf3--4a36--985d--1217c93c6109
    │ 254:2 0 100.2G 0 lvm
    ├─VG_XenStorage--9a4774b3--9142--7df9--a7c4--d76d19a1ac67-VHD--78fda4df--9582--4b36--8dde--5dde8735a549
    │ 254:3 0 8M 0 lvm
    └─VG_XenStorage--9a4774b3--9142--7df9--a7c4--d76d19a1ac67-VHD--f4faadf7--3c5d--4f9f--8198--6ec82a9beac5
    254:4 0 50.1G 0 lvm

    /dev/sdc isn't mounted anywhere, but as you can see, the base OS is seeing the VGs. I'm pretty sure this is why it can't be configured back into being an iSCSI target for my Xen servers.

  4. #4
    Join Date
    Sep 2012
    Posts
    6,323

    Default Re: No LUN for LIO iSCSI after reboot

    Quote Originally Posted by jcdick1 View Post
    as you can see, the base OS is seeing the VGs. I'm pretty sure this is why it can't be configured back into being an iSCSI target for my Xen servers.
    So did you test it by stopping these VGs?

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •