imperador / chromefy

Project Croissant: Install Chrome OS on any Computer - Transforming Chromium to Chrome
GNU General Public License v3.0
880 stars 80 forks source link

how do you resize data partition? #77

Closed chanhyokpark closed 4 years ago

chanhyokpark commented 5 years ago

I run chromefy.sh successfully and I installed chromium.img at my USB, but the installer doesn't work so I have to use dd command. it worked, but I have only 4gb data partition. what is the data partition in CrOS and how do you fix it?

Screenshot 2019-06-24 at 7 02 35 AM - Display 1 (sorry I'm korean)

chanhyokpark commented 5 years ago

I used GParted and succeed, but is there another solution?

dragon788 commented 5 years ago

You can't be booted into the ChromeOS you are fixing the STATE partition for (aka user data), but if you are booted from the Chromefy USB you can use a couple tools on the disk to resize or delete the STATE partition and recreate/extend it to fill the rest of the disk. I've found it is easier to delete and recreate, mostly because I'm also editing the size of the ROOT-A partition and having the STATE partition out of the way makes that a lot easier.

To view the partitions in the order they exist on disk you can use this command cgpt show -q /dev/sda | sort. This only shows the "types" and not the labels, but if you just run cgpt show /dev/sda you can see the labels as well.

Then you can use fdisk /dev/sda and p to print the partitions again to see the numbers that fdisk cares about. The STATE partition should be 1, so you can hit d to delete a partition, and then 1 to delete this partition, then I choose to hit w to write these changes. At some point you will get a prompt about removing/keeping the metadata (I think the label/filesystem type), you should choose the option to keep it. Then I hit n for new partition, and 1 to give it the ID that ChromeOS expects, and then hit w again to write out the changes which may automatically quit, otherwise you can type q to quit. The last thing we need to do is put a filesystem back into this partition, so we can mkfs.ext4 /dev/sda1 and it will put the right filesystem in place so when you reboot into ChromeOS and login and you should see a lot more available space. If you don't login and try to check it from Guest Mode you'll see an incorrect number, because Guest sessions are limited to a small amount that doesn't get to interact with the whole disk.