So slavealloc says it's enabled and I rm the error.flg from the foopy but watcher.log reports errors on start up: 'failed_pxe_booting' log snippet: 03/06/2014 16:35:03: DEBUG: Request GET http://mobile-imaging/api/device/panda-0357/state/... 03/06/2014 16:35:03: INFO: Starting new HTTP connection (1): mobile-imaging 03/06/2014 16:35:03: DEBUG: "GET /api/device/panda-0357/state/ HTTP/1.1" 200 31 03/06/2014 16:35:03: DEBUG: Status code: 200 03/06/2014 16:35:03: ERROR: Mozpool state is 'failed_pxe_booting' Not sure what to do. Will try to restart but if not in Mozpool, I don't know if I can.

I could not get past 'failed_pxe_booting' I found https://wiki.mozilla.org/ReleaseEngineering/How_To/Android_Tegras#How_to_deal_with_failing_pandas_in_mozpool which discusses 'failed_pxe_booting' and suggests at least opening a DC ops bug. /me changes product component on this bug.

I re-ran the self-test and host was able to complete. It is not in the "ready" state. entering state ready 2014-03-07T15:47:06 syslog selftest.py[INFO]: test_mmc_register[PASSED] oemid : 0x5344 2014-03-07T15:47:06 syslog selftest.py[INFO]: test_mmc_register[PASSED] preferred_erase_size : 4194304 2014-03-07T15:47:06 syslog selftest.py[INFO]: test_mmc_register[PASSED] scr : 0235800300000000 2014-03-07T15:47:06 syslog selftest.py[INFO]: test_mmc_register[PASSED] serial : 0x068b0ef9 2014-03-07T15:47:06 syslog selftest.py[INFO]: test_mmc_register[INFO] Ending diagnostic test 2014-03-07T15:47:06 syslog selftest.py[INFO]: Finished selftest.py

FYI - I did not replace the SD card.