New emonSD release: emonSD-26Oct17 :tada:

pb66 · 2017-11-25T15:08:24.555Z

Sorry you guys are having trouble installing the latest image, I have notified @glyn.hudson (he maintains the emonSD images) you are having issues, but haven’t heard back yet, but I’m sure he will take a look at it asap.

glyn.hudson · 2017-11-27T18:06:16.411Z

Hi Guys,

I’ve managed to test today. I downloaded the Oct17 image from the download link and checked the MD5, it matches the md5 on the download page.

I flashed the image to a couple of 8GB Kingston sd card using dd and Etcher (…very impressed with Etcher, very slick indeed).

I tested both SD card in a RasPi 3, both booted up fine. I’m sorry I have been unable to replicate the issue

The Oct17 image on the download link certainly works…at least for me! We used the same image in the factory for shop purchase assembled emonBase /emonPi

Any ideas how we can try and debug this further, it’s very strange that a number of users have reported issues.

Exangel · 2017-11-27T21:27:12.362Z

Hi,

I’ve done it once again.
The checksum of the img seems to be correct. I use this time Etcher instead of dd command and I still get the same error at the end.

Could it be because of the fash disk itself ? I have also a sandisk ultra 16Go.

no other clue …

rbrt · 2017-11-27T22:10:06.079Z

I’ve only been testing on SanDisk cards so far, I think it’s probably worth trying a different brand to eliminate that as a possible cause. Unfortunately I only have SanDisk cards here at home but might be able to find something different at work tomorrow to try.

Nolan_Garrett · 2017-11-27T22:28:11.543Z

rbrt:

I’ve only been testing on SanDisk cards so far

I’ve tested with a 4GB Transcend card (the one that came with the original emonPi) and a 16GB Kingston card. Both fail to successfully boot. I am going to pull down the image, md5 it again, then image it to the 4GB Transcend to test once more.

EDIT: Tried again, same problem. Used Etcher and also validated the MD5, which was correct. Also, I can apparently no longer add replies to this topic since I’ve hit a limit of 3 replies for new users. I guess I will just keep editing this post?

@glyn.hudson what do you see for output of fdisk -l on the Oct17 image? Mine still shows this, which I really think has to indicate the problem:

Disk emonSD-26Oct17.img: 3.6 GiB, 3838837248 bytes, 7497729 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0003ea3e

Device Boot Start End Sectors Size Id Type
emonSD-26Oct17.img1 * 8192 131071 122880 60M 6 FAT16
emonSD-26Oct17.img2 131072 7288831 7157760 3.4G 83 Linux
emonSD-26Oct17.img3 7288832 14786559 7497728 3.6G 83 Linux

The fact that the third partition shows a size much larger than the expected 4GB SD card size seems like an issue worth investigating?

Robert.Wall · 2017-11-27T23:24:15.246Z

Nolan_Garrett:

Also, I can apparently no longer add replies to this topic since I’ve hit a limit of 3 replies for new users. I guess I will just keep editing this post?

Hopefully that’s fixed - I’ve raised your Trust by one level.

Nolan_Garrett · 2017-11-27T23:36:28.177Z

That seems to have worked! It made me do a password reset and activation (I’d been using the “Sign in With Google” option), but it’s all good. Thank you!

glyn.hudson · 2017-11-28T17:19:08.393Z

Ok, I think I’ve managed to find and solve the issue. The issue was that there was a lot of free space at end of the third partition included in the image file. This was no problem when flashing the image back onto the same model of SD card that the image was created on (as I was doing) since the image fit perfectly. However if using a different brand of SD card the actual size of an 8GB card can vary causing the image not to boot correctly.

This Gparted screen shots illustrate the issue:

emonSD-compare1085×790 143 KB

I’ve trimmed the third partition to be 1GB, this should allow the image to easily fit on any 8GB SD card and reduce the size.

Selection_1461081×343 43.7 KB

Once the RasPi has booted image it’s possible to run $ sudo emonSDexpand to expand the third /data partition to fill the available SD card size. The third data partition is the RW partition (mounted in /home/pi/data) where Emoncms logging data is stored.

~~I’ve uploaded a the cut down version of emonSD-26Oct to test: slim-emonSD-26Oct.zip.~~

Update: This ‘sim’ image is now the standard image, please download using the normal URL: emonSD pre built SD card Download & Change Log · openenergymonitor/emonpi Wiki · GitHub

Please download the new and report experience on the thread. If all goes well this version will replace the standard emonSD-26Oct download.

md5sum:

slim-emonSD-26Oct17.img: 88f8ff9a5f7bc0e9b07012895a5cdd95
slim-emonSD-26Oct17.img.zip: 6726564f379d0127052e8c30a3ffa534

