UNSOLVED
B
brianluck1
40 Posts
0
2563
May 18th, 2006 21:00
SCSI bus resets driving me crazy
Hello all knowledgeable NetWorker Admins. I have been experiencing SCSI bus resets for the past 9 days. My environment is very unstable and I cannot trust anything I backup to be successfully recoverable due to SCSI bus resets. We have made the following changes to our system.
Disable CDI
Disable the Dynamic Drive Sharing
Disable TURs by editing the Windows host¿s registry
Disable the Removable Storage Management (RSM) service
Ensure that Non-Rewind Devices are used
Single initiator / Single Target Zoning must be used.
ESM must be met for all Host Operating System patches, HBAs, SAN Switches, etc.
Conducted a CDL Volume Label Check
QLogic HBA enable target resets were disabled.
After making all of the changes above I personally relabeled all available volumes leaving me with only 7 days of backups. I marked all these volumes as read only, manual recycle. This would prevent me from writing to a potentially corrupt volume. I then over wrote my schedules to conduct a full backup, and backed up 404 servers. Today I ran scanner on 81 volumes. I have examined 65 of these 81 volumes and found 6 volumes corrupt still. I have worked this issue for about 10 days from when the SCSI bus reset was detected. I have clocked more than 200 hours in 9 days and this is still not resolved. It was detected by an event viewer report ID 9 and 11.
Disable CDI
Disable the Dynamic Drive Sharing
Disable TURs by editing the Windows host¿s registry
Disable the Removable Storage Management (RSM) service
Ensure that Non-Rewind Devices are used
Single initiator / Single Target Zoning must be used.
ESM must be met for all Host Operating System patches, HBAs, SAN Switches, etc.
Conducted a CDL Volume Label Check
QLogic HBA enable target resets were disabled.
After making all of the changes above I personally relabeled all available volumes leaving me with only 7 days of backups. I marked all these volumes as read only, manual recycle. This would prevent me from writing to a potentially corrupt volume. I then over wrote my schedules to conduct a full backup, and backed up 404 servers. Today I ran scanner on 81 volumes. I have examined 65 of these 81 volumes and found 6 volumes corrupt still. I have worked this issue for about 10 days from when the SCSI bus reset was detected. I have clocked more than 200 hours in 9 days and this is still not resolved. It was detected by an event viewer report ID 9 and 11.
