Before making this diagnosis, it is very important to ensure that you are checking the bootlog containing the first unsuccessful mount attempt. Regardless of what the original problem is, the second attempt and all subsequent unsuccessful attempts to mount the volume will always log the “previous mount did not complete” message.

If you are 100% certain that the problem is an interrupted mount attempt, you should be able to correct the problem by entering “mount –f <volumename>” at the CLI. Check the system log to ensure that the mount is successful, and that there are no errors.

The above issue is the most common reason for mount failure, and a relatively minor problem. However, please be aware that other mount problems can be much more severe. If the mount failure occurs for any reason other than the above, or if the above solution does not work, the issue must be escalated. Do not use the “mount – f” command in an attempt to resolve a mount problem other than the one listed above.

Information required for escalation: A diagnostic email with all attachments should be sufficient for escalation. Verify that the boot logs are included with the diagnostics, and that they contain the mount attempt. Also, if possible, include information on the circumstances surrounding the mount problem and any attempts to correct it. Find out whether remote access is available to the site, and if appropriate, provide the necessary details to accomplish this.

Can’t write to file system

This is caused by a problem found at mount time. The problem can vary in degree, and the causes for this vary widely. This problem manifests as a complete inability to write for all users, including root.

The following are the messages that you will see in this case

/vol1 mounted read-only due to errors, run check

/vol1 is complete

The message “run check” refers to the filesystem check, or “fsck”. The filesystem check is a time consuming process, which is potentially destructive to data. This being the case, data should now be collected for escalation. Involving the engineering group at this time may make it possible to circumvent the lengthy volume repair process.

A diagnostic email, with all attachments, is required to escalate this type of issue. The primary source of information for this case is the bootlog. Also, collect as much information as possible about the circumstances surrounding the failure, e.g. did the system lose power, what symptoms were seen by the clients, was any hardware or

Chapter 2 NAS Head 2-71

Page 116 Page 118
Page 117
Image 117
Sun Microsystems 5310 NAS manual Can’t write to file system
Page 116 Page 118

5310 NAS specifications

Sun Microsystems, known for its innovative computing solutions, launched the Sun 5310 Network Attached Storage (NAS) system, which marked a significant advancement in the realm of storage solutions in the early 2000s. The 5310 NAS was designed to provide high-performance, reliable, and scalable storage tailored for enterprise environments.

One of the standout features of the Sun 5310 NAS is its file-serving capabilities, which support multiple protocols, notably NFS (Network File System) and CIFS (Common Internet File System). This dual-protocol support allowed organizations to seamlessly integrate the NAS into diverse IT ecosystems, facilitating interoperability between UNIX, Linux, and Windows systems. The enhanced file-sharing capabilities made it an ideal solution for businesses with mixed operating environments.

The Sun 5310 NAS incorporates cutting-edge technologies to ensure high availability and data integrity. The system utilized a RAID (Redundant Array of Independent Disks) technology, providing various RAID levels to protect against data loss while optimizing performance. Additionally, the device featured hot-swappable drives, enabling maintenance and upgrades with minimal downtime, a crucial factor for business continuity.

Equipped with advanced management software, the Sun 5310 NAS offered users an intuitive interface for monitoring storage health and performance. This software included comprehensive reporting functionalities that allowed IT administrators to oversee usage patterns and capacity planning efficiently.

Scalability was another defining characteristic of the Sun 5310 NAS. The system could easily expand with additional storage modules, accommodating the growing needs of an organization without the necessity for complete system overhauls. This flexibility ensured that businesses could adapt their storage solutions to meet evolving data storage needs without incurring significant costs or disruptions.

In terms of performance, the Sun 5310 NAS featured high I/O throughput achieved through its robust hardware architecture and optimized file serving capabilities. This performance baseline was crucial for organizations that relied on heavy data workloads and required rapid access to information.

In summary, the Sun 5310 NAS from Sun Microsystems embodied a forward-thinking approach to network storage, blending reliability, scalability, and multi-protocol support. Its user-friendly management software, combined with the robustness of RAID technology and hot-swappable drives, made it a preferred choice for enterprises looking to streamline their storage infrastructure while safeguarding critical data.
Top Page Image Contents