Time
5 hours 33 minutes
Difficulty
Beginner
CEU/CPE
3

Video Description

Troubleshooting Hard Drives and RAID Arrays (part 1) In this lesson we look at issues with hard disk drives and RAID Arrays and discuss some of the common issues that materialize with these devices. We examine the drive not being seen/recognized on boot-up and why that might occur, read/write failures and examine some of those causes such as a bad drive, cabling, or an incorrect slave/master slave setting. We also look at noises, such as a loud whining noise, or what happens if the operating system isn't found.

Video Transcription

00:04
Hi. Welcome to cyberia dot i t My name is Anthony, and I'm your look with subject matter expert here for a plus. Today we're gonna be talking about troubleshooting hard drives and raid arrays with appropriate tools. So what do we do when we're booting our computer or we're in our computer and working with our computer and we're noticing that we're having some issues with our hard drives or our raid arrays.
00:23
Well, let's take a look and see if we can diagnose some of these hard drive issues, see some of the common symptoms
00:27
and maybe check out some of the reasons that may be causing these symptoms. So first we're gonna talk about our hard drives. I will talk about rate raids and a little bit. Now, our hard drives say we get a complete failure to boot. Well, this could be because of improper improper bio settings or cabling
00:45
if our bios has a certain dr disabled on it.
00:50
Uh, and that's the drive that we have. Our
00:53
boot are have our operating system on that drive, and we have the drive disabled in the BIOS. Then we're not gonna be able to boot
01:00
improper cabling. Maybe our cable are cabling that our mother board recognizes is being the drive that it checks for. Operating system first on isn't correct.
01:11
We may have additional drives in our computer, and the cabling is plugged in wrong. Or maybe we have a scuzzy controller and we don't have
01:19
the proper cables plugged into our drives. Or maybe we don't have a right Terminator on the end. Or maybe we're using paid a payday, paid a cord and are paid A cable is plug is configured improperly or a pedo jumpers or set improperly. So improper bios, settings or improper cabling in our computer,
01:40
I can result in a failure to boot file corruption on the drive or a drive.
01:45
Failure can also result in inability to boot. If our computer cannot read information off that drive with the data data is corrupted. Or maybe the drive mechanically failed. Then we won't be able to boot or if we have bad some bad sectors on there. We have data overwritten on too bad bad
02:02
bits on the drive, bad areas on the drive.
02:05
Then we won't be able to boot to our drive because some of those issues we also have Ah, Dr not recognized. Now when we have dr not recognized appear on our screen, we may have some bad bios. Settings were selecting the wrong. We're selecting the wrong dr in order to try to boot from its not recognizing this is a boot device.
02:24
We get a drive not recognized.
02:25
We may have some bad cable and connectors again if we have a scuzzy controller. We have a scuzzy cable and scuzzy ribbon and we have the drives plugged in incorrectly. Or maybe we have ah, paid a drive and our drives are incorrect order. And they they don't match their jumpers. If they're not sick, selected on auto select.
02:46
Or we might just have a bad drive drive man, Mechanically failed
02:50
may have some data corruption on the drive and that may be causing our drive, not recognized error.
02:55
We also have operating system, not found. Operating system not found can be a result of again improper bios, settings or cabling is whenever our bios, whenever our computer is looking at our different drives and trying to find and assumes that this drive is the one that has our operating system on it. If
03:15
our BIOS has that Dr Turned off
03:16
or our cabling is letting our computer think it needs to look on a different drive for an operating system, that there is not an operating system on that drive. Then we might get an operating system not found error. But again, this may also be a result of file corruption as well as our dr failing or bad sectors on the drive.
03:36
And then, lastly, over here we'll have we have blue screen of death.
03:38
Our blue screen of death may be a result of a failing hard drive starting to happen. That's, um, bad sectors. It's starting to mechanically fail. So we may get are a blue screen of death. As we're trying to work on a computer and use our drive, they may be result of a crashing application or bad memory or bad drivers. We may all
03:57
I also have bad storage drivers.
04:00
All of these are potential reasons that can cause a blue screen of death. And almost all of our troubleshooting modules will be talking about the blue screen of death at least a little bit, because the blue screen of death can be an indicator of a very wide range of issues could be an indicator of a very wide array of problems.
04:18
It's not a singular blue screen of death means
04:21
this one particular issue type of thing. It could be We have to do a lot of trouble shooting with that. With the blue screen of death, it may not be very may not be very informative and the stop codes that gives us so we need to take everything into consideration and remember that it can be because of a lot of different issues.
04:40
Next, we have read and write failure. Maybe we're using our drive, and it's not reading or writing data properly.
04:46
We're trying to write a file. Maybe that file. We're having a lot of files that get corrupted after we write them, and when we try to read them later, it's failing and reading them.
04:56
This may be an issue. With the drive failing, there may be some bad sectors on the drive. It may be mechanically failing, and we're trying to write the data. It's not properly writing the data so that when we go to read it later, it again doesn't properly read it, or it tries to read those sectors and finds that they're corrupted.
05:13
There may be some cabling issues we're trying to read or write. If we're trying to read or write to an additional drive that we have plugged into our computer and it doesn't show up or it isn't showing up properly, then it made our. It's not reading or writing to the right drive and maybe because we have our cable switched around, we don't have our cables
05:30
cables assigned properly, your jumpers assigned properly on our drives.
05:34
And then we have bio settings. We do have bio settings that allow us to modify which drives are turned on, which drives air turned off. And we're for having trouble reading or writing to a drive. And maybe because the BIOS settings related to that Dr are incorrect
05:51
and then lastly, we have scuzzy settings and pay the jumpers.
05:57
Our scuzzy ribbons are scuzzy. Ribbon cables may have drives in the wrong location on the cable are the same with our payday cables on our payday cables are paid. A drives also may have jumpers that are set incorrectly if we don't have it set to auto detects,
06:14
even if it's on our cable correctly. If we don't have a drive set to auto detect. If the jumpers air set incorrectly, then we may not be able to read or write to that Dr. Because our our computer operating system or our motherboard maybe trying to read those drives in a certain way and the cabling or the jumpers don't match up.
06:31
So we need to check those cable that cabling. You need to check the jumpers.
06:34
If we're having issues with reading and writing toward Dr, then we have slow performance. Slocum performance can be an indicator of a fragment to drive. We've talked about how a fragment to Dr occurs when we're constantly reading. We're reading, writing to our drive all the time and the data starts breaking up and getting separated all over our Dr.
06:54
So are Dr has to constantly search all over the place for data that relates to a certain program are certain file.
07:00
So are Dr becomes fragmented. As we use our utilities, however, we can use check. We can use our defrag utility. We can check for how much to fragmentation there is on our drive on. If there is a lot of de fragmentation, then we can art. There's a lot of fragmentation. Then we can run a d fragmentation
07:19
in order to try to clean that up.
07:20
If there's not a lot of fragmentation that we may want to check out some of these other potential issues, these other potentials issues include our bio speed settings are bios, does have settings that enable how fast
07:34
our mother board tries to communicate with our drives. If those air set improperly, then we may experience some issues of our motherboard. Essentially, our bios throttling us down to a certain speed are motherboard. Connectors may not support a certain Dr Speed or may not support a certain read right speed,
07:54
so we may notice slower performance.
07:57
Then we're expecting with a particular drive or particular cable.
08:01
And then, lastly, we have Dr Beginning to fail. We may actually have a drive that it's physically beginning to fail. It's starting to have mechanical issues. It's having a hard time spinning the disc or reading data on the disc, so we experience slow performance. If we're noticing we aren't having any fragmentation, we aren't having Our bios is set correctly,
08:20
but our Dr may be beginning to fail.
08:22
There are a couple of issues that are related that may also cause slow read and write performance that we don't have. Listen hit here because there are a lot of them. It could be everything from having a lot of applications open on our computer, and they're constantly trying to read and write to the drive. And they're all competing essentially
08:41
for reading and writing ability on that drive. If we have a lot of different applications open,
08:45
we may have malware that is attempting to read or write or causing corruption issues on our drives or drive us having problems. And it's taking a lot longer to read and write data to our drive. We can check for these issues. We can check for resource issues for our DR
09:01
by actually going into our resource monitor going into our task manager
09:05
and checking how much usage is being put on our drive because it's a high amount of usage and we have slow performance than it's probably some ANAP lick a shin or it's what we're using the drive for that's causing the high reeds or rights. But
09:22
if we're just noticing overall, our computer really isn't sending that many requests for reads and writes to the drive, but it's still taking a long time. It's still having slower performance when it's trying to read and write data. When it's tryingto perform on our operating system, then it may be an issue with the drive itself,
09:39
and then we have a loud clicking sound. Ah, loud clicking sound may be an indicator of a fragment to drive as our drive, as our hard drive is trying to look all over for particular data or information.
09:50
And also maybe I's a strong indicator that our drive is beginning to fail are we may hear a loud clicking sound because we're beginning. We have the beginnings of a head crash. The head that reads our data may be beginning to tap against the drive as it's trying to read. It is very bad,
10:07
Um, or we may be having our drive. Actually, just moving inside the computer,
10:11
if it isn't securely in, are in the computer slot that it's in. If we maybe just laid it inside one of our late inside one of our rail sets and didn't actually properly install it, but there may be some moving around is it's clicking because our drive does move. There are moving parts so it can vibrate if it isn't held in properly.
10:31
Um,
10:31
if we're having issues, any of these issues that we've been talking about, especially those where it may be beginning the beginnings of a drive failure. Such a czar loud clicking sound slow performance reads and writes failure or read and write failures.
10:46
Air is telling us that we're having a lot of data corruption. We're trying to open different files blue screens of death
10:54
whenever we're experiencing issues with our hard drive, where a potential ah potential candidate for the symptoms were experiencing are is Dr Failure. We want to make sure one of the first things we do is back up the data on our drive
11:09
before we begin troubleshooting before we begin trying to do things such as defragmenting are hard drive or going in and changing settings and modifying, modifying different
11:20
cables and jumpers. We may want to go ahead and backup are hard drive because we would rather back it up right away and then find out okay. It wasn't the hard drive failing. It was just ah, bio setting or it was just a little bit fragmented. Then say, Well, let me try this and try this and move some of the cables around and change some bio settings. And then
11:39
a couple hours later, while we're
11:41
troubleshooting, our drive completely fails. It's gonna be a lot more expensive to recover. The data is gonna be a lot harder to recover the data. Once that Dr completely dies, then it would right before it dies. So especially our troubleshooting steps like defragmenting are hard drive
11:58
when we defragment are hard drive, it does a lot of reading and writing to the drive.
12:03
So if our drive is about to fail, if it's about to go that defragment operation, maybe what pushes it over the edge. So we want to make sure that we back up that data before we just willy nilly defragment the hard drive because that may cause or drive to fail. And then we're gonna have to spend hundreds, maybe even up to
12:22
over $1000 in order to recover the data off of our hard drive. If it's not backed up

Up Next

Troubleshoot Critical Systems

Diagnosing system malfunctions and finding a solution is an important skill for help desk professionals to develop. Expand your knowledge of the troubleshooting theory in less than an hour.

Instructed By

Instructor Profile Image
Anthony Harris
Systems Analyst and Administrator at SAIC
Instructor