No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

What are the Workarounds to the NFS Sharing Error Between the S5100 and the NAS Engine?

Publication Date:  2012-07-18 Views:  22 Downloads:  0
Issue Description
1. Networking: An S5100 is fully configured with three disk enclosures and ninety-six 750 GB hard disks. As for the storage configuration, each RAID group consists of 12 disks (namely, four RAID groups contain 11 disks, and the other four RAID groups contain 12 disks), each enclosure contains a hot spare disk, and each RAID group contains four LUNs of each approximately 2 TB. So, the maximum available capacity is 60,071,400 GB. (Two fully-configured S5100 storage devices are connected to two NAS gateways.) 2. Configuration introduction The S5100 is mounted to the Windows 2003 server, which does not support dynamic disks but only support a maximum of 26 drive letters ranging from A to Z on a single computer. Given the customer intends to mount all the 32 LUNs to the server, the LUNs that cannot be assigned drive letters are mounted by the NTFS instead (Mounting drives by NTFS is an easy way for mounting additional volumes that cannot be assigned driver letters.) 3. Failure symptom Error messages occur during the attempt of enabling the NFS sharing for the NTFS-mounted disk partitions through NAS folders. Alarm information: see attachment.
Alarm Information
None
Handling Process
1. Procedure (1) Create cross-partition volumes using dynamic disks to ensure that the number of resulted disks is no greater than 26. By doing this, each disk can be assigned a driver letter. (2) Activate dynamic disks with relevant scripts. (3) Start the nfs service after the dynamic disks are activated. 2. Configuration (1) Choose My Computer > Management > Services, and then change the startup mode of the server for NFS service to Manual. (2) Create a .txt file called online.txt in the root directory of the C drive with the following content: select disk 21 online exit where 21 stands for the ID of the starting dynamic disk. Create a batch file called invokeDisk.bat under c:\windows\system32\ with the following content. @echo off echo ==============Now invoke the dynamic disk!================ diskpart -s c:\online.txt echo ==============Complete invoke the dynamic disk!================ echo ==============Now start the NFS service!================ NET START "Server for NFS" echo ==============Complete start the NFS service!================ (3) Choose Start > Run, and type regedit to open the registry editor. And then, navigate to \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run and right-click the empty area to create a string value. Value Name: InvokeDisk Value data: c:\windows\system32\invokeDisk.bat
Root Cause
NAS systems in Windows 2003 only support enabling the NFS sharing for disk partitions that are assigned drive letters.
Suggestions
None

END