Sun StorageTek[TM] 5000 Series NAS arrays: Filesystem not mounted, previous mount did not complete

Asset ID:	1-71-1008158.1
Update Date:	2011-05-11
Keywords:

Solution Type Technical Instruction Sure

Solution 1008158.1 : Sun StorageTek[TM] 5000 Series NAS arrays: Filesystem not mounted, previous mount did not complete

Related Items


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

Related Categories


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

PreviouslyPublishedAs
211212

Description
Array experienced a power loss or crash during the mount operation. The filesystem does not appear in diagnostic email and is inaccessible via NFS/CIFS, underlying raid volume remains up and active.

Steps to Follow
The most common reason for the mount failure is a power loss or crash during the mount process. This causes a "mount failure" flag to be set on the volume. When the Sun StorEdge[TM] 5x10 NAS Appliance encounters this flag upon boot, it does not mount the volume, and logs the following message:

<Date> <Time> I sfs2: /volume - id=4D9721D3, extent 1 of 3, version 2
<Date> <Time> I sfs2: /volume - id=4D9721D3, extent 2 of 3, version 2
<Date> <Time> I sfs2: /volume - id=4D9721D3, extent 3 of 3, version 2
<Date> <Time> I /[2] fruitless bitmap 168 bytes
<Date> <Time> I /[1] fruitless bitmap 252 bytes
<Date> <Time> I /volume[0] fruitless bitmap 252 bytes
<Date> <Time> A /volume not mounted, previous mount did not complete. <----
<Date> <Time> A dpmgr: Error sfs2-mount isp1d020,3

In some cases, the bootlogs may not contain the original failure because too much time had passed. All subsequent unsuccessful attempts to mount the volume will log the same error message "previous mount did not complete".

The LunPath Information should show that the device is up and active.

Dasdid 600 isp1d020 has 2 paths, Owner Real 1 Current 1
P1: isp1d020 status(3) UP ACTIVE
P2: isp3d000 status(1) UP

If it is 100 percent certainty that the problem is an interrupted mount attempt, the filesystem will need to be force mounted and fsck'd. fsck can only run if the filesystem is mounted.

CLI command "mount -f /volume"

Check the log again to confirm that the filesystem mounted, and run fsck.

Product
Sun StorageTek 5210 NAS Appliance
Sun StorageTek 5310 NAS Gateway/Cluster System
Sun StorageTek 5310 NAS Gateway System
Sun StorageTek 5310 NAS Appliance
Sun StorageTek 5320 NAS Gateway/Cluster System
Sun StorageTek 5320 NAS Appliance
Sun StorageTek 5220 NAS Appliance

Internal Comments
This document contains normalized content and is managed by the the Domain Lead(s) of the respective domains. To notify content owners of a knowledge gap contained in this document, and/or prior to updating this document, please contact the domain engineers that are managing this document via the “Document Feedback” alias(es) listed below:

storage-nas-domain@sun.com

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

For more information about the fsck process on the NAS array: <Document: 1006816.1> Performing and understanding the fsck procedure on the
SunStorageTek[TM] 5000 Series NAS arrays to recover from a filesystem
crash

Information regarding this process is pulled directly from: http://pts-storage.west/products/SE5210/documents/SE5310_tsg_rev6.pdf

2.14 File System Issues

2.7.1 Filesystem Check (fsck) Procedure

5310, 5x10, 5210, 5220, 5320, 5320C, 5310C, fsck file system, nas, cifs, nfs, audi, mount, mounted, sfs2, audited
Previously Published As
85455

Change History
Publishing Information
Date: 2007-10-02
User Name: 7058
Action: Approved
Comment: OK to publish.
Version: 6

Attachments

This solution has no attachment