Raspberry pi Wheezy no longer possible to connect about soliscloud2pvoutput HOT 2 CLOSED

Seemed there was an unexpected system reboot at 23:30 and thereafter it came no longer online:

Jul 27 23:30:30 rickpi shutdown[2459]: shutting down for system reboot
Jul 27 23:54:05 rickpi shutdown[3653]: shutting down for system halt
Jul 28 00:00:56 rickpi shutdown[2490]: shutting down for system halt
Jul 28 00:01:52 rickpi shutdown[2329]: shutting down for system halt
Jul 28 00:02:52 rickpi shutdown[2333]: shutting down for system halt

Jul 27 23:17:19 rickpi kernel: [ 19.188315] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Jul 27 23:17:21 rickpi kernel: [ 20.521690] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Jul 27 23:30:49 rickpi kernel: [ 19.990648] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Jul 27 23:54:47 rickpi kernel: [ 30.814285] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Jul 28 00:00:09 rickpi kernel: [ 371.859129] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Jul 28 00:01:16 rickpi kernel: [ 20.104538] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

last syslog message at Jul 27 23:17:19:
Jul 27 23:17:02 rickpi /USR/SBIN/CRON[18952]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)

Because I could not connect remotely, I had to attach monitor and keyboard to the pi directly. There I could see there was a problem with the boot partition: FAT-fs (mmcblk0p1) Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

However, on Wheezy fixing this was not possible. I did check the SDCard on a Windows 10 machine and repaired it there. Thereafter the pi was able to boot normally.

I expect there was a small power dip at Jul 27 23:17, but not sure about that. So for now I keep this issue open and see over time.

from soliscloud2pvoutput.

Root cause was a SDCard with write errors. In the end I bought a new SDCard and reinstalled the latest Raspberry pi version, because Wheezy was no longer supported. For safety I now exit SolisCloud2PVOutput outside 5-23 hours and only start it once at 5:02 or at reboot in crontab.

from soliscloud2pvoutput.