VMware Cloud Community
pcdog
Contributor
Contributor

One ESXi "Not Responding" In VC

Hi folks

I have two ESX 3i Installations on a *K8N-DRE*. both went fine without any modifications at all.

I did install some of the VM' on the local storage, but most of them on the NFS share I have on a Solaris host (Thread earlier in this forum, Problems there resolved!)

now I have, stored on one of the ESXi, the VC virtual Machine. works fine, except I always loose the connection to the other Hardware! (showing "Not responding")

I can login fine via SSH, also ALL OF THE VM's that are there now on NFS; are still running. I just can't manage the host anymore.

if I am going to /var/ on the ESXi that is suppsed to hang, the shell stops which makes me think there must be something with the mount or similar.

here attached some logs:

Oct 28 07:22:40 vmkernel: 0:14:17:34.402 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 07:22:40 vmkernel: 0:14:17:34.402 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 07:22:52 vmkernel: 0:14:17:45.976 cpu1:1037)WARNING: FS3: 4785: Reservation error: Timeout

Oct 28 07:22:56 vmkernel: 0:14:17:50.246 cpu0:1510)FSS: 390: Failed with status Timeout (ok to retry) for fa7 40 3 b214e7e0 156b3058 9c4b4e6f ae2688dd 2b39 2b39 fffffffd 8fb5a73959 0 0 0

Oct 28 07:22:56 vmkernel: 0:14:17:50.246 cpu0:1510)WARNING: UserObj: 583: could not crossdup cwd: Timeout (ok to retry)

Oct 28 07:23:10 vmkernel: 0:14:18:04.456 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 07:23:10 vmkernel: 0:14:18:04.456 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 07:23:34 vmkernel: 0:14:18:27.998 cpu1:1037)WARNING: FS3: 4785: Reservation error: Timeout

Oct 28 07:23:36 vmkernel: 0:14:18:30.256 cpu0:1510)FSS: 390: Failed with status Timeout (ok to retry) for fa7 40 3 b214e7e0 156b3058 9c4b4e6f ae2688dd 2b39 2b39 fffffffd 8fb5a73959 0 0 0

Oct 28 07:23:36 vmkernel: 0:14:18:30.256 cpu0:1510)WARNING: UserObj: 583: could not crossdup cwd: Timeout (ok to retry)

Oct 28 07:23:40 vmkernel: 0:14:18:34.508 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 07:23:40 vmkernel: 0:14:18:34.508 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 07:24:10 vmkernel: 0:14:19:04.564 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 07:24:10 vmkernel: 0:14:19:04.564 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 07:24:16 vmkernel: 0:14:19:10.024 cpu1:1037)WARNING: FS3: 4785: Reservation error: Timeout

Oct 28 07:24:40 vmkernel: 0:14:19:34.624 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 07:24:40 vmkernel: 0:14:19:34.624 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 07:24:56 vmkernel: 0:14:19:50.268 cpu1:1510)FSS: 390: Failed with status Timeout (ok to retry) for fa7 40 3 b214e7e0 156b3058 9c4b4e6f ae2688dd 2b39 2b39 fffffffd 8fb5a73959 0 0 0

Oct 28 07:24:56 vmkernel: 0:14:19:50.268 cpu1:1510)WARNING: UserObj: 583: could not crossdup cwd: Timeout (ok to retry)

Oct 28 07:24:58 vmkernel: 0:14:19:52.038 cpu1:1037)WARNING: FS3: 4785: Reservation error: Timeout

Oct 28 07:25:10 vmkernel: 0:14:20:04.682 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 07:25:10 vmkernel: 0:14:20:04.682 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 07:25:11 -- MARK --

Oct 28 07:25:36 vmkernel: 0:14:20:30.280 cpu1:1510)FSS: 390: Failed with status Timeout (ok to retry) for fa7 40 3 b214e7e0 156b3058 9c4b4e6f ae2688dd 2b39 2b39 fffffffd 8fb5a73959 0 0 0

Oct 28 07:25:36 vmkernel: 0:14:20:30.280 cpu1:1510)WARNING: UserObj: 583: could not crossdup cwd: Timeout (ok to retry)

+Oct 28 07:25:36 watchdog-vpxa: '/opt/vmware/vpxa/sbin/vpxa +min=0,swap,group=vpxa' exited after 120 seconds

Oct 28 07:25:40 vmkernel: 0:14:20:34.054 cpu1:1037)WARNING: FS3: 4785: Reservation error: Timeout

