Recovery/Partition Issues with chrubuntu dual-boot - Chromebook Forum : Google Chromebook Forums
LinkBack Thread Tools
post #1 of 2 (permalink) Old 07-11-2012, 12:54 PM Thread Starter
Junior Member
Join Date: Jul 2012
Posts: 1
Recovery/Partition Issues with chrubuntu dual-boot

Hello and thanks for reading,

I recently installed Chrubuntu 12.04 64 bit on my CR-48 via Jay Lee's script (back when the dev kernel was 64 bit). It worked great and I enjoyed the simple dual boot, so that I could have ChromeOS when I wanted the web and Ubuntu when I wanted other features (e.g., calibre for my e-reader, musescore, editing files on flash drives without uploading them first).

Then I got greedy and decided to give my ubuntu install an extra GB of space to handle its apps; with google drive coming out this made a lot of sense at the time. Unfortunately, I tried using gparted in ubuntu to first resize the /dev/sda5 partition, and when I went to the chrome OS side to attempt to finish the task, I had to recover Chrome OS from a USB stick. The recovery process somehow deactivated my ability to switch to Ubuntu using "sudo cgpt add -i 6 -P 5 -S 1 /dev/sda", and I do not know how to proceed. I am really missing the Ubuntu abilities these days, and the CR-48 is just a netbook and not the laptop I used to have.

Would the recovery process have affected ROOT-C or KERN-C? I do not want to enable the switch to ubuntu, only to find out afterward that the kernel has been affected, or the system is otherwise completely inoperable, though I suppose as long as I can recover back to Chrome OS with my USB stick nothing is really lost (other than time).

Thank you for any and all recommendations; I am hoping for a simple and no-risk solution and will be happy to provide any information that you need to get there. (My alternative is switching the firmware and doing a full ubuntu install, as the lack of a 64-bit kernel in Chrome OS means that I cannot use the old script. I hope to avoid this and keep Chrome OS, as it is quite fun and helpful to have.)

(Note: I just found the following recommendation immediately after partition editing in an old ubuntu install guide.
At this point we should destroy the STATE partition contents, because otherwise at the next boot the startup scripts may notice that it's corrupted and will erase it using the old size (obtained from dumpe2fs) and not the new one. Best to be safe and just zap it now. This will take a couple of minutes to run:

dd if=/dev/zero of=/dev/sda bs=131072 seek=1040 count=47280

This may be where I went wrong with my partition edits, as I did not do this step.)

In case it helps, here are the outputs of parted -l and cgpt show /dev/sda:

parted -l:

Model: ATA SanDisk SSD P4 1 (scsi)
Disk /dev/sda: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
11 32.8kB 8421kB 8389kB RWFW
9 8422kB 8423kB 512B reserved
10 8423kB 8423kB 512B reserved
2 10.5MB 27.3MB 16.8MB KERN-A
4 27.3MB 44.0MB 16.8MB KERN-B
8 44.0MB 60.8MB 16.8MB OEM
12 128MB 145MB 16.8MB fat16 EFI-SYSTEM boot
1 145MB 965MB 820MB ext4 STATE
6 965MB 981MB 16.8MB KERN-C
7 981MB 11.7GB 10.7GB ROOT-C
5 11.7GB 13.9GB 2147MB ext2 ROOT-B
3 13.9GB 16.0GB 2147MB ext2 ROOT-A
Error: /dev/mapper/vroot: unrecognised disk label
Warning: Error fsyncing/closing /dev/mapper/vroot: Input/output error
Retry/Ignore? r
Warning: Error fsyncing/closing /dev/mapper/vroot: Input/output error
Retry/Ignore? i
Model: Linux device-mapper (verity) (dm)
Disk /dev/mapper/vroot: 891MB
Sector size (logical/physical): 4096B/4096B
Partition Table: unknown

cgpt show /dev/sda:

