search

drinkcat / chroagh

Chromium OS Archlinux Chroot Environment
BSD 3-Clause "New" or "Revised" License
241 stars 27 forks source link

Only 2G on my Arch #51

Open Jzarecta opened 10 years ago

Jzarecta commented 10 years ago

I wonder if people can advice me how to extend the memory of my Chromebook HP 14. I am on a 16GB HD but when I put chroagh only shows 2GB. I have a complex partition table which involves up to 12 different partitions.

If anyone is related with this setup can anyone advice me how to add more space. (I could mount/nuke one of these partitions are mount it as home?).

I dont want to touch it since they are label as ChromeOS partitions, but it seems a bit odd they are triplicated. Hopefully some chromebook expert can explain me why all those partitions and their porpouse.

drinkcat commented 10 years ago

Can you post the output of df and cgpt show /dev/sda?

Jzarecta commented 10 years ago

This is my partition

Disk identifier: 05F6321C-2C6C-A74A-9CCE-BE1945FE7702

Device Start End Size Type /dev/sda1 8671232 14434303 2.8G Microsoft basic data /dev/sda2 20480 53247 16M ChromeOS kernel /dev/sda3 4476928 8671231 2G ChromeOS root fs <-- I am here /dev/sda4 53248 86015 16M ChromeOS kernel /dev/sda5 282624 4476927 2G ChromeOS root fs <-- I have no idea whats this for? /dev/sda6 14434304 14467071 16M ChromeOS kernel /dev/sda7 14467072 31244287 8G ChromeOS root fs <--- I want to use this /dev/sda8 86016 118783 16M Microsoft basic data /dev/sda9 16450 16450 512B ChromeOS reserved /dev/sda10 16451 16451 512B ChromeOS reserved /dev/sda11 64 16447 8M unknown /dev/sda12 249856 282623 16M EFI System

my cgpt is as follows: cgpt show /dev/sda start size part contents 0 1 PMBR (Boot GUID: 3CAC10CD-7500-C3F4-0000-000000000000) 1 1 Pri GPT header 2 32 Pri GPT table 8671232 5763072 1 Label: "STATE" Type: Linux data UUID: 8F2B012B-660C-1C47-AAFE-2E8290AC1993 20480 32768 2 Label: "KERN-A" Type: ChromeOS kernel UUID: 099F0931-A639-7647-9E32-CDEEBD3FCCAE Attr: priority=0 tries=0 successful=0 4476928 4194304 3 Label: "ROOT-A" Type: ChromeOS rootfs UUID: 7BD8F2E9-51F4-F54E-A33B-3FFE73E32794 53248 32768 4 Label: "KERN-B" Type: ChromeOS kernel UUID: B51DC991-B153-6F46-B3D1-A99405E5A5EC Attr: priority=0 tries=0 successful=0 282624 4194304 5 Label: "ROOT-B" Type: ChromeOS rootfs UUID: 63CCE246-2DA6-4A4D-B4FA-660A7A5E65CB 14434304 32768 6 Label: "KERN-C" Type: ChromeOS kernel UUID: D0E854DB-9700-5D41-954F-DB0ABB0BE4CB Attr: priority=0 tries=0 successful=0 14467072 16777216 7 Label: "ROOT-C" Type: ChromeOS rootfs UUID: F5CEA87C-DA2C-DD40-99D6-FF2EFF8340BE 86016 32768 8 Label: "OEM" Type: Linux data UUID: DCD6DC9A-F952-7944-8C7E-25C10ECC5A36 16450 1 9 Label: "reserved" Type: ChromeOS reserved UUID: FA386655-F6C7-E54A-8C90-E27EFED9759E 16451 1 10 Label: "reserved" Type: ChromeOS reserved UUID: 3A6727B9-0A21-F041-97CE-CDCA41C07609 64 16384 11 Label: "RWFW" Type: ChromeOS firmware UUID: D23424A2-6D75-E74E-B1F1-90D327939C40 249856 32768 12 Label: "EFI-SYSTEM" Type: EFI System Partition UUID: 255B4DFF-A503-6341-B345-B2EE828B3034 31277199 32 Sec GPT table 31277231 1 Sec GPT header

drinkcat commented 10 years ago

It appears that you installed Chrubuntu at some point.

The easiest way to recover your partition table is to burn a recovery USB disk, and restore your system (that'll wipe everything, so backup your chroot first).

Alternatively, you could mount ROOT-C//dev/sda7 to a location of your choice and install crouton on that (you'll need to mount the partition on every boot).

Otherwise, you can also restore your partition table what you'd need to do is (I let you figure out the details):

Jzarecta commented 10 years ago

No I didnt, I tried to install Arch directly as dualboot. Which used /dev/sda7 as a root partition. https://wiki.archlinux.org/index.php/HP_Chromebook_14#Create_Filesystem_and_BIOS_Partition

However due to lack of drivers I decided to use this script to get arch through crouton, however the live partition is a very small 2GB partition, I would like to take out all the rest of the partitions and use my HD to the max. But I am not sure if I would nuke critical partitions for chromeOS.

UPDATE: I have bigger problems trying to move /usr/ to sda7 and basically bricked my Chromebook. I havent been able to restore to machine state even using the recovery image: https://support.google.com/chromebook/answer/6002417

I wont be able to go ahead with these steps until I have recovered chromeos effectively, however my original question still is active. I want to know what are those partitions used for and why are they needed by ChromeOS.

Regards.

drinkcat commented 10 years ago

No I didnt, I tried to install Arch directly as dualboot. Which used /dev/sda7 as a root partition.

Oh, ok. The "symptoms" are the same.

However due to lack of drivers I decided to use this script to get arch through crouton, however the live partition is a very small 2GB partition, I would like to take out all the rest of the partitions and use my HD to the max. But I am not sure if I would nuke critical partitions for chromeOS.

Have a look at my last post. KERN-C/ROOT-C are not needed by Chromium OS. The rest is (see http://www.chromium.org/chromium-os/chromiumos-design-docs/disk-format).

UPDATE: I have bigger problems trying to move /usr/ to sda7 and basically bricked my Chromebook. I havent been able to restore to machine state even using the recovery image: https://support.google.com/chromebook/answer/6002417

Oh, that should really not happen. What exactly have you tried? Are you getting any error message?