{"id":8774,"date":"2020-06-12T16:26:22","date_gmt":"2020-06-12T13:26:22","guid":{"rendered":"https:\/\/unihost.com\/help\/?p=8774"},"modified":"2023-01-19T13:58:26","modified_gmt":"2023-01-19T10:58:26","slug":"repartitioning-a-cloud-vps-after-an-upgrade","status":"publish","type":"post","link":"https:\/\/unihost.com\/help\/repartitioning-a-cloud-vps-after-an-upgrade\/","title":{"rendered":"Repartitioning a KVM VPS after an upgrade"},"content":{"rendered":"\n<p><\/p>\n\n\n<p><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">When you upgrade your&nbsp;<span class=\"caps\">VPS<\/span>, you might need to repartition your storage space. Here are the steps to<span class=\"widont\">&nbsp;<\/span>follow.<\/span><\/p>\n<pre><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\"><strong>Repartitioning could permanently damage your data.&nbsp;<span class=\"caps\">We<\/span>&nbsp;cannot be held responsible for any loss or damage to your data. Before doing anything, make sure you back up all of your data.<\/strong><\/span><\/pre>\n<p><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\"><!--more--><\/span><\/p>\n<h4 id=\"requirements\"><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">Requirements<\/span><\/h4>\n<ul>\n<li><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">You must have&nbsp;<span class=\"caps\">SSH<\/span>&nbsp;access to the&nbsp;<span class=\"caps\">VPS<\/span>&nbsp;(root<span class=\"widont\">&nbsp;<\/span>access).<\/span><\/li>\n<li><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">You need to reboot the VPS in <a href=\"https:\/\/unihost.com\/help\/activating-rescue-mode-on-cloud-vps\/\">rescue<span class=\"widont\">&nbsp;<\/span>mode<\/a>.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">Following an upgrade, the&nbsp;<span class=\"caps\">RAM<\/span>&nbsp;and processor (<span class=\"caps\">CPU<\/span>) will automatically be adjusted. This won\u2019t systematically be the case for the storage<span class=\"widont\">&nbsp;<\/span>space.<\/span><\/p>\n<pre><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\"><strong>This guide explains the steps you need to follow to increase your storage<span class=\"widont\">&nbsp;<\/span>space<\/strong>.<\/span><\/pre>\n<p><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">Attempting to extend a partition can lead to a loss of data. It is therefore&nbsp;<strong>strongly recommended<\/strong>&nbsp;that you back up the data on your<span class=\"widont\">&nbsp;<\/span><span class=\"caps\">VPS<\/span>.<\/span><\/p>\n<h4 id=\"unmount-the-partition\"><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">Unmount the partition<\/span><\/h4>\n<p><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">After logging in to your&nbsp;<span class=\"caps\">VPS<\/span> in <a href=\"https:\/\/unihost.com\/help\/activating-rescue-mode-on-cloud-vps\/\">rescue<span class=\"widont\">&nbsp;<\/span>mode<\/a>, your partition will automatically be mounted. In order to resize it, you will need to unmount it. If you know the name of your partition, you can skip the following step. If you don\u2019t know the name of your partition, use the following<span class=\"widont\">&nbsp;<\/span>command:<\/span><\/p>\n<pre><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\"><strong># lsblk<\/strong><\/span><\/pre>\n<p><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">The partition corresponding to rescue mode will be the one mounted in the \/ directory, which is actually the system root. In contrast, the partition of your&nbsp;<span class=\"caps\">VPS<\/span>&nbsp;will probably be placed in the directory associated with \/mnt, or not mounted at<span class=\"widont\">&nbsp;<\/span>all.<\/span><\/p>\n<pre><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\"><strong>NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT\nsda 254:0 <span class=\"m\">0<\/span> 10G <span class=\"m\">0<\/span> disk\n\u2514\u2500sda1 254:1 <span class=\"m\">0<\/span> 10G <span class=\"m\">0<\/span> part \/\nsdb 254:16 <span class=\"m\">0<\/span> 25G <span class=\"m\">0<\/span> disk\n\u2514\u2500sdb1 254:17 <span class=\"m\">0<\/span> 25G <span class=\"m\">0<\/span> part \/mnt\/sdb1<\/strong><\/span><\/pre>\n<p><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">To unmount your partition, use the following<span class=\"widont\">&nbsp;<\/span>command:<\/span><\/p>\n<pre><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\"><strong># umount \/dev\/sdb1<\/strong><\/span><\/pre>\n<h4 id=\"check-the-filesystem\"><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">Check the filesystem<\/span><\/h4>\n<p><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">After unmounting the partition, you should check the filesystem <strong>filesystem check<\/strong>&nbsp;to see if there are errors in the partition. The command is as<span class=\"widont\">&nbsp;<\/span>follows:<\/span><\/p>\n<pre><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\"><strong># e2fsck -yf \/dev\/sdb1\n\ne2fsck 1.42.9 <span class=\"o\">(<\/span>4-Feb-2014<span class=\"o\">)<\/span>\nPass 1: Checking inodes, blocks, and sizes\nPass 2: Checking directory structure\nPass 3: Checking directory connectivity\nPass 4: Checking reference counts\nPass 5: Checking group summary information\n\/dev\/sdb1: 37870\/1310720 files <span class=\"o\">(<\/span>0.2% non-contiguous<span class=\"o\">)<\/span>, 313949\/5242462 blocks<\/strong><\/span><\/pre>\n<pre><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\"><strong>If you receive a&nbsp;bad magic number in superblock&nbsp;error, do not proceed. A procedure to fix this issue is given at the end of this&nbsp;guide.<\/strong><\/span><\/pre>\n<h4 id=\"launch-the-fdisk-application\"><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">Launch the fdisk<span class=\"widont\">&nbsp;<\/span>application<\/span><\/h4>\n<p><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">If the filesystem check is completed successfully, launch the&nbsp;<strong>fdisk<\/strong>&nbsp;application. In the settings, you need to enter the name of the disk and not the name of the partition. For instance, if your partition is&nbsp;<strong>sdb1<\/strong>&nbsp;instead of&nbsp;<strong>vdb1<\/strong>, the disk name will be<em><strong><span class=\"widont\">&nbsp;<\/span>\/dev\/sdb<\/strong><\/em>.<\/span><\/p>\n<pre><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\"><strong># fdisk -u \/dev\/sdb<\/strong><\/span><\/pre>\n<pre><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\"><strong>This application has several sub-commands, which you can view with the command&nbsp;m.<\/strong><\/span><\/pre>\n<h4 id=\"delete-the-old-partition\"><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">Delete the old<span class=\"widont\">&nbsp;<\/span>partition<\/span><\/h4>\n<p><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">Before deleting the old partition, it is recommended that you write down the number corresponding to the first sector of the partition. You can find this information through the command&nbsp;<strong>p<\/strong>. The information is listed under the&nbsp;<strong>Start<\/strong>&nbsp;field. Save this data for<span class=\"widont\">&nbsp;<\/span>later.<\/span><\/p>\n<pre><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\"><strong>Command <span class=\"o\">(<\/span>m <span class=\"k\">for<\/span> <span class=\"nb\">help<\/span><span class=\"o\">)<\/span>: p\n\nDisk \/dev\/sdb: 21.5 GB, <span class=\"m\">21474836480<\/span> bytes\n<span class=\"m\">54<\/span> heads, <span class=\"m\">49<\/span> sectors\/track, <span class=\"m\">15851<\/span> cylinders, total <span class=\"m\">41943040<\/span> sectors\n<span class=\"nv\">Units<\/span> <span class=\"o\">=<\/span> sectors of <span class=\"m\">1<\/span> * <span class=\"nv\">512<\/span> <span class=\"o\">=<\/span> <span class=\"m\">512<\/span> bytes\nSector size <span class=\"o\">(<\/span>logical\/physical<span class=\"o\">)<\/span>: <span class=\"m\">512<\/span> bytes \/ <span class=\"m\">512<\/span> bytes\nI\/O size <span class=\"o\">(<\/span>minimum\/optimal<span class=\"o\">)<\/span>: <span class=\"m\">512<\/span> bytes \/ <span class=\"m\">512<\/span> bytes\nDisk identifier: 0x000132ff\n\nDevice Boot Start End Blocks Id System\n\/dev\/sdb1 * *2048* <span class=\"m\">41941745<\/span> <span class=\"m\">20969849<\/span> <span class=\"m\">83<\/span> Linux<\/strong><\/span><\/pre>\n<pre><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\"><strong>If you haven\u2019t backed up your data, this is the point of no return.<\/strong><\/span><\/pre>\n<p><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">Then delete the partition with the command&nbsp;<strong>d<\/strong>.<\/span><\/p>\n<pre><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\"><strong>Command <span class=\"o\">(<\/span>m <span class=\"k\">for<\/span> <span class=\"nb\">help<\/span><span class=\"o\">)<\/span>: d\nSelected partition 1<\/strong><\/span><\/pre>\n<p><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">The single partition will automatically be<span class=\"widont\">&nbsp;<\/span>deleted.<\/span><\/p>\n<h4 id=\"create-a-new-partition\"><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">Create a new<span class=\"widont\">&nbsp;<\/span>partition<\/span><\/h4>\n<p><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">You now need to create a new partition with the command&nbsp;<strong>n<\/strong>. It is recommended that you use the default<span class=\"widont\">&nbsp;<\/span>values.<\/span><\/p>\n<pre><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\"><strong>Command <span class=\"o\">(<\/span>m <span class=\"k\">for<\/span> <span class=\"nb\">help<\/span><span class=\"o\">)<\/span>: n\nPartition type:\np primary <span class=\"o\">(<\/span><span class=\"m\">0<\/span> primary, <span class=\"m\">0<\/span> extended, <span class=\"m\">4<\/span> free<span class=\"o\">)<\/span>\ne extended\nSelect <span class=\"o\">(<\/span>default p<span class=\"o\">)<\/span>: p\nPartition number <span class=\"o\">(<\/span>1-4, default 1<span class=\"o\">)<\/span>: 1\nFirst sector <span class=\"o\">(<\/span>2048-41943039, default 2048<span class=\"o\">)<\/span>: 2048\nLast sector, +sectors or +size<span class=\"o\">{<\/span>K,M,G<span class=\"o\">}<\/span> <span class=\"o\">(<\/span>2048-41943039, default 41943039<span class=\"o\">)<\/span>: 41943039.<\/strong><\/span><\/pre>\n<p><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">On the&nbsp;<strong>First sector<\/strong>&nbsp;line, check that the default value is the same as the one you have previously written down. If it is different, use the value you have written<span class=\"widont\">&nbsp;<\/span>down.<\/span><\/p>\n<h4 id=\"making-the-partition-bootable\"><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">Making the partition<span class=\"widont\">&nbsp;<\/span>bootable<\/span><\/h4>\n<p><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">You now need to ensure that the partition is bootable. You can do this using the command&nbsp;<strong>a<\/strong>.<\/span><\/p>\n<pre><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\"><strong>Command <span class=\"o\">(<\/span>m <span class=\"k\">for<\/span> <span class=\"nb\">help<\/span><span class=\"o\">)<\/span>: a\n\nPartition number <span class=\"o\">(<\/span>1-4<span class=\"o\">)<\/span>: 1<\/strong><\/span><\/pre>\n<p><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">Save your changes and exit the application with the command&nbsp;<strong>w<\/strong>:<\/span><\/p>\n<pre><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\"><strong>Command <span class=\"o\">(<\/span>m <span class=\"k\">for<\/span> <span class=\"nb\">help<\/span><span class=\"o\">)<\/span>: w\n\nThe partition table has been altered!\n\nCalling ioctl<span class=\"o\">()<\/span> to re-read partition table.\nSyncing disks.<\/strong><\/span><\/pre>\n<h4 id=\"extending-the-filesystem-on-the-partition\"><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">Extending the filesystem on the<span class=\"widont\">&nbsp;<\/span>partition<\/span><\/h4>\n<p><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">The partition has been extended, but the filesystem still occupies the same space as before. To extend it, simply enter the following<span class=\"widont\">&nbsp;<\/span>command:<\/span><\/p>\n<pre><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\"><strong># resize2fs \/dev\/sdb1\n\nresize2fs 1.42.9 <span class=\"o\">(<\/span>4-Feb-2014<span class=\"o\">)<\/span>\nResizing the filesystem on \/dev\/sdb1 to <span class=\"m\">5242624<\/span> <span class=\"o\">(<\/span>4k<span class=\"o\">)<\/span> blocks.\nThe filesystem on \/dev\/sdb1 is now <span class=\"m\">5242624<\/span> blocks long.<\/strong><\/span><\/pre>\n<h4 id=\"check-the-results\"><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">Check the results<\/span><\/h4>\n<p><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">In order to check if the extension has been successful, you can mount the newly created partition and verify its<span class=\"widont\">&nbsp;<\/span>size.<\/span><\/p>\n<pre><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\"><strong># mount \/dev\/sdb1 \/mnt<\/strong><\/span><\/pre>\n<pre><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\"><strong># df -h\n\nFilesystem Size Used Avail Use% Mounted on\n\/dev\/sda1 991M 793M 132M 86% \/\nnone 4.0K <span class=\"m\">0<\/span> 4.0K 0% \/sys\/fs\/cgroup\nudev 1.9G 12K 1.9G 1% \/dev\ntmpfs 386M 360K 386M 1% \/run\nnone 5.0M <span class=\"m\">0<\/span> 5.0M 0% \/run\/lock\nnone 1.9G <span class=\"m\">0<\/span> 1.9G 0% \/run\/shm\nnone 100M <span class=\"m\">0<\/span> 100M 0% \/run\/user\n\/dev\/sdb1 50G 842M 48G 2% \/mnt<\/strong><\/span><\/pre>\n<p><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">You will find the new partition size listed below the label&nbsp;<strong>size<\/strong>.<\/span><\/p>\n<h4 id=\"how-do-i-fix-a-bad-magic-number-in-superblock-error\"><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">How do I fix a&nbsp;<em>bad magic number in superblock<\/em><span class=\"widont\">&nbsp;<\/span>error?<\/span><\/h4>\n<p><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">If the command&nbsp;<strong>e2fsck<\/strong>&nbsp;returns the error message&nbsp;<strong>bad magic number in superblock<\/strong>, you should check and repair the filesystem by using a backup of the superblock. To see which backups of the superblock are available, enter the following<span class=\"widont\">&nbsp;<\/span>command:<\/span><\/p>\n<div>\n<pre><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\"><strong># dumpe2fs \/dev\/sdb1 | grep superblock\n\nPrimary superblock at 0, Group descriptors at 1-6\nBackup superblock at 32768, Group descriptors at 32769-32774\nBackup superblock at 98304, Group descriptors at 98305-98310\nBackup superblock at 163840, Group descriptors at 163841-163846\nBackup superblock at 229376, Group descriptors at 229377-229382\nBackup superblock at 294912, Group descriptors at 294913-294918\nBackup superblock at 819200, Group descriptors at 819201-819206\nBackup superblock at 884736, Group descriptors at 884737-884742\nBackup superblock at 1605632, Group descriptors at 1605633-1605638\nBackup superblock at 2654208, Group descriptors at 2654209-2654214\nBackup superblock at 4096000, Group descriptors at 4096001-4096006\nBackup superblock at 7962624, Group descriptors at 7962625-7962630\nBackup superblock at 11239424, Group descriptors at 11239425-11239430\nBackup superblock at 20480000, Group descriptors at 20480001-20480006\nBackup superblock at 23887872, Group descriptors at 23887873-23887878<\/strong><\/span><\/pre>\n<p><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\">Then use the first superblock backup to check and repair the<span class=\"widont\">&nbsp;<\/span>filesystem:<\/span><\/p>\n<pre><span style=\"font-family: Ubuntu, sans-serif; font-size: 12pt;\"><strong># fsck -b <span class=\"m\">32768<\/span> \/dev\/sdb1<\/strong><\/span><\/pre>\n<p><\/p>\n<\/div>\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>When you upgrade your&nbsp;VPS, you might need to repartition your storage space. Here are the steps to&nbsp;follow. Repartitioning could permanently damage your data.&nbsp;We&nbsp;cannot be held responsible for any loss or damage to your data. Before doing anything, make sure you back up all of your data.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[595],"tags":[596],"class_list":["post-8774","post","type-post","status-publish","format-standard","hentry","category-kvm-en","tag-cloud-vps"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v26.3 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Repartitioning a KVM VPS after an upgrade - Unihost.FAQ<\/title>\n<meta name=\"description\" content=\"When you upgrade your VPS, you might need to repartition your storage space. Here are the steps to follow. - Unihost.FAQ\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/unihost.com\/help\/repartitioning-a-cloud-vps-after-an-upgrade\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Repartitioning a KVM VPS after an upgrade - Unihost.FAQ\" \/>\n<meta property=\"og:description\" content=\"When you upgrade your VPS, you might need to repartition your storage space. Here are the steps to follow. - Unihost.FAQ\" \/>\n<meta property=\"og:url\" content=\"https:\/\/unihost.com\/help\/repartitioning-a-cloud-vps-after-an-upgrade\/\" \/>\n<meta property=\"og:site_name\" content=\"Unihost.FAQ\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/unihost\/\" \/>\n<meta property=\"article:published_time\" content=\"2020-06-12T13:26:22+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-01-19T10:58:26+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/unihost.com\/help\/minio.php?.\/unihost-logo-alt.png\" \/>\n\t<meta property=\"og:image:width\" content=\"250\" \/>\n\t<meta property=\"og:image:height\" content=\"141\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Unihost Support\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@unihost\" \/>\n<meta name=\"twitter:site\" content=\"@unihost\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Unihost Support\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/unihost.com\/help\/repartitioning-a-cloud-vps-after-an-upgrade\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/unihost.com\/help\/repartitioning-a-cloud-vps-after-an-upgrade\/\"},\"author\":{\"name\":\"Unihost Support\",\"@id\":\"https:\/\/unihost.com\/help\/#\/schema\/person\/bb5ae95f38577c920e6a7507888b715a\"},\"headline\":\"Repartitioning a KVM VPS after an upgrade\",\"datePublished\":\"2020-06-12T13:26:22+00:00\",\"dateModified\":\"2023-01-19T10:58:26+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/unihost.com\/help\/repartitioning-a-cloud-vps-after-an-upgrade\/\"},\"wordCount\":620,\"publisher\":{\"@id\":\"https:\/\/unihost.com\/help\/#organization\"},\"keywords\":[\"Cloud VPS\"],\"articleSection\":[\"03. KVM VPS\"],\"inLanguage\":\"en\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/unihost.com\/help\/repartitioning-a-cloud-vps-after-an-upgrade\/\",\"url\":\"https:\/\/unihost.com\/help\/repartitioning-a-cloud-vps-after-an-upgrade\/\",\"name\":\"Repartitioning a KVM VPS after an upgrade - Unihost.FAQ\",\"isPartOf\":{\"@id\":\"https:\/\/unihost.com\/help\/#website\"},\"datePublished\":\"2020-06-12T13:26:22+00:00\",\"dateModified\":\"2023-01-19T10:58:26+00:00\",\"description\":\"When you upgrade your VPS, you might need to repartition your storage space. Here are the steps to follow. - Unihost.FAQ\",\"breadcrumb\":{\"@id\":\"https:\/\/unihost.com\/help\/repartitioning-a-cloud-vps-after-an-upgrade\/#breadcrumb\"},\"inLanguage\":\"en\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/unihost.com\/help\/repartitioning-a-cloud-vps-after-an-upgrade\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/unihost.com\/help\/repartitioning-a-cloud-vps-after-an-upgrade\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Unihost\",\"item\":\"https:\/\/unihost.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Help\",\"item\":\"https:\/\/unihost.com\/help\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Repartitioning a KVM VPS after an upgrade\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/unihost.com\/help\/#website\",\"url\":\"https:\/\/unihost.com\/help\/\",\"name\":\"Unihost.FAQ\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/unihost.com\/help\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/unihost.com\/help\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/unihost.com\/help\/#organization\",\"name\":\"Unihost\",\"alternateName\":\"Unihost\",\"url\":\"https:\/\/unihost.com\/help\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en\",\"@id\":\"https:\/\/unihost.com\/help\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/unihost.com\/help\/minio.php?2026\/01\/minio.png\",\"contentUrl\":\"https:\/\/unihost.com\/help\/minio.php?2026\/01\/minio.png\",\"width\":300,\"height\":300,\"caption\":\"Unihost\"},\"image\":{\"@id\":\"https:\/\/unihost.com\/help\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/unihost\/\",\"https:\/\/x.com\/unihost\",\"https:\/\/www.instagram.com\/unihost\/?hl=en\",\"https:\/\/www.linkedin.com\/company\/unihost-com\",\"https:\/\/www.youtube.com\/channel\/UCITKsxMDnslQY8brN3advgw\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/unihost.com\/help\/#\/schema\/person\/bb5ae95f38577c920e6a7507888b715a\",\"name\":\"Unihost Support\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en\",\"@id\":\"https:\/\/unihost.com\/help\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/a0c9db17c2a0d93e8a0d5ac123f8c5db750ad4d3d5657369c0c4e480f5af77b8?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/a0c9db17c2a0d93e8a0d5ac123f8c5db750ad4d3d5657369c0c4e480f5af77b8?s=96&d=mm&r=g\",\"caption\":\"Unihost Support\"},\"sameAs\":[\"https:\/\/unihost.com\/\"],\"url\":\"https:\/\/unihost.com\/help\/author\/support\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Repartitioning a KVM VPS after an upgrade - Unihost.FAQ","description":"When you upgrade your VPS, you might need to repartition your storage space. Here are the steps to follow. - Unihost.FAQ","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/unihost.com\/help\/repartitioning-a-cloud-vps-after-an-upgrade\/","og_locale":"en_US","og_type":"article","og_title":"Repartitioning a KVM VPS after an upgrade - Unihost.FAQ","og_description":"When you upgrade your VPS, you might need to repartition your storage space. Here are the steps to follow. - Unihost.FAQ","og_url":"https:\/\/unihost.com\/help\/repartitioning-a-cloud-vps-after-an-upgrade\/","og_site_name":"Unihost.FAQ","article_publisher":"https:\/\/www.facebook.com\/unihost\/","article_published_time":"2020-06-12T13:26:22+00:00","article_modified_time":"2023-01-19T10:58:26+00:00","og_image":[{"width":250,"height":141,"url":"https:\/\/unihost.com\/help\/minio.php?.\/unihost-logo-alt.png","type":"image\/png"}],"author":"Unihost Support","twitter_card":"summary_large_image","twitter_creator":"@unihost","twitter_site":"@unihost","twitter_misc":{"Written by":"Unihost Support","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/unihost.com\/help\/repartitioning-a-cloud-vps-after-an-upgrade\/#article","isPartOf":{"@id":"https:\/\/unihost.com\/help\/repartitioning-a-cloud-vps-after-an-upgrade\/"},"author":{"name":"Unihost Support","@id":"https:\/\/unihost.com\/help\/#\/schema\/person\/bb5ae95f38577c920e6a7507888b715a"},"headline":"Repartitioning a KVM VPS after an upgrade","datePublished":"2020-06-12T13:26:22+00:00","dateModified":"2023-01-19T10:58:26+00:00","mainEntityOfPage":{"@id":"https:\/\/unihost.com\/help\/repartitioning-a-cloud-vps-after-an-upgrade\/"},"wordCount":620,"publisher":{"@id":"https:\/\/unihost.com\/help\/#organization"},"keywords":["Cloud VPS"],"articleSection":["03. KVM VPS"],"inLanguage":"en"},{"@type":"WebPage","@id":"https:\/\/unihost.com\/help\/repartitioning-a-cloud-vps-after-an-upgrade\/","url":"https:\/\/unihost.com\/help\/repartitioning-a-cloud-vps-after-an-upgrade\/","name":"Repartitioning a KVM VPS after an upgrade - Unihost.FAQ","isPartOf":{"@id":"https:\/\/unihost.com\/help\/#website"},"datePublished":"2020-06-12T13:26:22+00:00","dateModified":"2023-01-19T10:58:26+00:00","description":"When you upgrade your VPS, you might need to repartition your storage space. Here are the steps to follow. - Unihost.FAQ","breadcrumb":{"@id":"https:\/\/unihost.com\/help\/repartitioning-a-cloud-vps-after-an-upgrade\/#breadcrumb"},"inLanguage":"en","potentialAction":[{"@type":"ReadAction","target":["https:\/\/unihost.com\/help\/repartitioning-a-cloud-vps-after-an-upgrade\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/unihost.com\/help\/repartitioning-a-cloud-vps-after-an-upgrade\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Unihost","item":"https:\/\/unihost.com\/"},{"@type":"ListItem","position":2,"name":"Help","item":"https:\/\/unihost.com\/help\/"},{"@type":"ListItem","position":3,"name":"Repartitioning a KVM VPS after an upgrade"}]},{"@type":"WebSite","@id":"https:\/\/unihost.com\/help\/#website","url":"https:\/\/unihost.com\/help\/","name":"Unihost.FAQ","description":"","publisher":{"@id":"https:\/\/unihost.com\/help\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/unihost.com\/help\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en"},{"@type":"Organization","@id":"https:\/\/unihost.com\/help\/#organization","name":"Unihost","alternateName":"Unihost","url":"https:\/\/unihost.com\/help\/","logo":{"@type":"ImageObject","inLanguage":"en","@id":"https:\/\/unihost.com\/help\/#\/schema\/logo\/image\/","url":"https:\/\/unihost.com\/help\/minio.php?2026\/01\/minio.png","contentUrl":"https:\/\/unihost.com\/help\/minio.php?2026\/01\/minio.png","width":300,"height":300,"caption":"Unihost"},"image":{"@id":"https:\/\/unihost.com\/help\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/unihost\/","https:\/\/x.com\/unihost","https:\/\/www.instagram.com\/unihost\/?hl=en","https:\/\/www.linkedin.com\/company\/unihost-com","https:\/\/www.youtube.com\/channel\/UCITKsxMDnslQY8brN3advgw"]},{"@type":"Person","@id":"https:\/\/unihost.com\/help\/#\/schema\/person\/bb5ae95f38577c920e6a7507888b715a","name":"Unihost Support","image":{"@type":"ImageObject","inLanguage":"en","@id":"https:\/\/unihost.com\/help\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/a0c9db17c2a0d93e8a0d5ac123f8c5db750ad4d3d5657369c0c4e480f5af77b8?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/a0c9db17c2a0d93e8a0d5ac123f8c5db750ad4d3d5657369c0c4e480f5af77b8?s=96&d=mm&r=g","caption":"Unihost Support"},"sameAs":["https:\/\/unihost.com\/"],"url":"https:\/\/unihost.com\/help\/author\/support\/"}]}},"_links":{"self":[{"href":"https:\/\/unihost.com\/help\/wp-json\/wp\/v2\/posts\/8774","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/unihost.com\/help\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/unihost.com\/help\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/unihost.com\/help\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/unihost.com\/help\/wp-json\/wp\/v2\/comments?post=8774"}],"version-history":[{"count":39,"href":"https:\/\/unihost.com\/help\/wp-json\/wp\/v2\/posts\/8774\/revisions"}],"predecessor-version":[{"id":10354,"href":"https:\/\/unihost.com\/help\/wp-json\/wp\/v2\/posts\/8774\/revisions\/10354"}],"wp:attachment":[{"href":"https:\/\/unihost.com\/help\/wp-json\/wp\/v2\/media?parent=8774"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/unihost.com\/help\/wp-json\/wp\/v2\/categories?post=8774"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/unihost.com\/help\/wp-json\/wp\/v2\/tags?post=8774"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}