/build/static/layout/Breadcrumb_cap_w.png

Kace SDA Upgrade to 9

I upgraded my SDA from the latest version of 8 to 9 today. Since the reboot, I'm getting this type of message over and over (example from post on the internet, so CDB string is different and there are 3 or 4 different strings that cycle through):

(da0:mpt0:0:0:0): WRITE(10). CDB: 2a 00 04 6e d3 e2 00 00 40 00 (da0:mpt0:0:0:0): CAM status: SCSI Status Error (da0:mpt0:0:0:0): SCSI status: Busy (da0:mpt0:0:0:0): Retrying command, 4 more tries remain

My SDA is running on vSphere 6.7. I took a snapshot before the upgrade like I normally do, so I wonder if the delta disk confused it somehow this time.

Should I bail and revert to the snapshot, or is there something else I can try?



0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Posted by: tpr 1 year ago
2nd Degree Black Belt
0

Top Answer

Argh. 10 seconds after I posted, I thought to look at the disk space on the VM LUN. Almost full, so I added some space. Still on the error page, but it appears to have stopped cycling new messages so I'll see if it works it's way through it. If not, I'll reboot it.

ETA: Rebooted on its own and loaded, so I'm in GUI now.



Comments:
  • well the error message (from vmware) just said, that a writing operation was not able to made in the time requested. Yes. this can be a storage problem but usually you should also see massive accesses to the LUN which the SAN cannot handle anymore on a point. - Nico_K 1 year ago
    • Thanks. - tpr 1 year ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