[sudo-access] front door computer disk backup
Anthony Di Franco
di.franco at gmail.com
Mon Sep 24 16:52:45 PDT 2018
I can already get on the doorjam computer, so what I need additionally is:
- To know / agree upon what a good remote server to back up to would be
- To have a way to add authentication credentials for the doorjam
computer to that server
- To know what should be backed up and with what priority
We can look at it together in person on Wednesday if you are around, or set
another time, or I can just get your reply here and do my best.
On Mon, Sep 24, 2018 at 4:48 PM Jake <jake at spaz.org> wrote:
> i guess a local disk backup doesn't help if it goes missing :)
> thanks Anthony, lemme know how i can help
> On Mon, 24 Sep 2018, Anthony Di Franco wrote:
> > I would be happy to have a look at this. If we deem it adequate, I could
> > just write a cron job to rsync everything to a remote server and perhaps
> > also a spare local disk, or the like. I would need a quick primer on how
> > the thing is currently set up. I'll be around Wednesday evening so that
> > would be a convenient time for me to have a look at this.
> > Anthony
> > On Wed, Sep 19, 2018 at 12:46 PM Jake <jake at spaz.org> wrote:
> >> I notice sometimes when i log into the front door computer that the
> >> prompt is showing that the disk is in read-write mode. I'm worried that
> >> if too
> >> much activity happens to the eMMC disk of the beaglebone black that runs
> >> the
> >> door, that we might have a disk failure.
> >> either way I think we should have a backup of the door computers'
> >> filesystem,
> >> maybe an image of the whole disk, that we can automatically maintain so
> >> that if
> >> it ever gets corrupted or flooded or whatever we can easily replace it.
> >> is anyone on this list willing to take that on? I'm not an expert at
> >> and
> >> I feel like others might have an easier time with it.
> >> also I think we should consider migrating the entire system to an SD
> >> instead of using the soldered-on eMMC chip on the beaglebone (which
> >> eventually
> >> dies and ruins everythinng)
> >> here's the disk situation:
> >> /dev/disk/by-uuid/6b3e6ea0-eba5-402a-ae7a-ec2c7555affb on / type ext4
> >> (6b3e6ea0-eba5-402a-ae7a-ec2c7555affb == mmcblk1p2 AKA the eMMC)
> >> /dev/mmcblk1p1 on /boot/uboot type vfat
> >> /dev/mmcblk0p1 on /mnt/sd_card type ext4 (this is the actual sd card)
> >> the SDcard that's in there now is empty so it seems like someone could
> >> copying the system to it (whether for backup or to boot from it) but I
> >> have no
> >> idea how to make a BBB boot from SDcard instead of built-in eMMC
> >> i'm
> >> sure it's no big deal...
> >> anyway this is just a heads-up so that we make it easy to fix in case
> >> something
> >> happens to the door system disk. It's been extremely reliable for years
> >> but we
> >> can't take that for granite* and it's important infrastructure.
> >> -jake
> >> _______________________________________________
> >> access mailing list
> >> access at lists.sudoroom.org
> >> https://sudoroom.org/lists/listinfo/access
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the access