Am 14.01.19 um 19:45 schrieb Isaac Gelado:
> When I got the initramfs shell I also typed
>
> udevadm trigger --type=subsystems --action=add
> udevadm trigger --type=devices --action=add
>
> and tried to continue the boot process, but it failed. Then I typed
>
> udevadm trigger --type=devices
When I got the initramfs shell I also typed
udevadm trigger --type=subsystems --action=add
udevadm trigger --type=devices --action=add
and tried to continue the boot process, but it failed. Then I typed
udevadm trigger --type=devices --action=add -v
and it booted nicely. Somehow, the `-v` flag
Sorry for the late reply. I could not reboot my machine until today.
I added a sleep 5 and it didn’t work.
On Tue, Jan 8, 2019 at 9:15 AM Michael Biebl wrote:
> Am 08.01.19 um 18:11 schrieb Isaac Gelado:
> > As a side hint that might be helpful. I had two kernels 4.18 and 4.19
> > in my
I just encountered exactly the same problem. This made my Debian Sid
on workstation unable to boot... oops. I am using regular ext4
filesystems.
It would be great if we could solve it soon since this bug is really
devastating.
(email sent from Ubuntu 18.04)
--
Regards,
Boyuan Yang
4 matches
Mail list logo
