VMware Cloud Community
Janne07
Contributor
Contributor
‎08-26-2007 01:20 PM

Some problems with Nexsan SATAboy

We're little bit confused here right now. Our disks are going up and down. Rescan usualy brings them back, but then they will be lost again after sime time (random).

Here's the log vmkernel:

Aug 26 23:03:10 esxserver vmkernel: 0:03:41:14.255 cpu1:1032)LVM: 5095: Initialized vmhba0:0:2:1, devID 46d1dc7e-1465e49f-2b7d-00145e2b0932

Aug 26 23:03:10 esxserver vmkernel: 0:03:41:14.258 cpu1:1032)LVM: 5164: Zero volumeSize specified: using available space (1000176156672).

Aug 26 23:03:26 esxserver vmkernel: 0:03:41:30.849 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:03:26 esxserver vmkernel: 0:03:41:30.849 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:03:29 esxserver vmkernel: 0:03:41:33.850 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:03:29 esxserver vmkernel: 0:03:41:33.850 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:03:32 esxserver vmkernel: 0:03:41:36.851 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:03:32 esxserver vmkernel: 0:03:41:36.851 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:03:35 esxserver vmkernel: 0:03:41:39.852 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:03:35 esxserver vmkernel: 0:03:41:39.852 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:03:38 esxserver vmkernel: 0:03:41:42.854 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:03:38 esxserver vmkernel: 0:03:41:42.854 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:03:41 esxserver vmkernel: 0:03:41:45.855 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:03:41 esxserver vmkernel: 0:03:41:45.855 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:03:44 esxserver vmkernel: 0:03:41:48.856 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:03:44 esxserver vmkernel: 0:03:41:48.856 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:03:47 esxserver vmkernel: 0:03:41:51.857 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:03:47 esxserver vmkernel: 0:03:41:51.857 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:03:50 esxserver vmkernel: 0:03:41:54.858 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:03:50 esxserver vmkernel: 0:03:41:54.858 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:03:53 esxserver vmkernel: 0:03:41:57.859 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:03:53 esxserver vmkernel: 0:03:41:57.859 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:03:56 esxserver vmkernel: 0:03:42:00.861 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:03:56 esxserver vmkernel: 0:03:42:00.861 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:03:59 esxserver vmkernel: 0:03:42:03.862 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:03:59 esxserver vmkernel: 0:03:42:03.862 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:04:02 esxserver vmkernel: 0:03:42:06.863 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:04:02 esxserver vmkernel: 0:03:42:06.863 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:04:05 esxserver vmkernel: 0:03:42:09.864 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:04:05 esxserver vmkernel: 0:03:42:09.864 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:04:08 esxserver vmkernel: 0:03:42:12.865 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:04:08 esxserver vmkernel: 0:03:42:12.865 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:04:11 esxserver vmkernel: 0:03:42:15.866 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:04:11 esxserver vmkernel: 0:03:42:15.866 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:04:14 esxserver vmkernel: 0:03:42:18.868 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:04:14 esxserver vmkernel: 0:03:42:18.868 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:04:17 esxserver vmkernel: 0:03:42:21.869 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:04:17 esxserver vmkernel: 0:03:42:21.869 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:04:20 esxserver vmkernel: 0:03:42:24.870 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:04:20 esxserver vmkernel: 0:03:42:24.870 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:04:23 esxserver vmkernel: 0:03:42:27.871 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:04:23 esxserver vmkernel: 0:03:42:27.871 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:04:26 esxserver vmkernel: 0:03:42:30.872 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:04:26 esxserver vmkernel: 0:03:42:30.872 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:04:29 esxserver vmkernel: 0:03:42:33.873 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:04:29 esxserver vmkernel: 0:03:42:33.873 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:04:32 esxserver vmkernel: 0:03:42:36.875 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:04:32 esxserver vmkernel: 0:03:42:36.875 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:04:35 esxserver vmkernel: 0:03:42:39.876 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:04:35 esxserver vmkernel: 0:03:42:39.876 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:04:38 esxserver vmkernel: 0:03:42:42.877 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:04:38 esxserver vmkernel: 0:03:42:42.877 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:04:41 esxserver vmkernel: 0:03:42:45.878 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:04:41 esxserver vmkernel: 0:03:42:45.878 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:04:44 esxserver vmkernel: 0:03:42:48.879 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:04:44 esxserver vmkernel: 0:03:42:48.879 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:04:47 esxserver vmkernel: 0:03:42:51.880 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:04:47 esxserver vmkernel: 0:03:42:51.880 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:04:50 esxserver vmkernel: 0:03:42:54.882 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:04:50 esxserver vmkernel: 0:03:42:54.882 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:04:53 esxserver vmkernel: 0:03:42:57.883 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:04:53 esxserver vmkernel: 0:03:42:57.883 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:04:56 esxserver vmkernel: 0:03:43:00.884 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:04:56 esxserver vmkernel: 0:03:43:00.884 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:04:59 esxserver vmkernel: 0:03:43:03.885 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:04:59 esxserver vmkernel: 0:03:43:03.885 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:05:02 esxserver vmkernel: 0:03:43:06.886 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:05:02 esxserver vmkernel: 0:03:43:06.886 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:05:05 esxserver vmkernel: 0:03:43:09.887 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:05:05 esxserver vmkernel: 0:03:43:09.887 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:05:08 esxserver vmkernel: 0:03:43:12.889 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:05:08 esxserver vmkernel: 0:03:43:12.889 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:05:09 esxserver vmkernel: 0:03:43:13.777 cpu0:1024)WARNING: Helper: 1289: cancel request handle=1 fn=0x612ae4

