TABLE 2-16

POST Progress LED Code Table (Port 80h Codes) (Continued)

 

 

 

 

 

 

POST

 

Diagnostic LED Decoder

 

 

Code

(G = green, R = red, A = amber)

Description

ACh

A

 

G

R

Off

Prepare USB controllers for operating system.

AEh

A

 

G

A

Off

One beep to indicate end of POST. No beep if silent boot is

 

 

 

 

 

 

enabled.

000h

Off

 

Off

Off

Off

POST completed. Passing control to INT 19h boot loader next.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

2.7OS Operations

2.7.1Filesystem Check (fsck) Procedure

The first step in filesystem repair is to ensure that you have a complete, tested backup. The filesystem check carries some risk. Directories, files and filenames may be lost. A tested backup means that the data has been restored from tape, and checked for validity.

After the backup, the next step is to schedule the file system check. The volume that you are running the filesystem check against will be unavailable for the duration of the process. In addition, if this is the volume containing the /etc directory, all other volumes will be offline for the duration of the process. In any case, there will be a heavy load on the filesystem that will affect all clients. It is difficult to determine how long the process will take, as there are several variables which cause this time to vary, such as system specifications, size of volume, workload, and how many errors are found. The check should be run as soon as possible, as the filesystem problems can potentially worsen when writing to a damaged volume.

As a general rule, allow five hours for each run, more if a large number of errors are expected. Also note that if any errors are found, multiple runs are always required. Because of the time involved, consideration should be given to recreating the volume and restoring from a backup. This decision should be made based on the severity of the problem. A read-only filesystem check may be helpful in making this determination, but this may add several hours to the process.

Next, run the fsck procedure. This is done at the StorEdge CLI. It is strongly recommended to log the output of the filesystem check session for escalation purposes. Therefore, you should access the CLI with a client that is capable of logging, such as a LAN connected client or a serial console. Using a dial-up or WAN connected client is not recommended, as this can extend the run time of the procedure.

2-36Sun StorEdge 5310 NAS Troubleshooting Guide • December 2004

Page 81 Page 83
Page 82
Image 82
Sun Microsystems 5310 NAS manual OS Operations, Filesystem Check fsck Procedure
Page 81 Page 83

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