Oct 28 07:25:40 vmkernel: 0:14:20:34.738 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 07:25:40 vmkernel: 0:14:20:34.738 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 07:26:10 vmkernel: 0:14:21:04.788 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 07:26:10 vmkernel: 0:14:21:04.788 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 07:26:16 vmkernel: 0:14:21:10.292 cpu0:1510)FSS: 390: Failed with status Timeout (ok to retry) for fa7 40 3 b214e7e0 156b3058 9c4b4e6f ae2688dd 2b39 2b39 fffffffd 8fb5a73959 0 0 0

Oct 28 07:26:16 vmkernel: 0:14:21:10.292 cpu0:1510)WARNING: UserObj: 583: could not crossdup cwd: Timeout (ok to retry)

+Oct 28 07:26:16 watchdog-vpxa: Executing '/opt/vmware/vpxa/sbin/vpxa +min=0,swap,group=vpxa'

Oct 28 07:26:22 vmkernel: 0:14:21:16.070 cpu1:1037)WARNING: FS3: 4785: Reservation error: Timeout

Oct 28 07:26:40 vmkernel: 0:14:21:34.842 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 07:26:40 vmkernel: 0:14:21:34.842 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 07:26:56 vmkernel: 0:14:21:50.306 cpu0:1510)FSS: 390: Failed with status Timeout (ok to retry) for fa7 40 3 b214e7e0 156b3058 9c4b4e6f ae2688dd 2b39 2b39 fffffffd 8fb5a73959 0 0 0

Oct 28 07:26:56 vmkernel: 0:14:21:50.306 cpu0:1510)WARNING: UserObj: 583: could not crossdup cwd: Timeout (ok to retry)

Oct 28 07:27:04 vmkernel: 0:14:21:58.090 cpu1:1037)WARNING: FS3: 4785: Reservation error: Timeout

Oct 28 07:27:10 vmkernel: 0:14:22:04.898 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 07:27:10 vmkernel: 0:14:22:04.898 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 07:27:36 vmkernel: 0:14:22:30.318 cpu0:1510)FSS: 390: Failed with status Timeout (ok to retry) for fa7 40 3 b214e7e0 156b3058 9c4b4e6f ae2688dd 2b39 2b39 fffffffd 8fb5a73959 0 0 0

Oct 28 07:27:36 vmkernel: 0:14:22:30.318 cpu0:1510)WARNING: UserObj: 583: could not crossdup cwd: Timeout (ok to retry)

Oct 28 07:27:41 vmkernel: 0:14:22:34.946 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 07:27:41 vmkernel: 0:14:22:34.946 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 07:27:46 vmkernel: 0:14:22:40.112 cpu1:1037)WARNING: FS3: 4785: Reservation error: Timeout

Oct 28 07:28:11 vmkernel: 0:14:23:05.000 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 07:28:11 vmkernel: 0:14:23:05.000 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 07:28:28 vmkernel: 0:14:23:22.134 cpu1:1037)WARNING: FS3: 4785: Reservation error: Timeout

Oct 28 07:28:41 vmkernel: 0:14:23:35.054 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 07:28:41 vmkernel: 0:14:23:35.054 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 07:28:56 vmkernel: 0:14:23:50.330 cpu0:1510)FSS: 390: Failed with status Timeout (ok to retry) for fa7 40 3 b214e7e0 156b3058 9c4b4e6f ae2688dd 2b39 2b39 fffffffd 8fb5a73959 0 0 0

Oct 28 07:28:56 vmkernel: 0:14:23:50.330 cpu0:1510)WARNING: UserObj: 583: could not crossdup cwd: Timeout (ok to retry)

Oct 28 07:29:10 vmkernel: 0:14:24:04.152 cpu1:1037)WARNING: FS3: 4785: Reservation error: Timeout

Oct 28 07:29:11 vmkernel: 0:14:24:05.102 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 07:29:11 vmkernel: 0:14:24:05.102 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 07:29:36 vmkernel: 0:14:24:30.340 cpu1:1510)FSS: 390: Failed with status Timeout (ok to retry) for fa7 40 3 b214e7e0 156b3058 9c4b4e6f ae2688dd 2b39 2b39 fffffffd 8fb5a73959 0 0 0

Oct 28 07:29:36 vmkernel: 0:14:24:30.340 cpu1:1510)WARNING: UserObj: 583: could not crossdup cwd: Timeout (ok to retry)

+Oct 28 07:29:36 watchdog-vpxa: '/opt/vmware/vpxa/sbin/vpxa +min=0,swap,group=vpxa' exited after 120 seconds

