Annotated edit history of
ForcingReboots version 3, including all changes.
View license author blame.
| Rev |
Author |
# |
Line |
| 1 |
MichaelJager |
1 |
So I went to edit this page, discovered it didn't exist, and got this: |
| |
|
2 |
|
| |
|
3 |
''Three things are certain:%%% |
| |
|
4 |
Death, taxes and lost data.%%% |
| |
|
5 |
Guess which has occurred.'' |
| |
|
6 |
|
| |
|
7 |
How fitting. |
| |
|
8 |
|
| |
|
9 |
So you've got a bunch of processes waiting on disk because the device mounts on /home is hosed, and you know you can fix it, if you could just umount the f&^%ing thing. Now unless /home is NFS mounted (in which case you've probably got more than one machine with this problem, you poor bastard) with intr, you're probably screwed without a reboot. |
| |
|
10 |
|
| |
|
11 |
But you can't reboot, right? You can't sync, or kill the processes waiting waiting on disk (cause, well, they're waiting on disk), or whatever, because the device is poked. |
| |
|
12 |
|
| 3 |
PerryLorier |
13 |
Well, apparently the cunning folks that invented reboot (or halt, take your pick), have thought of this, and added the -n (don't sync before reboot/halt) and -f (do it now, really) options. So try your luck with <tt>reboot -ns</tt> (might want to comment out the /home line in fstab first, presumably the whole reason you're trying to force a reboot without hitting the reset button is because the machine's a long way away, and having it die on reboot because it can't mount the hosed <tt>/home</tt> media is not going to be a good look). |
| 1 |
MichaelJager |
14 |
|
| |
|
15 |
Danger Will Robinson, data loss may occur, etc, etc. Not my fault. |
| 3 |
PerryLorier |
16 |
|
| |
|
17 |
An even more abrupt way of rebooting the machine, if magic syskey is enabled you can use: |
| |
|
18 |
<tt>echo b >/proc/sysreq</tt>, or press <tt>Alt-Sysreq-B</tt> |
| 2 |
MichaelJager |
19 |
---- |
| |
|
20 |
CategoryErrors |
