Setting up disks manually - Revision history

Prabuanand: added Troubleshooting link

2026-03-26T04:44:07Z

added Troubleshooting link

← Older revision		Revision as of 04:44, 26 March 2026
Line 211:		Line 211:
	== Troubleshooting ==		== Troubleshooting ==

			Refer to [[System_Disk_Mode#Troubleshooting\|Troubleshooting]] page as most issues documented here earlier have been consolidated on that page.

	== See also ==		== See also ==

	* [https://www.rodsbooks.com/gdisk/index.html Gdisk official website] '' walkthroughs available for gdisk,cgdisk and sgdisk''		* [https://www.rodsbooks.com/gdisk/index.html Gdisk official website] '' walkthroughs available for gdisk,cgdisk and sgdisk''
	[[Category:Storage]]		[[Category:Storage]]

Prabuanand: cleaned up the introduction and added steps for Manual partitioning with a Note and Tip

2026-03-26T04:41:14Z

cleaned up the introduction and added steps for Manual partitioning with a Note and Tip

← Older revision		Revision as of 04:41, 26 March 2026
Line 1:		Line 1:
	Setting up disks manually involves creating partitions using partitioning tools and formatting ~~such partitions~~ using various filesystem utilities to allow [[System Disk Mode]] or traditional HDD Installation of Alpine Linux. In addition to the above information, this page also documents various Disk layouts involving RAID, Encryption and LVM.		Setting up disks manually involves creating or modifying partitions using partitioning tools and formatting them using various filesystem utilities to allow [[System Disk Mode]] or traditional HDD Installation of Alpine Linux at the end of [[Installation#Base configuration\|base configuration step]] of installation. In addition to the above information, this page also documents various Disk layouts involving RAID, Encryption and LVM.

			{{Tip\|The default [[Installation#setup-alpine based System Disk Install\|System Disk]] installation requires and uses an entire HDD. If you intend to install Alpine Linux on a specific partition follow the [[System Disk Mode#setup-disk based Installation\|setup-disk based installation page]].}}

	== Manual partitioning ==		== Manual partitioning ==

	~~[[System Disk Mode#setup-disk based Installation\|setup-disk based Installation]] allows installing~~ Alpine Linux on ~~a partition after manually partitioning~~ the ~~HDD~~ at the end of [[Installation#Base configuration\|~~Base~~ configuration step of ~~Installation~~]]. ~~However~~, the [[~~Installation~~#~~setup-alpine based System Disk Install~~\|~~setup-alpine based System Disk Install~~]] ~~requires and uses an entire HDD~~.		Creating partitions manually requires partitioning tool packages and formatting them requires appropriate filesystem utilities. Due to the minimal nature of Alpine Linux, the installation image environment may have only limited options. Depending on your requirements, install the necessary packages at the end of [[Installation#Base configuration\|base configuration step]] of installation before proceeding further.

			{{Note\|Some of the tools mentioned on this page may require working [[Configure_Networking#Connectivity_testing\|Internet access]].}}

			* Create a partition using the available [[#Partitioning tools\|Partitioning tools]]
			* If MBR partition table is used, some partitioning tool may require manual steps to set up bootable flag.
			* Once the necessary partition(s) have been created, do a reboot before proceeding further.
			* [[#Formatting partitions\|Format the partition]] using the appropriate tool based on the filesystem used. Some partition tools may format the partitions automatically.

	== Partitioning tools ==		== Partitioning tools ==

	~~The installation image environment may have only~~ the ~~very~~ basic busybox built-in <code>fdisk</code> command available. ~~Instead, Alpine Linux allows you to install~~ any of the below listed partitioning ~~tool~~ immediately after setting up [[Installation#Base_configuration\|base configuration]].		Only the basic busybox built-in <code>fdisk</code> command available by default along with <code>sfdisk</code>. Install any of the below listed partitioning tools immediately after setting up [[Installation#Base_configuration\|base configuration]].

	{\|class="wikitable" align="center" style="width:100%; border:1px #0771a6 solid; background:#f9f9f9; text-align:left; border-collapse:collapse;"		{\|class="wikitable" align="center" style="width:100%; border:1px #0771a6 solid; background:#f9f9f9; text-align:left; border-collapse:collapse;"
Line 77:		Line 86:
	{{Warning\|The {{Path\|/dev/sdXY}} is only an example. Make sure you use the right partition name/number. Use {{ic\|blkid}} command to verify the partition name/number. Choosing the wrong partition leads to data loss. If you are unsure, do not proceed, seek [[Alpine Linux:Support\|support]].}}		{{Warning\|The {{Path\|/dev/sdXY}} is only an example. Make sure you use the right partition name/number. Use {{ic\|blkid}} command to verify the partition name/number. Choosing the wrong partition leads to data loss. If you are unsure, do not proceed, seek [[Alpine Linux:Support\|support]].}}

	Whenever a partition is [[#Creating_partitions\|created]], the partition must be formatted first before using it. Depending on the filesystem to be used, the necessary [[Filesystems#Filesystem_Tools\|formatting tool]] for the filesystem must be installed first.		Whenever a partition is [[#Creating_partitions\|created]], the partition must be formatted first before using it. Depending on the filesystem to be used, the necessary [[Filesystems#Filesystem_Tools\|formatting tool]] for the filesystem must be installed first.
	{{:Filesystems}}		{{:Filesystems}}

Prabuanand: moved System Disk Mode to own page

2025-10-31T15:23:31Z

moved System Disk Mode to own page

Show changes

Prabuanand: added entry based on http://redd.it/1ofy187

2025-10-31T07:56:33Z

added entry based on http://redd.it/1ofy187

← Older revision		Revision as of 07:56, 31 October 2025
Line 262:		Line 262:
	After running the standard Alpine installation command: {{ic\|setup-disk -m sys /mnt}} and rebooting, the system gives the error mentioned in [[#Mounting on /dev/sdXY sysroot failed\|Mounting on /dev/sdXY sysroot failed]] with the expected disk (e.g., /dev/sda, /dev/nvme0n1) missing to show at the output of {{ic\| blkid}}. This prevents booting into the installed system.		After running the standard Alpine installation command: {{ic\|setup-disk -m sys /mnt}} and rebooting, the system gives the error mentioned in [[#Mounting on /dev/sdXY sysroot failed\|Mounting on /dev/sdXY sysroot failed]] with the expected disk (e.g., /dev/sda, /dev/nvme0n1) missing to show at the output of {{ic\| blkid}}. This prevents booting into the installed system.

	~~One possible cause and solution is presented in~~ [~~[#BIOS storage controller set to RAID\|~~BIOS storage controller set to RAID]]		Issue: As per [https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10615 bug report] this might be caused by BIOS storage controller being set to "RAID On (Intel Rapid Storage Technology)".

	~~=====~~ BIOS ~~storage controller set~~ to RAID ~~=====~~		Resolution: Switch the storage mode in BIOS/UEFI: Go to BIOS → Storage or SATA/NVMe Operation. Change setting from:RAID On (Intel Rapid Storage Technology) to: AHCI or AHCI/NVMeb.

	~~Issue: As per [https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10615 bug report] this might be caused by BIOS storage controller being set to "RAID~~ On ~~(Intel Rapid Storage Technology)"~~.		=== Blinking underscore ===

			On a UEFI system, at the end of Installation after rebooting, the computer screen appears with '''blinking underscore'''.

	~~Resolution: Switch~~ the ~~storage mode~~ in ~~BIOS/UEFI: Go~~ to ~~BIOS → Storage or SATA/NVMe Operation~~. ~~Change setting from~~:~~RAID On (Intel Rapid Storage Technology) to~~: ~~AHCI or AHCI~~/~~NVMeb~~.		Alpine Linux doesn't create entries in UEFI NVRAM and instead places the bootloader in {{Path\|\EFI\alpine\grubx64.efi}} and the fallback boot path {{Path\|\EFI\boot\bootx64.efi}}. However, some EFI firmware may fail to boot Alpine Linux from the fallback path. In such cases, at the end of installation, instead of rebooting, manually add an entry for Alpine Linux in the NVRAM as follows:
			* Install the {{pkg\|efibootmgr}} package:{{Cmd\|# apk add efibootmgr}}
			* Adjust the command based on your device name {{ic\|/dev/sdX}} and issue the command {{Cmd\|# efibootmgr --create --disk /dev/sdX --part 1 --label "Alpine" --loader '\EFI\alpine\grubx64.efi'}}

	== See also ==		== See also ==

Prabuanand: added package name for resize2fs

2025-09-16T02:06:20Z

added package name for resize2fs

← Older revision		Revision as of 02:06, 16 September 2025
Line 71:		Line 71:
	{{Warning\|Make sure to choose the correct disk device in the below section. If you choose the wrong device, you will lose your data. Make a backup first and do not proceed, if you are unsure.}}		{{Warning\|Make sure to choose the correct disk device in the below section. If you choose the wrong device, you will lose your data. Make a backup first and do not proceed, if you are unsure.}}

	{{ic\|cfdisk}} and {{ic\|resize2fs}} can be used to resize existing partitions of ext2/3/4 filsystem on the disk. For other filsystems, the necessary [[Filesystems#Filesystem_Tools\|filesystem tools]] must be installed. This can be done while booted.		{{ic\|cfdisk}} and {{ic\|resize2fs}} from {{pkg\|e2fsprogs-extra}} package can be used to resize existing partitions of ext2/3/4 filsystem on the disk. For other filsystems, the necessary [[Filesystems#Filesystem_Tools\|filesystem tools]] must be installed. This can be done while booted.

	[[File:Cfdisk screenshot alpine 2024-03-04 143916.png\|thumb\|cfdisk screenshot ]]		[[File:Cfdisk screenshot alpine 2024-03-04 143916.png\|thumb\|cfdisk screenshot ]]

Prabuanand: removed the draft/todo notices, added wikilinks

2025-08-29T16:16:40Z

removed the draft/todo notices, added wikilinks

← Older revision		Revision as of 16:16, 29 August 2025
Line 103:		Line 103:
	== Disk layouts ==		== Disk layouts ==

	~~{{Draft\|This entire section including RAID, Encryption and LVM needs to be updated.}}~~		It is possible to have one or more of [[#RAID\|RAID]], [[#Encryption\|encrypted]], and/or [[#LVM\|Logical Volume]] on your {{Path\|/}} (root) volume. However, the Alpine init script only knows how to handle them when they're layered in that order, and your initram and extlinux.conf files in the {{Path\|/boot}} partition are configured properly.

	It is possible to have one or more of RAID, encrypted, and/or Logical Volume on your {{Path\|/}} (root) volume. However, the Alpine init script only knows how to handle them when they're layered in that order, and your initram and extlinux.conf files in the {{Path\|/boot}} partition are configured properly.

	Your {{Path\|/boot}} directory cannot reside on an encrypted or LVM volume, at least not with Alpine's default bootloader (extlinux). (Grub2 can deal with {{Path\|/boot}} being on an LVM volume.) The usual practice is to create a small partition for {{Path\|/boot}}, then devote the rest of your disk to a separate partition on which you layer one or more of RAID, encryption, and/or Logical Volumes.		Your {{Path\|/boot}} directory cannot reside on an encrypted or LVM volume, at least not with Alpine's default bootloader (extlinux). (Grub2 can deal with {{Path\|/boot}} being on an LVM volume.) The usual practice is to create a small partition for {{Path\|/boot}}, then devote the rest of your disk to a separate partition on which you layer one or more of RAID, encryption, and/or Logical Volumes.
Line 157:		Line 155:

	=== RAID ===		=== RAID ===
			{{Main\|Setting up a software RAID array}}
	<code>setup-disk</code> will automatically build a RAID array if you supply the '''-r''' switch, or if you specify more than one device.		<code>setup-disk</code> will automatically build a RAID array if you supply the '''-r''' switch, or if you specify more than one device.

Line 174:		Line 172:
	extlinux --raid --install $MNT/boot --update		extlinux --raid --install $MNT/boot --update
	}}		}}

	{{Todo\|Does adding the <code>--update</code> option to <code>extlinux ...</code> suffice to make {{Path\|/boot/extlinux.conf}} be regenerated? Or do we need to manually tweak that file, or run <code>update-extlinux</code>, as well?}}

	You might also need to manually tweak {{Path\|$MNT/etc/fstab}}. And you might need to copy {{Path\|/usr/share/syslinux/mbr.bin}} to your disk's MBR.		You might also need to manually tweak {{Path\|$MNT/etc/fstab}}. And you might need to copy {{Path\|/usr/share/syslinux/mbr.bin}} to your disk's MBR.

	=== Encryption ===		=== Encryption ===
			{{Main\|Setting up encrypted volumes with LUKS}}

	~~See [[Setting up encrypted volumes with LUKS]].~~ You can add an additional Logical Volume layer, or just unlock the volume you've created (using <code>cryptsetup luksOpen ...</code>), and supply the {{Path\|/dev/mapper/<i>something</i>}} device directly to [[setup-disk]]. When you're finished, be sure to relock the volume (using <code>cryptsetup luksClose ...</code>) before rebooting.		You can add an additional Logical Volume layer, or just unlock the volume you've created (using <code>cryptsetup luksOpen ...</code>), and supply the {{Path\|/dev/mapper/<i>something</i>}} device directly to [[setup-disk]]. When you're finished, be sure to relock the volume (using <code>cryptsetup luksClose ...</code>) before rebooting.

	If you install your {{Path\|/}} (root) on an encrypted volume, you'll need to manually edit/rebuild your initram and your extlinux.conf file. The following assumes that <code>$MNT</code> holds the root directory you're installing into, that you've created the cryptvolume on the device {{Path\|/dev/md2}}, and that you want to unlock the encrypted volume into a virtual volume named "crypt":		If you install your {{Path\|/}} (root) on an encrypted volume, you'll need to manually edit/rebuild your initram and your extlinux.conf file. The following assumes that <code>$MNT</code> holds the root directory you're installing into, that you've created the cryptvolume on the device {{Path\|/dev/md2}}, and that you want to unlock the encrypted volume into a virtual volume named "crypt":
Line 193:		Line 190:
	extlinux --install $MNT/boot --update		extlinux --install $MNT/boot --update
	}}		}}

	{{Todo\|Does adding the <code>--update</code> option to <code>extlinux ...</code> suffice to make {{Path\|/boot/extlinux.conf}} be regenerated? Or do we need to manually tweak that file, or run <code>update-extlinux</code>, as well?}}

	You might also need to manually tweak {{Path\|$MNT/etc/fstab}}.		You might also need to manually tweak {{Path\|$MNT/etc/fstab}}.

	=== LVM ===		=== LVM ===
			{{Main\|Setting up Logical Volumes with LVM}}

	<code>setup-disk</code> will automatically build and use volumes in a LVM group if you supply the '''-L''' switch.		<code>setup-disk</code> will automatically build and use volumes in a LVM group if you supply the '''-L''' switch.
Line 215:		Line 211:
	extlinux --install $MNT/boot --update		extlinux --install $MNT/boot --update
	}}		}}

	{{Todo\|Does adding the <code>--update</code> option to <code>extlinux ...</code> suffice to make {{Path\|/boot/extlinux.conf}} be regenerated? Or do we need to manually tweak that file, or run <code>update-extlinux</code>, as well?}}

	You might also need to manually tweak {{Path\|$MNT/etc/fstab}}.		You might also need to manually tweak {{Path\|$MNT/etc/fstab}}.
Line 277:		Line 271:

	== See also ==		== See also ==

	* [[Bootloaders]] - For information on GRUB, Syslinux and rEFInd		* [[Bootloaders]] - For information on GRUB, Syslinux and rEFInd
	* [[Installing Alpine on HDD dualbooting\|Install to HDD with dual-boot]]		* [[Installing Alpine on HDD dualbooting\|Install to HDD with dual-boot]]

Prabuanand: added issue 10615 reported by user sho in https://irclogs.alpinelinux.org/%23alpine-linux-2025-05.log and in reddit

2025-05-16T13:38:43Z

added issue 10615 reported by user sho in https://irclogs.alpinelinux.org/%23alpine-linux-2025-05.log and in reddit

← Older revision		Revision as of 13:38, 16 May 2025
Line 236:		Line 236:

	# Verify that the partition name in which Alpine Linux was installed matches the above [[#Mounting on /dev/sdXY sysroot failed\|error]] by issuing the command and also note down the filesystem type of that partition (say TYPE="ext4") : {{Cmd\| blkid}}		# Verify that the partition name in which Alpine Linux was installed matches the above [[#Mounting on /dev/sdXY sysroot failed\|error]] by issuing the command and also note down the filesystem type of that partition (say TYPE="ext4") : {{Cmd\| blkid}}
			# If the expected disk (e.g., /dev/sda, /dev/nvme0n1) itself is missing in the output of {{ic\| blkid}}, check [[#Disks not detected after setup-disk\|Disks not detected after setup-disk]].
	# Ensure that sysroot exists by issuing the command. {{Cmd\|ls -ld /sysroot}}		# Ensure that sysroot exists by issuing the command. {{Cmd\|ls -ld /sysroot}}
	# Check if the above error message apears when issuing the command. {{Cmd\|mount /dev/sda8 /sysroot}}		# Check if the above error message apears when issuing the command. {{Cmd\|mount /dev/sda8 /sysroot}}
Line 262:		Line 263:

	*For a solution independent of [[Bootloaders\|bootloaders]], ensure that the file {{Path\|/etc/mkinitfs/mkinitfs.conf}} has the necessary filesystem module in it. Refer [[Initramfs init\|Initramfs]] page for more information and recreate initramfs image.		*For a solution independent of [[Bootloaders\|bootloaders]], ensure that the file {{Path\|/etc/mkinitfs/mkinitfs.conf}} has the necessary filesystem module in it. Refer [[Initramfs init\|Initramfs]] page for more information and recreate initramfs image.

			==== Disks not detected after setup-disk====

			After running the standard Alpine installation command: {{ic\|setup-disk -m sys /mnt}} and rebooting, the system gives the error mentioned in [[#Mounting on /dev/sdXY sysroot failed\|Mounting on /dev/sdXY sysroot failed]] with the expected disk (e.g., /dev/sda, /dev/nvme0n1) missing to show at the output of {{ic\| blkid}}. This prevents booting into the installed system.

			One possible cause and solution is presented in [[#BIOS storage controller set to RAID\|BIOS storage controller set to RAID]]

			===== BIOS storage controller set to RAID =====

			Issue: As per [https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10615 bug report] this might be caused by BIOS storage controller being set to "RAID On (Intel Rapid Storage Technology)".

			Resolution: Switch the storage mode in BIOS/UEFI: Go to BIOS → Storage or SATA/NVMe Operation. Change setting from:RAID On (Intel Rapid Storage Technology) to: AHCI or AHCI/NVMeb.

	== See also ==		== See also ==

Prabuanand: fixed wikitags and typo

2025-04-09T16:15:44Z

fixed wikitags and typo

← Older revision		Revision as of 16:15, 9 April 2025
Line 60:		Line 60:
	The following step installs the {{Pkg\|cfdisk}} package: {{cmd\|# apk add cfdisk }}		The following step installs the {{Pkg\|cfdisk}} package: {{cmd\|# apk add cfdisk }}

	~~<code>~~cfdisk~~</code> will be used~~ to create partitions~~. Before using <code>cfdisk</code>~~, the disk name must be identified by using ~~<code>~~blkid~~</code>~~:		Before using {{ic\|cfdisk}} to create partitions, the disk name must be identified by using {{ic\|blkid}}:{{cmd\|# blkid}}

	{{cmd\|# blkid}}
	<pre>		<pre>
	/dev/sdX1: LABEL="some" UUID="..." TYPE="vfat"		/dev/sdX1: LABEL="some" UUID="..." TYPE="vfat"
	/dev/sdX2: LABEL="other" UUID="..." TYPE="ext4"		/dev/sdX2: LABEL="other" UUID="..." TYPE="ext4"
	</pre>}}		</pre>

	When {{ic\|cfdisk}} is run as follows, it looks for existing partitions on the disk {{Path\|/dev/sdX}}: {{cmd\|# cfdisk /dev/sdX}}		When {{ic\|cfdisk}} is run as follows, it looks for existing partitions on the disk {{Path\|/dev/sdX}}: {{cmd\|# cfdisk /dev/sdX}}
Line 73:		Line 71:
	{{Warning\|Make sure to choose the correct disk device in the below section. If you choose the wrong device, you will lose your data. Make a backup first and do not proceed, if you are unsure.}}		{{Warning\|Make sure to choose the correct disk device in the below section. If you choose the wrong device, you will lose your data. Make a backup first and do not proceed, if you are unsure.}}

	~~<code>~~cfdisk~~</code>~~ and ~~<code>~~resize2fs~~</code>~~ can be used to resize existing partitions of ext2/3/4 filsystem on the disk. For other filsystems, the necessary [[Filesystems#Filesystem_Tools\|filesystem tools]] must be installed. This can be done while booted.		{{ic\|cfdisk}} and {{ic\|resize2fs}} can be used to resize existing partitions of ext2/3/4 filsystem on the disk. For other filsystems, the necessary [[Filesystems#Filesystem_Tools\|filesystem tools]] must be installed. This can be done while booted.

	[[File:Cfdisk screenshot alpine 2024-03-04 143916.png\|thumb\|cfdisk screenshot ]]		[[File:Cfdisk screenshot alpine 2024-03-04 143916.png\|thumb\|cfdisk screenshot ]]

	To resize disk, launch the ~~<code>~~cfdisk~~</code>~~:		To resize disk, launch the {{ic\|cfdisk}}: {{cmd\|# cfdisk {{path\|/dev/sda}}}}
	{{cmd\|# cfdisk {{path\|/dev/sda}}}}

	# Select the target partition, here as per image {{path\|/dev/sda3}}		# Select the target partition, here as per image {{path\|/dev/sda3}}
Line 92:		Line 89:
	=== Formatting partitions ===		=== Formatting partitions ===

	{{Warning\|The {{Path\|/dev/sdXY}} is only an example. Make sure you use the right partition name/number. Use ~~<code>~~blkid~~</code>~~ command to verify the partition name/number. Choosing the wrong partition leads to data loss. If you are unsure, do not proceed, seek [[Alpine Linux:Support\|support]].}}		{{Warning\|The {{Path\|/dev/sdXY}} is only an example. Make sure you use the right partition name/number. Use {{ic\|blkid}} command to verify the partition name/number. Choosing the wrong partition leads to data loss. If you are unsure, do not proceed, seek [[Alpine Linux:Support\|support]].}}

	Whenever a partition is [[#Creating_partitions\|created]], the partition must be formatted first before using it. Depending on the filesystem to be used, the necessary [[Filesystems#Filesystem_Tools\|formatting tool]] for the filesystem must be installed first.		Whenever a partition is [[#Creating_partitions\|created]], the partition must be formatted first before using it. Depending on the filesystem to be used, the necessary [[Filesystems#Filesystem_Tools\|formatting tool]] for the filesystem must be installed first.
Line 209:		Line 206:
	vgchange -an}}		vgchange -an}}
	before rebooting.		before rebooting.


	If <code>setup-disk</code> sees that you're using LVM, perhaps because you gave it the <code>-L</code> switch, then it will set up your initram and extlinux.conf file properly. However, in other cases, these might not be properly set up. In that case, you may need to manually edit/rebuild them. The following assumes that <code>$MNT</code> holds the root directory you're installing into:		If <code>setup-disk</code> sees that you're using LVM, perhaps because you gave it the <code>-L</code> switch, then it will set up your initram and extlinux.conf file properly. However, in other cases, these might not be properly set up. In that case, you may need to manually edit/rebuild them. The following assumes that <code>$MNT</code> holds the root directory you're installing into:

Prabuanand: fixed typo

2025-04-09T15:20:26Z

fixed typo

← Older revision		Revision as of 15:20, 9 April 2025
Line 56:		Line 56:
	{{ic\|cfdisk}} will be used in all examples here as it is based on text menu without any dependencies. However, installing the {{Pkg\|cfdisk}} package requires network to be available if using Standard ISO boot image. Alternately, {{Pkg\|<code>sfdisk</code>}} can be installed without network.		{{ic\|cfdisk}} will be used in all examples here as it is based on text menu without any dependencies. However, installing the {{Pkg\|cfdisk}} package requires network to be available if using Standard ISO boot image. Alternately, {{Pkg\|<code>sfdisk</code>}} can be installed without network.

	{{Tip\|Use {{ic\|cgdisk}} ~~available~~ from {{Pkg\|gptfdisk}} package for GPT partitions and for conversion from MBR to GPT.}}		{{Tip\|Use {{ic\|cgdisk}} from {{Pkg\|gptfdisk}} package for GPT partitions and for conversion from MBR to GPT.}}

	The following step installs the {{Pkg\|cfdisk}} package: {{cmd\|# apk add cfdisk }}		The following step installs the {{Pkg\|cfdisk}} package: {{cmd\|# apk add cfdisk }}

Prabuanand: added Tip and fixed wikitags

2025-04-09T15:19:46Z

added Tip and fixed wikitags

← Older revision		Revision as of 15:19, 9 April 2025
Line 54:		Line 54:

	{{Warning\|Make sure to choose the correct disk device in the below section. If you choose the wrong device, you will lose your data. Make a backup first and do not proceed, if you are unsure.}}		{{Warning\|Make sure to choose the correct disk device in the below section. If you choose the wrong device, you will lose your data. Make a backup first and do not proceed, if you are unsure.}}
	~~<code>~~cfdisk~~</code>~~ will be used in all examples here as it is based on text menu without any dependencies. However, installing the ~~package~~ {{Pkg\|~~<code>~~cfdisk~~</code>~~}} requires network to be available if using Standard ISO boot image.		{{ic\|cfdisk}} will be used in all examples here as it is based on text menu without any dependencies. However, installing the {{Pkg\|cfdisk}} package requires network to be available if using Standard ISO boot image. Alternately, {{Pkg\|<code>sfdisk</code>}} can be installed without network.
	<code>~~cgdisk~~</code> ~~is also recommended for its excellent support for GPT partitions and conversion from MBR to GPT~~.

	~~Alternately,~~ {{Pkg\|~~<code>sfdisk</code>~~}} ~~is available in Standard ISO boot image~~ and ~~can be installed without network~~.		{{Tip\|Use {{ic\|cgdisk}} available from {{Pkg\|gptfdisk}} package for GPT partitions and for conversion from MBR to GPT.}}

	The following step installs the ~~package~~ {{Pkg\|~~<code>~~cfdisk~~</code>~~}}:		The following step installs the {{Pkg\|cfdisk}} package: {{cmd\|# apk add cfdisk }}
	{{cmd\|# apk add cfdisk }}

	<code>cfdisk</code> will be used to create partitions. Before using <code>cfdisk</code>, the disk name must be identified by using <code>blkid</code>:		<code>cfdisk</code> will be used to create partitions. Before using <code>cfdisk</code>, the disk name must be identified by using <code>blkid</code>:
Line 68:		Line 66:
	/dev/sdX1: LABEL="some" UUID="..." TYPE="vfat"		/dev/sdX1: LABEL="some" UUID="..." TYPE="vfat"
	/dev/sdX2: LABEL="other" UUID="..." TYPE="ext4"		/dev/sdX2: LABEL="other" UUID="..." TYPE="ext4"
	</pre>		</pre>}}

	When ~~<code>~~cfdisk~~</code>~~ is run as follows, it looks for existing partitions on the disk {{Path\|/dev/sdX}} :		When {{ic\|cfdisk}} is run as follows, it looks for existing partitions on the disk {{Path\|/dev/sdX}}: {{cmd\|# cfdisk /dev/sdX}}
	{{cmd\|# cfdisk /dev/sdX}}

	=== Resizing an existing partition ===		=== Resizing an existing partition ===

← Older revision		Revision as of 02:06, 16 September 2025
Line 71:		Line 71:
	{{Warning\|Make sure to choose the correct disk device in the below section. If you choose the wrong device, you will lose your data. Make a backup first and do not proceed, if you are unsure.}}		{{Warning\|Make sure to choose the correct disk device in the below section. If you choose the wrong device, you will lose your data. Make a backup first and do not proceed, if you are unsure.}}

	{{ic\|cfdisk}} and {{ic\|resize2fs}} can be used to resize existing partitions of ext2/3/4 filsystem on the disk. For other filsystems, the necessary [[Filesystems#Filesystem_Tools\|filesystem tools]] must be installed. This can be done while booted.		{{ic\|cfdisk}} and {{ic\|resize2fs}} from {{pkg\|e2fsprogs-extra}} package can be used to resize existing partitions of ext2/3/4 filsystem on the disk. For other filsystems, the necessary [[Filesystems#Filesystem_Tools\|filesystem tools]] must be installed. This can be done while booted.

	[[File:Cfdisk screenshot alpine 2024-03-04 143916.png\|thumb\|cfdisk screenshot ]]		[[File:Cfdisk screenshot alpine 2024-03-04 143916.png\|thumb\|cfdisk screenshot ]]

← Older revision		Revision as of 15:20, 9 April 2025
Line 56:		Line 56:
	{{ic\|cfdisk}} will be used in all examples here as it is based on text menu without any dependencies. However, installing the {{Pkg\|cfdisk}} package requires network to be available if using Standard ISO boot image. Alternately, {{Pkg\|<code>sfdisk</code>}} can be installed without network.		{{ic\|cfdisk}} will be used in all examples here as it is based on text menu without any dependencies. However, installing the {{Pkg\|cfdisk}} package requires network to be available if using Standard ISO boot image. Alternately, {{Pkg\|<code>sfdisk</code>}} can be installed without network.

	{{Tip\|Use {{ic\|cgdisk}} ~~available~~ from {{Pkg\|gptfdisk}} package for GPT partitions and for conversion from MBR to GPT.}}		{{Tip\|Use {{ic\|cgdisk}} from {{Pkg\|gptfdisk}} package for GPT partitions and for conversion from MBR to GPT.}}

	The following step installs the {{Pkg\|cfdisk}} package: {{cmd\|# apk add cfdisk }}		The following step installs the {{Pkg\|cfdisk}} package: {{cmd\|# apk add cfdisk }}