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>Search


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


Why Homedir share inaccessible after Normal share is referred

Publication Date:  2012-09-18 Views:  76 Downloads:  0
Issue Description
Software edition:V100R001SPC003
Client windows edition:Windows XP SP2
Customer N8000 system provide both Homedir and Normal share services. After access to Normal share and back to root directory, attempt to access to Homedir share would fail. There is only prompt of no authorization, instead of username/password prompt window. 
Alarm Information
Handling Process
This problem can be dodged by changing access sequence. Customer can refer to Homedir share first, and then both Homedir and Normal share are available for normal read-write of files.
1. Upgrade Windows system, and install SP3. More information on Windows XP upgrades introduction documentation.
2. Upgrade N8000 to V100R001SPC006 can avoid this bug. Exact process is in delivery-attached upgrade instructor for relative software edition.
Some fundamental upgrade steps:
(1) Log on N8000 as master with SSH:
N8000> cluster show
N8000> upgrade show
(2) check if the cluster status normal, check cluster NAS engine software edition:
(3) connect to cluster NAS engine master node through console administration port IP address with SSH tool, and upload upgrade packet to directory /home/support:
(4) input upgrade in DOS prompt to enter upgrade mode
(5) use the command of patch install to complete the process of upgrade。
N8000.Upgrade> patch install scp://support@
Enter password for user 'support': ********
(6) input y and enter button for the next step to continue the upgrade:
RP1 patch upgrade is divided into 2 stages: first upgrade the sub-nodes and wait for these sub-nodes reboot automatically; second is the upgrade of the master node. Both 2 stages run automatically on all nodes under master administration mode. Never reboot nodes manually during upgrade, or the upgrade process will fail.
(7) 1st stage:
prompt below appear after 1st stage of upgrade, and all sub-nodes reboot automatically.
Patch applied on N8000_02, but it is not part of the cluster. N8000 cluster is running on rest of the nodes. All the nodes in the cluster will now be brought down and then N8000_02 will be rebooted. N8000 services will not be available untill N8000_02 comes up functioning with new patch. Patch installation on rest of the cluster will be started when N8000_02 comes up. You need to reconnect to console after N8000_02 boots up.
Original SSH connection interrupt
(8) 2nd stage of upgrade:
2nd stage start after all sub-nodes reboot successfully, we can log on cluster NAS engine again to observe upgrade progress.
All the nodes left would reboot automatically to complete the whole upgrade progress.
(9) use the following commands check edition and status of upgraded cluster NAS node:
N8000> upgrade show
N8000> cluster show
N8000> cifs server status                                                         
N8000> nfs server status

Root Cause
Some system bugs exist in Windows XP SP2 edition. If access to Normal share and back to root directory, information recorded in system will prevent user access to Homedir share.
As many batch customers access to NAS share services, it is inconvenient for unified installation of SP3 patch packet. So it is recommended that upgrade N8000 edition.