KernSafe Technology

Here is the packet capture in text form: No. Time Source Destination Protocol Info 1 07:39:19.727704 192.168.1.3 192.168.1.1 iSCSI SCSI Command: 0x01 LUN:0x00 Frame 1 (114 bytes on wire, 114 bytes captured) Ethernet II, Src: SuperMic_01:37:49 (00:25:90:01:37:49), Dst: IntelCor_07:36:86 (00:1b:21:07:...

Thanks that fixed the inquiry problem. Now I have a new problem :-) Access to the tape drive works okay until the device is closed and the LInux st driver issues a rewind. It looks like maybe the device stops responding while the rewind takes place. Here are the messages logged on the Linux system: ...

The initiator view does show full access. I've tried it with all combinations of "Hold and Update" and "Construct MBR" checked and unchecked. This is with the latest version 1.60 (x64) on Windows SBS 2008 64 bit. Here is part of /var/log/messages: Feb 26 05:31:12 fedora-xen kernel: Buffer I/O error ...

I created a Generic SCSI bridge device with a Tape drive. But when I connect to it from a Centos 5.4 client the inquiry data is messed up, here is the output from the tapeinfo command: Product Type: Disk Drive Vendor ID: '' Product ID: '' Revision: '' Attached Changer API: No SerialNumber: '' MinBlo...

I created a Partition to Disk bridged device on Windows SBS 2008 using iStorage Server and it seemed to work fine when connected read-only. When I used CHAP authentication for full access I got a lot of disk errors logged on the Windows 7 client using the builtin initiator.