Partition to Disk bridged device
Partition to Disk bridged device
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.
-
- Posts: 205
- Joined: Thu Nov 05, 2009 5:52 pm
- Contact:
Re: Partition to Disk bridged device
It seems that the initiator still haven't got the full access, you can view it at the Initiators view of iStorage Server Management Console, and see FAQs for help:
http://www.kernsafe.com/product.aspx?id=5&name=Faqs
If you are using the version before 1.40, please upgrade it to the newest version.
If the problem can't be resolved, please tell me the following information:
Which version of iStorage Server? Version number and architecture (x32, x86 or Itanium).
Do you select any partition table construction or just leave RAW (Nothing selected) mapping?
http://www.kernsafe.com/product.aspx?id=5&name=Faqs
If you are using the version before 1.40, please upgrade it to the newest version.
If the problem can't be resolved, please tell me the following information:
Which version of iStorage Server? Version number and architecture (x32, x86 or Itanium).
Do you select any partition table construction or just leave RAW (Nothing selected) mapping?
KernSafe Support Team
iSCSI SAN, iSCSI Target, iSCSI initiator and related technological support.
[email protected]
iSCSI SAN, iSCSI Target, iSCSI initiator and related technological support.
[email protected]
Re: Partition to Disk bridged device
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 on device sdd1, logical block 0
Feb 26 05:31:12 fedora-xen kernel: Buffer I/O error on device sdd1, logical block 1
Feb 26 05:31:12 fedora-xen kernel: Buffer I/O error on device sdd1, logical block 2
Feb 26 05:31:12 fedora-xen kernel: Buffer I/O error on device sdd1, logical block 3
Feb 26 05:31:12 fedora-xen kernel: Buffer I/O error on device sdd1, logical block 4
Feb 26 05:31:12 fedora-xen kernel: Buffer I/O error on device sdd1, logical block 5
Feb 26 05:31:12 fedora-xen kernel: Buffer I/O error on device sdd1, logical block 6
Feb 26 05:31:12 fedora-xen kernel: Buffer I/O error on device sdd1, logical block 7
Feb 26 05:31:12 fedora-xen kernel: Buffer I/O error on device sdd1, logical block 8
Feb 26 05:31:12 fedora-xen kernel: Buffer I/O error on device sdd1, logical block 9
Feb 26 05:31:12 fedora-xen kernel: sd 34:0:0:0: [sdd] Unhandled sense code
Feb 26 05:31:12 fedora-xen kernel: sd 34:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 26 05:31:12 fedora-xen kernel: sd 34:0:0:0: [sdd] Sense Key : Medium Error [current]
Feb 26 05:31:12 fedora-xen kernel: sd 34:0:0:0: [sdd] Add. Sense: Id CRC or ECC error
Feb 26 05:31:12 fedora-xen kernel: end_request: I/O error, dev sdd, sector 63
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 on device sdd1, logical block 0
Feb 26 05:31:12 fedora-xen kernel: Buffer I/O error on device sdd1, logical block 1
Feb 26 05:31:12 fedora-xen kernel: Buffer I/O error on device sdd1, logical block 2
Feb 26 05:31:12 fedora-xen kernel: Buffer I/O error on device sdd1, logical block 3
Feb 26 05:31:12 fedora-xen kernel: Buffer I/O error on device sdd1, logical block 4
Feb 26 05:31:12 fedora-xen kernel: Buffer I/O error on device sdd1, logical block 5
Feb 26 05:31:12 fedora-xen kernel: Buffer I/O error on device sdd1, logical block 6
Feb 26 05:31:12 fedora-xen kernel: Buffer I/O error on device sdd1, logical block 7
Feb 26 05:31:12 fedora-xen kernel: Buffer I/O error on device sdd1, logical block 8
Feb 26 05:31:12 fedora-xen kernel: Buffer I/O error on device sdd1, logical block 9
Feb 26 05:31:12 fedora-xen kernel: sd 34:0:0:0: [sdd] Unhandled sense code
Feb 26 05:31:12 fedora-xen kernel: sd 34:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 26 05:31:12 fedora-xen kernel: sd 34:0:0:0: [sdd] Sense Key : Medium Error [current]
Feb 26 05:31:12 fedora-xen kernel: sd 34:0:0:0: [sdd] Add. Sense: Id CRC or ECC error
Feb 26 05:31:12 fedora-xen kernel: end_request: I/O error, dev sdd, sector 63
-
- Posts: 205
- Joined: Thu Nov 05, 2009 5:52 pm
- Contact:
Re: Partition to Disk bridged device
We found it, it heppens when client machine try to write Parition Table, but it is readonly and can't modified, the RAW (do not select Construct MBR and GPT) method is working without any problem.
We will improve the mechanism at the next version.
We will improve the mechanism at the next version.
KernSafe Support Team
iSCSI SAN, iSCSI Target, iSCSI initiator and related technological support.
[email protected]
iSCSI SAN, iSCSI Target, iSCSI initiator and related technological support.
[email protected]