start size part contents
0 1 PMBR (Boot GUID: 44CAE856-3522-E645-B95A-2E829506B7D7)
1 1 Pri GPT header
2 32 Pri GPT table
282624 1601536 1 Label: "STATE"
Type: Linux data
UUID: D3FE12F7-0BE9-1949-AC2E-312A673626C4
20480 32768 2 Label: "KERN-A"
Type: ChromeOS kernel
UUID: FD8DBAD3-B52C-064B-B989-D43D571DF5C8
Attr: priority=1 tries=0 successful=1
27082752 4194304 3 Label: "ROOT-A"
Type: ChromeOS rootfs
53248 32768 4 Label: "KERN-B"
Type: ChromeOS kernel
UUID: D6C832CC-43C3-FB41-BCEB-F5E3E7F11010
Attr: priority=3 tries=0 successful=1
22888448 4194304 5 Label: "ROOT-B"
Type: ChromeOS rootfs
UUID: D174D10B-9CFB-C742-8E7F-14900DDE483A
1884160 32768 6 Label: "KERN-C"
Type: ChromeOS kernel
UUID: DE85139A-1F85-D24D-89AF-475E4545151E
Attr: priority=2 tries=15 successful=1
1916928 20971520 7 Label: "ROOT-C"
Type: ChromeOS rootfs
UUID: 2CA51AEB-A147-944D-AD63-BA03B424CC18
86016 32768 8 Label: "OEM"
Type: Linux data
UUID: B6857F5F-A63B-A542-9BAC-534A0B79B0BF
16450 1 9 Label: "reserved"
Type: ChromeOS reserved
UUID: C52C0A6F-F1B1-5541-9D9D-10ED1AE7A43E
16451 1 10 Label: "reserved"
Type: ChromeOS reserved
UUID: 7F8909B6-0EDD-B34F-88C2-EBEB3D5A6685
64 16384 11 Label: "RWFW"
Type: ChromeOS firmware
UUID: 0F95CA2E-F111-AE47-B769-FDE0EC278923
249856 32768 12 Label: "EFI-SYSTEM"
Type: EFI System Partition
UUID: 44CAE856-3522-E645-B95A-2E829506B7D7
31277199 32 Sec GPT table
31277231 1 Sec GPT header
johnfrye48 is offline  
Sponsored Links
post #2 of 2 (permalink) Old 08-19-2020, 01:44 PM
Junior Member
Join Date: Aug 2020
Posts: 20
Here is your step-by-step guide to installing Linux on your Chromebook using chrx. Before proceeding, double-check your compatibility, ensure Developer Mode is enabled, and that you have an active internet connection.

First up, press CTRL + ALT + T to open the Chrome OS terminal, then input shell

You now need to update the Chromebook firmware to allow legacy booting. Input cd; curl -LO && sudo bash When the firmware update script loads, press 1, then Enter to Install/Update RW_Legacy Firmware.

Once your firmware update completes, input cd ; curl -Os && sh go. Press N to install to your system storage.

Enter the storage size for the Linux partition, then hit Enter. The default installation option, GalliumOS, requires a minimum 3GB storage. Once the installation completes, press Enter to restart your system.

Once your system reboots, you will encounter a message stating, ďYour system is repairing itself. Please wait.Ē As worrying as this sounds, it is perfectly normal. Wait for this to complete. The time it takes depends on your hard drive. For example, I have a 128GB hard drive in my Chromebook, and the process took nearly 20 minutes.

When you arrive at your desktop, open the Chrome OS terminal, input shell, then cd ; curl -Os && sh go to being the second phase of the installation. When the installation finishes, press Enter.

At the boot screen, press CTRL + L to boot into Gallium OS (or an alternative Linux distro).

Apps4Rent | O365CloudExperts | CloudDesktopOnline
TerranceM is offline  

Thread Tools
Show Printable Version Show Printable Version
Email this Page Email this Page

Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

For the best viewing experience please update your browser to Google Chrome