Found the problem! For anyone else who happens across this issue, I had to uninstall the SPTD driver that comes with VSAN (just leave it removed). I can now see the tape drive and library in the VSAN console.

yaroslav (staff) wrote:Hi,

Did you try downgrading the tape redirector to your previous build?

I haven't, but it was broken on the previous build as well (I tried to upgrade to the latest version to resolve this problem)

Is the disk visible in the disk management? Tape drives don't show up in disk management, but they do show up in the Device Manager, if you check the two attached screenshots called "Drive" and "Library" you'll see it shows as currently connected. I can also use the tools for th...

Hi, Is the drive available now? StarWind cannot access the drive so the StarWind software cannot be a problem here. Try disabling the firewall and antivirus if there is any (do not forget to restart the machine afterward). Did you check the cabling? Nope, still offline. There's no AV for this machi...

Thanks yaroslav, It's a bit strange, the drivers are installed and according to the device manager, the loader and tape drive are both visible and online. I've tried re-installing and updating the drivers for the FC HBA PCI card, the loader and the tape drive itself and it hasn't resolved the issue....

Hi everyone, I've had a bit of a weird issue where my Tape Autoloader and Drive are no longer visible in VSAN. The loader is connected via a Fiber Channel HBA and the physical link is directly between the loader and the host (i.e. no FC switch in the picture). I don't think anything has changed on t...

For anyone who happens across this in future, we got to the bottom of it. There were several contributing factors: 1. The thick-provsion lazy zero VMDK which held the Starwind Volume needed to be a thick-provision eager zero disk 2. Using the LSI SAS controller as the virtual RAID controller for the...

Hi entr0p1, Happy to know that the issue was resolved. Yes, logs look fine now: .img files can be accessed and I see operations with them. Cache is still there but it can be accessed as well as the disk. Hi yaroslav, Thanks for all your help so far, I've just sent you a PM because we're still not q...

yaroslav, I've discovered that with all the mucking about with the virtual storage controllers, the disks were placed into read-only mode which I missed and I'm guessing that's why you saw that error code in the logs. I have fixed the read-only disks and things have improved significantly, the issue...

yaroslav (staff) wrote:We recommend using LSI Logic SAS one.

Okay no problem, I have now switched to the LSI SAS controller.

Just an update - I've switched back to Server 2019 and re-provisioned the underlying VMDK as a Thick Provision Eager Zeroed disk. The same errors are still being generated in the logs sadly, I'll wait to hear back.

Thanks for your response, once I've got more resources added to the physical host I will definitely make those changes. I've gathered the logs and sent them to you in a PM. The SCSI controller is a VMware Paravirtual, I've tried the LSI controller as well and get the same result. VMware tools are al...

Hi everyone, I'm having some issues with VSAN serving up an iSCSI LUN to a VMware ESXi 6.7 server. The VSAN VM resides on the same physical server it is serving the LUN to. The VM has two NICs configured as storage NICs, these are passed through a Standard vSwitch to two physical NICs on the host (w...