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 14:44]
cubebuilder 		slab [2024/07/28 12:30] (current)
kobi
Line 1: Line 1:
-=====How to setup 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 lots of NVME cache.+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.
  
-A storage slab is simply like a extra "hard drive" for your KVM Slice that runs on a different partition.+===== How to setup a storage slab on Linux =====
  
-This guide will help you setup your Storage Slab. +__** WARNING, please make sure you follow this guide correctly or you risk wiping your boot drive.**__
  
-** Warning, make sure you follow this correctly or you could 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 1) Enable the slab in the Storage Volumes section on the [[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.
- +
-Step 2) Run fdisk -l to find out what the file system is for that slab.+
  
 <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+
  
-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: 
 +<code> 
 +parted /dev/sda mklabel gpt
 </code> </code>
  
-You should see your boot drive, which we don't have to touch. We want to find the slabs filesystem. For example, on my VPS the filesystem is /dev/sda. You can tell because it shows the disk model as "SLAB" or has 256GB of storage.+This will create the GPT on /dev/sda. 
 + 
 +Now, you're going to create the actual partition. To do this, run the following command:
  
-Step 3) Run 
 <code> <code>
-$ sudo fdisk /dev/sda # or whatever filesystem your slab is in +parted /dev/sda mkpart primary 0% 100%
- +
-Welcome to fdisk (util-linux 2.33.1). +
-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>
  
-Step 4) Type the letter **g** to create a new GPT partition table. +This will create a partition using the entire slab's storage capacity. 
- +
-Step 5) Type the letter **n** to create a new partition. Use the default partition letter and sectors by pressing enter. +
- +
-Step 6) You can now quit fdisk by typing the letter **w** to write the new changes to the slab and quit.+
  
 +**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>
-$ sudo fdisk /dev/sda+$ sudo lsblk -o name,vendor,model,size 
 +NAME   VENDOR   MODEL             SIZE 
 +sda    BUYVM    SLAB                250G 
 +└─sda1 
 +sr0    QEMU     QEMU DVD-ROM     1024M 
 +vda    0x1af4                      10G 
 +├─vda1                            9.5G 
 +└─vda2                            512M
  
-Welcome to fdisk (util-linux 2.33.1). +</code>
-Changes will remain in memory only, until you decide to write them. +
-Be careful before using the write command.+
  
  
-Command (m for help): g +**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  
-Created a new GPT disklabel (GUID: ECA757E9-5304-594C-A9CA-17E061B2E516). +<code> 
-The old dos signature will be removed by a write command. +mkfs.ext4 /dev/sda1
- +
-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> </code>
  
-Step 7) Run fdisk -l again to see what the new partition is. +This might take a few seconds depending on the size of your slab.
-<code> +
-$ fdisk -l +
-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 +**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.
-/dev/vda1  *        2048 39843455 39841408  19G 83 Linux +
-/dev/vda2       39843456 41940607  2097152   1G 82 Linux swap / Solaris+
  
 +First, you need to determine the slab's UUID. You can do that by running: 
 +<code>blkid</code>
  
-Disk /dev/sda: 256 GiB, 274877906944 bytes, 536870912 sectors +In this case, the device you're looking for is /dev/sda1. The line should look like:  
-Disk model: SLAB +<code>/dev/sda1: UUID="1cb43a43-105c-46f1-9d7f-1c736c10ffdf" TYPE="ext4"</code>
-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 +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: 
-/dev/sda1        2048 536870911 536868864  256G 83 Linux+<code> 
 +UUID=1cb43a43-105c-46f1-9d7f-1c736c10ffdf /mnt/slab ext4 defaults 0 0
 </code> </code>
  
-You should be able to see a new partition on the bottom. We want to keep note of the device, for example, mine is /dev/sda1. +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.
- +
-Step 8) Now we can mount the slab. Either run <code>sudo mount /dev/sda1 /mnt/slab # FOR TEMPORARY MOUNT</code> or edit /etc/fstab with your favorite text editor for permanent mount.+
  
 <code> <code>
Line 125: Line 91:
 # swap was on /dev/vda2 during installation # swap was on /dev/vda2 during installation
 UUID=a1103972-6b3e-49d1-ac18-d6bf16ea0f68 none            swap    sw              0       0 UUID=a1103972-6b3e-49d1-ac18-d6bf16ea0f68 none            swap    sw              0       0
-# Your slab goes here, as always replace /dev/sda1 with your slabs filesystem. +#SLAB 
-/dev/sda1 /mnt/slab ext4 defaults 0 0+UUID=1cb43a43-105c-46f1-9d7f-1c736c10ffdf /mnt/slab ext4 defaults 0 0
 </code> </code>
  
-Step 9) Run+ 
 +**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> <code>
-mkfs.ext4 /dev/sda1 (or whatever your slab is)+mkdir /mnt/slab/
 </code> </code>
-This will format the drive and make it EXT4 
  
-Step 10) Run df -h to check if the drive has been correctly formatted. If it has you should be able to see your slab. It will say 0G used for you, but I'm already using my slab.+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> <code>
 $ df -h $ df -h
 Filesystem      Size  Used Avail Use% Mounted on Filesystem      Size  Used Avail Use% Mounted on
-udev            474M     0  474M   0% /dev +[...] 
-tmpfs            98M   11M   88M  11% /run +/dev/sda1       251G  81M   250G 1% /mnt/slab 
-/dev/vda1        19G   16G  2.4G  87% / +[...]
-tmpfs           490M     0  490M   0% /dev/shm +
-tmpfs           5.0M     0  5.0M   0% /run/lock +
-tmpfs           490M     0  490M   0% /sys/fs/cgroup +
-/dev/sda1       251G  221G   18G  93% /mnt/slab +
-tmpfs            98M  4.0K   98M   1% /run/user/0+
 </code> </code>
  
-You can now use your slab for whatever you'd like! Such as storing backups or many other things!+ 
 +===== 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 
 + 
 + 
slab.1619300680.txt.gz · Last modified: 2021/04/24 14:44 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