This post explains the issue well: How to trim disk images to partition size | Linux M0nk3ys

Nolan_Garrett · 2017-11-28T18:40:56.339Z

glyn.hudson:

this should allow the image to easily fit on any 8GB SD card

Awesome, I am going to try this in a few moments! I am assuming from this note above that the new standard minimum emonSD storage size will be 8GB, up from the 4GB minimum.

Nolan_Garrett · 2017-11-28T19:16:40.397Z

Looks like I can confirm this boots! I’ll mess with it later today and ensure the whole image is working, but the boot was successful, so I think we’ve found the root cause of that problem. Thank you, @glyn.hudson for your work on this! I’ll post back if I find any other problems as I am setting it up.

Exangel · 2017-11-28T21:28:24.271Z

glyn.hudson:

88f8ff9a5f7bc0e9b07012895a5cdd95

It seems to work also on my side. It’s booting right now.
It should be fine then.
Thanks.

glyn.hudson · 2017-11-29T03:37:13.515Z

Nolan_Garrett:

minimum emonSD storage size will be 8GB, up from the 4GB minimum.

Correct. It has been realistically 8GB for the Nov16 release also once the image is expanded to a usable size.

Nolan_Garrett:

Looks like I can confirm this boots! I’ll mess with it later today and ensure the whole image is working, but the boot was successful, so I think we’ve found the root cause of that problem. Thank you, @glyn.hudson for your work on this! I’ll post back if I find any other problems as I am setting it up.

Exangel:

It seems to work also on my side. It’s booting right now.

It should be fine then.

Thanks.

Excellent. I will make the this ‘slim’ image the new emonSD-26Oct17 image download. The download link above will stop working. Please use the normal emonSD-26Oct17 download link: emonSD pre built SD card Download & Change Log · openenergymonitor/emonpi Wiki · GitHub

garzak · 2017-11-29T17:03:21.858Z

OK! Thanks.
Now it works. I was able to install on a 64GB ScanDisk microSD card.

rbrt · 2017-11-30T07:50:38.342Z

I can also confirm that the new image works fine as well on my SanDisk cards, thanks @glyn.hudson

garzak · 2017-12-07T17:34:58.807Z

Well… I have now another problem:

when i do the “emonSDexpand” the raspberry reboots and then stays very slow and nothing works! I cant enter emoncms etc…
after the comand (sudo emonSDexpand) i get a warning: “Re-reading the partition table failed”

Does anyone gets the same?

garzak · 2017-12-07T18:21:52.553Z

When I try to enter emoncms I get:
“Can’t connect to database, please verify credentials/configuration in settings.php
Error message: **Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)”

garzak · 2017-12-07T18:35:44.005Z

After running the comand “sudo systemctl status mysql.service -l”
I get:
● mysql.service - LSB: Start and stop the mysql database server daemon
Loaded: loaded (/etc/init.d/mysql)
Active: failed (Result: exit-code) since Thu 2017-12-07 18:07:11 WET; 27min ago
Process: 3877 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE)

Dec 07 18:07:11 emonpi mysql[3877]: df: ‘/home/pi/data/mysql/.’: No such file or directory
Dec 07 18:07:11 emonpi mysql[3877]: /etc/init.d/mysql: ERROR: The partition with /home/pi/data/mysql is too full! … failed!
Dec 07 18:07:11 emonpi /etc/init.d/mysql[3897]: ERROR: The partition with /home/pi/data/mysql is too full!
Dec 07 18:07:11 emonpi systemd[1]: mysql.service: control process exited, code=exited status=1
Dec 07 18:07:11 emonpi systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Dec 07 18:07:11 emonpi systemd[1]: Unit mysql.service entered failed state.

And this is how much:
df -hlx tmpfs
Filesystem Size Used Avail Use% Mounted on
/dev/root 3.4G 2.0G 1.2G 63% /
devtmpfs 481M 0 481M 0% /dev
/dev/mmcblk0p1 60M 22M 39M 37% /boot
/dev/mmcblk0p3 11G 39M 11G 1% /home/pi/data

The microSD is of 16GB and the image is brand new!

garzak · 2017-12-07T18:57:39.287Z

Just realised now, that I have to mount:
sudo mount /dev/mmcblk0p3 /home/pi/data
and then start the mysql service again to solve the problem each time the raspberry pi reboots!
Crazy!

pb66 · 2017-12-07T19:03:29.991Z

Not if it is defined in /etc/fstab, then it will mount at boot.

you should have a line there something like

/dev/mmcblk0p3 /home/pi/data ext2 defaults,rw,noatime,nodiratime,errors=remount-ro 0 2

garzak · 2017-12-08T19:20:14.656Z

Thanks!
Dont know why, but that line was with # (comented!)