Oct 28 07:29:41 vmkernel: 0:14:24:35.155 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 07:29:41 vmkernel: 0:14:24:35.155 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 07:29:52 vmkernel: 0:14:24:46.174 cpu1:1037)WARNING: FS3: 4785: Reservation error: Timeout

Oct 28 07:30:01 crond[1286]: USER root pid 168846 cmd /sbin/decodeSel.sh #Every 10 minutes, translate the latest IPMI SEL data

Oct 28 07:30:11 vmkernel: 0:14:25:05.206 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 07:30:11 vmkernel: 0:14:25:05.206 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 07:30:16 vmkernel: 0:14:25:10.352 cpu1:1510)FSS: 390: Failed with status Timeout (ok to retry) for fa7 40 3 b214e7e0 156b3058 9c4b4e6f ae2688dd 2b39 2b39 fffffffd 8fb5a73959 0 0 0

Oct 28 07:30:16 vmkernel: 0:14:25:10.352 cpu1:1510)WARNING: UserObj: 583: could not crossdup cwd: Timeout (ok to retry)

+Oct 28 07:30:16 watchdog-vpxa: Executing '/opt/vmware/vpxa/sbin/vpxa +min=0,swap,group=vpxa'

Oct 28 07:30:34 vmkernel: 0:14:25:28.190 cpu1:1037)WARNING: FS3: 4785: Reservation error: Timeout

Oct 28 07:30:41 vmkernel: 0:14:25:35.262 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 07:30:41 vmkernel: 0:14:25:35.263 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 07:30:56 vmkernel: 0:14:25:50.362 cpu1:1510)FSS: 390: Failed with status Timeout (ok to retry) for fa7 40 3 b214e7e0 156b3058 9c4b4e6f ae2688dd 2b39 2b39 fffffffd 8fb5a73959 0 0 0

Oct 28 07:30:56 vmkernel: 0:14:25:50.362 cpu1:1510)WARNING: UserObj: 583: could not crossdup cwd: Timeout (ok to retry)

Oct 28 07:31:11 vmkernel: 0:14:26:05.322 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 07:31:11 vmkernel: 0:14:26:05.322 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 07:31:16 vmkernel: 0:14:26:10.214 cpu1:1037)WARNING: FS3: 4785: Reservation error: Timeout

Oct 28 07:31:36 vmkernel: 0:14:26:30.374 cpu0:1510)FSS: 390: Failed with status Timeout (ok to retry) for fa7 40 3 b214e7e0 156b3058 9c4b4e6f ae2688dd 2b39 2b39 fffffffd 8fb5a73959 0 0 0

Oct 28 07:31:36 vmkernel: 0:14:26:30.374 cpu0:1510)WARNING: UserObj: 583: could not crossdup cwd: Timeout (ok to retry)

Oct 28 07:31:41 vmkernel: 0:14:26:35.379 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 07:31:41 vmkernel: 0:14:26:35.379 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 07:31:58 vmkernel: 0:14:26:52.228 cpu1:1037)WARNING: FS3: 4785: Reservation error: Timeout

Oct 28 07:32:11 vmkernel: 0:14:27:05.432 cpu0:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 07:32:11 vmkernel: 0:14:27:05.433 cpu0:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 07:32:40 vmkernel: 0:14:27:34.246 cpu1:1037)WARNING: FS3: 4785: Reservation error: Timeout

Oct 28 07:32:41 vmkernel: 0:14:27:35.490 cpu0:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 07:32:41 vmkernel: 0:14:27:35.491 cpu0:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 07:32:56 vmkernel: 0:14:27:50.390 cpu0:1510)FSS: 390: Failed with status Timeout (ok to retry) for fa7 40 3 b214e7e0 156b3058 9c4b4e6f ae2688dd 2b39 2b39 fffffffd 8fb5a73959 0 0 0

Oct 28 07:32:56 vmkernel: 0:14:27:50.390 cpu0:1510)WARNING: UserObj: 583: could not crossdup cwd: Timeout (ok to retry)

Oct 28 07:33:11 vmkernel: 0:14:28:05.550 cpu0:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 07:33:11 vmkernel: 0:14:28:05.551 cpu0:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 07:33:22 vmkernel: 0:14:28:16.256 cpu1:1037)WARNING: FS3: 4785: Reservation error: Timeout

Oct 28 07:33:31 dropbear[169373]: Child connection from 10.2.253.254:50585

