One issue for the connectivity loss is that the firmware on the card
is out dated. We see the following in the logs

Apr 11 13:26:21 quadstore kernel: qla2xxx [0000:05:00.1]-0063:6:
Failed to load firmware image (ql2400_fw.bin).
Apr 11 13:26:21 quadstore kernel: qla2xxx [0000:05:00.1]-0090:6:
Firmware image unavailable.
Apr 11 13:26:21 quadstore kernel: qla2xxx [0000:05:00.1]-0091:6:
Firmware images can be retrieved from:
http://ldriver.qlogic.com/firmware/

You can get a more recent firmware by installing the firmware-qlogic
package (non-free)

Or you can get ql2400_fw.bin from the QLogic site in the link
mentioned above and place is under /lib/firmware/.

Then run /quadstor/bin/qlainst to recreate the initrd image.



On Tue, Apr 11, 2017 at 11:32 PM, QUADStor Support <supp...@quadstor.com> wrote:
> Which OS is the host running ? Anything in the host logs which can
> tell why the FC connection was lost ?
>
> The warnings in the kernel logs seem ok and some of them are not
> really warnings and should be removed.
>
> After the restart, at around Apr 11 13:55:11 the VDisk should be
> accessible again over FC. Try a host rescan and let us know if there
> are any errors in the host logs.
>
> On Tue, Apr 11, 2017 at 6:26 PM, Artem Shvidky <tema...@gmail.com> wrote:
>>
>>
>> вторник, 11 апреля 2017 г., 15:04:48 UTC+3 пользователь quadstor написал:
>>>
>>> Can you send the diagnostics logs (HTML UI -> System -> Run
>>> Diagnostics -> Submit) to sup...@quadstor.com
>>>
>>> On Tue, Apr 11, 2017 at 5:16 PM, Artem Shvidky <tem...@gmail.com> wrote:
>>> > Some issue with vdisk. Yestarday host loose the disk connection(host
>>> > connect
>>> > to quadstor via FC).
>>> >
>>> > vDisk information available in system(via gui and via cli too):
>>> >
>>> >
>>> > -------------------------------------------------------------------------------------------------------------
>>> > Name       Pool    Serial Number                    Size(GB) LUN
>>> > Status
>>> > backupdisk Default 6e739d5a30881f0793f06fb02270a357 27889    1     D E
>>> >
>>> >  /quadstor/bin/vdconfig -l -v backupdisk -g Default
>>> >                    Name: backupdisk
>>> >                    Pool: Default
>>> >                    Size: 27889
>>> >               Threshold: 0
>>> >           Deduplication: Yes
>>> >             Compression: No
>>> >             Verfication: No
>>> >              Write Size: 15.439 TB
>>> >               Write Ops: 18996376
>>> >               Read Size: 6.96 GB
>>> >                Read Ops: 274976
>>> >          Unaligned Size: 95.50 MB
>>> >            Data Deduped: 3.233 TB
>>> >            Dedupe Ratio: 1.265
>>> >           Data Unmapped: 0.00 KB
>>> >               Unmap Ops: 0
>>> >           Blocks Zeroed: 0.00 KB
>>> >       Uncompressed Size: 12.206 TB
>>> >         Compressed Size: 0.00 KB
>>> >        Compression Hits: 0.00 KB
>>> >      Compression Misses: 0.00 KB
>>> >             Verify Hits: 0.00 KB
>>> >           Verify Misses: 0.00 KB
>>> >           Verify Errors: 0.00 KB
>>> >                 CW Hits: 0
>>> >               CW Misses: 0
>>> >             XCopy Write: 0.00 KB
>>> >               XCopy Ops: 0
>>> >         Write Same Size: 0.00 KB
>>> >          Write Same Ops: 0
>>> >     Populate Token Size: 0.00 KB
>>> >      Populate Token Ops: 0
>>> >        Write Token Size: 0.00 KB
>>> >         Write Token Ops: 0
>>> >
>>> > ----------------------------------------------------------------------------------------------------------------
>>> >
>>> > In quadstor.log i have: Tue Apr 11 10:44:54 2017 Err: Reading serial
>>> > number
>>> > failed for /dev/sdd1
>>> > In message log i have:
>>> >
>>> >
>>> > ------------------------------------------------------------------------------------------------------------------
>>> > Apr 11 10:33:34 quadstore kernel: __kern_exit:812 rcache exit
>>> > Apr 11 10:33:34 quadstore kernel: __kern_exit:815 groups free
>>> > Apr 11 10:33:34 quadstore kernel: __kern_exit:818 clear fc rules
>>> > Apr 11 10:33:34 quadstore kernel: __kern_exit:821 end
>>> > Apr 11 10:33:34 quadstore mdaemon: WARN: tl_ioctl2:152 failed to exect
>>> > cmd
>>> > TLTARGIOCTDISKSTATS errno 1 Operation not permitted
>>> > Apr 11 10:33:34 quadstore mdaemon: WARN: tl_ioctl2:152 failed to exect
>>> > cmd
>>> > TLTARGIOCTDISKSTATS errno 1 Operation not permitted
>>> > Apr 11 10:33:34 quadstore mdaemon: WARN: tl_ioctl2:152 failed to exect
>>> > cmd
>>> > TLTARGIOCTDISKSTATS errno 1 Operation not permitted
>>> > Apr 11 10:33:34 quadstore mdaemon: WARN: tl_ioctl2:152 failed to exect
>>> > cmd
>>> > TLTARGIOCTDISKSTATS errno 1 Operation not permitted
>>> > Apr 11 10:33:34 quadstore mdaemon: WARN: tl_ioctl2:152 failed to exect
>>> > cmd
>>> > TLTARGIOCTDISKSTATS errno 1 Operation not permitted
>>> > Apr 11 10:33:34 quadstore mdaemon: WARN: tl_ioctl2:152 failed to exect
>>> > cmd
>>> > TLTARGIOCTDISKSTATS errno 1 Operation not permitted
>>> > Apr 11 10:33:34 quadstore mdaemon: WARN: tl_ioctl2:152 failed to exect
>>> > cmd
>>> > TLTARGIOCTDISKSTATS errno 1 Operation not permitted
>>> > Apr 11 10:33:34 quadstore mdaemon: WARN: tl_ioctl2:152 failed to exect
>>> > cmd
>>> > TLTARGIOCTDISKSTATS errno 1 Operation not permitted
>>> > Apr 11 10:33:35 quadstore kernel: __kern_exit:727 kern_inited; 0
>>> > Apr 11 10:33:36 quadstore mdaemon: ERROR: disk_getsize:87 Unable to open
>>> > device /dev/sdc
>>> > Apr 11 10:33:40 quadstore kernel: ddtable_global_update_peer_count:240
>>> > max
>>> > ddtables 6 max ddlookup_count 3626800 max roots 524288 peer count 6
>>> > free_threshold 3659568 crit threshold 3692336 threshold 32768
>>> > Apr 11 10:44:42 quadstore kernel: dd_load_thread:1387 ddtable load for
>>> > group
>>> > Default took 660046 msecs
>>> > Apr 11 10:44:44 quadstore kernel: scsi10 : QUADStor ldev
>>> > Apr 11 10:44:44 quadstore kernel: scsi 10:0:0:0: Direct-Access
>>> > QUADSTOR
>>> > VDISK            2.0  PQ: 0 ANSI: 6
>>> > Apr 11 10:44:44 quadstore kernel: sd 10:0:0:0: Attached scsi generic sg4
>>> > type 0
>>> > Apr 11 10:44:44 quadstore kernel: sd 10:0:0:0: [sdd] 58487472128
>>> > 512-byte
>>> > logical blocks: (29.9 TB/27.2 TiB)
>>> > Apr 11 10:44:44 quadstore kernel: sd 10:0:0:0: [sdd] Write Protect is
>>> > off
>>> > Apr 11 10:44:44 quadstore kernel: sd 10:0:0:0: [sdd] Write cache:
>>> > enabled,
>>> > read cache: enabled, supports DPO and FUA
>>> > Apr 11 10:44:44 quadstore kernel: sdd: sdd1 sdd2
>>> > Apr 11 10:44:44 quadstore kernel: sd 10:0:0:0: [sdd] Attached SCSI disk
>>> > Apr 11 10:44:54 quadstore mdaemon: ERR: tl_server_dev_mapping:2150
>>> > Reading
>>> > serial number failed for /dev/sdd1
>>> > Apr 11 10:44:54 quadstore mdaemon: ERR: tl_server_dev_mapping:2150
>>> > Reading
>>> > serial number failed for /dev/sdd2
>>> >
>>> > ------------------------------------------------------------------------------------------------------------
>>> >
>>> > what i can do to recovery system?
>>> >
>>> > --
>>> > You received this message because you are subscribed to the Google
>>> > Groups
>>> > "QUADStor Storage Virtualization" group.
>>> > To unsubscribe from this group and stop receiving emails from it, send
>>> > an
>>> > email to quadstor-vir...@googlegroups.com.
>>> > For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "QUADStor Storage Virtualization" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to quadstor-virt+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"QUADStor Storage Virtualization" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to quadstor-virt+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to