Partitioning (正體中文)

相關文章
File systems
fdisk
gdisk
Parted (正體中文)
fstab (正體中文)
LVM
Swap
Arch boot process
Unified Extensible Firmware Interface
systemd-repart
本條目或段落需要進行
翻譯
。
註記:
Translation in progress. (
討論
)
翻譯狀態：
本文章是
Partitioning
的翻譯版本。最近一次的翻譯時間：2025-03-05。點擊
本連結
查看英文頁面之後的變更。
英文維基百科
寫道：
磁碟分割，就是在
第二級記憶體
上建立一或多個區塊，各區塊可以獨立進行管理。
An entire disk may be allocated to a single partition, or multiple ones for cases such as dual-booting, maintaining a
swap
partition, or to logically separate data such as audio and video files. The partitioning scheme is stored in a
partition table
such as Master Boot Record (MBR) or GUID Partition Table (GPT).
Partition tables are created and modified using one of
many partitioning tools
. The tools available for Arch Linux are listed in the
#分割工具
section.
Partitions usually contain a
file system
directly which is accomplished by creating a file system on (a.k.a.
formatting
) the partition. Alternatively, partitions can contain
LVM
,
block device encryption
or
RAID
, which ultimately provide device files on which a file system can be placed (or the devices can be stacked further).
Any
block device
(e.g. disk, partition, LUKS device, LVM logical volume or RAID array) that directly contains a mountable file system is called a
volume
.
分割表
有兩種主流的分割表 (partition table) 可供使用。以下段落 (
#主開機記錄
(MBR)、
#GUID 分割表
(GPT)) 分別介紹這兩種分割表，接續的段落則討論如何從這兩種分割表之間做出選擇。第三種較少見的分割方式是無分割磁碟 (partitionless disk)，也會在最後一併進行討論。
使用
#分割工具
檢視
區塊裝置
的分割表：
# parted
/dev/sdX
print
或
# fdisk -l
/dev/sdX
提示
上述指令中的
/dev/sdX
對應要檢視的
區塊裝置
代號。例如 SATA 碟可能是
/dev/sda
、
NVMe
碟可能是
/dev/nvme0n1
、eMMC 碟可能是
/dev/mmcblk0
。關於區塊裝置命名方式的詳細資訊，請參閱
Device file#Block device names
。
主開機記錄
主開機記錄
(MBR) 是儲存裝置的最初 512 位元組。內含作業系統啟動程序載入程式，以及該儲存裝置的分割表，在
BIOS
系統中扮演重要的角色。關於 MBR 的結構，請見
Wikipedia:Master boot record#Disk partitioning
。
註記
MBR 不位於分割內，它位於裝置的第一個磁區 (實體位移 0)，在第一個分割之前。
若開機磁區位於無分割的裝置或獨立的分割中，則稱為
磁碟區開機記錄 (VBR)
。
主開機記錄 (啟動程式碼)
主開機記錄 (MBR) 的最初 440 位元組為
啟動程式碼區域 (bootstrap code area)
。BIOS 系統的啟動程式碼內通常含有第一階段啟動程序載入程式。啟動程式碼可以
透過 dd
備份、還原或移除。
主開機記錄 (分割表)
In the MBR partition table (also known as DOS or MS-DOS partition table) there are 3 types of partitions:
Primary
Extended
Logical
Primary
partitions can be bootable and are limited to four partitions per disk or RAID volume. If the MBR partition table requires more than four partitions, then one of the primary partitions needs to be replaced by an
extended
partition containing
logical
partitions within it.
Extended partitions can be thought of as containers for logical partitions. A hard disk can contain no more than one extended partition. The extended partition is also counted as a primary partition so if the disk has an extended partition, only three additional primary partitions are possible (i.e. three primary partitions and one extended partition). The number of logical partitions residing in an extended partition is unlimited. A system that dual boots with Windows will require for Windows to reside in a primary partition.
The customary numbering scheme is to create primary partitions
sda1
through
sda3
followed by an extended partition
sda4
. The logical partitions on
sda4
are numbered
sda5
,
sda6
, etc.
Tip
When partitioning a MBR disk consider leaving at least 33 512-byte sectors (16.5 KiB) of free unpartitioned space at the end of the disk in case you ever decide to
convert it to GPT
. The space will be required for the backup GPT header.
GUID 分割表
GUID Partition Table
(GPT) is a partitioning scheme that is part of the
Unified Extensible Firmware Interface
specification; it uses
globally unique identifiers
(GUIDs), or UUIDs in the Linux world, to define partitions and
partition types
. It is designed to succeed the
Master Boot Record
partitioning scheme method.
At the start of a GUID Partition Table disk there is a
protective Master Boot Record
(PMBR) to protect against GPT-unaware software. This protective MBR just like an ordinary MBR has a
bootstrap code area
which can be used for BIOS/GPT booting with boot loaders that support it.
選擇 GPT 或是 MBR
GUID 分割表 (GPT) 是另一個現代的分割方式，設計用來取代老舊的主開機記錄 (MBR) 系統。GPT 有幾項優點，不像 MBR 有一些古怪之處，這些古怪之處源自於久遠的 MS-DOS 年代。不過由於格式化工具最近的發展，想要提升 GPT 和 MBR 的可靠度和性能都很容易。
註記
在使用 BIOS 的系統上，要讓 GRUB 啟動使用 GPT 分割的硬碟，需要先規劃一個
BIOS 開機分割
。
Some points to consider when choosing:
To dual-boot with Windows (both 32-bit and 64-bit) using Legacy BIOS, the MBR scheme is required.
To dual-boot Windows 64-bit using
UEFI
mode instead of BIOS, the GPT scheme is required.
If you are installing on older hardware, especially on old laptops, consider choosing MBR because its BIOS might not support GPT (but
see below
how to fix it).
If you are partitioning a disk that is larger than 2 TiB (≈2.2 TB), you need to use GPT.
It is recommended to always use GPT for
UEFI
boot, as some UEFI implementations do not support booting to the MBR while in UEFI mode.
If none of the above apply, choose freely between GPT and MBR. Since GPT is more modern, it is recommended in this case.
Some advantages of GPT over MBR are:
Provides a unique disk GUID and unique partition GUID (
PARTUUID
) for each partition – a good filesystem-independent way of referencing partitions and disks. GUIDs are a prerequisite for the
Discoverable Partitions Specification
that can be utilized in a systemd-enabled initramfs.
Provides a filesystem-independent partition name (
PARTLABEL
).
Arbitrary number of partitions - depends on space allocated for the partition table - No need for extended and logical partitions. By default the GPT table contains space for defining 128 partitions. However if you want to define more partitions, you can allocate more space to the partition table (currently only
gdisk
is known to support this feature).
Uses 64-bit LBA for storing Sector numbers - maximum addressable disk size is 2 ZiB. MBR is limited to addressing 2 TiB of space per drive.
[1]
Stores a backup header and partition table at the end of the disk that aids in
recovery
in case the primary ones are damaged.
CRC32 checksums to detect errors and corruption of the header and partition table.
The section on
#分割工具
contains a table indicating which tools are available for creating and modifying GPT and MBR tables.
Tip
It is possible to convert between MBR and GPT. See
gdisk#Convert between MBR and GPT
.
無分割磁碟
This article or section needs expansion.
Reason:
Explain when one might want to use a partitionless disk (e.g. in VMs) and when not and why. (Discuss in
Talk:Partitioning (正體中文)
)
Partitionless disk a.k.a.
superfloppy
refers to a storage device without a partition table, having one file system occupying the whole storage device. The boot sector present on a partitionless device is called a
volume boot record (VBR)
.
Btrfs 分割
Btrfs
can occupy an entire data storage device and replace the
MBR
or
GPT
partitioning schemes. See the
Btrfs#Partitionless Btrfs disk
instructions for details.
分割計畫
This article or section needs expansion.
Reason:
Introduce
LVM
,
mdadm
,
dm-crypt
, etc. They could be placed in a new subsection together with the information about Btrfs subvolumes. (Discuss in
Talk:Partitioning (正體中文)
)
並沒有硬性規定如何分割硬碟。不過使用者仍可以遵循以下通則。分割計畫 (partitioning scheme) 取決於多項因素，例如期望的彈性、速度、安全性、可用磁碟空間的限制等，完全依個人偏好而定。若要雙開 Arch Linux 和 Windows 作業系統，請參閱
雙開 Windows
。
註記
UEFI
系統通常需要一個
EFI 系統分割
。
以
GPT
進行分割的 BIOS 系統，如果搭配
GRUB
作為啟動程序載入程式，則需要一個
BIOS 開機分割
。
提示
若使用
Btrfs
，副磁碟區 (subvolume) 可用來模擬分割。請參閱
Btrfs#掛接副磁碟區
一節。
單一根分割
這是最簡單又最有彈性的方法。有鑑於消費級儲存裝置的空間大小不斷提升，單一根分割應該足以應對大部分的使用情況。 A
swap file
can be created and easily resized as needed. It usually makes sense to start by considering a single
/
partition and then separate out others based on specific use cases like RAID, encryption, a shared media partition, etc… See
#多個分割
for a description of some common to uncommon dedicated partitions.
The suggested minimum size is 23–32 GiB for a single root partition. More space may be needed for user files and when using a swap file. A bare minimal installation requires about 2 GiB. As examples, a simple server can fit under 4 GiB while a full
KDE Plasma
installation uses 10 GiB. Both examples require frequent
purges of the package cache
.
Warning
A separate physical (in the main partition table of the disk, not under LVM, software RAID or in a file system subvolume etc.)
/boot partition
is needed unless your
boot loader
is capable of accessing the
/boot
directory that resides in
/
. That means the boot loader must have support for everything starting from the block devices, stacked block devices (LVM, RAID, dm-crypt, LUKS, etc.) and ending with the file system on which the kernel(s) and initramfs image(s) reside.
A GPT partition should have the "Linux root (x86-64)" type GUID
4F68BCE3-E8CD-4DB1-96E7-FBCAF984B709
(
8304
type for
gdisk
). An MBR partition should have the default "Linux" type ID
83
.
多個分割
Separating out a path as a partition allows for the choice of a different filesystem and mount options. In some cases like a media partition, they can also be shared between operating systems.
Below are some example layouts that can be used when partitioning, and the following subsections detail a few of the directories which can be placed on their own separate partition and then
mounted
at mount points under
/
. See
file-hierarchy(7)
for a full description of the contents of these directories.
/
The
root directory
is the top of the hierarchy, the point where the primary filesystem is mounted and from which all other filesystems stem. All files and directories appear under the root directory
/
, even if they are stored on different physical devices. The contents of the root filesystem must be adequate to boot, restore, recover, and/or repair the system. Therefore, certain directories under
/
are not candidates for separate partitions.
The
/
partition or root partition is necessary and it is the most important. The other partitions can be replaced by it.
Warning
Directories essential for booting (except for
/boot
)
must
be on the same partition as
/
or mounted in early userspace by the
initramfs
. These essential directories are:
/etc
and
/usr
[2]
.
/
traditionally contains the
/usr
directory, which can grow significantly depending upon how much software is installed. 15–20 GiB should be sufficient for most users with modern hard disks. If you plan to store a swap file here and do not plan on using a separate
/var
, you might need a larger partition size (i.e. adding the size of your RAM to be able to hibernate and an additional 8–12 GiB for
/var
).
A GPT partition should have the "Linux root (x86-64)" type GUID
4F68BCE3-E8CD-4DB1-96E7-FBCAF984B709
(
8304
for
gdisk
). An MBR partition should have the default "Linux" type ID
83
.
/boot
The
/boot
directory contains the
vmlinuz
and
initramfs
images as well as the boot loader configuration file and boot loader stages. It also stores data that is used before the kernel begins executing user-space programs.
/boot
is not required for normal system operation, but only during boot and kernel upgrades (when regenerating the initial ramdisk).
Warning
Your
boot loader
must be capable of accessing the
/boot
partition. That means the boot loader must have support for everything starting from the block devices, stacked block devices (LVM, RAID, dm-crypt, LUKS, etc.) and ending with the file system on which the kernel(s) and initramfs image(s) reside.
File systems can get new features not yet supported by
boot loaders
(e.g.
archlinux/packaging/packages/grub#7
,
FS#79857
,
FS#59047
,
FS#58137
,
FS#51879
,
FS#46856
,
FS#38750
,
FS#21733
and
fscrypt
encrypted directories), making them unsuitable for a
/boot
partition unless disabling incompatible features. This can be typically avoided by using
FAT32
since it is supported by practically everything and it will not be getting any new features.
See
Arch boot process#Boot loader
for more information on boot loader requirements and capabilities.
Note
On UEFI systems it is possible to mount the
EFI system partition
to
/boot
avoiding the need to create another separate partition. See
EFI system partition#Mount the partition
for more information.
When using an EFI system partition as
/boot
, the requirements are as described in the
EFI system partition
article—the correct partition type must be set.
In other cases, it is recommended to set the partition type to
Extended Boot Loader (XBOOTLDR) Partition
which is GPT partition type GUID
BC13C2FF-59E6-4262-A352-B275FD6F7172
(
ea00
type for
gdisk
,
xbootldr
type for
fdisk
) or MBR partition type ID
ea
.
In both cases the suggested size for the partition is 1 GiB, which should give enough space to house multiple kernels. If still in doubt, 4 GiB ought to be enough for anybody.
/home
The
/home
directory contains user-specific configuration files, caches, application data and media files.
Separating out
/home
allows
/
to be re-partitioned separately, but note that you can still reinstall Arch with
/home
untouched even if it is not separate—the other top-level directories just need to be removed, and then pacstrap can be run.
You should not share home directories between users on different distributions, because they use incompatible software versions and patches. Instead, consider sharing a media partition or at least using different home directories on the same
/home
partition. The size of this partition varies.
A GPT partition should have the "Linux home" type GUID
933AC7E1-2EB4-4F13-B844-0E14E2AEF915
(
8302
type for
gdisk
,
home
type for
fdisk
). An MBR partition should have the default "Linux" type ID
83
.
Swap
A
swap
is a file or partition that provides disk space used as virtual memory. Swap files and swap partitions are equally performant, but swap files are much easier to resize as needed. A swap partition can
potentially
be shared between operating systems, but not if hibernation is used.
Since computers have gained memory capacities superior to a gibibit, the previous "twice the amount of physical RAM" rule has become outdated. A sane
default size
is 4 GiB.
To use hibernation (a.k.a suspend to disk) it is advised to create the swap partition at the size of RAM. Although the kernel will try to compress the suspend-to-disk image to fit the swap space there is no guarantee it will succeed if the used swap space is significantly smaller than RAM. See
Power management/Suspend and hibernate#Hibernation
for more information.
A GPT partition should have the "Linux swap" type with GUID
0657FD6D-A4AB-43C4-84E5-0933C84B4F4F
(
8200
type for
gdisk
,
swap
type for
fdisk
). An MBR partition should have the "Linux swap" type ID
82
.
/data
One can consider mounting a "data" partition to cover various files to be shared by all users. Using the
/home
partition for this purpose is fine as well. The size of this partition varies.
A GPT partition should have the default "Linux filesystem" type GUID
0FC63DAF-8483-4772-8E79-3D69D8477DE4
. An MBR partition should have the default "Linux" type ID
83
.
/var
The
/var
directory stores variable data such as spool directories and files, administrative and logging data,
pacman
's cache, etc. It is used, for example, for caching and logging, and hence frequently read or written. Keeping it in a separate partition avoids running out of disk space due to flunky logs, etc.
It exists to make it possible to mount
/usr
as read-only. Everything that historically went into
/usr
that is written to during system operation (as opposed to installation and software maintenance) must reside under
/var
.
Note
/var
contains many small files. The choice of file system type should consider this fact if a separate partition is used.
Since
/var
is frequently read or written, it is recommended that you
consider the location of this partition on a spinning disk
.
/var
will contain, among other data, the
pacman
cache. Retaining these packages is helpful in case a package upgrade causes instability, requiring a
downgrade
to an older, archived package. The pacman cache will grow as the system is expanded and updated, but it can be safely
cleared
if space becomes an issue.
8–12 GiB on a desktop system should be sufficient for
/var
, depending on how much software will be installed. For users of
NVIDIA, Wayland and GDM
, consider adding to this partition size as to
have enough free space to fit your whole video memory
.
A GPT partition should have the "Linux variable data" a.k.a "Linux /var" type GUID
4D21B016-B534-45C2-A9FB-5C16E091FD2D
(
8310
type for
gdisk
). An MBR partition should have the default "Linux" type ID
83
.
分割示例
以下範例假設
/dev/sda
為待操作的磁碟，
/dev/sda1
為第一個分割。如果分割的是
NVMe
硬碟、SD 或 eMMC 卡，區塊裝置的命名方式會有所不同，例如
/dev/nvme0n1
的分割從
/dev/nvme0n1p1
開始；
/dev/mmcblk0
的分割從
/dev/mmcblk0p1
開始。詳細資訊請參閱
Device file#Block device names
。
註記
UEFI 開機不需要 "boot" 旗標 (flag)，開機只需要 NVRAM 中的開機項目 (boot entry)。
Parted
及其前端在 GPT 上使用 "boot" 旗標是為了標示該分割為 EFI 系統分割。
不一定要將所有必要/想要的分割全部建立在同一個磁碟上，也不一定要每個磁碟都使用同一種分割表格。
UEFI/GPT 分割示例
系統掛接點
分割
分割類型 GUID
建議大小
/boot
或
/efi
1
/dev/sda1
C12A7328-F81F-11D2-BA4B-00A0C93EC93B
:
EFI 系統分割
1 GiB
[SWAP]
/dev/sda2
0657FD6D-A4AB-43C4-84E5-0933C84B4F4F
: Linux
swap
至少 4 GiB 或 RAM 的大小才能使用
休眠
/
/dev/sda3
4F68BCE3-E8CD-4DB1-96E7-FBCAF984B709
: Linux x86-64 root (/)
裝置的剩餘空間。至少 23–32 GiB。
BIOS/MBR 分割示例
系統掛接點
分割
分割類型 ID
啟動旗標
建議大小
[SWAP]
/dev/sda1
82
: Linux
swap
否
至少 4 GiB 或 RAM 的大小才能使用
休眠
/
/dev/sda2
83
: Linux
是
裝置的剩餘空間。至少 23–32 GiB。
N/A
未分配空間
2
N/A
N/A
至少 16.5 KiB，位於磁碟末端。
BIOS/GPT 分割示例
系統掛接點
分割
分割類型 GUID
建議大小
None
/dev/sda1
21686148-6449-6E6F-744E-656564454649
:
BIOS boot partition
3
1 MiB
[SWAP]
/dev/sda2
0657FD6D-A4AB-43C4-84E5-0933C84B4F4F
: Linux
swap
至少 4 GiB 或 RAM 的大小才能使用
休眠
/
/dev/sda3
4F68BCE3-E8CD-4DB1-96E7-FBCAF984B709
: Linux x86-64 root (/)
裝置的剩餘空間。至少 23–32 GiB。
如果選用的啟動程序載入程式 (boot loader) 能夠存取核心和 initramfs 映像所在的檔案系統，則 ESP 可以掛接在
/efi
。詳細資訊請參閱
EFI system partition#Typical mount points
；相關警告請參閱
Arch boot process#Boot loader
。
若使用 MBR 進行分割，在磁碟末端至少要保留 33 個 512 位元組大小的磁區 (16.5 KiB)，日後才能
轉換成 GPT
。此空間會用於備份 GPT 標頭。
只有在 BIOS 以
GRUB
從 GPT 磁碟開機時才需要使用 BIOS 開機分割。使用其他的啟動程序載入程式並不需要此分割。此分割與
/boot
無關。請勿將其格式化或掛接檔案系統。
工具
分割工具
The following programs are used to create and/or manipulate device partition tables and partitions. See the linked articles for the exact commands to be used.
This table will help you to choose utility for your needs:
Name
Package
MBR
GPT
CLI
TUI
Scripting utility
fdisk
util-linux
Yes
Yes
fdisk(8)
cfdisk(8)
sfdisk(8)
GPT fdisk
gptfdisk
No
Yes
gdisk(8)
cgdisk(8)
sgdisk(8)
Parted
parted
Yes
Yes
parted(8)
No
parted(8)
GUI 前端
blivet-gui
— Graphical tool for storage configuration. It uses
parted
as backend via
python-blivet
AUR
and
libblockdev
.
https://github.com/storaged-project/blivet-gui
||
blivet-gui
AUR
GNOME Disks
— A GNOME utility for dealing with storage devices. It uses
parted
as backend via
udisks2
and
libblockdev
. Part of
gnome
.
https://apps.gnome.org/DiskUtility/
||
gnome-disk-utility
GParted
— Partition editor for graphically managing your disk partitions. It can be used to resize, copy and move partitions without data loss. It uses
parted
as backend.
https://gparted.org/
||
gparted
KDE Partition Manager
— Utility to help you manage the disks, partitions, and file systems on your computer. It uses
sfdisk
as backend via
kpmcore
. Part of
kde-system
.
https://apps.kde.org/partitionmanager/
||
partitionmanager
備份
fdisk
can create a backup of the partitions table. See
fdisk#Backup and restore partition table
.
GPT fdisk
can create a binary backup consisting of the protective MBR, the main GPT header, the backup GPT header, and one copy of the partition table. See
GPT fdisk#Backup and restore partition table
.
復原
gpart
— A utility that guesses the contents of a destroyed MBR partition table. Its usage is explained in the
gpart(8)
man page.
https://github.com/baruch/gpart
||
gpart
GPT fdisk
— A partitioning tool that can restore the primary GPT header (located at the start of the disk) from the secondary GPT header (located at the end of the disk) or vice versa.
https://www.rodsbooks.com/gdisk/
||
gptfdisk
TestDisk
— A utility that supports recovering lost partitions on both MBR and GPT.
https://www.cgsecurity.org/index.html?testdisk.html
||
testdisk
對齊分割
經驗法則表示應該將分割的起點和大小以 mebibyte 為單位對齊。請見
Advanced Format#Partition alignment
。
警告
未正確對齊的分割將無法以 4096 位元組磁區使用
dm-crypt/LUKS
。
GPT 核心支援
The
CONFIG_EFI_PARTITION
option in the kernel config enables GPT support in the kernel (despite the name, EFI PARTITION which looks close to
EFI system partition
). This option must be built in the kernel and not compiled as a loadable module. This option is required even if GPT disks are used only for data storage and not for booting. This option is enabled by default in all Arch's
officially supported kernels
. In case of a custom kernel, enable this option by doing
CONFIG_EFI_PARTITION=y
.
疑難排解
誘導舊型 BIOS 從 GPT 開機
Some old BIOSes (from before year 2010) attempt to parse the boot sector and refuse to boot it if it does not contain a bootable MBR partition. This is a problem if one wants to use GPT on this disk, because, from the BIOS viewpoint, it contains only one, non-bootable, MBR partition of type
ee
(i.e., the protective MBR partition). One can mark the protective MBR entry as bootable using
fdisk -t mbr /dev/sda
, and it will work on some BIOSes. However, the UEFI specification prohibits the protective MBR partition entry from being bootable, and UEFI-based boards do care about this, even in the legacy boot mode. So, this matters if one wants to create a GPT-based USB flash drive that is supposed to boot both on modern UEFI-based boards and also on old BIOSes that insist on finding a bootable MBR partition. It is not possible to solve this problem using traditional tools such as
fdisk
or
gdisk
, but it is possible to create a fake MBR partition entry suitable for both kinds of BIOSes manually as a sequence of bytes.
The command below will overwrite the second MBR partition slot and add a bootable partition there of type 0 (i.e. unused), covering only the first sector of the device. It will not interfere with the GPT or with the first MBR partition entry which normally contains a protective MBR partition.
# printf '\200\0\0\0\0\0\0\0\0\0\0\0\001\0\0\0' | dd of=/dev/sda bs=1 seek=462
The end result will look like this:
# fdisk -t mbr -l /dev/sda
Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Disk model: ST3250820AS
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot Start       End   Sectors   Size Id Type
/dev/sda1           1 488397167 488397167 232.9G ee GPT
/dev/sda2  *        0         0         1   512B  0 Empty

