{"id":9052,"date":"2021-06-11T22:03:51","date_gmt":"2021-06-11T19:03:51","guid":{"rendered":"https:\/\/kifarunix.com\/?p=9052"},"modified":"2021-06-11T22:03:55","modified_gmt":"2021-06-11T19:03:55","slug":"setup-software-raid-on-debian-10","status":"publish","type":"post","link":"https:\/\/kifarunix.com\/setup-software-raid-on-debian-10\/","title":{"rendered":"Setup Software RAID on Debian 10"},"content":{"rendered":"\n<p>In this tutorial, you will learn how to setup software raid on Debian 10. RAID is an acronym for Redundant Array of Independent Disks. The term\u00a0<code><strong>inexpensive<\/strong><\/code>\u00a0can occasionally be used instead of\u00a0<strong><code>independent<\/code><\/strong>.\u00a0<em>RAID is  used to combine multiple devices\/inexpensive disk drives into an array which yields performance that is better than that of one large and expensive drive<\/em>.<\/p>\n\n\n\n<p>Some of the major reasons to use RAID include:<\/p>\n\n\n\n<p>\u2022 enhanced transfer speed<br>\u2022 enhanced number of transactions per second<br>\u2022 increased single block device capacity<br>\u2022 greater efficiency in recovering from a single disk failure<\/p>\n\n\n\n<p>There are three possible types of RAID:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Firmware RAID<\/li><li>Hardware RAID<\/li><li>Software RAID.<\/li><\/ul>\n\n\n\n<p>This guide focuses on setting up Software RAID on Debian 10.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Setup Software RAID on Debian 10<\/h2>\n\n\n\n<p>Software RAID is used to implement the various RAID levels in the kernel block device code.&nbsp;<em>The Linux kernel contains a&nbsp;<strong><code>multiple device&nbsp;(MD)<\/code><\/strong>&nbsp;driver that allows the RAID solution to be completely hardware independent.<\/em><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">RAID Levels<\/h3>\n\n\n\n<p>The various RAID levels that can be implemented include;<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Raid Level 0 (striping)<\/h4>\n\n\n\n<ul class=\"wp-block-list\"><li>With RAID level 0, data is striped\/written across the member disks of the array.<\/li><li>Striping means data is broken down into small chunks.<\/li><li>The data is striped across the member drives of the array.<\/li><li>Storage capacity of the array is equal to the sum of the capacity of the member disks\/partitions<\/li><li>RAID Level 0 provides high I\/O performance<\/li><li>Doesn\u2019t provide fault tolerance and hence if one device in the array fails, then the whole array fails.<\/li><li>Requires a minimum of two storage devices.<\/li><\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">RAID Level 1 (mirroring)<\/h4>\n\n\n\n<ul class=\"wp-block-list\"><li>With RAID Level 1, a mirrored copy (identical) of data is written to each member drive of the array.<\/li><li>Provides redundancy and hence, high data availability. If one of the drive member of the array fails, the data in the other drives can be used. When you add another disk to the array, the data on existing disk will be copied to the new disk as well.<\/li><li>The storage capacity of the level 1 array is equal to the capacity of the smallest mirrored hard disk in a Hardware RAID or the smallest mirrored partition in a Software RAID hence less space efficient.<\/li><li>Requires a minimum of two storage devices.<\/li><\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Raid Level 5 (Striping with Parity)<\/h4>\n\n\n\n<ul class=\"wp-block-list\"><li>This is the most commonly used RAID level.<\/li><li>Requires at least three storage drives\/devices.<\/li><li>In this level, data is stripped across the member drives in the array along with the parity information. Parity is a raw binary data whose value is calculated so it can be used to reconstruct striped data from the other drives if one of the drives in the array fails.<\/li><li>Provides fault tolerance.<\/li><li>The storage capacity is equal to the capacity of the smallest member partition multiplied by the number of partitions&nbsp;<em>minus one<\/em>.<\/li><\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">RAID Level 6 (Striping with double parity)<\/h4>\n\n\n\n<ul class=\"wp-block-list\"><li>Similar to RAID level 5 except that it supports dual parity.<\/li><li>It can withstand 2 disk failure in the array.<\/li><li>Requires at least 4 devices<\/li><\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">RAID Level 10 (mirroring+stripping)<\/h4>\n\n\n\n<ul class=\"wp-block-list\"><li>RAID level 10 combines&nbsp;<em>the performance advantages of level 0 with the redundancy of level 1<\/em>.<\/li><li>Often denoted as RAID 1+0 (&nbsp;stripe of mirrors).<\/li><li>Requires at least 4 devices.<\/li><li>half of the storage devices is used for data mirroring hence, less space efficient.<\/li><li>most expensive of the RAID levels with lower usable capacity and high system costs.<\/li><\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Setup Software RAID on Debian 10<\/h3>\n\n\n\n<p>So how do you setup Software RAID on Debian 10? In this tutorial, we will demonstrate how to setup RAID Level 1 on Debian 10.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Creating RAID Partitions on RAID disk<\/h4>\n\n\n\n<p>To setup RAID Level 1, you need at least two drives\/partitions. In our demo server, we already have attached two disks,&nbsp;<code><strong>\/dev\/sdb<\/strong><\/code>&nbsp;and&nbsp;<strong><code>\/dev\/sdc<\/code><\/strong>&nbsp;each of 4GB as shown below;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>lsblk<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT\nsda      8:0    0   15G  0 disk \n\u251c\u2500sda1   8:1    0   13G  0 part \/\n\u251c\u2500sda2   8:2    0    1K  0 part \n\u2514\u2500sda5   8:5    0    2G  0 part &#91;SWAP]\nsdb      8:16   0    4G  0 disk \nsdc      8:32   0    4G  0 disk<\/code><\/pre>\n\n\n\n<p>In order to use a disk as RAID disk, you need to create a RAID partition type on each disk.<\/p>\n\n\n\n<p>In this demo, we use\u00a0<code><strong>parted<\/strong><\/code>\u00a0command for this purpose. <strong>parted<\/strong> may not be installed by default on Debian. Hence;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>apt install parted<\/code><\/pre>\n\n\n\n<ul class=\"wp-block-list\"><li>Set the type of partition on the disk. We use\u00a0<code>msdos<\/code>\u00a0in this setup. If prompted whether to delete existing data, accept and proceed.<\/li><\/ul>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>parted -a optimal \/dev\/sdb mklabel msdos<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>parted -a optimal \/dev\/sdc mklabel msdos<\/code><\/pre>\n\n\n\n<ul class=\"wp-block-list\"><li>Create the partition and set the filesystem type.<\/li><\/ul>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>parted -a optimal \/dev\/sdb mkpart primary ext4 0% 100%<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>parted -a optimal \/dev\/sdc mkpart primary ext4 0% 100%<\/code><\/pre>\n\n\n\n<ul class=\"wp-block-list\"><li>Set the partition as software RAID partition.<\/li><\/ul>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>parted -a optimal \/dev\/sdb set 1 raid on<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>parted -a optimal \/dev\/sdc set 1 raid on<\/code><\/pre>\n\n\n\n<ul class=\"wp-block-list\"><li>Display the partition table.<\/li><\/ul>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>parted -a optimal \/dev\/sdb print<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>Model: ATA VBOX HARDDISK (scsi)\nDisk \/dev\/sdb: 4295MB\nSector size (logical\/physical): 512B\/512B\nPartition Table: msdos\nDisk Flags: \n\nNumber  Start   End     Size    Type     File system  Flags\n 1      1049kB  4295MB  4294MB  primary               raid<\/code><\/pre>\n\n\n\n<pre id=\"block-0ca897f5-8a12-447f-a676-1e158f592c47\" class=\"wp-block-preformatted\">parted -a optimal \/dev\/sdc print<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>Model: ATA VBOX HARDDISK (scsi)\nDisk \/dev\/sdc: 4295MB\nSector size (logical\/physical): 512B\/512B\nPartition Table: msdos\nDisk Flags: \n\nNumber  Start   End     Size    Type     File system  Flags\n 1      1049kB  4295MB  4294MB  primary  ext4         raid<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">Setup Software RAID on Debian 10<\/h4>\n\n\n\n<p>Now that we have two disks setup, you can now go ahead and setup software RAID on Debian 10.<\/p>\n\n\n\n<p>Before you can proceed, ensure that you have&nbsp;<code><strong>mdadm<\/strong><\/code>&nbsp;package installed.&nbsp;<code><strong>mdadm<\/strong><\/code>&nbsp;is a utility that can be used to manage MD devices aka Linux Software RAID.<\/p>\n\n\n\n<p>Check if the package is installed.;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>apt list -a mdadm<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>Listing... Done\nmdadm\/focal,now 4.1-5ubuntu1 amd64 &#91;installed,automatic]<\/code><\/pre>\n\n\n\n<p>If not installed, you can install it by running the command below;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>apt install mdadm<\/code><\/pre>\n\n\n\n<p>The basic command line syntax for&nbsp;<strong><code>mdadm<\/code><\/strong>&nbsp;commad is;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>mdadm &#91;mode] &lt;raiddevice&gt; &#91;options] &lt;component-devices&gt;<\/code><\/pre>\n\n\n\n<p><strong>[mode]<\/strong>&nbsp;specifies any major mdadm operation mode which can be one of the following;<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><strong><code>Assemble (-A, --assemble)<\/code><\/strong>: assembles the components of a previously created array into an active array.<\/li><li><strong><code>Build (-B, --build)<\/code><\/strong>: Builds an array that doesn\u2019t have per-device metadata (superblocks).<\/li><li><strong><code>Create (-C, --create)<\/code><\/strong>: Creates a new array with per-device metadata (superblocks).<\/li><li><strong><code>Follow\/Monitor (-F, --follow, --monitor)<\/code><\/strong>: Monitor one or more md devices and act on any state changes. This is only meaningful for RAID1, 4, 5, 6, 10 or multipath arrays.<\/li><li><strong><code>Grow (-G, --grow)<\/code><\/strong>: Grow (or shrink) an array, or otherwise reshape it in some way.<\/li><li><code><strong>Incremental Assembly (-I, --incremental)<\/strong><\/code>: Add a single device to an appropriate array.<\/li><li><strong><code>Manage<\/code><\/strong>: This is for doing things to specific components of an array such as adding new spares and removing faulty devices.<\/li><li><strong><code>Misc<\/code><\/strong>: This is an \u2018everything else\u2019 mode that supports operations on active arrays, operations on component devices such as erasing old superblocks, and information gathering operations.<\/li><li><strong>Auto-detect (\u2013auto-detect)<\/strong>: This mode does not act on a specific device or array, but rather it requests the Linux Kernel to activate any auto-detected arrays.<\/li><\/ul>\n\n\n\n<p>So as an example, let us see how to create RAID level 1 using the two disks we setup above.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>mdadm --create \/dev\/md0 --level=1 --raid-devices=2 \/dev\/sd[bc]1<\/code><\/pre>\n\n\n\n<p>The options;<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><strong>-l, \u2013level=<\/strong>&nbsp;Sets RAID level which can be one of the;&nbsp;<strong>linear, raid0, 0, stripe, raid1, 1, mirror, raid4, 4, raid5, 5, raid6, 6, raid10, 10, multipath<\/strong><\/li><li><strong>-n, \u2013raid-devices=<\/strong>&nbsp;specifies the number of active devices in the array.<\/li><\/ul>\n\n\n\n<p>To use short command line options;<\/p>\n\n\n\n<pre id=\"block-78902f8b-2994-4cca-8d14-1262cb734b65\" class=\"wp-block-preformatted\">mdadm -C \/dev\/md0 -l raid1 -n=2 \/dev\/sd[bc]1<\/code><\/pre>\n\n\n\n<p>For other command line options, consult,&nbsp;<code><strong>man mdadm<\/strong><\/code>.<\/p>\n\n\n\n<p>The above command creates an \/dev\/md0 as a RAID1 array consisting of \/dev\/sdb1 and \/dev\/sdc1 drives.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>mdadm: Note: this array has metadata at the start and\n    may not be suitable as a boot device.  If you plan to\n    store '\/boot' on this device please ensure that\n    your boot-loader understands md\/v1.x metadata, or use\n    --metadata=0.90\nContinue creating array? y\nmdadm: Defaulting to version 1.2 metadata\nmdadm: array \/dev\/md0 started.<\/code><\/pre>\n\n\n\n<p>Check the status of the RAID;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>mdadm --detail \/dev\/md0<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>\/dev\/md0:\n           Version : 1.2\n     Creation Time : Fri Jun 11 07:13:55 2021\n        Raid Level : raid1\n        Array Size : 4190208 (4.00 GiB 4.29 GB)\n     Used Dev Size : 4190208 (4.00 GiB 4.29 GB)\n      Raid Devices : 2\n     Total Devices : 2\n       Persistence : Superblock is persistent\n\n       Update Time : Fri Jun 11 07:14:35 2021\n             State : clean, resyncing \n    Active Devices : 2\n   Working Devices : 2\n    Failed Devices : 0\n     Spare Devices : 0\n\nConsistency Policy : resync\n\n     Resync Status : 35% complete\n\n              Name : debian:0  (local to host debian)\n              UUID : c2afb48c:8391bfc4:41455be3:18ce0c01\n            Events : 5\n\n    Number   Major   Minor   RaidDevice State\n       0       8       17        0      active sync   \/dev\/sdb1\n       1       8       33        1      active sync   \/dev\/sdc1<\/code><\/pre>\n\n\n\n<p>To list detailed information about each RAID device;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>mdadm --examine \/dev\/sd[bc]1<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>\/dev\/sdb1:\n          Magic : a92b4efc\n        Version : 1.2\n    Feature Map : 0x0\n     Array UUID : c2afb48c:8391bfc4:41455be3:18ce0c01\n           Name : debian:0  (local to host debian)\n  Creation Time : Fri Jun 11 07:13:55 2021\n     Raid Level : raid1\n   Raid Devices : 2\n\n Avail Dev Size : 8380416 (4.00 GiB 4.29 GB)\n     Array Size : 4190208 (4.00 GiB 4.29 GB)\n    Data Offset : 6144 sectors\n   Super Offset : 8 sectors\n   Unused Space : before=6064 sectors, after=0 sectors\n          State : active\n    Device UUID : 20315496:2688da76:1ce6f030:36585c40\n\n    Update Time : Fri Jun 11 07:15:22 2021\n  Bad Block Log : 512 entries available at offset 16 sectors\n       Checksum : ba07c260 - correct\n         Events : 11\n\n\n   Device Role : Active device 0\n   Array State : AA ('A' == active, '.' == missing, 'R' == replacing)\n\/dev\/sdc1:\n          Magic : a92b4efc\n        Version : 1.2\n    Feature Map : 0x0\n     Array UUID : c2afb48c:8391bfc4:41455be3:18ce0c01\n           Name : debian:0  (local to host debian)\n  Creation Time : Fri Jun 11 07:13:55 2021\n     Raid Level : raid1\n   Raid Devices : 2\n\n Avail Dev Size : 8380416 (4.00 GiB 4.29 GB)\n     Array Size : 4190208 (4.00 GiB 4.29 GB)\n    Data Offset : 6144 sectors\n   Super Offset : 8 sectors\n   Unused Space : before=6064 sectors, after=0 sectors\n          State : active\n    Device UUID : 777754fd:4bef2715:3abb3ae7:cb25d0d1\n\n    Update Time : Fri Jun 11 07:15:22 2021\n  Bad Block Log : 512 entries available at offset 16 sectors\n       Checksum : 7131292 - correct\n         Events : 11\n\n\n   Device Role : Active device 1\n   Array State : AA ('A' == active, '.' == missing, 'R' == replacing)<\/code><\/pre>\n\n\n\n<p>You can also check the status by running the command below;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>cat \/proc\/mdstat<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>Personalities : &#91;linear] &#91;multipath] &#91;raid0] &#91;raid1] &#91;raid6] &#91;raid5] &#91;raid4] &#91;raid10] \nmd0 : active raid1 sdc1&#91;1] sdb1&#91;0]\n      4190208 blocks super 1.2 &#91;2\/2] &#91;UU]\n      \nunused devices: &lt;none&gt;<\/code><\/pre>\n\n\n\n<p>From the output above;<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><strong><code>Personalities<\/code><\/strong>\u00a0line shows the RAID level the kernel currently supports.<\/li><li><strong>md0<\/strong> device line shows the state of the array, the current raid level set on the device and the devices used in the array.<\/li><li>The other line indicates the usable size of the array in blocks<\/li><li><strong>[n\/m]<\/strong> e.g [2\/2] \u00a0shows that the array would have n devices however, currently, m devices are in use. When m >= n then things are good.<\/li><li><strong>[UU]<\/strong> means both disks on the RAID array are UP.<\/li><\/ul>\n\n\n\n<p>Read more on&nbsp;<a href=\"https:\/\/raid.wiki.kernel.org\/index.php\/Mdstat\" target=\"_blank\" rel=\"noreferrer noopener\">Mdstat page<\/a>.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Create a Filesystem on RAID Device<\/h4>\n\n\n\n<p>Once you have created a RAID device, you need to create a filesystem on it for you to mount and use it.<\/p>\n\n\n\n<p>Note that as shown above, we created RAID 1 which combined two 4G disks into a single 4G disk.<\/p>\n\n\n\n<p>Hence, to create a filesystem on md0 device, then run the command below to create an ext4 filesystem on the RAID device.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>mkfs.ext4 \/dev\/md0<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>mke2fs 1.45.5 (07-Jan-2020)\nCreating filesystem with 1047552 4k blocks and 262144 inodes\nFilesystem UUID: 97240b9e-8286-49fe-a304-a98bd3f66c42\nSuperblock backups stored on blocks: \n\t32768, 98304, 163840, 229376, 294912, 819200, 884736\n\nAllocating group tables: done                            \nWriting inode tables: done                            \nCreating journal (16384 blocks): done\nWriting superblocks and filesystem accounting information: done<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">Mounting Software RAID Device on Debian 10<\/h4>\n\n\n\n<p>You can now mount your RAID device on your convenient location.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>mount \/dev\/md0 \/mnt\/<\/code><\/pre>\n\n\n\n<p>To confirm the mounting;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>df -hT -P \/mnt\/<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>Filesystem     Type  Size  Used Avail Use% Mounted on\n\/dev\/md0       ext4  3.9G   16M  3.7G   1% \/mnt<\/code><\/pre>\n\n\n\n<p>To automount the device on boot, update&nbsp;<strong><code>\/etc\/fstab<\/code><\/strong>&nbsp;file by adding the line similar to the below;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>\/dev\/md0 \/mnt ext4 defaults 0 0<\/code><\/pre>\n\n\n\n<p>Also, you need to update the&nbsp;<strong><code>\/etc\/mdadm\/mdadm.conf<\/code><\/strong>&nbsp;by creating a prototype config file that describes currently active arrays that are known to be made from partitions of IDE or SCSI drives using the&nbsp;<code><strong>mdadm --detail --scan<\/strong><\/code>&nbsp;command<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>mdadm --detail --scan<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>ARRAY \/dev\/md0 metadata=1.2 name=ubuntu20:0 UUID=244a7fd9:d6fcc210:9b559249:df999270<\/code><\/pre>\n\n\n\n<p>To write the information to&nbsp;<strong><code>mdadm.conf<\/code><\/strong>, then run;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>mdadm --detail --scan &gt;&gt; \/etc\/mdadm\/mdadm.conf<\/code><\/pre>\n\n\n\n<p>Once you update the&nbsp;<code><strong>mdadm.conf<\/strong><\/code>, you can then update initramfs.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>update-initramfs -u<\/code><\/pre>\n\n\n\n<p>When done, updating the initramfs, you can reboot the system to confirm if the RAID device can mount automatically.<\/p>\n\n\n\n<p>So, if one of the disks get damaged, when you re-add the disk to the array, then your data should be restored!<\/p>\n\n\n\n<p>And that marks the end of our guide on how to setup Software RAID on Debian 10.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Other Tutorials<\/h3>\n\n\n\n<p><a href=\"https:\/\/kifarunix.com\/install-and-setup-glusterfs-storage-cluster-on-centos-8\/\" target=\"_blank\" rel=\"noreferrer noopener\">Install and Setup GlusterFS Storage Cluster on CentOS 8<\/a><\/p>\n\n\n\n<p><a href=\"https:\/\/kifarunix.com\/setup-glusterfs-distributed-replicated-volume-on-centos-8\/\" target=\"_blank\" rel=\"noreferrer noopener\">Setup GlusterFS Distributed Replicated Volume on CentOS 8<\/a><\/p>\n\n\n\n<p><a href=\"https:\/\/kifarunix.com\/install-and-configure-ceph-block-device-on-ubuntu-18-04\/\" target=\"_blank\" rel=\"noreferrer noopener\">Install and Configure Ceph Block Device on Ubuntu 18.04<\/a><\/p>\n\n\n\n<p><a href=\"https:\/\/kifarunix.com\/setup-three-node-ceph-storage-cluster-on-ubuntu-18-04\/\" target=\"_blank\" rel=\"noreferrer noopener\">Setup Three Node Ceph Storage Cluster on Ubuntu 18.04<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>In this tutorial, you will learn how to setup software raid on Debian 10. RAID is an acronym for Redundant Array of Independent Disks. The<\/p>\n","protected":false},"author":1,"featured_media":9057,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rank_math_lock_modified_date":false,"footnotes":""},"categories":[39,121,3426],"tags":[3660,3659,997,3656,3658,3657,3655,3427],"class_list":["post-9052","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-storage","category-howtos","category-raid","tag-add-disk-to-raid-array","tag-configure-raid-on-debian","tag-debian-10","tag-debian-setup-raid","tag-mdadm","tag-raid-devices-debian","tag-raid-level-1-debian-10","tag-setup-software-raid","generate-columns","tablet-grid-50","mobile-grid-100","grid-parent","grid-50","resize-featured-image"],"_links":{"self":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts\/9052"}],"collection":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/comments?post=9052"}],"version-history":[{"count":3,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts\/9052\/revisions"}],"predecessor-version":[{"id":9058,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts\/9052\/revisions\/9058"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/media\/9057"}],"wp:attachment":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/media?parent=9052"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/categories?post=9052"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/tags?post=9052"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}