2.2.4 to 2.2.5 failed upgrade (atapi_identify, cam status: command timeout)
-
I get these ATAPI_IDENTIFY and CAM Status: Command Timeout errors when I upgrade my pfsense 2.2.4 box, that is running on a VMWare ESXi v6.0 host, to 2.2.5. I just turn off the VM and boot it again and everything seems to be running fine after that. It also seems to be successful in the upgrade. I tried restoring from a full backup just to try if the issue reproducible and it indeed is.
Meanwhile, I upgrade my pfsense 2.2.4 box, that is running on a physical AMD machine, to 2.2.5 and did not have any of these errors.
Why is this happening?
-
Which device specifically is mentioned before the CAM status timeout?
ESX has historically had some oddities with CD drives on some people's systems. Guessing maybe it's the CD drive, especially accompanied with ATAPI.
I've upgraded several dozen ESX VMs myself alone, and no doubt a lot of other ESX VMs have been upgraded of the roughly 1.3 TB of 2.2.5 updates we've served. Haven't heard of any others with issues along those lines. OS-level changes, which is the likely cause, are very minimal between 2.2.4 and 2.2.5, and nothing directly CAM or ATAPI related.
-
@cmb:
Which device specifically is mentioned before the CAM status timeout?
ESX has historically had some oddities with CD drives on some people's systems. Guessing maybe it's the CD drive, especially accompanied with ATAPI.
I've upgraded several dozen ESX VMs myself alone, and no doubt a lot of other ESX VMs have been upgraded of the roughly 1.3 TB of 2.2.5 updates we've served. Haven't heard of any others with issues along those lines. OS-level changes, which is the likely cause, are very minimal between 2.2.4 and 2.2.5, and nothing directly CAM or ATAPI related.
How would I know which device is being specified by the error? I don't see it specified when the error comes up. But I've just re-checked and the CD drive is disconnected from this particular VM.
-
Right in front of "CAM status" it logs something like "(ada1:ahcich1:0:0:0)".
The CD drive being disconnected is the circumstance with ESX that can make weird things happen. Should connect it, or remove it entirely, to avoid problems.