[arch-general] After 4.20.10 update - fsck check caused dump to maintenance shell for missing mdadm raid1 UUID?

[David C. Rankin]

On 02/18/2019 03:43 PM, Ralph Corderoy wrote:
> Hi David,
> 
>> The timing of any change would be from today back through whatever
>> number of days the default fsck check schedule is.
> 
> The journal may show the previous fscks on the same device and narrow
> the time range.  `journalctl -t systemd-fsck'.
> https://jlk.fjfi.cvut.cz/arch/manpages/man/systemd-fsck%40.service.8
> 

Thank you Ralph! Very handy. The default looks to be weekly, e.g.

<snip>
-- Reboot --
Feb 14 04:17:33 phoinix systemd-fsck[424]: boot: clean, 355/51200 files,
31430/51152 blocks
Feb 14 04:17:33 phoinix systemd-fsck[425]: home: clean, 159266/57688064 files,
11967988/230736048 blocks
-- Reboot --
Feb 14 13:11:55 phoinix systemd-fsck[413]: boot: clean, 355/51200 files,
31433/51152 blocks
Feb 14 13:11:55 phoinix systemd-fsck[412]: home: clean, 159266/57688064 files,
11967988/230736048 blocks
-- Reboot --
Feb 18 13:30:14 phoinix systemd-fsck[371]: boot: clean, 355/51200 files,
31437/51152 blocks
Feb 18 13:30:14 phoinix systemd-fsck[372]: home: clean, 159312/57688064 files,
11968467/230736048 blocks
-- Reboot --
Feb 18 13:34:03 phoinix systemd-fsck[432]: boot: clean, 355/51200 files,
31437/51152 blocks
Feb 18 13:34:03 phoinix systemd-fsck[431]: home: clean, 159312/57688064 files,
11968467/230736048 blocks

Yep, today shows two reboots after 4.20.10, 1st out of maintenance shell into
LTS and then to 4.20.10

No issues shown with any of the checks. I'm at a loss here.


-- 
David C. Rankin, J.D.,P.E.