Ubuntu "reboot" inhibited
by jan128 from LinuxQuestions.org on (#5J50G)
"Just questions - not really a problem"
Attempt to "reboot" after few minutes of successful start of 20.10 OS , for test purpose generated this "unknown" response.
However, my guess is that "mdraid" "check-job" is something to be expected sometime, OS reboot being a good time to to do so , hence not really problem.
1. Would this explain unusual HDD activity AFTER booting the OS?
2. Is there a way to option boot process , say in "grub" to actually let user know that "raid" is active ? (yes, I know how to manually run "mdadm" to see raid state)
q@q-desktop-320:~$ reboot
Operation inhibited by "Disk Manager" (PID 1249 "udisksd", user root), reason is "Unknown (mdraid-check-job)".
Please retry operation after closing inhibitors and logging out other users.
Alternatively, ignore inhibitors and users with 'systemctl reboot -i'.
q@q-desktop-320:~$
Attempt to "reboot" after few minutes of successful start of 20.10 OS , for test purpose generated this "unknown" response.
However, my guess is that "mdraid" "check-job" is something to be expected sometime, OS reboot being a good time to to do so , hence not really problem.
1. Would this explain unusual HDD activity AFTER booting the OS?
2. Is there a way to option boot process , say in "grub" to actually let user know that "raid" is active ? (yes, I know how to manually run "mdadm" to see raid state)
q@q-desktop-320:~$ reboot
Operation inhibited by "Disk Manager" (PID 1249 "udisksd", user root), reason is "Unknown (mdraid-check-job)".
Please retry operation after closing inhibitors and logging out other users.
Alternatively, ignore inhibitors and users with 'systemctl reboot -i'.
q@q-desktop-320:~$