chromeos-install fails on Pixel

[Yufeng Shen]

Starting recently chromeos-install no longer works on Pixel for me.

For example, I am booting from USB key with ChromeOS-test-R34-5205.0.0-link test image,

run chromeos-install --debug

and I got error msg :

+ echo This will install from '/dev/sdb' to '/dev/sda'.

This will install from '/dev/sdb' to '/dev/sda'.

+ echo This will erase all data at this destination: /dev/sda

This will erase all data at this destination: /dev/sda

+ [ 1 -eq 1 ]

+ read -p Are you sure (y/N)?  SURE

Are you sure (y/N)? + [ y != y ]

+ [ -n  ]

+ [ 1 -eq 0 ]

+ [ INTEL = ARM ]

+ dd bs=512 count=1 if=/dev/sdb of=/tmp/gptmbr.bin

1+0 records in

1+0 records out

512 bytes (512 B) copied, 0.000181913 s, 2.8 MB/s

+ [ 1 -eq 1 ]

+ write_base_table /dev/sda /tmp/gptmbr.bin

+ create_image /dev/sda 12406720 512

+ local dev=/dev/sda

+ local min_disk_size=12406720

+ local block_size=512

+ [ -b /dev/sda ]

+ dd if=/dev/zero of=/dev/sda conv=notrunc bs=512 count=32

dd: writing '/dev/sda': Input/output error

1+0 records in

0+0 records out

0 bytes (0 B) copied, 0.00106192 s, 0.0 kB/s

+ cleanup_on_failure

+ set +e

+ echo Running a hw diagnostics test -- this might take a couple minutes.

Running a hw diagnostics test -- this might take a couple minutes.

+ badblocks -sv /dev/sda

+ tee /tmp/hardware_diagnostics.log

Checking blocks 0 to 31266647

Checking for bad blocks (read-only test): 0

1

2

3

....

key information here

+ dd if=/dev/zero of=/dev/sda conv=notrunc bs=512 count=32

dd: writing '/dev/sda': Input/output error

shows that dd can't open /dev/sda at all.

Does anyone know what's the problem ?

Thanks,

---- Yufeng Shen

[Vincent Palatin]

the Sandisk iSSD ...

is it a PVT/MP machine or an older proto ?

on previous proto, the iSSD firmware and PHY settings have known issues.

if that's a mass prod machine, maybe gwendal@ is interested by your machine ?

[Yufeng Shen]

I have tried 2 machines one is DVT and the other is DVT2.

They were working a few weeks ago and suddenly stop working this week.

Also if I put in a recovery image it works, only that if I chromeos-install from a test image it fails.

[Chris Sosa]

Did you do any adjust part modifications to the test image? Those can sometimes cause issues in chromeos-install

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

[Yufeng Shen]

I was playing with test image built by myself with adjust part. But I also tried downloaded test image ChromeOS-test-R34-5205.0.0-link

which should have the default layout.

[Gwendal Grignou]

"dd: writing '/dev/sda': Input/output error" is indeed not good.

Interestingly, reading from the device seems fine: "write_base_table /dev/sda /tmp/gptmbr.bin" worked fine.

Can you open a bug a share the system logs, in particular /var/log/messages? 

I also need the output of 'mount' 

[use generate_logs to get these 2]

and the output of

for i in  /sys/block/sd* ; do echo -n "$i: " ; cat $i/device/model ; done

Thanks,

Gwendal.

[Yufeng Shen]

bug filed  https://code.google.com/p/chromium/issues/detail?id=332465

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-d...@chromium.org.

[Chris Sosa]

As another data point, I tried to re-create your problem (since I had made somewhat recent changes to chromeos-install a few weeks back) but no luck. I just tried on an MP Pixel with a more recent canary test image (R34-5208.0.0) and it installed through fine with chromeos-install.

[Gwendal Grignou]

As Vincent mentioned, there is a SATA link error:

 ata1: SError: { Proto TrStaTrns UnrecFIS }

It looks after that the link can not be re-established so the kernel offline the device.

Your only hope is to power cycle the machine and try again.

From Vincent message, it should not happen with PVT machines.