Hi
A brief history at first. I've had several problems with making my Bunny Quack after upgrading from 1.0 to 1.3 last week. After the upgrade, nothing was written on screen. Payloads executed as I could see LED's changing color, but nothing was written. Have tried both Windows 10 and Ubuntu 17.
Well, i then decided to reset my Bunny using the 3 pull-out method. After getting back to 1.0_167 I couldn't mount the Bunny in arming mode on Linux, as it complained about a .git file / folder (from the GitBunnyGit payload). On Windows I could mount the Bunny, and was able to Quack again.
When SSH'ing into the Bunny it showed the ".git" file / folder thingy, but I was unable to remove it, as I received: "cannot remove .git input/output error" (not exactly, but that wording. I then did the restore again, but this has only made matters worse...
On Windows and Linux I get the Bunny mounted, but not under the "BashBunny" name, but a generic drive letter, and the drive is empty! No files, nothing!
Tried to place a 1.1 upgrade file on there and reboot in arming mode, but the bunny flashes red/blue a few times, then reboots in arming mode. I also tried creating the folder structure as well as an version.txt containing 1.0_167. Still the same.
I then used the serial console to access the bunny, from which I can no longer mount the nandf system:
root@bunny:~# mount -o sync /dev/nandf /root/udisk/
mount: wrong fs type, bad option, bad superblock on /dev/nandf,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
So.... How do I get back to square one? Completely restore this thing? Or somehow recreate the udisk filesystem.... As of now the BB is an expensive 2GB usb drive, and not much more :S
Thanks