This is an interesting idea and pretty cool to try and safeguard against SD 
failure. I know Tom has a Raspberry Pi weewx test running for 4+ years - 
but personally I can't seem to keep my class 10 SD cards working longer 
than a year or 18 months. Maybe I have too much logging turned on :) 

What if there's a power failure? Do you have to babysit the BerryBoot to 
boot to the NAS correctly or can you automate that?


On Friday, June 14, 2019 at 8:21:47 AM UTC-4, Peter_F wrote:
>
> Just thought I would share the following in case anyone else is 
> interested...
>
> Up until a few months ago I was running weewx on a Raspberry Pi but with 
> the following three directories mounted from an NFS share on a Synology NAS:
>
> /var/lib/weewx
> /usr/share/weewx
> /etc/weewx
>
> This basically kept the weewx configs and SQLite3 database off the SD 
> Card.  My main reason for doing this was just in case the SD Card died.  I 
> could rebuild a new one, install weewx again and mount the same directories 
> and everything should be back to normal with nothing lost.  This all worked 
> very well and I never had any problems.
>
> A few months ago I decided to take it a step further.  I discovered a 
> Raspberry Pi bootloader called BerryBoot (
> https://www.berryterminal.com/doku.php/berryboot).  It's main purpose is 
> to allow you to have multiple Linux distributions on a single SD Card and 
> select which one you want to run using a boot menu at boot time.  It uses 
> squashfs base images and overlay technology to only write changes to the 
> filesystem - delete these changes and you are back to the base image 
> again.  BerryBoot facilitates having multiple base images on the one SD 
> Card.
>
> The other feature that BerryBoot supports, which sparked my interest, is 
> to be able to use an iSCSI network drive to store the files instead of the 
> SD Card.  Using this method, you end up with the whole Linux operating 
> system running on network storage and the SD Card is purely for booting 
> up.  Basically the root filesystem is on the NAS and the /boot filesystem 
> is the only thing on the SD Card.  The only time anything is written to the 
> card is if the Linux kernel is updated when using 'sudo apt update/upgrade'.
>
> I have been running this way for a few months now and it has been working 
> beautifully.  The only thing you need to think about is to make sure you 
> shut down the Raspberry Pi when you want to reboot the NAS.  I still leave 
> those three weewx directories as NFS mounts (on the same NAS).  That way 
> they are still separate from the operating system - but this is completely 
> optional.  You could leave everything within the iSCSI disk if you wanted 
> to.
>
> The steps for setting up BerryBoot to use iSCSI on a Synology NAS is here (
> https://www.berryterminal.com/doku.php/storing_your_files_on_a_synology_nas_using_iscsi).
>   
> The screen shots are from an older version of DSM (Synology Operating 
> System) but you should get the idea.  Also, any standard iSCSI Target 
> should work - it doesn't have to be on a Synology NAS.
>
> Cheers,
>
> Peter
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9318eb91-748d-4fe4-b805-62634dd7fe93%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to