How to Add a New Disk Larger Than 2TB to An Existing Linux

If You Appreciate What We Do Here On TecMint, You Should Consider:

  1. Stay Connected to: Twitter | Facebook | Google Plus
  2. Subscribe to our email updates: Sign Up Now
  3. Use our Hosting referral link if you planning to start your blog ($3.82/month).
  4. Become a Supporter - Make a contribution via PayPal
  5. Support us by purchasing our premium books in PDF format.
  6. Support us by taking our online Linux courses

We are thankful for your never ending support.

Lakshmi Dhandapani

I work on various platforms including IBM-AIX, Solaris, HP-UX, and storage technologies ONTAP and OneFS and have hands on experience on Oracle Database.

Your name can also be listed here. Got a tip? Submit it here to become an TecMint author.

RedHat RHCE and RHCSA Certification Book
Linux Foundation LFCS and LFCE Certification Preparation Guide

You may also like...

7 Responses

  1. luvr says:

    “By default RHEL/CentOS have Kernel with GPT support, but for Debian/Ubuntu you need to recompile the kernel after changing the config.”

    That will certainly have been true years ago, but it is no longer correct. I have both Ubuntu (first 14.04, now 16.04) and Debian (first 8, now 9 testing), plus Slackware (first 14.1, os 14.2) on my laptop with one 1-TB harddisk that I partitioned using the GPT scheme, and none of these systems has ever had any troubles with GPT.

    In fact, the only minor issue that I encountered was with the LILO bootloader under Slackware 14.1, because it didn’t support being installed onto the boot sector of a GPT partition. Even that got resolved with Slackware 14.2.

    • Lakshmi Dhandapani says:

      @luvr

      Thanks for the comments…As you said this stands true for older versions…New versions come with GPT support…Keep posting your comments

  2. Iulian Murgulet says:

    Hello, one important observation – NEVER/EVER format anything using something like “mkfs.ext4 /dev/xvdd1“.

    The same thing for mounting.

    Use instead of /dev/disk/xvdd1 this /dev/disk/by-id/scsi-SATA_HGST_HDN724040A_PK2238P4XGDZ4A-part1, because:

    -if your HDD/partition if fail, you it is very simple to identify the HDD(in my example, HGST is the manufacturer, HDN724040A is the model of HDD, PK2238P4XGDZ4A is the SerialNumber printed on the HDD label, and part1 is the partition number)

    • if you change the HDD controller, sda, could be sdb, so you will have problems
    • if you have several HDD who are identical (manufacturer, capacity, model) it is very easy to make mistakes
    • if you move the HDDs in another system, you can have probblems (sda -> sdb)

    Anything like this are history if you start to use /dev/disk/by-id. You could see what it is in your system with:

    # ls -l /dev/disk/by-id/
    
  3. Alexey An says:

    Thank you for your article. AFAIK, we can use percent % instead of GB in mkpart command to define a maximum storage size.

    In some cases using % easier than to remember what size of your HDD is. Especially, if it is necessary to install a several HDD’s of various size each one on several servers.

  4. anish says:

    Nice post… Like the hands on approach in the article without delving into too much theory…

Got something to say? Join the discussion.

Your email address will not be published. Required fields are marked *

Join Over 300K+ Linux Users
  1. 257,757
  2. 11,967
  3. 39,682

Are you subscribed?