pongo2g Posted December 1, 2015 Posted December 1, 2015 HI, i get the failure "***warning - bad CRC, using default environment" and the system don't boot. I tested it with an banana pi, cubieboard2 and olimex A20 Olinux Lime2 and all the same failure. Of course with the specific image. I flashed the image with ubuntu 14.04 lts (no virtual maschine) with dd bs=1M if=filename.raw of=/dev/sdb. I using the direkt letter of the drive sdb and not the specific partition sdb1. The windows flash tool dont works, i get an error when click on "copy", whats that, missing framework? What i make wrong?
Igor Posted December 1, 2015 Posted December 1, 2015 BADCRC is ok: http://www.denx.de/wiki/view/DULG/WarningBadCRCUsingDefaultEnvironment What is your hardware?
pongo2g Posted December 1, 2015 Author Posted December 1, 2015 Hi, i use banana pi, cubieboard2 and olimex A20 Olinux Lime2 and how can i set the saveenv? It don't react on keyboard.
Igor Posted December 1, 2015 Posted December 1, 2015 I don't understand what are you doing wrong. First you need to use a proper image - some images might work on non dedicated hw some not. If it stuck on u-boot it's possible that your SD card is invalid, was not written properly, some strange device is attached to USB, ... If you can't type, your USB keyboard might not be supported by u-boot,
jimandroidpc Posted January 17, 2017 Posted January 17, 2017 I had a similar bad crc error after I was updating my working banana pro with the Micro Home Server install script. The installation of Syncthing failed, and on a reboot after the system froze, it said the same as what his does..
Igor Posted January 17, 2017 Posted January 17, 2017 I had a similar bad crc error after I was updating my working banana pro with the Micro Home Server install script. The installation of Sync thing failed, and on a reboot after the system froze, it said the same as what his does.. Bad CRC within bootloader is not an bug. This is some other problem ... it's possible that apt-get upgrade (which is conduced prior to install on that script) was broken during kernel upgrade and you ended up with not boot-able system. Without more detailed data, screenshot, initial image version, ... I can only guess. Check this.
jimandroidpc Posted January 17, 2017 Posted January 17, 2017 Have a Samsung Evo 32gb microsd card, I believe the error did occur during the apt-get upgrade part of the install. I did fsck the sd card on my laptop and no errors found I set it up so long ago and it was so stable I dont remember much of what I had to do...Looks like I copied the sdcard to the hdd for booting too.. Luckily all data is on the HDD but Id like to learn to fix it if possible to increase my linux knowledge, PCs arent my day job - medicine is... Since I copied the "OS" from the sdcard to the HDD, could I somehow just go back to boot from the SD card?
Recommended Posts