Storage Device Buses Overview

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
or

Already have an account? Sign In »

Time
21 hours 25 minutes
Difficulty
Intermediate
CEU/CPE
21
Video Transcription
00:00
>> Hello there, Cybrarians.
00:00
Welcome back to the Linux+ course here at Cybrary.
00:00
I'm your instructor [inaudible].
00:00
In today's lesson, we are going to be
00:00
covering storage device buses.
00:00
Upon completion of today's lesson,
00:00
you are going to be able to understand
00:00
the types of storage buses that are used in
00:00
Linux and explain the differences
00:00
between these different buses.
00:00
But finally, we're going to examine
00:00
device locations to find
00:00
storage devices and use
00:00
the lsblk command in a demo at the end of this lesson.
00:00
There are three different types of
00:00
storage buses that you may want to consider.
00:00
Two of these are actually going to be on the exam.
00:00
Integrated drive electronics or
00:00
IDE devices have a drive controller
00:00
integrated into the drive itself.
00:00
An IDE supports two devices in a chain.
00:00
It's not actually covered on Linux+,
00:00
but you may see these drives are very old drives and
00:00
example of one of them is the
00:00
>> upper picture on the right.
00:00
>> Then the other types of storage buses are
00:00
the Small Computer System Interface, SCSI,
00:00
which is pronounced SCSI,
00:00
and the Serial ATA Attachment bus, which is SATA.
00:00
Now SCSI and SATA are covered on Linux+ exam,
00:00
so we're going to talk a lot more about them here.
00:00
Now, SCSI is a parallel interface used to
00:00
connect devices and SCSI devices
00:00
are connected in a chain,
00:00
either through an internal or external cable.
00:00
The last device on a chain always
00:00
has something called a terminator installed.
00:00
Ultra 320 SCSI is
00:00
the latest SCSI specification that I could
00:00
find and it transfers data at 320 megabytes per second.
00:00
Now, each SCSI device has an ID,
00:00
and the ID determines the priority of the device.
00:00
There's a maximum of 16 devices on a SCSI bus,
00:00
and the host bus adapter always
00:00
>> has the highest priority.
00:00
>> The priority numbering in SCSI is a little weird.
00:00
The highest priority number is seven,
00:00
and then it goes 7, 6, 5, 4,
00:00
3, 2, 1, 0,
00:00
and it goes all the way back up
00:00
>> to 15 and down to eight.
00:00
>> Now SCSI device interfaces are still
00:00
used for hard disk drives and servers,
00:00
it just became SAS,
00:00
which is Serial Attached SCSI.
00:00
Some virtualization uses SCSI interfaces
00:00
for virtual disk, notably, VMware.
00:00
Now, SATA communicates bit by
00:00
bit serial over a dedicated channel.
00:00
It uses a high-speed cable.
00:00
Just like we saw with the USB,
00:00
the Serial ATA speed has
00:00
gotten faster with each and every release.
00:00
It started out as SATA 1 with 150 megabytes per second.
00:00
Now we're as SATA 3,
00:00
which carries 600 megabytes per second.
00:00
We also have eSATA,
00:00
which allows us to connect
00:00
external devices to the system,
00:00
and eSATAp, which allows us to connect
00:00
those external devices and
00:00
provide power through the same cable.
00:00
Most modern hard drives,
00:00
and optical drives, so CD, DVD,
00:00
Blu-ray drives in any system will use SATA.
00:00
Because everything is a file in Linux,
00:00
the Linux kernel creates
00:00
device files in dev and we know this.
00:00
Dev is used by the kernel and applications to
00:00
communicate with the devices and for storage devices.
00:00
This means that it's used for storing
00:00
and retrieving data on these devices.
00:00
Each device on the system has to have an entry in dev,
00:00
just like we see hardware IDs
00:00
and processes have an entry in proc.
00:00
In device files in dev, though,
00:00
they come in a few different flavors.
00:00
There's character device files.
00:00
Those are things like terminals and
00:00
USB devices that transfer data one character at a time.
00:00
For internal we're typing one character at a time,
00:00
same thing with USB.
00:00
Then there are block device files which
00:00
are storage devices that we're used to
00:00
like hard drives and
00:00
those transfer files in blocks of data.
00:00
Now remember this when talking about block storage,
00:00
the lsblk command is the command that you
00:00
use to list block devices on a Linux system.
00:00
The command list all system
00:00
block devices by device and partitions.
00:00
Alternatively, you can see
00:00
the full path in the name column by using
00:00
lsblk-p. Let's have a look at
00:00
these commands and file locations with some demo time.
00:00
Here we are in our demo environment on Ubuntu.
00:00
Let's take a look at all of
00:00
the device files by just running ls dev.
00:00
This shows us character devices such as the tty files,
00:00
but we also see block devices such as sda and sda1.
00:00
We can also see the device files for standard error,
00:00
standard output, and standard in right here.
00:00
What do you think these do? Well, check this out.
00:00
This is cool. We can do echo
00:00
something and put it to dev stdl,
00:00
and then just write something to the screen.
00:00
Really, that's all the echo does.
00:00
Just as with other device files,
00:00
these exists as a way to talk to
00:00
devices via applications in the kernel.
00:00
Here echo is talking to standard out
00:00
the screen via a device file.
00:00
In the dev mapper directory,
00:00
so you do an ls on dev mapper.
00:00
Here we can see virtually mapped block devices.
00:00
There are none here, but if you go back to Module 4,
00:00
if you need a refresher on this.
00:00
Now let's take a look at the lsblk command.
00:00
We can see all the block devices with lsblk.
00:00
We can also see where the devices are mounted,
00:00
but what if we want to know the path
00:00
to the devices themselves?
00:00
Well, we can run lsblk-p,
00:00
and now we can see the path in the name column.
00:00
What if we wanted to see the
00:00
file system that it's actually mounted to?
00:00
Well, we can run lsblk-p and then fs.
00:00
Now we can actually see the mount point for
00:00
all of these block devices.
00:00
There are a few more lsblk options, but in general,
00:00
just always remember the help option
00:00
is usually there when you do
00:00
a -h and you can see
00:00
all of the various options for lsblk.
00:00
But with that, we've reached the end of this lesson.
00:00
In this lesson, we covered
00:00
the different types of storage
00:00
buses that are used in Linux.
00:00
We talked about some differences
00:00
between SATA and this SCSI buses.
00:00
Then we found out how to
00:00
>> examine device locations to find
00:00
>> storage information and use
00:00
the lsblk command to list block devices.
00:00
Thanks so much for being here and I look
00:00
forward to seeing you in the next lesson.
Up Next