| 1 |
fjpop-guest |
11832 |
<!-- retain these comments for translator revision tracking -->
|
| 2 |
fjp |
56246 |
<!-- original version: 56142 untranslated -->
|
| 3 |
fjpop-guest |
11832 |
|
| 4 |
|
|
|
| 5 |
|
|
<sect1 id="device-names">
|
| 6 |
|
|
<title>Device Names in Linux</title>
|
| 7 |
|
|
<para>
|
| 8 |
|
|
|
| 9 |
|
|
Linux disks and partition names may be different from other operating
|
| 10 |
|
|
systems. You need to know the names that Linux uses when you create
|
| 11 |
|
|
and mount partitions. Here's the basic naming scheme:
|
| 12 |
|
|
|
| 13 |
|
|
</para>
|
| 14 |
|
|
<itemizedlist arch="not-s390">
|
| 15 |
|
|
<listitem><para>
|
| 16 |
|
|
|
| 17 |
|
|
The first floppy drive is named <filename>/dev/fd0</filename>.
|
| 18 |
|
|
|
| 19 |
|
|
</para></listitem>
|
| 20 |
|
|
<listitem><para>
|
| 21 |
|
|
|
| 22 |
|
|
The second floppy drive is named <filename>/dev/fd1</filename>.
|
| 23 |
|
|
|
| 24 |
|
|
</para></listitem>
|
| 25 |
|
|
<listitem><para>
|
| 26 |
|
|
|
| 27 |
|
|
The first SCSI disk (SCSI ID address-wise) is named
|
| 28 |
|
|
<filename>/dev/sda</filename>.
|
| 29 |
|
|
|
| 30 |
|
|
</para></listitem>
|
| 31 |
|
|
<listitem><para>
|
| 32 |
|
|
|
| 33 |
|
|
The second SCSI disk (address-wise) is named
|
| 34 |
|
|
<filename>/dev/sdb</filename>, and so on.
|
| 35 |
|
|
|
| 36 |
|
|
</para></listitem>
|
| 37 |
|
|
<listitem><para>
|
| 38 |
|
|
|
| 39 |
|
|
The first SCSI CD-ROM is named <filename>/dev/scd0</filename>, also
|
| 40 |
|
|
known as <filename>/dev/sr0</filename>.
|
| 41 |
|
|
|
| 42 |
|
|
</para></listitem>
|
| 43 |
|
|
<listitem><para>
|
| 44 |
|
|
|
| 45 |
|
|
The master disk on IDE primary controller is named
|
| 46 |
|
|
<filename>/dev/hda</filename>.
|
| 47 |
|
|
|
| 48 |
|
|
</para></listitem>
|
| 49 |
|
|
<listitem><para>
|
| 50 |
|
|
|
| 51 |
|
|
The slave disk on IDE primary controller is named
|
| 52 |
|
|
<filename>/dev/hdb</filename>.
|
| 53 |
|
|
|
| 54 |
|
|
</para></listitem>
|
| 55 |
|
|
<listitem><para>
|
| 56 |
|
|
|
| 57 |
|
|
The master and slave disks of the secondary controller can be called
|
| 58 |
|
|
<filename>/dev/hdc</filename> and <filename>/dev/hdd</filename>,
|
| 59 |
|
|
respectively. Newer IDE controllers can actually have two channels,
|
| 60 |
|
|
effectively acting like two controllers.
|
| 61 |
|
|
|
| 62 |
|
|
</para></listitem>
|
| 63 |
|
|
</itemizedlist>
|
| 64 |
|
|
|
| 65 |
|
|
<itemizedlist arch="s390">
|
| 66 |
|
|
<listitem><para>
|
| 67 |
|
|
|
| 68 |
fjpop-guest |
19101 |
The first DASD device is named
|
| 69 |
|
|
<filename>/dev/dasda</filename>.
|
| 70 |
fjpop-guest |
11832 |
|
| 71 |
|
|
</para></listitem>
|
| 72 |
fjpop-guest |
19101 |
<listitem><para>
|
| 73 |
|
|
|
| 74 |
|
|
The second DASD device is named
|
| 75 |
|
|
<filename>/dev/dasdb</filename>, and so on.
|
| 76 |
|
|
|
| 77 |
|
|
</para></listitem>
|
| 78 |
fjpop-guest |
11832 |
</itemizedlist>
|
| 79 |
|
|
|
| 80 |
|
|
<para arch="not-s390">
|
| 81 |
|
|
|
| 82 |
|
|
The partitions on each disk are represented by appending a decimal
|
| 83 |
|
|
number to the disk name: <filename>sda1</filename> and
|
| 84 |
|
|
<filename>sda2</filename> represent the first and
|
| 85 |
|
|
second partitions of the first SCSI disk drive in your system.
|
| 86 |
|
|
|
| 87 |
|
|
</para><para arch="not-s390">
|
| 88 |
|
|
|
| 89 |
|
|
Here is a real-life example. Let's assume you have a system with 2
|
| 90 |
|
|
SCSI disks, one at SCSI address 2 and the other at SCSI address 4.
|
| 91 |
|
|
The first disk (at address 2) is then named <filename>sda</filename>,
|
| 92 |
|
|
and the second <filename>sdb</filename>. If the
|
| 93 |
|
|
<filename>sda</filename> drive has 3 partitions on it, these will be
|
| 94 |
|
|
named <filename>sda1</filename>, <filename>sda2</filename>, and
|
| 95 |
|
|
<filename>sda3</filename>. The same applies to the
|
| 96 |
|
|
<filename>sdb</filename> disk and its partitions.
|
| 97 |
|
|
|
| 98 |
|
|
</para><para arch="not-s390">
|
| 99 |
|
|
|
| 100 |
|
|
Note that if you have two SCSI host bus adapters (i.e., controllers),
|
| 101 |
|
|
the order of the drives can get confusing. The best solution in this
|
| 102 |
|
|
case is to watch the boot messages, assuming you know the drive models
|
| 103 |
|
|
and/or capacities.
|
| 104 |
|
|
|
| 105 |
fjp |
39614 |
</para><para arch="x86">
|
| 106 |
fjpop-guest |
11832 |
|
| 107 |
|
|
Linux represents the primary partitions as the drive name, plus the
|
| 108 |
|
|
numbers 1 through 4. For example, the first primary partition on the
|
| 109 |
|
|
first IDE drive is <filename>/dev/hda1</filename>. The logical partitions are
|
| 110 |
|
|
numbered starting at 5, so the first logical partition on that same
|
| 111 |
|
|
drive is <filename>/dev/hda5</filename>. Remember that the extended
|
| 112 |
|
|
partition, that is, the primary partition holding the logical
|
| 113 |
|
|
partitions, is not usable by itself. This applies to SCSI disks as
|
| 114 |
|
|
well as IDE disks.
|
| 115 |
|
|
|
| 116 |
|
|
</para><para arch="sparc">
|
| 117 |
|
|
|
| 118 |
|
|
Sun disk partitions allow for 8 separate partitions (or slices). The
|
| 119 |
fjp |
29119 |
third partition is usually (and is preferred to have) the <quote>Whole
|
| 120 |
|
|
Disk</quote> partition. This partition references all of the sectors of the
|
| 121 |
|
|
disk, and is used by the boot loader (either SILO, or Sun's).
|
| 122 |
fjpop-guest |
11832 |
|
| 123 |
|
|
</para><para arch="s390">
|
| 124 |
|
|
|
| 125 |
fjpop-guest |
19101 |
The partitions on each disk are represented by appending a decimal
|
| 126 |
|
|
number to the disk name: <filename>dasda1</filename> and
|
| 127 |
|
|
<filename>dasda2</filename> represent the first and
|
| 128 |
|
|
second partitions of the first DASD device in your system.
|
| 129 |
fjpop-guest |
11832 |
|
| 130 |
|
|
</para>
|
| 131 |
|
|
</sect1>
|
Parent Directory
| 
Revision Log