Sun Storage 5210 NAS Appliance
 
Sun Storage 5220 NAS Appliance
 
Sun Storage 5310 NAS Appliance
 
Sun Storage 5320 NAS Gateway/Cluster System
 
Sun Storage 5320 NAS Appliance
 

GCS>Sun Microsystems>Storage - Disk>Network Attached Storage
 

Check if any one of the following is applicable.

1. A volume can appear in brackets when seen from the telnet menu using the following option
D - Disks and Volumes

 Drive       Volume(s)                                     Available
A. ide1d1      /cvol /dvol                                        0B
B. isp2d020    /home                                         398.6GB
C.isp4d001    [vol1]                                         407.7GB

perform a force mount of this volume by doing a mount -f <volume name>
This should get the volume mounted.
The brackets will not be seen anymore

2. If the following can be seen via the telnet menu interface or the Web Admin GUI.
example:
SE5310a StorEdge 5310 NAS Disks & Volumes

 Drive       Volume(s)                                     Available
A. ide1d1      /cvol /dvol                                        0B
B. isp2d020    /home                                         398.6GB
C. isp4d001    /vol1                                         407.7GB
D. isp2d022    -- no partition table

Refer to document # <Document: 1009473.1>
This is not the only resolution for such a problem.
This problem has also been seen when an incorrect version of NVRAM is used,
Note the NVRAM version that was used to update the controllers and compare it with the NVRAM in the NAS OS version patch used.
If the above solution is not applicable,then contact Sun Support.

3. If there are iscsi luns and these luns are unavailable, then please refer to document # <Document: 1008016.1> This was due to bug 6442222 which was fixed in 4.20 B31.

4. It might be worthwhile to check the NVSRAM on the Raid controllers. One of the ways that this can be done is to use the lsi_menu available on the NAS telnet GUI
Use document # <Document: 1004239.1> to use the lsi_menu.

Collect the support data and check the file nram.txt that is collected.
( this will be only applicable for non-gateway systems)
Checking the file, if you see the following:

NVSRAM version = N399X-619843-004

NVSRAM Host Type Table

  NVSRAM HOST TYPE INDEX DEFINITIONS

  INDEX         AVT STATUS  TYPE
0 (Default)  Disabled    Solaris_MPxIO

then you can be sure that the NAS will definitely have a problem accessing the storage.
This indicates an incorrect NVSRAM in the controllers.

The correct NVSRAM should have the following setting:
NVSRAM version = N399X-619843-004

NVSRAM Host Type Table

  NVSRAM HOST TYPE INDEX DEFINITIONS

  INDEX         AVT STATUS  TYPE
0 (Default)  Enabled    Sun_SE5xxx

Contact Sun Support for help in upgrading the NVSRAM.

5. In a cluster system, check the status of the heads. In a normal functioning system, the heads should be Normal / Normal.
If not, then there will be no access to the volumes from the Quiet head.
Check document # <Document: 1004239.1> for understanding cluster head states.
You might want to refer to document # <Document: 1011415.1>  if the usual recovery procedures don't help.

6.If this is a cluster system, then currently there is a requirement for the cluster that requires the partner head to manually scan for new disks when the LUN ownerships were assigned by the other head

7. Again if this is a cluster system, and if NAS OS log is showing Unowned LUN. NAS OS disk CLI command is showing 0KB and CLI menu command option D. "Disk and Volumes" is showing disks with "-- no partition table".
Refer to document # <Document: 1004169.1> for recovery procedures.

8. Occasionally a NAS volume may not get mounted and is placed in a read-only.state

Typical messages are:

 02/11/05 15:23:13 E /vol1: mount error (-1): FS mounted read-only
02/11/05 15:23:13 E !/vol1: unable to create ACL database
02/11/05 15:23:13 E !/vol1: security DB initialization error
02/11/05 15:23:13 I /vol1 is complete
02/11/05 15:23:13 I sfs2_dtq_create: Could not create DTQ file, rc=5

Normally this happens when the NAS has detected some problem with the volume.
The first step in such cases is to run a filesystem check on this volume.
See Info Doc # <Document: 1006816.1>
There were also issues with the older firmware which contributed to this problem but most of these have been fixed.
If running multiple fscks does not help, then go the next step.

9. Finally if the above steps don't help, then collect the diagnostic data and nas extractor and contact Sun support. See Info Doc # <Document: 1005474.1>

To access documents internally, add "central" to the url http://sunsolve.sun.com to make it http://sunsolve.central.sun.com

The Knowledge Work Queue for this article is KNO-STO-NAS

This solution has no attachment