doing the image build and noticed this.... wazzit mean?

[Deidre]

Pending 5, Ready 4, Running 0, Retrying 0, Total 314 [Time 17m47.5s
Load 1.79 1.75 1.67]
Started chromeos-base/chromeos-chrome-9.0.600.0 (logged in /tmp/
chromeos-chrome-9.0.600.0-yCexsG)
Pending 5, Ready 3, Running 1, Retrying 0, Total 314 [Time 17m52.5s
Load 1.72 1.73 1.67]
Pending 5, Ready 3, Running 1, Retrying 0, Total 314 [Time 17m57.5s
Load 1.67 1.72 1.66]
=== Start output for job chromeos-chrome-9.0.600.0 (0m11.2s) ===
chromeos-chrome-9.0.600.0: >>> Emerging binary (1 of 1) chromeos-base/
chromeos-chrome-9.0.600.0 from chromiumos for /home/isadora/trunk/src/
build/images/x86-generic/0.9.131.2010_12_08_0012-a1/rootfs/
chromeos-chrome-9.0.600.0: * chromeos-chrome-9.0.600.0.tbz2 MD5 SHA1
size ;-) ... [ ok ]
chromeos-chrome-9.0.600.0: * CPV: chromeos-base/chromeos-
chrome-9.0.600.0
chromeos-chrome-9.0.600.0: * REPO: chromiumos
chromeos-chrome-9.0.600.0: * USE: autotest build_tests chrome_debug
chrome_remoting elibc_glibc kernel_linux tests_desktopui_BrowserTest
tests_desktopui_PyAutoFunctionalTests
tests_desktopui_SyncIntegrationTests tests_desktopui_UITest
userland_GNU x86
chromeos-chrome-9.0.600.0:
chromeos-chrome-9.0.600.0: bunzip2: Data integrity error when
decompressing.
chromeos-chrome-9.0.600.0: Input file = /build/x86-generic/packages/
chromeos-base/chromeos-chrome-9.0.600.0.tbz2, output file = (stdout)
chromeos-chrome-9.0.600.0:
chromeos-chrome-9.0.600.0: It is possible that the compressed file(s)
have become corrupted.
chromeos-chrome-9.0.600.0: You can use the -tvv option to test
integrity of such files.
chromeos-chrome-9.0.600.0:
chromeos-chrome-9.0.600.0: You can use the `bzip2recover' program to
attempt to recover
chromeos-chrome-9.0.600.0: data from undamaged sections of corrupted
files.
chromeos-chrome-9.0.600.0:
chromeos-chrome-9.0.600.0: tar: Unexpected EOF in archive
chromeos-chrome-9.0.600.0: tar: Unexpected EOF in archive
chromeos-chrome-9.0.600.0: tar: Error is not recoverable: exiting now
chromeos-chrome-9.0.600.0: !!! Error Extracting '/build/x86-generic/
packages/chromeos-base/chromeos-chrome-9.0.600.0.tbz2'
chromeos-chrome-9.0.600.0: >>> Failed to emerge chromeos-base/chromeos-
chrome-9.0.600.0 for /home/isadora/trunk/src/build/images/x86-generic/
0.9.131.2010_12_08_0012-a1/rootfs/, Log file:
chromeos-chrome-9.0.600.0: >>> '/build/x86-generic/tmp/portage/
chromeos-base/chromeos-chrome-9.0.600.0/temp/build.log'
=== Complete: job chromeos-chrome-9.0.600.0 (0m11.2s) ===
Failed chromeos-base/chromeos-chrome-9.0.600.0 (in 0m11.2s), retrying
later.
Started chromeos-base/chromeos-imageburner-0.0.1-r8 (logged in /tmp/
chromeos-imageburner-0.0.1-r8-sCpREs)
Completed chromeos-base/chromeos-imageburner-0.0.1-r8 (in 0m3.0s)

[Deidre]

BC4A229F-AE54-4647-999A-2FA41C569410
start size part contents
0 1 PMBR (Boot GUID: BC4A229F-
AE54-4647-999A-2FA41C569410)
1 1 Pri GPT header
2 32 Pri GPT table
1794048 2097152 1 Label: "STATE"
Type: Linux data
UUID: DB34DBBE-66FE-A24D-B4F5-
E8B2DB990847
4096 32768 2 Label: "KERN-A"
Type: ChromeOS kernel
UUID: 85A2F8F9-1B41-234F-
AAF3-0E273F6E6E31
Attr: priority=15 tries=15 successful=0
36864 1757184 3 Label: "ROOT-A"
Type: ChromeOS rootfs
UUID: 0C8A249B-E173-B244-AFF2-
D4C2FCFFA9DB
3956736 32768 4 Label: "KERN-B"
Type: ChromeOS kernel
UUID:
EF941C58-434D-924D-96CC-4B747F5E64C5
Attr: priority=0 tries=15 successful=0
3989504 1 5 Label: "ROOT-B"
Type: ChromeOS rootfs
UUID: 8478AC6E-4B70-CE4C-
A6B8-12F6DECF563B
34 1 6 Label: "KERN-C"
Type: ChromeOS kernel
UUID: 12585C0B-5086-4141-
BE3C-1384B6C27FD5
Attr: priority=0 tries=15 successful=0
35 1 7 Label: "ROOT-C"
Type: ChromeOS rootfs
UUID: D78EFEAB-7FE7-184A-A102-
D34F4E2A8CBC
3891200 32768 8 Label: "OEM"
Type: Linux data
UUID: 54ECC971-3252-E34E-
A67F-77C11D0AA481
36 1 9 Label: "reserved"
Type: ChromeOS reserved
UUID: B5885F72-DF4B-0B4B-A58F-
CF573A2C37A2
37 1 10 Label: "reserved"
Type: ChromeOS reserved
UUID: 9E41A1FC-FFD4-7C47-94C1-
E94903A0DA18
38 1 11 Label: "reserved"
Type: ChromeOS reserved
UUID: B620196D-
D1D9-8244-8F6E-9E078F01D338
3923968 32768 12 Label: "EFI-SYSTEM"
Type: EFI System Partition
UUID: BC4A229F-
AE54-4647-999A-2FA41C569410
3989506 32 Sec GPT table
3989538 1 Sec GPT header

[Deidre]

[binary N ] app-portage/gentoolkit-0.3.0_rc10-r1 to /home/isadora/
trunk/src/build/images/x86-generic/0.9.131.2010_12_08_0012-a1/rootfs/
usr/local/ [1]
[binary N ] chromeos-base/gmerge-0.0.1-r52 to /home/isadora/trunk/
src/build/images/x86-generic/0.9.131.2010_12_08_0012-a1/rootfs/usr/
local/ [1]
[binary N ] chromeos-base/minifakedns-0.0.1-r2 to /home/isadora/
trunk/src/build/images/x86-generic/0.9.131.2010_12_08_0012-a1/rootfs/
usr/local/ [1]
[binary N ] dev-python/pycairo-1.8.8 to /home/isadora/trunk/src/
build/images/x86-generic/0.9.131.2010_12_08_0012-a1/rootfs/usr/local/
USE="-doc -examples -svg" [0]
[binary N ] dev-python/pygtk-2.14.1-r1 to /home/isadora/trunk/src/
build/images/x86-generic/0.9.131.2010_12_08_0012-a1/rootfs/usr/local/
USE="-doc -examples -test" [0]
[binary N ] dev-python/pyopenssl-0.10 to /home/isadora/trunk/src/
build/images/x86-generic/0.9.131.2010_12_08_0012-a1/rootfs/usr/local/
USE="-doc" [0]
[binary N ] sys-apps/dmidecode-2.10 to /home/isadora/trunk/src/
build/images/x86-generic/0.9.131.2010_12_08_0012-a1/rootfs/usr/local/
[0]
[binary N ] media-gfx/imagemagick-6.5.8.8-r3 to /home/isadora/
trunk/src/build/images/x86-generic/0.9.131.2010_12_08_0012-a1/rootfs/
usr/local/ USE="X bzip2 corefonts png zlib -autotrace -djvu -doc -fftw
-fontconfig -fpx -graphviz -gs -hdri -jbig -jpeg -jpeg2k -lcms -lqr -
nocxx -openexr -openmp -perl -q32 -q8 -raw -svg -tiff -truetype -wmf -
xml" [1]
[binary N ] chromeos-base/chromeos-dev-0.1.0-r30 to /home/isadora/
trunk/src/build/images/x86-generic/0.9.131.2010_12_08_0012-a1/rootfs/
usr/local/ USE="X hardened opengl" [1]

[Deidre]

Error mounting: mount: wrong fs type, bad option, bad superblock on /
dev/sdb3,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or


the other two main mount points work on the usb but not the c-root?