Another 22.04 problem, reboot fails, have to power cycle
Chris Green
cl at isbd.net
Mon Aug 1 13:32:08 UTC 2022
On Sun, Jul 31, 2022 at 09:48:32AM +0100, Colin Law wrote:
> On Sun, 31 Jul 2022 at 07:36, Grizzly via ubuntu-users
> <ubuntu-users at lists.ubuntu.com> wrote:
> >
> > 30 July 2022 at 21:35, Chris Green wrote:
> > Another 22.04 problem, reboot fails (at least in part)
> >
> > I've seen this on 18.04, 20.04 and now 22.04 (maybe on 16.04 but not sure), I
> > never chased it up, assumed it was hardware on that box, A Dell, it just sits
> > on "F2 F12" window, so I tend to
> >
> > "shutdown now -P"
> >
> > then power on again, the box "should" boot from keyboard key but it has never
> > worked that way, it's a Wireless USB KB so that may explain it
> >
> > >I have another problem after upgrading from 21.10 to 22.04, my system
> > >won't reboot.
> >
> > >If I reboot the system (from command line or GUI) it shuts down and
> > >hangs. I have to power down and up again, then it boots OK.
> >
> > >Has anyone else had an issue like this and/or know how to fix it?
>
> Make sure the BIOS/UEFI firmware on the mother board is up to date.
>
> Look in /var/syslog to see if there are any clues there.
>
> Does
> sudo shutdown -r now
> work?
>
I have a bit more information on my failed restart.
It's "losing" one of the disk drives! If I leave the system long
enough after a restart I get the following messages:-
Gave up waiting for suspend/resume device
Common problems:
-Boot arge (cat /proc/cmdline)
- check rootdelay= (did the system wait long enough?)
- missing modules (cat /proc/modules; ls /dev)
ALERT: UUID=2d6ff70c-1894-4afa-a35c-5abb40549d3b does not exist.
Dropping to a shell!
It's not surprising it's failing to reboot, UUID=2d6ff70c-1894-4afa-a35c-5abb40549d3b
is my / drive.
The question is why did it work in 21.10 and now doesn't work in
22.04, and why does power cycling make the drive reappear? What
probably complicates things rather is that the drive is an NVME SSD and
isn't visible to the BIOS.
My system's /boot is on a different drive which is visible to the BIOS
and, after booting, Linux can 'see' the NVME SSD.
--
Chris Green
More information about the ubuntu-users
mailing list