Expanding available storage on your bootable USB

Follow

Comments

7 comments

  • Phil Reilly

    You can easily resize the installer with gparted on a Linux machine.

  • shashank

    gparted created 9.62gb fat32 on my 16gb usb but didn't work. any help?

     update: adding new partition and the above code somehow didn't work. extended the sdb16 from 1.1gb to remaining 9.62gb (in gparted) worked.space increased to 10.6gb

  • Phil Reilly

    Resize NOT create!

  • Jon Thomas

    There seems to be some code missing from that sequence.  I tried to follow it 3 times and it bombs out at the "0700" input point.

     

    I understand that it is supposed to be a command line script for gdisk, but please fill in the blanks so it can work properly.  I would like to try using a 32Gb USB disk as a test bed before installing Chromium on a couple of my computers.

     

    Thanks in advance for any information provided.  Will follow this thread.

  • Phil Reilly

    Just use gparted to drag the slider to its maximum. Click the apply check mark. The partion will be maximized.

  • Armin Wies

    Actually neither gparted (quit with errors) nor this procedure here worked for me at first.

    However, based on this procedure here I was able to expand my STATE-Partition to use all of the free space on my USB-thumb drive.

    What I did not understand:
    Why the procedure describes to delete the first partition, then create the same partition from new...?

    Instead, I deleted the first and also the 16th partition and only created partition 16 from new, using the first block as the former 16th partition and the last block of my former 1st partition.

    I did a sfdisk -l /dev/sdX before, which looked like this:

    Device Start End Sectors Size Type
    /dev/sdc1 11083842 30851038 19767197 9.4G Microsoft basic data
    /dev/sdc2 65 65 1 512B ChromeOS reserved
    /dev/sdc3 66 66 1 512B ChromeOS reserved
    /dev/sdc4 67 67 1 512B ChromeOS reserved
    /dev/sdc5 68 68 1 512B ChromeOS reserved
    /dev/sdc6 69 69 1 512B ChromeOS reserved
    /dev/sdc7 70 70 1 512B ChromeOS reserved
    /dev/sdc8 71 71 1 512B ChromeOS reserved
    /dev/sdc9 72 72 1 512B ChromeOS reserved
    /dev/sdc10 73 73 1 512B ChromeOS reserved
    /dev/sdc11 74 74 1 512B ChromeOS reserved
    /dev/sdc12 75 75 1 512B ChromeOS reserved
    /dev/sdc13 76 76 1 512B ChromeOS reserved
    /dev/sdc14 77 77 1 512B ChromeOS reserved
    /dev/sdc15 78 78 1 512B ChromeOS reserved
    /dev/sdc16 8593474 11083841 2490368 1.2G Microsoft basic data
    /dev/sdc17 20546 53313 32768 16M ChromeOS kernel
    /dev/sdc18 2351170 8593473 6242304 3G ChromeOS root fs
    /dev/sdc19 53314 86081 32768 16M ChromeOS kernel
    /dev/sdc20 2347074 2351169 4096 2M ChromeOS root fs
    /dev/sdc21 16514 16514 1 512B ChromeOS kernel
    /dev/sdc22 16515 16515 1 512B ChromeOS root fs
    /dev/sdc23 86082 2183233 2097152 1G Microsoft basic data
    /dev/sdc24 16516 16516 1 512B ChromeOS reserved
    /dev/sdc25 16517 16517 1 512B ChromeOS reserved
    /dev/sdc26 130 16513 16384 8M unknown
    /dev/sdc27 2314306 2347073 32768 16M EFI System

    when I re-created partition 16, I used 8593474 as start and 30851038 as the end  (I believe that this was pretty much the default). For the rest I followed the instructions above.

    Worked for me in version 61.0.3163.140 (64-bit).

  • Phil Reilly

    This needs to be updated to first run:

    sudo disable_varity

    or bad things will happen especially if you expand the user partition on a separate linux system with gparted.

Please sign in to leave a comment.