Oct 28 07:33:36 vmkernel: 0:14:28:30.402 cpu0:1510)FSS: 390: Failed with status Timeout (ok to retry) for fa7 40 3 b214e7e0 156b3058 9c4b4e6f ae2688dd 2b39 2b39 fffffffd 8fb5a73959 0 0 0

Oct 28 07:33:36 vmkernel: 0:14:28:30.402 cpu0:1510)WARNING: UserObj: 583: could not crossdup cwd: Timeout (ok to retry)

+Oct 28 07:33:36 watchdog-vpxa: '/opt/vmware/vpxa/sbin/vpxa +min=0,swap,group=vpxa' exited after 120 seconds

Oct 28 07:33:41 dropbear[169373]: password auth succeeded for 'root' from 10.2.253.254:50585

Oct 28 07:33:41 vmkernel: 0:14:28:35.602 cpu0:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 07:33:41 vmkernel: 0:14:28:35.603 cpu0:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 07:33:41 vmkernel: 0:14:28:35.620 cpu1:169373)WARNING: UserObj: 555: Failed to crossdup fd 6, fs: def5 oid: 16000000030000000 type CHAR: Busy

Oct 28 07:34:04 vmkernel: 0:14:28:58.272 cpu1:1037)WARNING: FS3: 4785: Reservation error: Timeout

Any Clues of what I could do to fix this issue? I did change the harddisk - and as the VM's are still running and I can access the log here I guess the controller is fine too

The memory is ECC! so I don't think I have a memory Problem

Thanks for some hints,

Silvan

Reply
0 Kudos
3 Replies
pcdog
Contributor
Contributor

Update:

are VirtualCenter Version 2.5.0

Build 119598

ESXi is the newest Build ("Firmware upgrade just applied yesterday after I reinstalled the whole host)

Update2:

I just discovered that the last VM that is stored on the local harddisk (one out of two Exchange Boxes, Running in a cluster) is also unreachable. I guess I have replaced a faulty drive with a faulty drive?

can someone look through my logs here? the bios on the boot says "S.M.A.R.T OK"

I have about 10 such lines per minute in my logs:

Oct 28 08:19:46 vmkernel: 0:15:14:40.395 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 08:19:46 vmkernel: 0:15:14:40.395 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 08:20:01 crond[1286]: USER root pid 178309 cmd /sbin/decodeSel.sh #Every 10 minutes, translate the latest IPMI SEL data

Oct 28 08:20:09 vmkernel: 0:15:15:03.856 cpu1:2134)WARNING: UserSocketInet: 588: waiters list not empty!

Oct 28 08:20:09 Hostd: Activation : Invoke done on

Oct 28 08:20:09 Hostd: Throw vmodl.fault.RequestCanceled

Oct 28 08:20:09 Hostd: Result:

Oct 28 08:20:09 Hostd: (vmodl.fault.RequestCanceled) { dynamicType = <unset>, msg = "" }

Oct 28 08:20:09 Hostd:

Oct 28 08:20:09 Hostd: Failed to send response to the client: Broken pipe

Oct 28 08:20:16 vmkernel: 0:15:15:10.449 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 08:20:16 vmkernel: 0:15:15:10.449 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 08:20:17 vmkernel: 0:15:15:11.432 cpu1:1037)WARNING: FS3: 4785: Reservation error: Timeout

Oct 28 08:20:46 vmkernel: 0:15:15:40.503 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 08:20:46 vmkernel: 0:15:15:40.503 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 08:20:57 vmkernel: 0:15:15:51.147 cpu0:1510)FSS: 390: Failed with status Timeout (ok to retry) for fa7 40 3 b214e7e0 156b3058 9c4b4e6f ae2688dd 2b39 2b39 fffffffd 8fb5a73959 0 0 0

Oct 28 08:20:57 vmkernel: 0:15:15:51.147 cpu0:1510)WARNING: UserObj: 583: could not crossdup cwd: Timeout (ok to retry)

Oct 28 08:20:59 vmkernel: 0:15:15:53.448 cpu1:1037)WARNING: FS3: 4785: Reservation error: Timeout

Oct 28 08:21:16 vmkernel: 0:15:16:10.555 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 08:21:16 vmkernel: 0:15:16:10.555 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 08:21:37 vmkernel: 0:15:16:31.160 cpu1:1510)FSS: 390: Failed with status Timeout (ok to retry) for fa7 40 3 b214e7e0 156b3058 9c4b4e6f ae2688dd 2b39 2b39 fffffffd 8fb5a73959 0 0 0

