Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
slab [2021/04/24 16:22]
cubebuilder 		slab [2021/05/09 14:31] (current)
kobi
Line 1: Line 1:
-=====How to set up your Storage Slab=====+====== How to set up your Storage Slab ======
  
 BuyVM offers storage slabs for all KVM Slice customers in all locations. BuyVM offers storage slabs for all KVM Slice customers in all locations.
  
-Storage slabs cost **$5 per TB** and are running on enterprise 7200RPM hard drives with an NVME cache. A storage slab is simply like an extra hard drive for your KVM Slice.+Storage slabs cost **$5 per TB** and are running on enterprise 7200RPM hard drives with an NVME cache and a 40Gbit+ InfiniBand to give you near local storage performance. A storage slab is simply like an extra hard drive for your KVM Slice. 
 + 
 +===== How to setup a storage slab on Linux ===== 
 +//[[http://doku.cubebuilder.me/doku.php?id=slab#how_to_setup_a_storage_slab_on_microsoft_windows|For setting up your storage slab on Microsoft Windows please click here.]]//
  
 __** WARNING, please make sure you follow this guide correctly or you risk wiping your boot drive.**__ __** WARNING, please make sure you follow this guide correctly or you risk wiping your boot drive.**__
Line 9: Line 12:
 **Step 1)** Attach the slab to your desired KVM slice in the Storage Volumes section in [[https://manage.buyvm.net/|Stallion]]. **Step 1)** Attach the slab to your desired KVM slice in the Storage Volumes section in [[https://manage.buyvm.net/|Stallion]].
  
-**Step 2)** Run ''fdisk -l'' to find out what the device path is for the slab you've just attached.+**Step 2)** Run ''sudo lsblk -o name,vendor,model,size'' to find out what the device path is for the slab you've just attached.
  
 <code> <code>
-$ sudo fdisk -l +$ sudo lsblk -o name,vendor,model,size
-Disk /dev/vda: 20 GiB, 21474836480 bytes, 41943040 sectors +
-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: 0x19ed42f3+
  
-Device     Boot    Start      End  Sectors Size Id Type +NAME   VENDOR   MODEL             SIZE 
-/dev/vda1  *        2048 39843455 39841408  19G 83 Linux +sda    BUYVM    SLAB                250G 
-/dev/vda2       39843456 41940607  2097152   1G 82 Linux swap / Solaris+sr0    QEMU     QEMU DVD-ROM     1024M 
 +vda    0x1af4                      10G 
 +├─vda1                            9.5G 
 +└─vda2                            512M 
 +</code>
  
 +In this case, you can see that the ''sda'' device has the vendor "BUYVM" and the model "SLAB" with a size of 250GB. This means that the device path will be ''/dev/sda''.
  
-Disk /dev/sda: 256 GiB, 274877906944 bytes, 536870912 sectors +**Step 3)** Now that you've identified your slab's device path, you need to create a partition on your slab. To do this, you will be using ''parted''. Please note that ''parted'' might not be installed by default on some systems. You should be able to install it with your system's package manager.
-Disk model: SLAB +
-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: 0x716cfadf +
-</code> +
- +
-In this case, there are 2 drives. One of them is the boot drive which is usually ''/dev/vda''. This is not the device we are looking for. What we're looking for is the newly attached slab's device path. You can usually tell which disk it is because every slab's Disk Model is "SLAB". In this case, the device path is /dev/sda.+
  
-**Step 3)** Now, you need to create a partition on your slab. Run ''sudo fdisk /dev/sda'' to use the fdisk partitioner on /dev/sda.+First, you're going to create the GUID Partition Table (GPT). To do this, run the following command:
 <code> <code>
-Welcome to fdisk (util-linux 2.33.1). +parted /dev/sda mklabel gpt
-Changes will remain in memory only, until you decide to write them. +
-Be careful before using the write command. +
- +
- +
-Command (m for help):+
 </code> </code>
  
-Type the letter **g** to create a new GPT partition table.+This will create the GPT on /dev/sda.
  
-Type the letter **n** to create a new partition. Use the default partition letter and sectors by pressing enter. +Now, you're going to create the actual partition. To do this, run the following command:
- +
- You can now quit fdisk by typing the letter **w** to write the new changes to the slab and quit.+
  
 <code> <code>
-$ sudo fdisk /dev/sda+parted /dev/sda mkpart primary 0% 100% 
 +</code>
  
-Welcome to fdisk (util-linux 2.33.1). +This will create a partition using the entire slab's storage capacity. 
-Changes will remain in memory only, until you decide to write them. +
-Be careful before using the write command. +
- +
- +
-Command (m for help): g +
-Created a new GPT disklabel (GUID: ECA757E9-5304-594C-A9CA-17E061B2E516). +
-The old dos signature will be removed by a write command. +
- +
-Command (m for help): n +
-Partition number (1-128, default 1): 1 +
-First sector (2048-536870878, default 2048): 2048 +
-Last sector, +/-sectors or +/-size{K,M,G,T,P} (2048-536870878, default 536870878): 536870878 # Set this to your own default by pressing enter. +
- +
-Created a new partition 1 of type 'Linux filesystem' and of size 256 GiB. +
- +
-Command (m for help): w +
-</code>+
  
-**Step 4)** Run fdisk -l again to see the new partition you just created (''/dev/sda1'').+**Step 4)** Run ''sudo lsblk -o name,vendor,model,size'' again to see the new partition you just created (which should be ''/dev/sda1'').
 <code> <code>
-$ fdisk -l +$ sudo lsblk -o name,vendor,model,size 
-[... your boot drive ...]+NAME   VENDOR   MODEL             SIZE 
 +sda    BUYVM    SLAB                250G 
 +└─sda1 
 +sr0    QEMU     QEMU DVD-ROM     1024M 
 +vda    0x1af4                      10G 
 +├─vda1                            9.5G 
 +└─vda2                            512M
  
-Disk /dev/sda: 256 GiB, 274877906944 bytes, 536870912 sectors 
-Disk model: SLAB 
-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: 0x716cfadf 
- 
-Device     Boot Start       End   Sectors  Size Id Type 
-/dev/sda1        2048 536870911 536868864  256G 83 Linux 
 </code> </code>
  
  
-**Step 5)** Now, you need to format the slab to have an actual filesystem. The most common filesystem is ext4 so we will be using that in this guide. To create an ext4 filesystem on your slab, run +**Step 5)** Now, you need to format the slab to have an actual filesystem. The most common filesystem is ext4 so I will be using that in this guide. To create an ext4 filesystem on your slab, run 
 <code> <code>
 mkfs.ext4 /dev/sda1 mkfs.ext4 /dev/sda1
Line 155: Line 121:
  
  
-===== Setting up a Storage Slab on Windows =====+===== How to setup a Storage Slab on Microsoft Windows ===== 
 +** WARNING, please make sure you follow this guide correctly or you risk wiping your boot drive.** 
 + 
 +**This guide should work on Windows Server 2012 R2, 2016 and 2019.** 
 To setup your storage slab on Windows you need to make sure that the Slab is attached on the Stallion. To setup your storage slab on Windows you need to make sure that the Slab is attached on the Stallion.
  
slab.1619306541.txt.gz · Last modified: 2021/04/24 16:22 by cubebuilder
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International


  • Show page
  • Old revisions
  • Backlinks
  • Recent Changes
  • Media Manager
  • Sitemap