How to find the local disks and SAN disks in linux

[senthil_kumar_1]

Hi

we are using Redhat and Suse linux.

I want to find the local disks and remote disks.

[Taifur]

Hi Kumar


You can check by "fdisk -l" and you will see new disk appearing in the output which will be represented as "/dev/sdb" or "/dev/sdc"

#fdisk -l

Rgds//
Taifur

[Ivan Ferreira]

The lssd command reports the device and the model. By checking the model you can identify if it's local or remote.

[UVK · Accepted solution]

fdisk -l and lssd commands will help your purpose

Cheers,
uvk

[Sivakumar MJ._1]

1.Check in /proc/partitions

2.(man fdisk)
fdisk -l [-u] [device ...]

The device is usually one of the following:

/dev/hda
/dev/hdb
/dev/sda
/dev/sdb

(/dev/hd[a-h] for IDE disks, /dev/sd[a-p] for SCSI disks, /dev/ed[a-d] for ESDI disks, /dev/xd[ab] for XT disks). A device name refers to the entire disk.

The partition is a device name followed by a partition number. For example, /dev/hda1 is the first partition on the first IDE hard disk in the system. Disks can have up to 15 partitions.


3.Read the Forum Postings
https://support.hpe.com/hpesc/public/docDisplay?docId=c01731722

4.Read the article ... http://searchsystemschannel.techtarget.com/generic/0,295582,sid99_gci1241976,00.html

[Huc_1]

You can also use

# parted -l

but best have a look at man parted it is full of possibility/options you may also have a GUI version like Gparted under GNOME

enjoy life.

Jean-Pierre Huc

[Matti_Kurkela]

RHEL 5 has "lsscsi" command, which displays the bus IDs and model strings of each storage device.

Another way is to examine the /sys filesystem. To know how e.g. /dev/sda is connected to the system, run "ls -l /sys/block/sda". There is a symlink "device" and the long directory listing tells you where the symlink points to. The target of the symlink is typically something like "../../devices/pci0000:00/0000:00:1f.1/host..." where "0000:00:1f.1" is a PCI device ID. Use "lspci" to identify it.

(There are probably a lot of fancy GUI tools that can automatically use this information to identify the disks, but often the GUI tools are not installed on our servers. Less software on servers => less things to patch.)

MK

[senthil_kumar_1]

Hi

I am not able to see some disks in lsscsi

Ex:

# cd /sys/block
# ll

drwxr-xr-x 5 root root 0 Feb 27 21:25 cciss!c0d0
drwxr-xr-x 5 root root 0 Feb 27 21:25 sda
drwxr-xr-x 3 root root 0 Feb 27 21:25 sdb
drwxr-xr-x 2 root root 0 Feb 27 21:26 sddlmab
drwxr-xr-x 4 root root 0 Feb 27 21:26 sddlmac
drwxr-xr-x 2 root root 0 Feb 27 21:26 sddlmfdrv0


So it is showing five disks c0d0, sda, sdb, sddlmab, sddlmac.

But my lsscsi show in just two disks only.

Ex:


emdlagas71:/sys/block # lsscsi
[0:0:0:0] tape HP Ultrium 3-SCSI G65W /dev/st0
[0:0:0:1] tape HP Ultrium 3-SCSI G65W /dev/st1
[0:0:0:2] storage HP NS E1200-160 5928 -
[0:0:1:0] disk HITACHI OPEN-V*3 6004 /dev/sda
[0:0:1:1] disk HITACHI OPEN-V*5 6004 /dev/sdb
[1:0:0:0] mediumx HP MSL6000 Series 0520 -
[1:0:0:1] tape HP Ultrium 3-SCSI G65W /dev/st2
[1:0:0:2] tape HP Ultrium 3-SCSI G65W /dev/st3
[1:0:0:3] storage HP NS E1200-160 5928 -


Pls explain me the difference

what is the problem.

pls explain me both.

[Uwe Zessin]

All those are Fibre Channel attached devices:

Looks like a MSL5000/6000 library with 2 tape drives, (E1200 is the FC/SCSI bridge)
[0:0:0:0] tape HP Ultrium 3-SCSI G65W /dev/st0
[0:0:0:1] tape HP Ultrium 3-SCSI G65W /dev/st1
[0:0:0:2] storage HP NS E1200-160 5928 -

Fibre Channel attached storage array (HDS or HP XP?)
[0:0:1:0] disk HITACHI OPEN-V*3 6004 /dev/sda
[0:0:1:1] disk HITACHI OPEN-V*5 6004 /dev/sdb

A second library, but on a different FC adapter port.
[1:0:0:0] mediumx HP MSL6000 Series 0520 -
[1:0:0:1] tape HP Ultrium 3-SCSI G65W /dev/st2
[1:0:0:2] tape HP Ultrium 3-SCSI G65W /dev/st3
[1:0:0:3] storage HP NS E1200-160 5928 -

This one looks like a local SmartArray RAID controller.
> drwxr-xr-x 5 root root 0 Feb 27 21:25 cciss!c0d0

Can you say something more about the server hardware involved?

[Sivakumar MJ._1]

Uwe Zessin has given you the details

Let us know exactly what you are missing.