Aug 26 23:05:09 esxserver vmkernel: 0:03:43:13.777 cpu0:1024)Helper: 772: Dumping non-active requests on HELPER_MISC_QUEUE at 40181859208170

Aug 26 23:05:09 esxserver vmkernel: 0:03:43:13.777 cpu0:1024)Helper: 772: Dumping active requests on HELPER_MISC_QUEUE at 40181859354773

Aug 26 23:05:09 esxserver vmkernel: 0:03:43:13.777 cpu0:1024)Helper: 779: 0: status=2 func=0x612ae4 since=39792752401125

Aug 26 23:05:09 esxserver vmkernel: 0:03:43:13.777 cpu0:1024)VMNIX: Mod: 4166: Waiting for long-running helper request

Aug 26 23:05:11 esxserver vmkernel: 0:03:43:15.890 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:05:11 esxserver vmkernel: 0:03:43:15.890 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:05:14 esxserver vmkernel: 0:03:43:18.891 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:05:14 esxserver vmkernel: 0:03:43:18.891 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:05:17 esxserver vmkernel: 0:03:43:21.892 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:05:17 esxserver vmkernel: 0:03:43:21.892 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:05:20 esxserver vmkernel: 0:03:43:24.893 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:05:20 esxserver vmkernel: 0:03:43:24.893 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:05:23 esxserver vmkernel: 0:03:43:27.894 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:05:23 esxserver vmkernel: 0:03:43:27.894 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:05:26 esxserver vmkernel: 0:03:43:30.896 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:05:26 esxserver vmkernel: 0:03:43:30.896 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:05:29 esxserver vmkernel: 0:03:43:33.897 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:05:29 esxserver vmkernel: 0:03:43:33.897 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:05:32 esxserver vmkernel: 0:03:43:36.898 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:05:32 esxserver vmkernel: 0:03:43:36.898 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:05:35 esxserver vmkernel: 0:03:43:39.899 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:05:35 esxserver vmkernel: 0:03:43:39.899 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:05:38 esxserver vmkernel: 0:03:43:42.900 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:05:38 esxserver vmkernel: 0:03:43:42.900 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:05:41 esxserver vmkernel: 0:03:43:45.901 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:05:41 esxserver vmkernel: 0:03:43:45.901 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:05:44 esxserver vmkernel: 0:03:43:48.903 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:05:44 esxserver vmkernel: 0:03:43:48.903 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:05:47 esxserver vmkernel: 0:03:43:51.904 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:05:47 esxserver vmkernel: 0:03:43:51.904 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:05:50 esxserver vmkernel: 0:03:43:54.905 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:05:50 esxserver vmkernel: 0:03:43:54.905 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:05:53 esxserver vmkernel: 0:03:43:57.906 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:05:53 esxserver vmkernel: 0:03:43:57.906 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:05:56 esxserver vmkernel: 0:03:44:00.907 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:05:56 esxserver vmkernel: 0:03:44:00.907 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:05:59 esxserver vmkernel: 0:03:44:03.908 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:05:59 esxserver vmkernel: 0:03:44:03.908 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:06:02 esxserver vmkernel: 0:03:44:06.910 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:06:02 esxserver vmkernel: 0:03:44:06.910 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:06:05 esxserver vmkernel: 0:03:44:09.911 cpu1:1032)SCSI: 8021: vmhba0:0:2:1 status = 2/0 0xb 0x8 0x0

Aug 26 23:06:05 esxserver vmkernel: 0:03:44:09.911 cpu1:1032)SCSI: 8062: vmhba0:0:2:1 Retry (aborted cmd)

Aug 26 23:06:05 esxserver vmkernel: 0:03:44:09.911 cpu1:1032)WARNING: SCSI: 5615: status I/O error, rstatus 0xc0de04 for vmhba0:0:2. residual R 945, CR 80, ER 3

Aug 26 23:06:05 esxserver vmkernel: 0:03:44:09.911 cpu1:1032)WARNING: Vol3: 1478: Sataboy-Tera2/46d1dc8b-8f9d44b0-3643-00145e2b0932: Error initializing root directory: I/O error

Aug 26 23:06:05 esxserver vmkernel: 0:03:44:09.911 cpu1:1032)WARNING: Vol3: 1666: Error creating system files: I/O error

