Refresh in Disk Management causes coraiddisk connection fail
Posted: Mon Oct 06, 2008 4:04 am
Hardware Details:
SR1521
firmware: SR20080915
VS21
firmware: VS20080801
Installed StarPort 3.6 on Microsoft Windows Server 2003 Standard Edition Service Pack 2.
- Launch StarPort and click on Add Device
- Device Type: Remote AoE (ATA-over-Ethernet) device
- Choose the correct nic, Set LSO Off, Jumbo 4500
- Choose the correct lun
- The disk appeared in Computer Management > Storage > Disk Management.
- Initialise the disk and create a partition then format it
- If the disk is in idle (no process accessing the disk), then refresh (press F5) in Disk Management will show the disk need to be initialised and it is not accessible.
- Status of the disk changed from Connected to Failed in StarPort control panel.
- It doesn't not recover from status failed to connected even though "Automount the device" option is chosen
- In the event viewer, System log will have EventID 15 shown.
- Either "Force Remove Device" and read the disk or reboot the machine seems to fix the issue.
Is there something that I configured wrongly or there is a known bug?
SR1521
firmware: SR20080915
VS21
firmware: VS20080801
Installed StarPort 3.6 on Microsoft Windows Server 2003 Standard Edition Service Pack 2.
- Launch StarPort and click on Add Device
- Device Type: Remote AoE (ATA-over-Ethernet) device
- Choose the correct nic, Set LSO Off, Jumbo 4500
- Choose the correct lun
- The disk appeared in Computer Management > Storage > Disk Management.
- Initialise the disk and create a partition then format it
- If the disk is in idle (no process accessing the disk), then refresh (press F5) in Disk Management will show the disk need to be initialised and it is not accessible.
- Status of the disk changed from Connected to Failed in StarPort control panel.
- It doesn't not recover from status failed to connected even though "Automount the device" option is chosen
- In the event viewer, System log will have EventID 15 shown.
- Either "Force Remove Device" and read the disk or reboot the machine seems to fix the issue.
Is there something that I configured wrongly or there is a known bug?