Neil Rickert composed on 2017-11-06 21:02 (UTC-0600): Thank you!
Felix Miata wrote:
OTOH, I'm having brainlock over when to boot vis a vis when to change the RTC and in which direction. Maybe this needs to wait until I can better concentrate, not too easy lately.
Boot into your BIOS settings. Set the hardware clock back by 1 hour. Then boot into opensuse. See if it forces file checks.
What you will be doing, is setting up your system so that the file system dates on boot will be 1 hour in the future. And that's very likely what happened before, as I noted in a reply yesterday.
Retarded clock and booted to 42.3/kernel 4.4.87-25, which took more than 2 minutes: # journalctl | grep rblock | grep "Nov 0" Nov 05 02:13:38 p5bse systemd-fsck[700]: h50usrlcl: Superblock last write time is in the future. Nov 05 02:13:43 p5bse systemd-fsck[697]: h50boot03: Superblock last write time is in the future. Nov 05 02:13:45 p5bse systemd-fsck[704]: os421h50: Superblock last write time is in the future. Nov 05 02:13:51 p5bse systemd-fsck[706]: os131h50: Superblock last write time is in the future. Nov 05 02:14:31 p5bse systemd-fsck[712]: h50home09: Superblock last write time is in the future. Nov 05 02:14:41 p5bse systemd-fsck[701]: h50pub11: Superblock last write time is in the future. Nov 06 21:22:07 p5bse systemd-fsck[339]: os423h50: Superblock last mount time is in the future. Nov 06 21:22:07 p5bse systemd-fsck[339]: os423h50: Superblock last write time is in the future. Nov 06 21:22:28 p5bse systemd-fsck[650]: h50home09: Superblock last mount time is in the future. Nov 06 21:22:28 p5bse systemd-fsck[650]: h50home09: Superblock last write time is in the future. Nov 06 21:22:39 p5bse systemd-fsck[646]: h50boot03: Superblock last mount time is in the future. Nov 06 21:22:39 p5bse systemd-fsck[646]: h50boot03: Superblock last write time is in the future. Nov 06 21:22:40 p5bse systemd-fsck[663]: h50usrlcl: Superblock last mount time is in the future. Nov 06 21:22:40 p5bse systemd-fsck[663]: h50usrlcl: Superblock last write time is in the future. Nov 06 21:22:48 p5bse systemd-fsck[648]: h50pub11: Superblock last mount time is in the future. Nov 06 21:22:48 p5bse systemd-fsck[648]: h50pub11: Superblock last write time is in the future. Nov 06 21:23:58 p5bse systemd-fsck[645]: os131h50: Superblock last write time is in the future. Nov 06 21:24:35 p5bse systemd-fsck[639]: os421h50: Superblock last write time is in the future. I reset the clock and rebooted, which took less than a minute, then tried again with TW20171006/4.13.4-1 last logged in 9 Oct. Boot time felt normal before and after BIOS clock change. I switched BIOS clock back to normal, booted again 2-3 times, then switched back an hour and booted again. Still no write time in the future in journal, and no apparent boot delay. I repeated the switching process with 42.2/4.4.87-18.29, with results like 42.3: # journalctl | grep rblock | grep "Nov 0" | wc -l 14 Seems like this might solve itself by the time distribution 15 is released.
You could disconnect the network cables to avoid any NTP issues. But I don't think it actually matters. The system won't start NTP until after it has checked the file systems.
I skipped cable disconnection. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org