I was commissioning a new Intel Edison with a windows PC and the sparkfun base circuit.
At first all was fine, as soon as I connected the two USB ports, I saw the Edison as a drive and got access to the shell (the drivers were already installed on my PC).
I was able to configure the edison name and wifi. I realized the image was not current and started the integrated installer to upgrade it. At some point the installer asked to disconnect the USB port and reconnect it. The process continued with the PC making several times the sound of a device connecting/disconnecting. At some point the installet terminated indicating a failure to upgrade.
Now I am stucked and wonder how to recover.
- The edison is not visible anymore as a drive on the PC.
- The console shell access still works but I received a series of system warnings when I log in (see hereunder)
- Wifi does not work anymore. If i try to run Configure_edison -w , no network is found and I get the message sh: wpa_cli: not foundft
- On the PC device manager I see the Intel SOC - DnX driver and the serial driver. Nothing else pertaining to the Edison.
In other words, the only remaining active link between the Edison and the outside world seems to be serial SSH .
Here is what I see when I log to the root:
Poky (Yocto Project Reference Distro) 1.6 Eduardo ttyMFD2
Eduardo login: root
[ 108.188194] systemd-fsck: fsck.ext2: Bad magic number in super-block while trying to open /dev/mmcblk0p10
[ 108.190719] systemd-fsck: /dev/mmcblk0p10:
[ 108.192756] systemd-fsck: The superblock could not be read or does not describe a correct ext2
[ 108.194928] systemd-fsck: filesystem. If the device is valid and it really contains an ext2
[ 108.196789] systemd-fsck: filesystem (and not swap or ufs or something else), then the superblock
[ 108.201575] systemd-fsck: is corrupt, and you might try running e2fsck with an alternate superblock:
[ 108.203491] systemd-fsck: e2fsck -b 8193 <device>
No directory, logging in with HOME=/