rebooting on read-only /?

rebooting on read-only /?

[Robert Edmonds]

I have a server using runit as init and the only drive in the machine
has experienced a block layer failure and has been write-protected.

Now, when I attempt to reboot,

   # init 6
   init: fatal: unable to create /etc/runit/stopit: read-only file system

Is there any way to signal runit to reboot the machine without touching
the filesystem, even uncleanly?  Maybe something akin to sysvinit's
"reboot -f"?

-- 
Robert Edmonds

Re: rebooting on read-only /?

[Gerrit Pape]

On Wed, Jun 28, 2006 at 06:27:19PM +0000, Robert Edmonds wrote:
> I have a server using runit as init and the only drive in the machine
> has experienced a block layer failure and has been write-protected.
> 
> Now, when I attempt to reboot,
> 
>    # init 6
>    init: fatal: unable to create /etc/runit/stopit: read-only file system
> 
> Is there any way to signal runit to reboot the machine without touching
> the filesystem, even uncleanly?  Maybe something akin to sysvinit's
> "reboot -f"?

Send the runsvdir process a TERM signal, so that stage 2 exits cleanly.
runit will then enter stage 3.

runsvdir(8):
SIGNALS
       If runsvdir receives a TERM signal,  it exits with 0 immediately.
runit(8):
STAGE 2
       runit runs /etc/runit/2, which  should  not  return  until system
       shutdown; if it crashes, or exits 111, it will be restarted.


IIRC 'reboot -f' doesn't do anything with the init process, but simply
hard-reboots the machine,  I posted a simple program that also does that
here
 http://article.gmane.org/gmane.comp.sysutils.supervision.general/315

HTH, Gerrit.