Partition table entries are not in disk order.
啟用 RAID 時裝置無法顯示
If a SATA or NVMe drive is visible in firmware setup, but not to Linux (e.g.
fdisk -l
does not list it), it is possible that the controller is in firmware RAID mode.
For NVMe, the
journal
should show something like:
kernel: ahci 0000:00:17.0: Found 1 remapped NVMe devices.
kernel: ahci 0000:00:17.0: Switch your BIOS from RAID to AHCI mode to use them.
The solution is to enter firmware setup and disable NVMe RAID mode and change the
SATA controller operation mode
from
RAID
to
AHCI
. Mind that the setting may have a different name (e.g. "Intel Rapid Storage Technology", "Intel RST", "Intel VMD controller" or "VMD") and it could also be per-controller or per-port.
Warning
When
dual booting with Windows
, preparations need to be made before changing the controller mode. See
How to Enable AHCI in Windows 8 and Windows 10 after Installation
.
Note
Some firmware do not have a dedicated NVMe RAID mode setting and, despite the terms not making any sense, use the SATA controller operation mode setting for the NVMe controller too. These firmware simply interpret "SATA operation mode" being set to "AHCI" on NVMe controllers to mean "use native operating mode without firmware RAID".
[3]
[4]
[5]
另請參閱
Wikipedia:Disk partitioning
Wikipedia:Binary prefix
Understanding Disk Drive Terminology
Rod Smith's page on
What's a GPT?
and
Booting OSes from GPT
Make the most of large drives with GPT and Linux - IBM Developer
Microsoft's Windows and GPT FAQ
Partition Alignment
(with examples)