Chromium OS 'Your system is repairing itself" and restarts without end.

Zach Hembree

unread,

Apr 9, 2013, 6:56:18 PM4/9/13

to chromium-...@chromium.org

A few days ago I imaged Chromium to a flash drive so I could try it on my old notebook. It did boot, but it only went as far as the "Your system is repairing itself" screen and restarted. I thought there might be an issue in booting from USB so I duplicated the drive in a Ubuntu livecd, and it's still the same. Any help would be appreciated. Thanks.

Gateway M675 Specs

Chipset : 865PE

CPU: Pentium 4 @ 3.00GHz

RAM: 1GB - PC3200 (one module)

GPU: ATI Radeon 9600 64MB

HDD: IDE/PATA 60GB

Networking: Broadcom BCM94306/Intel 82547EI

Zach Hembree

unread,

Apr 9, 2013, 7:02:44 PM4/9/13

to chromium-...@chromium.org

EDIT

A few days ago I imaged Chromium to a flash drive so I could try it on my old notebook. It did boot, but it only went as far as the "Your system is repairing itself" screen and restarted. I thought there might be an issue in booting from USB so I duplicated the drive to the HDD using a Ubuntu livecd, and it's still the same. Any help would be appreciated. Thanks

----------------

By what logic is it a good idea not to allow someone to edit their posts?

Hung-Te Lin

unread,

Apr 10, 2013, 1:56:05 AM4/10/13

to zhemb...@gmail.com, Chromium OS discuss

That may happen if your imaging process was incomplete, or corrupted.

We've seen that on Linux distributions with auto-mount features, or people who did "dd" manually without waiting sync to complete (ex, sync or "oflag=sync").

Can you mount the first (stateful) partition of your flash drive, and see what's inside unencrypted/clobber.log ?

--
--
Chromium OS discuss mailing list: chromium-...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

Zach Hembree

unread,

Apr 12, 2013, 5:54:25 PM4/12/13

to chromium-...@chromium.org

After an few attempted runs on the Gateway laptop I couldn't seem to locate the stateful partition, but after I tried it with a newer Sony VAIO I found one. That failed to get past repair as well, but it actually began the repair, and on the other it rebooted almost immediately after the repair screen appeared.

Clobber log

2013/04/10 01:23:28 UTC (repair): /dev/sdb1 Self-repair corrupted stateful partition

dumpe2fs 1.42 (29-Nov-2011)

dumpe2fs: Bad magic number in super-block while trying to open /dev/sdb1

Couldn't find valid filesystem superblock.

-- File system /dev/sdb1 block data (gz+base64):

H4sIABC/ZFEAA+3BMQEAAADCoPVPbQhfoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

AAAAAAAAAAAAAAAAAAAAPgMc6jinAAAQAA==

-- File system /dev/sdb1 block data dump complete.

2013/04/10 01:23:28 UTC (preserve log): /sbin/clobber-state keepimg

2013/04/10 01:28:34 UTC (restore log): /sbin/clobber-state keepimg

Zach Hembree

unread,

Apr 12, 2013, 6:01:41 PM4/12/13

to chromium-...@chromium.org

Is it me or does it look like the imaging was corrupted? I was using a 16GB Sandisk Cruzer (SDCZ36).

Hung-Te Lin

unread,

Apr 15, 2013, 12:09:19 AM4/15/13

to Zach Hembree, Chromium OS discuss

"Couldn't find valid filesystem superblock."

Yes your image on USB stick is corrupted.

Try to re-image with image_to_usb.sh command, and disable all auto-mount features on your Linux box.

On Sat, Apr 13, 2013 at 6:01 AM, Zach Hembree <zhemb...@gmail.com> wrote:

Is it me or does it look like the imaging was corrupted? I was using a 16GB Sandisk Cruzer (SDCZ36).

--

Anirudh Bhat

unread,

Jun 26, 2013, 6:45:47 PM6/26/13

to chromium-...@chromium.org

Dude i used the same pen drive and got the same error

julis

unread,

Jun 27, 2013, 8:36:58 AM6/27/13

to chromium-...@chromium.org

I do not think that this is a usb flash drive problem. With the same USB flash drive boots ok on eeepc1000, but with the same USB flash drive on very old acer travelmate it shows "Your system is repairing itself"

Hung-Te Lin

unread,

Jun 27, 2013, 11:34:37 PM6/27/13

to jul...@gmail.com, Chromium OS discuss

Whenever you see "system is repairing", please wait it to finish (and probably reboots),

unplug the USB stick to your desktop, mount partition one (ext3/ext4), find a file "unencrypted/clobber.log" and look at its contents.

That file may contain information for why you see the repair screen.

Mike Frysinger

unread,

Jun 28, 2013, 12:04:12 AM6/28/13

to Hung-Te Lin, jul...@gmail.com, Chromium OS discuss

i wonder if we should make this process similar to the firmware/recovery ? there, can't you generally hit tab to have it show you details of why it's in the state that it is ? seems like we get this question enough (even comes up sometimes at Google) that having such a shortcut would speed up the triage process ?

-mike

--

Hung-Te Lin

unread,

Jun 28, 2013, 12:22:18 AM6/28/13

to Mike Frysinger, Chromium OS discuss

That's a good idea... it may be not easy to hook TAB, but we can show the detail reasons in Ctrl-Alt-F2 console -- although user may see corrupted progress bar after that.

Mike Frysinger

unread,

Jun 28, 2013, 12:31:49 AM6/28/13

to Hung-Te Lin, Chromium OS discuss

i've filed http://crbug.com/255324 to track

-mike

Justin Buser

unread,

Aug 19, 2014, 9:48:07 AM8/19/14

to chromium-...@chromium.org

I'm having the same problem, on several older Panasonic Toughbooks, it has nothing to do with the drive your using if it's the same issue I'm dealing with.

I've tracked it down to the mount-encrypted binary, which crashes(throws "Illegal Instruction") when mount_var_and_home_chronos is called from chromeos_startup.

It seems to be something to do with random number generation, as it breaks after RAND_bytes is called from cryptohome/mount-encrypted.c

Anyway, FYI...

Mike Frysinger

unread,

Aug 19, 2014, 10:16:59 AM8/19/14

to justin...@gmail.com, Chromium OS discuss

what CPU does your laptop have, and what build exactly are you using ?

-mike

Wonhyuk Cho

unread,

May 20, 2016, 4:52:55 PM5/20/16

to Chromium OS discuss, justin...@gmail.com

I have exactly a same problem

J Seed

unread,

Nov 19, 2016, 6:35:21 AM11/19/16

to Chromium OS discuss

Was there ever a solution to this?

I have the same problem on a Pentium M CPU Netbook

Rody Mens

unread,

Jan 7, 2017, 9:36:33 AM1/7/17

to Chromium OS discuss

I have also the same problem. I'm booting with plop manager to acces the usb ports on this laptop which is so old that you can't boot from usb ports in the BIOS.

Then I look up the usb and it boots. Shows chromium on the screen, then it suddenly says 'repairing' and screen goes black.

Op woensdag 10 april 2013 00:56:18 UTC+2 schreef Zach Hembree:

Reply all

Reply to author

Forward