Differences

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

Link to this comparison view

Next revision
Previous revision
Last revision Both sides next revision
slab [2021/04/24 12:29]
moo created
slab [2021/04/27 14:19]
kobi
Line 1: Line 1:
-Once you've bought your new storage slab it's pretty simple to setup.+====== How to set up your Storage Slab ======
  
-Step 1: Mount the slab in the Stallion.+BuyVM offers storage slabs for all KVM Slice customers in all locations.
  
-Step 2: Run fdisk -to find out what the file system is for that slab.+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.**__ 
 + 
 +**Step 1)** Attach the slab to your desired KVM slice in the Storage Volumes section in [[https://manage.buyvm.net/|Stallion]]. 
 + 
 +**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 -+$ sudo lsblk -o name,vendor,model,size
-Disk /dev/vda: 20 GiB21474836480 bytes41943040 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+
  
-Device     Boot Start       End   Sectors  Size Id Type +First, you're going to create the GUID Partition Table (GPT). To do this, run the following command: 
-/dev/sda1        2048 536870911 536868864  256G 83 Linux+<code> 
 +parted /dev/sda mklabel gpt
 </code> </code>
  
-You should see your boot drivewhich we don't have to touchWe want to find the slabs filesystem. For example, on my VPS the filesystem is /dev/sda. You can tell because it's 256 GiB+This will create the GPT on /dev/sda. 
 + 
 +Nowyou're going to create the actual partitionTo do this, run the following command: 
 + 
 +<code> 
 +parted /dev/sda mkpart primary 0% 100% 
 +</code> 
 + 
 +This will create a partition using the entire slab's storage capacity.  
 + 
 +**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> 
 +$ sudo lsblk -o name,vendor,model,size 
 +NAME   VENDOR   MODEL             SIZE 
 +sda    BUYVM    SLAB                1T 
 +└─sda1 
 +sr0    QEMU     QEMU DVD-ROM     1024M 
 +vda    0x1af4                      10G 
 +├─vda1                            9.5G 
 +└─vda2                            512M 
 + 
 +</code> 
 + 
 + 
 +**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 slabrun  
 +<code> 
 +mkfs.ext4 /dev/sda1 
 +</code> 
 + 
 +This might take a few seconds depending on the size of your slab. 
 + 
 +**Step 6)** Now you are going to prepare to mount the slab. To do this, you're going to need to run a few commands to figure out the UUID of the device. 
 + 
 +First, you need to determine the slab's UUID. You can do that by running:  
 +<code>blkid</code> 
 + 
 +In this case, the device you're looking for is /dev/sda1. The line should look like:  
 +<code>/dev/sda1: UUID="1cb43a43-105c-46f1-9d7f-1c736c10ffdf" TYPE="ext4"</code> 
 + 
 +Now, you're going to add the slab's UUID to ''/etc/fstab'' so your slab will automatically mount when your server is booted. Open up ''/etc/fstab'' with your favorite text editor. At the end of the file, you will need to add the following line: 
 +<code> 
 +UUID=1cb43a43-105c-46f1-9d7f-1c736c10ffdf /mnt/slab ext4 defaults 0 0 
 +</code> 
 + 
 +This tells the system that ''/dev/sda1'' (''1cb43a43-105c-46f1-9d7f-1c736c10ffdf'') should be mounted at ''/mnt/slab''. You can change ''/mnt/slab'' to another directory if you'd like. 
 + 
 +<code> 
 +# /etc/fstab: static file system information. 
 +
 +# Use 'blkid' to print the universally unique identifier for a 
 +# device; this may be used with UUID= as a more robust way to name devices 
 +# that works even if disks are added and removed. See fstab(5). 
 +
 +# <file system> <mount point>   <type>  <options>       <dump>  <pass> 
 +# / was on /dev/vda1 during installation 
 +UUID=813b9d75-c617-4db0-b0f2-6758d17b31f4 /               ext4    errors=remount-ro 0       1 
 +# swap was on /dev/vda2 during installation 
 +UUID=a1103972-6b3e-49d1-ac18-d6bf16ea0f68 none            swap    sw              0       0 
 +#SLAB 
 +UUID=1cb43a43-105c-46f1-9d7f-1c736c10ffdf /mnt/slab ext4 defaults 0 0 
 +</code> 
 + 
 + 
 +**Step 7)** Creating the mount point 
 + 
 +You're almost there! One of the last things you need to do is create the mount point. In this guide, ''/mnt/slab'' is being used as the mount point. So, run: 
 + 
 +<code> 
 +mkdir /mnt/slab/ 
 +</code> 
 + 
 +This will create the directory for the slab to be mounted at and it will be the path you use to access the slab.  
 + 
 + 
 +**Step 8)** Mounting the Slab! 
 +<code>mount -a</code>  
 +This will mount the device you just added in /etc/fstab at /mnt/slab/. You can check out the newly mounted slab with ''df -h''
 + 
 +<code> 
 +$ df -h 
 +Filesystem      Size  Used Avail Use% Mounted on 
 +[...] 
 +/dev/sda1       251G  81M   250G 1% /mnt/slab 
 +[...] 
 +</code> 
 + 
 + 
 +===== 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. 
 + 
 +Once you have attached it follow these steps. 
 + 
 +  - Go to the Start Menu (Windows logo on the taskbar) 
 +  - Type "Disk Management" and open it 
 +  - You will see a Window that pops up that says "Initialize Disk" and the storage slab should show up as "Disk 1" 
 +  - Select the disk, and click OK 
 +  - The disk will then show up on Disk Management  
 +  - Right click on the unallocated space where your storage slab is and click "New Simple Volume"
 +  - After you've clicked "New Simple Volume" a setup wizard will show up. Assign the drive letter you want or mount it in empty folder. 
 +  - Click next, format the drive as NTFS, quick format and you can label the drive whatever you want to then click next. 
 +  - After that the drive should be formatted and will show up in File Explorer 
  
-Step 3: Run <code>fdisk /dev/sda # or whatever filesystem your slab is</code>