Aug 26 23:06:05 esxserver vmkernel: 0:03:44:09.911 cpu1:1032)FSS: 741: dev \[46d1dc73-c3298ebe-c37c-00145e2b] fs \[Sataboy-Tera2] type \[vmfs3] fbSize 1048576 => I/O error

And here is the "esxcfg-mpath -l":

Disk vmhba0:0:0 /dev/sda (476837MB) has 1 paths and policy of Fixed

FC 4:4.0 210000e08b87d14b<->5000402001f416d8 vmhba0:0:0 On active preferred

Disk vmhba0:0:1 /dev/sdb (953674MB) has 1 paths and policy of Fixed

FC 4:4.0 210000e08b87d14b<->5000402001f416d8 vmhba0:0:1 On active preferred

Disk vmhba0:0:2 /dev/sdc (953865MB) has 1 paths and policy of Fixed

FC 4:4.0 210000e08b87d14b<->5000402001f416d8 vmhba0:0:2 On active preferred

Disk vmhba0:1:0 /dev/sdd (476837MB) has 1 paths and policy of Fixed

FC 4:4.0 210000e08b87d14b<->5000402301f416d8 vmhba0:1:0 On active preferred

Disk vmhba1:0:0 /dev/sde (140012MB) has 1 paths and policy of Fixed

Local 8:14.0 vmhba1:0:0 On active preferred

Disk vmhba1:1:0 /dev/sdf (140013MB) has 1 paths and policy of Fixed

Local 8:14.0 vmhba1:1:0 On active preferred

Processor Device vmhba1:15:0 (0MB) has 1 paths and policy of Fixed

Local 8:14.0 vmhba1:15:0 On active preferred

0 Kudos
12 Replies
salii
Contributor
Contributor
‎08-26-2007 01:51 PM

Se on ihan paska se...

0 Kudos
christianZ
Champion
Champion
‎08-27-2007 04:34 AM

Have you only one Esx host?

Are you sure that "fixed" is right for your storage?

Have you this problem only with vmhba0:0:2

Janne07
Contributor
Contributor
‎08-27-2007 04:40 AM

No, I'm not sure. We have about 12 ESX Servers using that SAN storage.

0 Kudos
acr
Champion
Champion
‎08-27-2007 04:43 AM

Tried to find out if this should be fixed (lots of entry level SANs are mru)..

But i dont see this SAN on the HCL..?

http://www.vmware.com/pdf/vi3_san_guide.pdf

0 Kudos
Janne07
Contributor
Contributor
‎08-27-2007 04:47 AM

I didn't eather.

The problem is that this storage has been installed before I had anything to say. We have a IBM DS storage waiting for installation. This storage has worked fine for over half year.

We need to get this online to migrate virtualmachines to the new storage.

0 Kudos
acr
Champion
Champion
‎08-27-2007 04:51 AM

They often do, its when issues arise when things become difficult, actually im suprised Nexsan isnt on the HCL, they've been arround long enough..

The IBM DS is and its mru..

0 Kudos
christianZ
Champion
Champion
‎08-27-2007 04:58 AM

Maybe the first try should be to check whether only vmhba002 (the mapped lun) makes problems or not.

0 Kudos
Janne07
Contributor
Contributor
‎08-27-2007 05:06 AM

Well, I think it goes like this:

vmhba0:0:1,

vmhba0:0:2,

vmhba0:0:3

are jumping online / offline.

vmhba0:1:0 is stable.

And these are all in tha same storage, different controller.

0 Kudos
christianZ
Champion
Champion
‎08-27-2007 06:20 AM

Important for san storage - each lun shoud be presented for each esx host with the same lun id.

Is that configured this way by you?

0 Kudos
tbrown
Contributor
Contributor
‎08-27-2007 04:14 PM

Janne,

Sorry to be bearer of bad news but those SATABOYs are junk... I've seen the exact same this and I can tell you why.

That system storage system runs its iSCSI services in a VM through Microsoft Virtual Server (I have asked the rep and he has told me M$ forbids the to get VMware approved because they run on Virtual server on their product) The SATABOY Iscsi Services crash the watchdog restarts them and in the mean time you've lost your stoarge until you rescan.

Nexsan triend to give one to my company we dismissed it as junk and returned it to them.

The SATABeast is a even worse POS and will eat your data if anyone is curious to why it can be answered via PM or @ VMworld Smiley Happy

0 Kudos
christianZ
Champion
Champion
‎08-27-2007 11:20 PM

When you really have an iscsi box then I think your chance to get it working is bad.

Have your storage redundand controllers?

0 Kudos
jallen1
Contributor
Contributor
‎08-28-2007 06:38 AM

You must have a vendor axe to grind. We've had 3 SATABeasts from Nexsan connected to our ESX servers for over a year and have never had a problem. We never worried about the HCL either - any vendir with the $$ to pay for it can get registered - no biggie. We'll be moving them to a SAN here shortly which will give greater flexibility for adding storage in the future.

0 Kudos