“The problem with the new firmware appears to be syntax related; “commit=120” on the line for the data volume in /etc/fstab is the issue. Reading from here: Ext2/Ext3 File System it looks like you are trying to use an EXT3 feature on an EXT2 filesystem, so removing the argument from /etc/fstab should have 0 effect (other than allowing the new 4.4 kernel to boot fully).”
which makes sense given that if I remove the commit line the thing boots again, and that is has gone from the version of FSTAB on GITHUB. Assuming I can get Samba to work again I have a working update which is way less work than rolling a new image.
I’ll now have another dig in case there is anything else that has changed between versions before I play with images again. From memory the image I made up from the build guide was pretty close to the released image which is why I didn’t change to it.
Ah yes, the fstab in the emonpi repo is symlinked to /etc/fstab on the 08May16 image:
I’m not sure if this is the case with yours, probably not.
Yes this issue was brought to my attention and commit=120 was removed from the current emonpi fstab.
If you did want to use the new image you could just disable the emonPiLCD service from running, this would ensure the GPIO pin was not used. But I can understand that moving to a different image is more work than quickly fixing your current one! Nice work tracking down the issue