![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||
Solution Type Problem Resolution Sure Solution 1621436.1 : T10000D - DIV Problem With SAM QFS And Solaris Configuration
In this Document
Applies to:StorageTek T10000D Tape Drive - Version All Versions to All Versions [Release All Releases]Information in this document applies to any platform. SymptomsErrors when reading back a DIV written tape: Feb 1 08:04:44 bridgekeeper scsi: [ID 107833 kern.notice] Sense Key: Hardware_Error
Feb 1 08:04:44 bridgekeeper scsi: [ID 107833 kern.notice] ASC: 0x10 (logical block guard check failed), ASCQ: 0x1, FRU: 0x0
CauseThe DIV (Date Integrity Validation) feature requires you to configure the /kernel/drv/st.conf file. See settings in Solution below. If you write DIV data and then change the st.conf settings for CRC, the previous data will become un-readable. Note: DIV is only available for Solaris 11.0 or greater. Solaris 10 customers do not have this config problem.
SolutionPrior to writing any DIV data, edit the st.conf so the D drive uses the Intel CRC32C for SAM DIV. If you don't edit st.conf for the D drive you will have problems using SAM DIV. # cat /kernel/drv/st.conf
st_dadp_settings= "STK T10000C", "crc32c", "stk-crc32c", "STK T10000D", "crc32c", "stk-crc32c"; # update_drv -i st Note: 24-Feb-2014 Please don't use the -i with update_drv because the syntax is incorrect for update_drv(1M). Also reference Doc ID 1622062.1 Note: If you make any changes to this file, the ST driver (tape drives) needs to be idle, so the module is able to load the configuration.
This problem should only affect the SAM QFS application, that is expecting the crc32c CRC method vs. the Reed Soloman CRC method, that the drive is normally set for. Attachments This solution has no attachment |
||||||||||||||||
|