Scribd
Upload
25 views3 pages

ASSIGNMENT Trobleshooting HDD and RAID

The document provides steps to troubleshoot hard disk drive issues like overheating, sounds, ensuring connections are proper, and using an external enclosure. It also provides steps to troubleshoot RAID issues like verifying disk recognition, checking event logs, using management software, and detailed steps to address a broken RAID issue.

Uploaded by

Ndifon Erlich
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
25 views3 pages

ASSIGNMENT Trobleshooting HDD and RAID

The document provides steps to troubleshoot hard disk drive issues like overheating, sounds, ensuring connections are proper, and using an external enclosure. It also provides steps to troubleshoot RAID issues like verifying disk recognition, checking event logs, using management software, and detailed steps to address a broken RAID issue.

Uploaded by

Ndifon Erlich
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

DEPARTMENT: COMPUTER HARDWARE MAINTAINANCE

COURSE NAME: ASSEMBLY AND REPAIRS


Name: NYAME MEBUNE THIERRY
STEPS IN TROBLESHOOTING HARD DISK DRIVE (HDD)

1. READ/WRITE ERRORS occur only after the system has been running for a while particularly during
warm weather or if you have recently added a fast video card or other heat-producing component it's
possible that the drive is overheating. Remove the case access panel and use your finger as a
temperature probe. The hard drive should feel warm (perhaps quite warm) to the touch, but not so hot
that it's uncomfortable to press your finger against it for several seconds. If the drive is very hot, leave the
side panel off and point a standard house fan directly into the case to cool the drive. If the read/write
errors disappear, it's very likely that overheating is causing the problem. Install a hard drive cooler
(available from any online or brick-and-mortar computer store) and/or add supplemental cooling fans to
the case.

2. PAY ATTENTION TO THE SOUNDS THE DRIVE IS MAKING


If the drive makes clicking and grinding noises when it starts up, then shut your computer down
immediately. Those clicking and grinding noises indicate damage to the read/write heads of your drive,
and that is a mechanical.
If you turn your computer on and it makes a series of beeps, then turn it off and change the hard drive.

3. TURN OFF YOUR COMPUTER


The operating system on your computer is constantly scanning, accessing, and writing data to your hard
drive. When your hard drive starts to fail, your operating system could wind up interpreting bad sectors as
blank sectors and start writing to them. That means that your drive will sustain more damage and you will
lose more data by the second.

4. CHECK YOUR CONNECTIONS


Open up your computer and make sure that the power and data connection cables for your hard drive are
plugged in and working. Look at your cables and make sure that they are not frayed or damaged in some
way. It is always best to start with the obvious things first when you are trying to figure out how to recover
data from a damaged hard drive.

5. LOOK FOR YOUR DRIVE IN YOUR BIOS


When you first turn on your computer, a message will flash for a few seconds that will tell you what button
to push to access your computer’s BIOS. Press that button and then follow the on-screen instructions to
find your hard drive listing. If you want to learn how to recover a hard drive, it is important to first make
sure that the computer can see the drive.
If you see your hard drive listed in your BIOS, then you have a chance at being able to recover your drive
through your operating system. If your drive is not there, then turn the computer off and open the case.
On the back of your hard drive will be a power cable and a data cable. Make sure they are both plugged
in properly. If they are plugged in, then replace the data cable as a precaution. If your BIOS can see your
hard drive after replacing your data cable, then you probably just solved your problem. If it does not see
the drive, then you will need to move on to the next step.

6. PUT THE DRIVE IN AN ETERNAL ENCLOSURE


To recover hard drive data safely, you need to connect your hard drive to a second computer that has a
working operating system. Remove your damaged hard drive and put it in an external enclosure that can
be connected to a second computer through a USB port
When you connect the hard drive to a second computer, you will be able to:
 Mirror the damaged drive to a fresh drive to salvage your data
 Scan the damaged drive with scanning software you can find online to see if data can be recovered
 Analyze the drive with computer software without damaging th

STEPS IN TROBLESHOOTING REDUNDANT ARRAY OF INDEPENDENT Disks (RAID) case study the
Sun Storage J4500
1. Initial Start-up
If you are unable to see the array drives after powering on the array, check the following:
 Ensure all cables are properly connected (power and SAS).
 Be sure you are using SAS cables supported for use with the array. Using longer, or non-certified
cables is not supported. For a list of supported cables, see the Sun Storage J4500 Array Service
Manual, 820-3160.
 You should carefully follow the configuration rules listed in Chapter 1, Hardware Overview. Not
following these rules could result in an unsupported configuration.
 Check the array indicator LEDs to make sure all components are operating normally and the link
LEDs are green.
 The proper startup sequence for the array is to power-on the array first, wait one minute, then
power-up the server.

2. Check the Event and Performance Logs


The operating system event log is a good first place to start in identifying problems or potential issues with
the array enclosure or its disks. If you experience disk problems, such as disk errors or invalid
read/writes, the system event log can help identify the problem disk

3. Using the Array Management Software to Monitor Enclosure Health


Your J4500 array supports a powerful set of SMP (Serial Management Protocol) and SES-2 (SCSI
Enclosure Services) enclosure management features. Some or all of these features are available through
supported management software (for example, the Sun Common Array Manager (CAM), or the Sun
Storage Tek RAID Manager software) to provide a system administrator at the array-connected server or
network-connected management console the following capabilities:
 Monitor the enclosure status (on/off line status, component health)
 Monitor the enclosure environment (voltage and temperature)
 Remotely identify and locate enclosure components
 Obtain FRU identification and status (expanders, hard disks, fans, power supplies)
 Remove and install FRU components
 Remotely reset the enclosure hardware
 Remotely upgrade the enclosure's firmware (expanders and hard disk—must use CAM)
 View the enclosure event log to aid in troubleshooting

4. Detailed troubleshooting steps for Broken RAID issue on CPM


1. Schedule a maintenance window 
2. Log the session of the CPM interfaction.
3. Verify if the two drives are recognized by executing the "cat /proc/scsi/scsi" command.  If there are two
disks shown within the /proc/scsi/scsi file, one can use the /crossbeam/bin/xos-raid-add utility to start
RAID sync.
[root@CBS root]# /crossbeam/bin/xos-raid-add
4. In addition, please gather the following and upload to the case for review:
cat /proc/mdstat 
cat /proc/partitions 
smartctl -a /dev/sda 
smartctl -a /dev/sdb 
Collect the local logs from the CPM that has the broken RAID alarm (/crossbeam/logs/* & /var/log/*)
5. If the drive is not recognized in step3, please schedule and power cycle the CPM in question, and then
run the same set of data collection steps (listed in step 4) after the reboot. 
6. 'show module status' cpX to check raid status and go to next step if you see "Broken RAID" 
7. Run '/crossbeam/bin/xos-raid-add ' and run "cat /proc/mdstat " to very RAID status 
8. Collect the local logs from the CPM that has the broken RAID alarm (/crossbeam/logs/* & /var/log/*) 
9. Upload the requested data from step5 for review. 
10. Monitor for re-occurrence of the disk issue. 
11. If the RAID rebuilt process fails, please contact support.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy