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
 
Sun Storage 5310 NAS Gateway System
 

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

To check the NAS system log, connect to the Web Admin and navigate to Monitoring and Notification / View System Events / Display System Log. After a few seconds, the system log will appear.

The log should be checked as quickly as possible after the attempt to access the share, so that the messages from the attempt are easy to find. In the web admin, the most recent messages are found at the top of the screen. The following are messages that could indicate a problem:

token[DOMAIN\User]: CANT_ACCESS_DOMAIN_INFO

This message indicates that the NAS has lost contact with the Domain Controller, and can no longer authenticate. In this case, it will be necessary to re-enter user credentials to re-join the domain. See <Document: 1008222.1>  for details on this process. If unsuccessful in re-joining the domain, see <Document: 1009917.1> . 

user: Access Granted to /share (but still can't access)

The "access granted" message comes from the fact that the security for shares comes from the underlying directory. The NAS supports credentials only on files and directories. If you cannot access a share after this message, the problem is directory security. Check and/or grant the pemissions from a Windows client using an Admin account. The NAS CLI cacls utility can also be used to view security settings. See <Document: 1008222.1> for details.

mlrpc[0x0F]: error: NO_TRUST_SAM_ACCOUNT (0xC000018B)

This message indicates that a user from outside the Domain cannot access the NAS due to a broken or non-existent trust releationship. Trusts are configured on CIFS Domain Controllers from both to allow inter-domain sharing of resources. If this occurs, the trust relationship must be re-established or created between domains. Also, verify that the remote domain controller is available, because a temporary outage can show similar symptoms.

NOTE: Other Windows servers may continue to allow access for some time due to longer caching of user token information. In this case, the problem may appear to affect only the NAS, but the cause and solution remain as documented above..

Share Database Corrupt

This message indicates a problem with the database that contains the CIFS/SMB shares. Typically this can be fixed by repairing the database. The database consists of two files per volume: .shares.db and .shares.idx. Do not use the dbck command unless the above message is logged, unless under the explicit instruction of a Sun Engineer.

To Repair the Database:

(NOTE: For OS versions prior to 4.21, it will be necessary to enter "admin" at the [menu] prompt before the second step)

• Open a telnet or ssh connection to the NAS
• Type the administrator password
• At the CLI, enter load dbck
• Enter dbck /<volumename>/.shares.
  The following is displayed:
  *** Checking /vol1/.shares
  Should repairs be needed, do you want them made?
• Select option N, for No. This allows the database to be checked read-only.
• If errors are reported, run dbck again as above, this time selecting option Y to perform the repairs.

This solution has no attachment