Greets, everyone, from a place of great anguish.
Sat down at the desktop machine last night and to my surprise it was off. I turned it on. As it booted, it found and fixed some orphaned inodes, per usual for a dirty shutdown (no idea what caused the shutdown, btw), and all was well, seemed to be happy, but then it got to where it said: [TIME] Timed out waiting for device dev-sdb1.device - /dev/sdb1. [DEPEND] Dependency failed for mnt-sdb1.mount - /mnt/sdb1.
There it sat. It's probably worth mentioning that there is no sdb in the machine. Only a big sda partitioned into several partitions, per usual.
After a while I did the c-a-d thing, but instead of rebooting it seemed to continue the boot in progress until it came to: [*** ]Job systemd-fsck@dev-disk-by\x2duuid-f33fcb46[many numbers and letters].service/stop running (4min 5s / no limit)
It's not lying about the no limit -- it stayed there, counting, all night.
I booted a System Rescue disk from USB. Could find no evidence of anything wrong, though that's not saying much in that I didn't really go poking around lest I *really* break something.
So. Anyone know how I can tell the machine to stop looking for stuff that isn't there and just to go ahead and boot?
Thanks!
dep Pictures: http://www.ipernity.com/doc/depscribe/album Column: https://ofb.biz/author/dep/