[arm-allstar] arm-allstar Digest, Vol 16, Issue 31

[B. McIntosh [Pace]]

Hi Doug,

Careless of me not to notice that you'd already written the application for
push button shutdown - I thought I'd read all of your How-to documents.  Yes
of course it fits the requirement perfectly.

Regarding fsck - it's a very common problem with the Debian based PI
distributions. If the system is shutdown incorreclty it often will not
restart until you execute fsck interactively - but to do that you need
keyboard and monitor plugged in - it can't be done via SSH - what a pain.
There is a way of changing the config though and we do that with all of our
Debian based machines.

Although the wiki page doesn't explicitly state that Arch Linux doesn't
insist on this, it is certainly implied - and the fact that you've never
experienced a problem also kind of backs up the fact that fsck runs
non-interactivly on reboot. That'll do for me. As you say, the key is to
always have plenty of copies of SD cards - they're never going to be the
most reliable of technology although I have had some running for years in a
stable environment with no problem.

Best Regards

Bernie 
GM4WZG


 




Message: 1
Date: Thu, 10 Sep 2015 13:56:21 -0400
From: Doug Crompton <doug at crompton.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] fsck on PI image
Message-ID: <BLU171-W8869B65FCC642D7CDC413EBA510 at phx.gbl>
Content-Type: text/plain; charset="iso-8859-1"

Bernie,

 There are a number of ways to shutdown the Pi. Already in the 
code is the ability to shutdown with a GPIO push button. You 
just have to add the button and activate it in the allstar.env 
file. A howto is on the web page.

There are also functions in rpt.conf that are commented out 
that allow dtmf asterisk restart, linux reboot, and system 
halt. You could uncomment them and possibly change the dtmf codes.

As far a power down problems without shutting down properly I 
have never seen a problem with the RPi2 image but of course it 
is always a good idea to shutdown properly. It does not take 
much to run the RPI2 for hours of power failure. A 400 watt UPS 
would run it all day.

The image is ext4 and does the same things it would do on any other OS.

https://wiki.archlinux.org/index.php/Fsck

I don't think it is anything you have to really worry about as 
long as you take a few precautions and of course always have an 
image backup on hand. They are easy to make with the backup scripts.

73 Doug
WA3DSP
http://www.crompton.com/hamradio


> From: bmcintosh at paceprofessional.co.uk
> To: arm-allstar at hamvoip.org
> Date: Thu, 10 Sep 2015 17:13:53 +0100
> Subject: [arm-allstar] fsck on PI image
> 
>  
> Hi,
> 
> I recently put together a remote base using Baofeng UV5R and 
Doug's PI 
> image. One of the problems that I have had with using Pis in a shared 
> environment is folk switching them off without shutting them 
down properly.
> I normally rig up a push switch that makes the PI do  a clean 
shutdown 
> for you when you don't have a terminal handy to do it via SSH.
> (http://www.feednet.org.uk/powerdownpi.htm   )
> 
> I also usually enable non-interactive use of fsck on reboot to cope 
> with those cases where a clean shutdown hasn't been made. This is to 
> avoid those circumtances where the machine won't allow you to go 
> further without logging in as root, but you can't login as 
root because SSH hasn't started yet.
> 
> I'm not familiar with Arch Linux - can someone advise how to ensure 
> that if the OS runs fsck on a reboot, that it completes 
without any intervention ?
> Or perhaps this is already done with Doug's image ?
> 
> Thanks !
> 
> Bernie
> GM4WZG
> 
> 
> _______________________________________________
> 
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> 
> Visit the BBB and RPi2 web page - http://hamvoip.org
> 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.hamvoip.org/pipermail/arm-allstar/attachments/2015
0910/6026350a/attachment-0001.html>

------------------------------