Hello
I'm running ESX 3.5 connected to MD3000 (iSCSI)
1. I discovered some hosts SLES-SP2 with filesystem in ReadOnly (EXT3 Journaling abort)
2. Searching in my ESX Logs , I've found bad errors ...
Do you have an Idea how to Solve that ??? My colleage said to just move my System to Reizer :_| .
I think it's more related to iSCSI error .
Thanks for all.
Jun 16 11:59:15 esx-6950-0308 vmkernel: 50:18:35:28.068 cpu3:1078)iSCSI: session 0x352543d0 (1 0 4 0) finished error recovery at 438692803
Jun 16 11:59:15 esx-6950-0308 vmkernel: 50:18:35:28.069 cpu0:1024)StorageMonitor: 196: vmhba32:4:0:0 status = 0/5 0x0 0x0 0x0
Jun 16 11:59:15 esx-6950-0308 vmkernel: 50:18:35:28.074 cpu3:1027)StorageMonitor: 196: vmhba32:4:0:0 status = 24/0 0x0 0x0 0x0
Jun 16 11:59:22 esx-6950-0308 vmkernel: 50:18:35:34.906 cpu3:1086)VSCSI: 2803: Reset request on handle 8192 (3 outstanding commands)
Jun 16 11:59:22 esx-6950-0308 vmkernel: 50:18:35:34.906 cpu3:1056)VSCSI: 3019: Resetting handle 8192
Jun 16 11:59:22 esx-6950-0308 vmkernel: 50:18:35:34.906 cpu3:1056)WARNING: VSCSIFs: 235: Failed reset of virtual target
Jun 16 11:59:22 esx-6950-0308 vmkernel: 50:18:35:34.906 cpu3:1078)iSCSI: session 0x352543d0 sending mgmt 17129707 abort for itt 17129689 task 0x35201460 cmnd 0x3ee3f600 cdb 0x28 to (1 0 4 0) at 438693487
Jun 16 11:59:26 esx-6950-0308 vmkernel: 50:18:35:38.448 cpu2:1156)LinSCSI: 3201: Abort failed for cmd with serial=2148401231, status=bad0001, retval=bad0001
Jun 16 11:59:26 esx-6950-0308 vmkernel: 50:18:35:38.533 cpu1:1125)LinSCSI: 3201: Abort failed for cmd with serial=2148401212, status=bad0001, retval=bad0001
Jun 16 11:59:28 esx-6950-0308 vmkernel: 50:18:35:40.503 cpu1:1156)VSCSI: 2803: Reset request on handle 8211 (1 outstanding commands)
Jun 16 11:59:28 esx-6950-0308 vmkernel: 50:18:35:40.503 cpu1:1156)VSCSI: 2803: Reset request on handle 8212 (1 outstanding commands)
Jun 16 11:59:28 esx-6950-0308 vmkernel: 50:18:35:40.503 cpu1:1156)VSCSI: 2803: Reset request on handle 8213 (1 outstanding commands)
Jun 16 11:59:28 esx-6950-0308 vmkernel: 50:18:35:40.503 cpu1:1056)VSCSI: 3019: Resetting handle 8211
Jun 16 11:59:28 esx-6950-0308 vmkernel: 50:18:35:40.503 cpu1:1056)WARNING: VSCSIFs: 235: Failed reset of virtual target
Jun 16 11:59:28 esx-6950-0308 vmkernel: 50:18:35:40.503 cpu1:1056)VSCSI: 3019: Resetting handle 8212
Jun 16 11:59:28 esx-6950-0308 vmkernel: 50:18:35:40.503 cpu1:1056)WARNING: VSCSIFs: 235: Failed reset of virtual target
Jun 16 11:59:28 esx-6950-0308 vmkernel: 50:18:35:40.503 cpu1:1056)VSCSI: 3019: Resetting handle 8213
Jun 16 11:59:28 esx-6950-0308 vmkernel: 50:18:35:40.503 cpu1:1056)WARNING: VSCSIFs: 235: Failed reset of virtual target
Jun 16 11:59:28 esx-6950-0308 vmkernel: 50:18:35:40.589 cpu1:1125)VSCSI: 2803: Reset request on handle 8204 (1 outstanding commands)
Jun 16 11:59:28 esx-6950-0308 vmkernel: 50:18:35:40.589 cpu1:1125)VSCSI: 2803: Reset request on handle 8205 (0 outstanding commands)
Jun 16 11:59:28 esx-6950-0308 vmkernel: 50:18:35:40.589 cpu1:1125)VSCSI: 2803: Reset request on handle 8206 (2 outstanding commands)
Jun 16 11:59:28 esx-6950-0308 vmkernel: 50:18:35:40.589 cpu1:1056)VSCSI: 3019: Resetting handle 8204
Jun 16 11:59:28 esx-6950-0308 vmkernel: 50:18:35:40.589 cpu1:1056)WARNING: VSCSIFs: 235: Failed reset of virtual target
Jun 16 11:59:28 esx-6950-0308 vmkernel: 50:18:35:40.589 cpu1:1056)VSCSI: 3019: Resetting handle 8205
Jun 16 11:59:28 esx-6950-0308 vmkernel: 50:18:35:40.589 cpu1:1056)VSCSI: 2871: Completing reset on handle 8205 (0 outstanding commands)
Jun 16 11:59:28 esx-6950-0308 vmkernel: 50:18:35:40.589 cpu1:1056)VSCSI: 3019: Resetting handle 8206
Jun 16 11:59:28 esx-6950-0308 vmkernel: 50:18:35:40.589 cpu1:1056)WARNING: VSCSIFs: 235: Failed reset of virtual target
Jun 16 11:59:36 esx-6950-0308 vmkernel: 50:18:35:49.064 cpu0:1069)iSCSI: session 0x352543d0 task mgmt 17129707 response timeout at 438694903
Jun 16 11:59:36 esx-6950-0308 vmkernel: 50:18:35:49.064 cpu3:1078)iSCSI: session 0x352543d0 sending mgmt 17129708 abort task set to (1 0 4 0) at 438694903
Jun 16 11:59:47 esx-6950-0308 vmkernel: 50:18:36:00.064 cpu0:1069)iSCSI: session 0x352543d0 task mgmt 17129708 response timeout at 438696003
Jun 16 11:59:47 esx-6950-0308 vmkernel: 50:18:36:00.064 cpu3:1078)iSCSI: session 0x352543d0 sending mgmt 17129710 LUN reset to (1 0 4 0) at 438696003
Jun 16 11:59:47 esx-6950-0308 vmkernel: 50:18:36:00.067 cpu3:1079)iSCSI: session 0x352543d0 LUN reset success for mgmt 17129710, itt 17129689, task 0x35201460, cmnd 0x3ee3f600
Jun 16 14:53:32 esx-6950-0308 vmkernel: 50:21:29:45.049 cpu0:1053)StorageMonitor: 196: vmhba32:1:0:0 status = 0/1 0x2 0x8 0x0
Jun 16 14:53:32 esx-6950-0308 vmkernel: 50:21:29:45.050 cpu0:1053)StorageMonitor: 196: vmhba32:1:0:0 status = 0/1 0x2 0x8 0x0
Jun 16 14:53:32 esx-6950-0308 vmkernel: 50:21:29:45.050 cpu0:1053)WARNING: SCSI: 5306: vml.02000000006090a02850045e31c17ae4490000d0a6313030452d30: Too many failed retries 33 (32), Returning I/O failure. 0x28 1/0x0 0x2 0x8 0x0
Jun 16 14:53:32 esx-6950-0308 vmkernel: 50:21:29:45.240 cpu0:1024)SCSI: 4480: Cannot find a path to device vmhba32:1:0 in a good state. Trying path vmhba32:1:0. Retry count 0.
Jun 16 14:53:32 esx-6950-0308 vmkernel: 50:21:29:45.240 cpu0:1024)StorageMonitor: 196: vmhba32:1:0:0 status = 0/1 0x2 0x8 0x0
Jun 16 14:53:32 esx-6950-0308 vmkernel: 50:21:29:45.240 cpu0:1024)SCSI: 5226: vml.02000000006090a02850045e31c17ae4490000d0a6313030452d30: Cmd failed. Blocking device during path failover.
Jun 16 14:53:32 esx-6950-0308 vmkernel: 50:21:29:45.241 cpu3:1054)SCSI: 4480: Cannot find a path to device vmhba32:1:0 in a good state. Trying path vmhba32:1:0. Retry count 1.
Jun 16 14:53:32 esx-6950-0308 vmkernel: 50:21:29:45.241 cpu3:1054)StorageMonitor: 196: vmhba32:1:0:0 status = 0/1 0x2 0x8 0x0
Jun 16 14:53:32 esx-6950-0308 vmkernel: 50:21:29:45.243 cpu0:1053)SCSI: 4480: Cannot find a path to device vmhba32:1:0 in a good state. Trying path vmhba32:1:0. Retry count 2.
Jun 16 14:53:32 esx-6950-0308 vmkernel: 50:21:29:45.243 cpu0:1053)StorageMonitor: 196: vmhba32:1:0:0 status = 0/1 0x2 0x8 0x0
Jun 16 14:53:32 esx-6950-0308 vmkernel: 50:21:29:45.244 cpu1:1051)StorageMonitor: 196: vmhba32:1:0:0 status = 0/1 0x2 0x8 0x0
Jun 16 14:53:32 esx-6950-0308 vmkernel: 50:21:29:45.245 cpu0:1053)StorageMonitor: 196: vmhba32:1:0:0 status = 0/1 0x2 0x8 0x0
Jun 16 14:53:32 esx-6950-0308 vmkernel: 50:21:29:45.246 cpu3:1054)StorageMonitor: 196: vmhba32:1:0:0 status = 0/1 0x2 0x8 0x0
Jun 16 14:53:32 esx-6950-0308 vmkernel: 50:21:29:45.247 cpu1:1052)StorageMonitor: 196: vmhba32:1:0:0 status = 0/1 0x2 0x8 0x0
Jun 16 14:53:32 esx-6950-0308 vmkernel: 50:21:29:45.248 cpu0:1053)StorageMonitor: 196: vmhba32:1:0:0 status = 0/1 0x2 0x8 0x0
Jun 16 14:53:32 esx-6950-0308 vmkernel: 50:21:29:45.249 cpu0:1053)SCSI: 4480: Cannot find a path to device vmhba32:1:0 in a good state. Trying path vmhba32:1:0. Retry count 8.