e5379ae202a9
Update
author | Steve Losh <steve@stevelosh.com> |
---|---|
date | Sun, 02 Feb 2020 00:11:16 -0500 |
parents | 14fa5850fa5c |
children | f65b93a5eed2 |
branches/tags | (none) |
files | README.markdown |
Changes
--- a/README.markdown Sat Feb 01 21:11:46 2020 -0500 +++ b/README.markdown Sun Feb 02 00:11:16 2020 -0500 @@ -344,3 +344,14 @@ came from telling it to use RAM as its temporary filesystem with `-t /dev/shm`, which cut the time down to 1/3. Guess all this RAM *is* actually good for something. + +After rebooting later, the boot process was suddenly hanging for over a minute. +Another fucking yak to shave. Figured out how to disable the goddamn splash +screen (edit `/etc/default/grub` to remove `quiet` and `default` and then +`update-grub2`) so I could get some logs. Eventually saw some systemd horseshit +about `a job is running for dev-disk-by\x2duuid-…`. Tried to figure out which +drive had that UUID, but none of them did. After a bunch of flailing in `fstab` +I realized that it might be the UUID of *the old backup drive I killed*. Sure +enough, there was still an entry in `/etc/crypttab` for it, and a bunch of +systemd shit in `/run/systemd/generator/` left over that I had to clean out. +After that, everything boots fast(ish) again. I hate computing.