sudo reboot -nq

-n file system cache not flushed

-q restarted quickly and ungracefully, and only the flushing of the file system cache is performed (if the -n option is not specified)

Notes:

• Both options should probably not be used: first try without, then -q, then -qn.
• Wait 5-15 minutes.
• Don't expect a shutdown acknowledgement.
• A "Broken pipe" disconnect message appears later then with regular reboots.

sudo reboot -nq

-n file system cache not flushed

-q restarted quickly and ungracefully, and only the flushing of the file system cache is performed (if the -n option is not specified)

Notes:

• Both options should probably not be used: first try without, then -q, then -qn.
• Wait 5-15 minutes.
• Don't expect a shutdown acknowledgement.
• A "Broken pipe" disconnect message appears later then with regular reboots.

This is a uncontrolled shutdown and the only worse thing for data / filesystem is holding the power button, but if you've already quit all the apps that can quit and waited 10 minutes, it's not likely a clean landing can happen at this point.

sudo reboot -nq

• Wait 5-15 minutes.
• Don't expect a shutdown acknowledgement.
• A "Broken pipe" disconnect message appears later then with regular reboots.

sudo reboot -nq

-n file system cache not flushed

-q restarted quickly and ungracefully, and only the flushing of the file system cache is performed (if the -n option is not specified)

Notes:

• Both options should probably not be used: first try without, then -q, then -qn.
• Wait 5-15 minutes.
• Don't expect a shutdown acknowledgement.
• A "Broken pipe" disconnect message appears later then with regular reboots.

Sudo reboot -nq

• Wait 5-15 minutes.
• Don't expect a shutdown acknowledgement.
• A "Broken pipe" disconnect message appears later then with regular reboots.

sudo reboot -nq

• Wait 5-15 minutes.
• Don't expect a shutdown acknowledgement.
• A "Broken pipe" disconnect message appears later then with regular reboots.