On 01/12/2018 14.13, George from the tribe wrote:
On 12/1/18 5:24 AM, Carlos E. R. wrote:
On 01/12/2018 11.32, George from the tribe wrote:
So I ran the distribution upgrade for tumbleweed, the latest one being as of yesterday, Nov 30.
It will not boot on the current kernel, which is 4.19.4-1. It also will not boot on kernel 4.19.2-1, the last upgrade a week ago, which is when this problem started. I was hoping that the new upgrade, which I did yesterday, would fix the problem, but it didn't.
However, it will boot on kernel 4.18.15-1, and that is what I am on at the moment.
Watching it boot, it hangs at around 30-35 seconds on the following line, right after it says "[ OK ] Reached target Initrd Root Device.": [** ]A start job is running for dev-disk-by\x2duuid-d3224276\x2d28fa\x2d44ad\x2db96e\x2dcd3d84fd2e6e.device
(35s / 1min 30s)
I think that device number is the device number for the initrd, because it does not show up on my device list when I run ls -l /dev/disk/by-uuid.
Can't be. Initrd doesn't have such a thing.
[ TIME ] Timed out waiting for device dev-disk-by\x2duuid-d3224276\x2d28fa\x2d44ad\x2db96e\x2dcd3d84fd2e6e.device.
[ DEPEND ] Dependency failed for Resume from hibernation using device /dev/disk/by-uuid/d3224276-28fa-44ad-b96e-cd3d84fd2e6e.
It might be swap.
Maybe your initrd refers to that partition
It's not the swap, according to this: # blkid /dev/sdb7 /dev/sdb7: LABEL="swap" UUID="78e12fe1-1805-475f-bd43-ed40c991fc6e" TYPE="swap" PARTLABEL="swap" PARTUUID="08891476-54b5-4b4f-a3c3-243a6f80b2dc"
I don't know if knowing what exactly has that UUID is the key to figuring out why the system hangs on boot at 30seconds in trying to start that device. But that UUID does not match any of my partitions on either my SSD or my regular main HD for this laptop.
The system hangs because it does not exist, so you will not find it. I suspect it thinks it is swap space. You have to find what is requesting that UUID. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)