Oct 28 08:21:37 vmkernel: 0:15:16:31.160 cpu1:1510)WARNING: UserObj: 583: could not crossdup cwd: Timeout (ok to retry)

Oct 28 08:21:37 watchdog-vpxa: '/opt/vmware/vpxa/sbin/vpxa ++min=0,swap,group=vpxa' exited after 120 seconds

Oct 28 08:21:41 vmkernel: 0:15:16:35.462 cpu1:1037)WARNING: FS3: 4785: Reservation error: Timeout

Oct 28 08:21:46 vmkernel: 0:15:16:40.611 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 08:21:46 vmkernel: 0:15:16:40.611 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 08:22:16 vmkernel: 0:15:17:10.665 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 08:22:16 vmkernel: 0:15:17:10.665 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 08:22:17 vmkernel: 0:15:17:11.175 cpu1:1510)FSS: 390: Failed with status Timeout (ok to retry) for fa7 40 3 b214e7e0 156b3058 9c4b4e6f ae2688dd 2b39 2b39 fffffffd 8fb5a73959 0 0 0

Oct 28 08:22:17 vmkernel: 0:15:17:11.175 cpu1:1510)WARNING: UserObj: 583: could not crossdup cwd: Timeout (ok to retry)

Oct 28 08:22:17 watchdog-vpxa: Executing '/opt/vmware/vpxa/sbin/vpxa ++min=0,swap,group=vpxa'

Oct 28 08:22:23 vmkernel: 0:15:17:17.480 cpu1:1037)WARNING: FS3: 4785: Reservation error: Timeout

Oct 28 08:22:46 vmkernel: 0:15:17:40.713 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 08:22:46 vmkernel: 0:15:17:40.713 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 08:22:57 vmkernel: 0:15:17:51.189 cpu0:1510)FSS: 390: Failed with status Timeout (ok to retry) for fa7 40 3 b214e7e0 156b3058 9c4b4e6f ae2688dd 2b39 2b39 fffffffd 8fb5a73959 0 0 0

Oct 28 08:22:57 vmkernel: 0:15:17:51.189 cpu0:1510)WARNING: UserObj: 583: could not crossdup cwd: Timeout (ok to retry)

Oct 28 08:23:05 vmkernel: 0:15:17:59.496 cpu1:1037)WARNING: FS3: 4785: Reservation error: Timeout

Oct 28 08:23:16 vmkernel: 0:15:18:10.769 cpu1:1055)VSCSI: 3019: Resetting handle 8192

Oct 28 08:23:16 vmkernel: 0:15:18:10.769 cpu1:1055)WARNING: LinSCSI: 3494: The driver failed to call scsi_done from its abort handler and yet it returned SUCCESS

Oct 28 08:23:37 vmkernel: 0:15:18:31.198 cpu1:1510)FSS: 390: Failed with status Timeout (ok to retry) for fa7 40 3 b214e7e0 156b3058 9c4b4e6f ae2688dd 2b39 2b39 fffffffd 8fb5a73959 0 0 0

Oct 28 08:23:37 vmkernel: 0:15:18:31.198 cpu1:1510)WARNING: UserObj: 583: could not crossdup cwd: Timeout (ok to retry)

_Controller, or Harddrive?? _

Reply
0 Kudos
MZ11
Enthusiast
Enthusiast

Hi,

I have the same problem on tow of three HP BL465c G5. They were running ESXi Build 120505 since October 2008 just fine. Last sunday I detected the same situation an one of the blades; the local disks are not accessible. Because there was no way to evacuate the VMs i shut them down and tries a reboot, but it takes a long time and nothing happens. In fact I killed the bladeserver hard using Onboard Administrator. Booting the server the SmartArray Controller showed "POST Error: 1792-Drive Array Reports Valid Data Found in Array Accelerator", but all was fine again. Now (one week later) the second server had the same problem. I don't think this is a Controller problem because two blades were affected and previously running fine for five month.

I have searched the KB and Release Notes but nothing in there.

Is there any solution for this?

Regards,

MZ1

Reply
0 Kudos
shen390s
Contributor
Contributor

I met the exact same problem with:

Motherboard: Supermicro X7DVL

CPU: Xeon E5405

Memory: 4G ECC FBD memory

HD: ST3500320AS REV:SD15 (SATA)

ESX: 3.5 UP2 Build 123629

The problem occurs immediatelly when I will command 'portsnap fetch update' in a FreeBSD 7.1 Guest

I have asked hardware vendor to replace HD

Can anyone help us?

Thanks

Reply
0 Kudos