Cant get past dev clean screen but different

I’m not sure about that, let me see.

I restarted and that issue is gone, but restarting takes forever

is there any message when youre restarting?

No just the dev clean message

so check logs with:
journalctl --boot -1 --no-pager
and copy logs after: system powering down
use formatting, put them inside this icon in the editor: </>

May 29 15:08:37 EdgyAsPc audit: BPF prog-id=0 op=UNLOAD
May 29 15:08:37 EdgyAsPc audit: BPF prog-id=0 op=UNLOAD
May 29 15:08:37 EdgyAsPc audit: BPF prog-id=0 op=UNLOAD
May 29 15:08:37 EdgyAsPc audit: BPF prog-id=0 op=UNLOAD
May 29 15:08:37 EdgyAsPc audit: BPF prog-id=0 op=UNLOAD
May 29 15:08:37 EdgyAsPc audit: BPF prog-id=0 op=UNLOAD
May 29 15:08:37 EdgyAsPc systemd[1]: Using hardware watchdog 'iTCO_wdt', version 0, device /dev/watchdog0
May 29 15:08:37 EdgyAsPc systemd[1]: Watchdog running with a timeout of 10min.
May 29 15:08:37 EdgyAsPc kernel: watchdog: watchdog0: watchdog did not stop!
May 29 15:08:37 EdgyAsPc systemd-shutdown[1]: Using hardware watchdog 'iTCO_wdt', version 0, device /dev/watchdog0
May 29 15:08:37 EdgyAsPc systemd-shutdown[1]: Watchdog running with a timeout of 10min.
May 29 15:08:37 EdgyAsPc systemd-shutdown[1]: Syncing filesystems and block devices.
May 29 15:08:37 EdgyAsPc systemd-shutdown[1]: Sending SIGTERM to remaining processes...
May 29 15:08:37 EdgyAsPc systemd-journald[371]: Received SIGTERM from PID 1 (systemd-shutdow).
May 29 15:08:37 EdgyAsPc systemd-journald[371]: Journal stopped

are those all logs after the message: system powering down?
it looks like it could be the watchdog …

I used the finder to look for system powering down and there is no specific message for that

its probably the watchdog:
kernel: watchdog: watchdog0: watchdog did not stop!
you can disable it, i have it disabled too:
run this command:
sudo nano /etc/modprobe.d/blacklist.conf
inside it copy these 2 lines:
blacklist iTCO_wdt
blacklist iTCO_vendor_support
then press ctrl+x to save the file
then run this command:
sudo mkinitcpio -P
then reboot

Rebooting still takes a long time, it might be multiple things.

run these commands:
cat /proc/sys/kernel/watchdog
cat /proc/sys/kernel/nmi_watchdog
both should give you ‘0’

oh the first one gives me 1

I guess I did something wrong

so its not disabled…
run this:
kate /etc/modprobe.d/blacklist.conf
and check if these 2 lines are there and the spelling is also the same:
blacklist iTCO_wdt
blacklist iTCO_vendor_support

they are there

properly in kate as well

blacklist iTCO_wdt
blacklist iTCO_vendor_support

good so now open this file:
kate /etc/default/grub
and in this line GRUB_CMDLINE_LINUX_DEFAULT inside the “” quotes put this: nowatchdog - dont remove anything from there, just add it there… and copy the line here if its correct, just to be sure

“quiet apparmor=1 security=apparmor udev.log_priority=3 nowatchdog”

Is this proper?

good, so save the file, it will prompt you for password, then run this command:
sudo update-grub
then reboot
check again with:
cat /proc/sys/kernel/watchdog
cat /proc/sys/kernel/nmi_watchdog

both are 0, but it still takes 3 minutes.

I think the problem is prior to it turning back on, because it’s launching is lightning fast.

yes because it was not yet disabled, its disabled now, so test it - reboot and see if it still takes a long time

I did just reboot, and it took 3 minutes.

There were two separate dev clean screens. the first one took forever, but the second one goes away after like 4 seconds.