Unsolved
This post is more than 5 years old
20 Posts
0
348483
May 29th, 2008 14:00
Problem with MD3000i and W2K8 Std x64 using iSCSI MPIO
Hardware: Dell PowerEdge 2900, Dell PowerConnect 5424, Dell PowerVault MD3000i
OS: Windows 2008 Server Standard 64 bit
Short description of problem: Multipath MPIO properties fail on iscsi connected MD3000i disk on PE2900 sever with windows 2008 64 bit
Detailed description:
When installing and connecting the iscsi LUN in windows 2008 following the resource CD documentation everything looks fine. I am able to create partitions, robocopy files to the MD box etc.
But if I check properties and the MPIO page on the LUN in diskmanager I get an empty error message, and after it a 4th path that is failed is added to the path list.
When checking the windows eventlog there are many iscsi related errors (see below).
I also upgraded firmware on all hardware and then removed and re-connected/configured the iscsi initator, virtual disks, etc but still get the same problem.
I have verified the iSCSI LAN, pinged all ports on the MD boxes from the server and everything looks correct there so it seems unlikely that the server should have a problem connecting to the box.
Any idea what the problem could be?
Eventlog errors:
Log Name: SystemSource: iScsiPrtDate: 26.05.2008 20:09:45Event ID: 1Task Category: NoneLevel: ErrorKeywords: ClassicUser: N/AComputer: file0108Description:Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data.
Log Name: SystemSource: Virtual Disk ServiceDate: 28.05.2008 17:45:00Event ID: 1Task Category: NoneLevel: ErrorKeywords: ClassicUser: N/AComputer: file0108Description:Unexpected failure. Error code: 48F@02000018
Log Name: SystemSource: iScsiPrtDate: 26.05.2008 20:10:17Event ID: 7Task Category: NoneLevel: ErrorKeywords: ClassicUser: N/AComputer: file0108Description:The initiator could not send an iSCSI PDU. Error status is given in the dump data.
Log Name: SystemSource: diskDate: 28.05.2008 17:45:00Event ID: 15Task Category: NoneLevel: ErrorKeywords: ClassicUser: N/AComputer: file0108Description:The device, \Device\Harddisk13\DR13, is not ready for access yet.
Log Name: SystemSource: mpioDate: 28.05.2008 17:44:40Event ID: 16Task Category: NoneLevel: ErrorKeywords: ClassicUser: N/AComputer: file0108Description:A fail-over on \Device\MPIODisk9 occurred.
Log Name: SystemSource: iScsiPrtDate: 28.05.2008 11:22:51Event ID: 20Task Category: NoneLevel: ErrorKeywords: ClassicUser: N/AComputer: file0108Description:Connection to the target was lost. The initiator will attempt to retry the connection.
dzenz
175 Posts
0
May 29th, 2008 22:00
Can you check and report on the values of both LinkDownTime and TimeOutValue in the registry? Please make sure the values are from the CurrentControlSet.
Dave
Snorway
20 Posts
0
May 30th, 2008 13:00
I found these values:
HKLM\System\CurrentControlSet\Services\Disk
TimeOutvalue REG_DWORD a0 (160)
HKLM\System\CurrentControlSet\Class\{4D36E97B-11CE-BFC1-08002BE10318}\0000\Parameters
LinkDownTime REG_DWORD 90 (144)
I think they were set by the script from the resource cd : iSCSI_req_changer_win2K8
I don't experience any problem with file i/o to the boxes (using Robocopy and HDTach) so I suspect some paths are working and some are not, well I dont trust that multi pathing and failover works with all these errors in the log but I have not tested filecopying while removing one cable from the path yet.
Thanks for any help,
SB
pablito.arias
8 Posts
0
June 2nd, 2008 13:00
SB,
I am assuming you did not check the MS MPIO install option during iSCSI initiator install. The installation CD installs its own version of the failover driver. Also, I am assuming that you independently configured 4 paths to the array. Can you please confirm?
Thanks
Pablo
pablito.arias
8 Posts
0
June 2nd, 2008 16:00
SB,
The messages in the event log might be related to the fact the MS initiator does not randomize the TCP ports every time it boots, it uses the same port. If the reboot happens fast enough, the MD3000i does not have time to timeout the connections and close them. When the server boots and tries to open a connection the MD3000i reject them and that causes the errors in the event log. The initiator then will retry and connect without problem.
I hope this helps to explain the messages you are seeing.
Pablo
Snorway
20 Posts
0
June 2nd, 2008 16:00
iSCSI initiator is already installed by default on Windows 2008 so I did not install that. I did not add the MPIO from the Add Features in windows, it was installed by the MDSM installation wizard.
I did configure all 4 logins at the same time. But I got errors in eventlog at boot time about not finding target and errors in hard disk properties on MPIO page - seems like this is related to only one path maybe.
I found out I had gateway ip configured on the MD3000i iscsi ports even though this is an isolated network with no router so i changed those to 0.0.0.0 (not possible to put blank). Usually this should not have any effect since there is no reason to do route hopping but we will see....
Now I'm reinstalling the OS with the Dell Build dvd and I'm going to try to only connect 1 login / 1 path at first then see if I still get iscsi initator errors in the eventlog at booting time. Then I will add more paths/logins to see if there is one specific path creating the problem. I will also try to use the integrated broadcom NIC this time for the first path instead of the extra Intel server card in case there is an issue there.
Hopefully it will work better this time or maybe I have to give up 64 bit and/or w2k8 for now - maybe the software works better on w2k3? I have also registered a track with Dell support so maybe they have some good ideas too later on :)
Thanks for any ideas :)
SB
Snorway
20 Posts
0
June 2nd, 2008 17:00
Interresting that might explain while file copying never stopped working to the SAN/MD 3000 box.
Will post eventlogs from my 3rd attempt later :)
Snorway
20 Posts
0
June 2nd, 2008 18:00
Ok now I have reinstalled the whole OS and the MDSM software. I have configured one path from the server to the SAN in MS ISCSI Initiator. I have not made any host mapping or virtual disk assign from the SAN yet.
At boot the following SAN/iscsi related events are recorded:
Following events related to SAN:
Log Name: Application
Source: SMagent
Date: 02.06.2008 21:21:04
Event ID: 1
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: File0108
Description:
Message from SM agent service: SMagent: PowerVault Modular Disk Storage Manager Agent, Version 10.00.36.02
Built Tue Nov 06 14:13:33 CST 2007
Copyright 2005-2007 Dell Inc. All rights reserved. Use is subject to license terms
Checking device \\.\PHYSICALDRIVE0 : Skipping
Checking device \\.\PHYSICALDRIVE1 : Skipping
Log Name: Application
Source: SMagent
Date: 02.06.2008 21:21:04
Event ID: 1
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: File0108
Description:
Message from SM agent service: SMagent: The SMagent service attempted to start but terminated. Possible causes include: [1] The access virtual disk is disabled in NVSRAM. [2] No RAID controller modules with compatible firmware were found. [3] The default logical unit number (LUN) assigned to the access virtual disk (typically 7 or 31) is not in the range supported by the host or is already in use by the host for another device. See your storage management documentation for more details.
The Host Context Agent did NOT start because 0 RAID controller modules were found.
Log Name: Application
Source: SMagent
Date: 02.06.2008 21:21:04
Event ID: 1
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: File0108
Description:
Message from SM agent service: SMagent: The SMagent service attempted to start but terminated. Possible causes include: [1] The access virtual disk is disabled in NVSRAM. [2] No RAID controller modules with compatible firmware were found. [3] The default logical unit number (LUN) assigned to the access virtual disk (typically 7 or 31) is not in the range supported by the host or is already in use by the host for another device. See your storage management documentation for more details.
The Host Context Agent did NOT start because 0 RAID controller modules were found.
Log Name: Application
Source: SMmonitor
Date: 02.06.2008 21:21:04
Event ID: 0
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: File0108
Description:
Message from SM monitoring service: SMmonitor: Event Monitor started.
Log Name: System
Source: iScsiPrt
Date: 02.06.2008 21:20:32
Event ID: 5
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: File0108
Description:
Failed to setup initiator portal. Error status is given in the dump data.
Data: \Device\RaidPort5
Binary: 000004000100000000000000050000C0000000000000000000000000000000000000000000000000070200C0
Log Name: System
Source: iScsiPrt
Date: 02.06.2008 21:21:03
Event ID: 1
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: File0108
Description:
Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data.
Data: \Device\RaidPort5
Binary: 000006000100000000000000010000C0000000000000000000000000000000000000000000000000BC0CAC1CB297
If these are not a problem its strange that they are listed as errors and not warnings?
Next I'm going to do host mapping and assign a virtual disk to see if I get the same MPIO properties error as before with only one path.
Then I will add more paths.
pablito.arias
8 Posts
0
June 2nd, 2008 19:00
SB,
They are reported as errors because from MS point of view it is an error, because the TCP connection establishment failed, but when I said there is not a problem I meant that MS will retry and establish the connection. The only annoyance here are the messages in the event log
Let me know the outcome of the rest
Thanks,
Pablo
Snorway
20 Posts
0
June 3rd, 2008 14:00
I have now created a virtual disk and mapped to the file server.
After mapping the disk I get the following eventlog warnings:
Log Name: System
Source: md3dsm
Date: 03.06.2008 16:35:47
Event ID: 10
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: File0108
Description:
NorSan04:1 Failover command issued.
Log Name: System
Source: md3dsm
Date: 03.06.2008 16:35:50
Event ID: 801
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: File0108
Description:
Failover succeeded to NorSan04:1.
For some reason there is a failover done it seems. Since there is only one cable/one port from the server I guess the failover must be a change of controller on the MD box?
I then restarted the server, there are no errors from the SMagent this time (application log), however I still get the iScsiPrt error (system log) – but I notice that the iScsiPrt error happens before the eventlog say that the network activity is started on that network interface card. This might be why the error happens, the iscsi service is trying to connect before the network driver is ready? However the 2nd iscsiPrt error is 2 seconds after the network is up and running it seems. The 3rd error is 27 seconds after the network is supposed to be ready. However 30-60 seconds later MPIO says disk is ok so maybe this is just a timing issue after all?
Log Name: Application
Source: SMmonitor
Date: 03.06.2008 16:46:33
Event ID: 0
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: File0108
Description:
Message from SM monitoring service: SMmonitor: Event Monitor started.
Log Name: Application
Source: SMagent
Date: 03.06.2008 16:46:34
Event ID: 1
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: File0108
Description:
Message from SM agent service: SMagent: PowerVault Modular Disk Storage Manager Agent, Version 10.00.36.02
Built Tue Nov 06 14:13:33 CST 2007
Copyright 2005-2007 Dell Inc. All rights reserved. Use is subject to license terms
Checking device \\.\PHYSICALDRIVE0 : Skipping
Checking device \\.\PHYSICALDRIVE1 : Skipping
Checking device \\.\PHYSICALDRIVE2 : Skipping
Checking device \\.\SYMsmUTMLun0 : Activating
Log Name: Application
Source: SMagent
Date: 03.06.2008 16:46:34
Event ID: 1
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: File0108
Description:
Message from SM agent service: SMagent: Running...
Log Name: System
Source: iScsiPrt
Date: 03.06.2008 16:45:32
Event ID: 5
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: File0108
Description:
Failed to setup initiator portal. Error status is given in the dump data.
Log Name: System
Source: Tcpip
Date: 03.06.2008 16:45:32
Event ID: 4201
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: File0108
Description:
The system detected that network adapter iSCSI Green Subnet 172-28-179 was connected to the network, and has initiated normal operation.
Log Name: System
Source: iScsiPrt
Date: 03.06.2008 16:45:35
Event ID: 5
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: File0108
Description:
Failed to setup initiator portal. Error status is given in the dump data.
Log Name: System
Source: iScsiPrt
Date: 03.06.2008 16:46:00
Event ID: 1
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: File0108
Description:
Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data.
Log Name: System
Source: mpio
Date: 03.06.2008 16:46:05
Event ID: 1
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: File0108
Description:
\Device\MPIODisk0 created.
Log Name: System
Source: Service Control Manager
Date: 03.06.2008 16:46:32
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: File0108
Description:
The Microsoft iSCSI Initiator Service service entered the running state.
Log Name: System
Source: Service Control Manager
Date: 03.06.2008 16:46:33
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: File0108
Description:
The Modular Disk Storage Manager Event Monitor service entered the running state.
Log Name: System
Source: Service Control Manager
Date: 03.06.2008 16:46:34
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: File0108
Description:
The Modular Disk Storage Manager Agent service entered the running state.
Checking Server Disk Management, everything looks okay (no MPIO error like before), only one path listed as for now I have not added more. Notice that the load balance policy is display now – before when I had the MPIO error it was blank.
pablito.arias
8 Posts
0
June 3rd, 2008 15:00
SB,
About the failover, your assumption is right. The failover command might be issued because the Virtual Disk is mapped to a different controller from the one where you have the single connection. It is also possible that some of the errors are timing related.
Pablo
Snorway
20 Posts
0
June 4th, 2008 11:00
After restart the following shows up in the eventlog:
Log Name: Application
Source: SMmonitor
Date: 04.06.2008 13:58:13
Event ID: 0
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: NorFile0108
Description:
Message from SM monitoring service: SMmonitor: Event Monitor started.
Log Name: Application
Source: SMagent
Date: 04.06.2008 13:58:15
Event ID: 1
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: NorFile0108
Description:
Message from SM agent service: SMagent: PowerVault Modular Disk Storage Manager Agent, Version 10.00.36.02
Built Tue Nov 06 14:13:33 CST 2007
Copyright 2005-2007 Dell Inc. All rights reserved. Use is subject to license terms
Checking device \\.\PHYSICALDRIVE0 : Skipping
Checking device \\.\PHYSICALDRIVE1 : Skipping
Checking device \\.\PHYSICALDRIVE2 : Skipping
Checking device \\.\SYMsmUTMLun0 : Activating
Checking device \\.\SYMsmUTMLun1 : Activating
Checking device \\.\SYMsmUTMLun2 : Activating
Checking device \\.\SYMsmUTMLun3 : Activating
Log Name: Application
Source: SMagent
Date: 04.06.2008 13:58:15
Event ID: 1
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: NorFile0108
Description:
Message from SM agent service: SMagent: Running...
Log Name: System
Source: iScsiPrt
Date: 04.06.2008 13:57:39
Event ID: 5
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: NorFile0108
Description:
Failed to setup initiator portal. Error status is given in the dump data.
Log Name: System
Source: iScsiPrt
Date: 04.06.2008 13:57:42
Event ID: 5
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: NorFile0108
Description:
Failed to setup initiator portal. Error status is given in the dump data.
Log Name: System
Source: iScsiPrt
Date: 04.06.2008 13:58:06
Event ID: 1
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: NorFile0108
Description:
Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data.
Log Name: System
Source: iScsiPrt
Date: 04.06.2008 13:58:06
Event ID: 1
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: NorFile0108
Description:
Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data.
Log Name: System
Source: iScsiPrt
Date: 04.06.2008 13:58:06
Event ID: 1
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: NorFile0108
Description:
Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data.
Log Name: System
Source: iScsiPrt
Date: 04.06.2008 13:58:06
Event ID: 1
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: NorFile0108
Description:
Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data.
Log Name: System
Source: mpio
Date: 04.06.2008 13:58:11
Event ID: 1
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: NorFile0108
Description:
\Device\MPIODisk0 created.
Log Name: System
Source: mpio
Date: 04.06.2008 13:58:11
Event ID: 2
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: NorFile0108
Description:
Added device to \Device\MPIODisk0. DumpData contains the current number of paths.
Log Name: System
Source: mpio
Date: 04.06.2008 13:58:11
Event ID: 2
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: NorFile0108
Description:
Added device to \Device\MPIODisk0. DumpData contains the current number of paths.
Log Name: System
Source: mpio
Date: 04.06.2008 13:58:11
Event ID: 2
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: NorFile0108
Description:
Added device to \Device\MPIODisk0. DumpData contains the current number of paths.
Log Name: System
Source: Service Control Manager
Date: 04.06.2008 13:58:27
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: NorFile0108
Description:
The Microsoft iSCSI Initiator Service service entered the running state.
Log Name: System
Source: Service Control Manager
Date: 04.06.2008 13:58:27
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: NorFile0108
Description:
The Modular Disk Storage Manager Event Monitor service entered the running state.
Log Name: System
Source: Service Control Manager
Date: 04.06.2008 13:58:27
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: NorFile0108
Description:
The Modular Disk Storage Manager Agent service entered the running state.
Snorway
20 Posts
0
June 4th, 2008 11:00
One thing I am not sure about is the configuration of the “MS iSCSI Initiator” discovery on the windows server connecting to the MD box.
Following the Dell MD3000 manual it seems that you first create only one connection in the “Discovery Tab – Portal Targets” then later you create 4 logins in the “Targets” tab for the 4 paths to the MD box (4 iscsi ports).
When I first installed I made the logic assumption that you should also have 4 “portal targets” in the discovery tab but this is not how the procedure in the manual looks so this time I only added one. I figured that was maybe why I got the MPIO/load balancing policy error the first time. But then I noticed this posting in the vmware forum where somebody else is saying you should have 4 discovery portal targets:
http://communities.vmware.com/thread/149711?tstart=0
“Yes. All paths have to be seen, and in iSCSI, you register them in the discovery tab.”
What is the correct configuration?
4 discovery portal targets and 4 logon in the target page or just 1 discovery portal target and 4 logins on the target page?
Well I have tried both options now and I get the MPIO hard disk property page path error no matter what I do... :(
Snorway
20 Posts
0
June 4th, 2008 11:00
I added 3 more logins to the iscsi initiator to get all paths up and running:
Source - Target - Status - Type - Weight - Connection - ID
172.28.178.81/1728 - 172.28.178.151/3260 - Connected - (This one was already connected yesterday) - Active n/a - 0x0
172.28.178.81/1728 - 172.28.178.141/3260 - Connected - Active - n/a - 0x3
172.28.179.80/1728 - 172.28.179.140/3260 - Connected - Active - n/a - 0x4
172.28.179.80/1728 - 172.28.179.150/3260 - Connected - Active - n/a - 0x5
Note: Why are connections labeled 0,3,4,5 – what happened to 1 and 2? All have “round robin” listed.
The following events are registered:
Log Name: System
Source: mpio
Date: 04.06.2008 13:35:07
Event ID: 2
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: NorFile0108
Description:
Added device to \Device\MPIODisk0. DumpData contains the current number of paths.
Log Name: System
Source: Microsoft-Windows-User-PnP
Date: 04.06.2008 13:35:07
Event ID: 20001
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: NorFile0108
Description:
Driver Management concluded the process to install driver FileRepository\disk.inf_4470f8b3\disk.inf for Device Instance ID SCSI\DISK&VEN_DELL&PROD_MD3000I\1&1C121344&0&000100 with the following status: 0.
Log Name: System
Source: Microsoft-Windows-User-PnP
Date: 04.06.2008 13:35:08
Event ID: 20003
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: NorFile0108
Description:
Driver Management has concluded the process to add Service disk for Device Instance ID
Log Name: System
Source: Microsoft-Windows-User-PnP
Date: 04.06.2008 13:35:08
Event ID: 20001
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: NorFile0108
Description:
Driver Management concluded the process to install driver FileRepository\disk.inf_4470f8b3\disk.inf for Device Instance ID SCSI\DISK&VEN_DELL&PROD_UNIVERSAL_XPORT\1&1C121344&0&00011F with the following status: 0.
Log Name: System
Source: Microsoft-Windows-User-PnP
Date: 04.06.2008 13:36:58
Event ID: 20003
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: NorFile0108
Description:
Driver Management has concluded the process to add Service disk for Device Instance ID SCSI\DISK&VEN_DELL&PROD_MD3000I\1&1C121344&0&000200 with the following status: 0.
Log Name: System
Source: mpio
Date: 04.06.2008 13:36:58
Event ID: 2
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: NorFile0108
Description:
Added device to \Device\MPIODisk0. DumpData contains the current number of paths.
Log Name: System
Source: Microsoft-Windows-User-PnP
Date: 04.06.2008 13:36:58
Event ID: 20001
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: NorFile0108
Description:
Driver Management concluded the process to install driver FileRepository\disk.inf_4470f8b3\disk.inf for Device Instance ID SCSI\DISK&VEN_DELL&PROD_MD3000I\1&1C121344&0&000200 with the following status: 0.
Log Name: System
Source: Microsoft-Windows-User-PnP
Date: 04.06.2008 13:36:59
Event ID: 20003
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: NorFile0108
Description:
Driver Management has concluded the process to add Service disk for Device Instance ID SCSI\DISK&VEN_DELL&PROD_UNIVERSAL_XPORT\1&1C121344&0&00021F with the following status: 0.
Log Name: System
Source: Microsoft-Windows-User-PnP
Date: 04.06.2008 13:36:59
Event ID: 20001
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: NorFile0108
Description:
Driver Management concluded the process to install driver FileRepository\disk.inf_4470f8b3\disk.inf for Device Instance ID SCSI\DISK&VEN_DELL&PROD_UNIVERSAL_XPORT\1&1C121344&0&00021F with the following status: 0.
Log Name: System
Source: Microsoft-Windows-User-PnP
Date: 04.06.2008 13:37:12
Event ID: 20003
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: NorFile0108
Description:
Driver Management has concluded the process to add Service disk for Device Instance ID SCSI\DISK&VEN_DELL&PROD_MD3000I\1&1C121344&0&000300 with the following status: 0.
Log Name: System
Source: mpio
Date: 04.06.2008 13:37:12
Event ID: 2
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: NorFile0108
Description:
Added device to \Device\MPIODisk0. DumpData contains the current number of paths.
Snorway
20 Posts
0
June 4th, 2008 11:00
But checking MPIO property page now on the harddisk the configuration does not look good:
Only 3 paths listed and “load balance policy” has gone blank now... same error as before....
Clicking OK brings back the infamous error message with no text
And going back to properties on Disk2 on the MD3000 we see a 4th path is now added as “failed”
paths:
path id - path state - tpg - tpg state - weight (weight empty on all paths)
ffff fa80 0f67 e770 - Standby - 65535 - unavailable
1 - active/optimized - 0 - active/unoptimized
1 - unavailable - 0 - active/optimized
1e85aaa0 - failed - 105 - unavailable
Snorway
20 Posts
0
June 4th, 2008 11:00
Disk performance measured in HDTach on the MD3000i virtual disk show an improvement from average read 51 mb/s to 61 mb/s with more paths added but I’m not sure if this is a permanent better speed or just other factors at this time - the burst speed seems to be about the same 80 vs 78 mb/s.
In comparison average speed is 220 mb/s and burst is 340 mb/s on the internal drives on raid 50.
Robocopy test:
Copying 3,3 gb file from c: to g:
(from local raid 50 with 8x300gb 15k sas to MD3000i partition on 6x400g 10k drives raid5)
takes 14 seconds – 14349 mb/min.
Compared to about 5 seconds copying from c: to c: at about 35 000 mb/min.
So in other word the disk on MD3000i over iscsi works but with lots of errors in the logs and I highly doubt that failover is solid - I guess I should test that next. It's also less than half the speed of the internal drives.