Maasi I fubar'd my own system yesterday due to impatience and spent 10 hours in tty and live disk.
What Staudey gave you: https://getsol.us/articles/troubleshooting/general-troubleshooting/en/ saved my life.
I have a hard time believing you have no broken packages with that grep command.

try: sudo eopkg check | grep Broken
at least you can see what happened.
sudo eopkg rdb is fast and deletes another variable.
moreover----read that help article and use those two terminal commands to check your lts

how I wrapped this up in 12 hours? throwing everything at the wall until finally using that troubleshooting page...

      Maasi There's no way you're getting that message if you just enter that command correctly.
      Are you perhaps mistakenly putting a space between the dashes and reinstall? It should be exactly like this:
      --reinstall all characters connected, without anything in between.

          Staudey Unless they've removed their repository, then you wouldn't find anything. 😁

            Staudey it was space, thank you.

            now nvidia is fine and udisks is still broken. I reinstall them and check after that I reboot, still black screen.

                brent

                tried the link, the one eith linux-lts does not work but linux-current works. saw clr-boot-manager boot and my computer have the same kernels.

                also tried sudo eopkg rdb.

                nvidia is not broken now but udisks still is broken. I reboot the system still black screen.

                  the comparison thing was just to see if version numbers matched, I belive. then there was a plan i the help page from there.

                  blank screen patience. my ctrl+alt+whatever took a lot longer to appear.
                  you are right about one thing: when it was close to come back to life for me, udisk and nvidia were prominent.

                  it took a LONG time but the grep command finally worked in TTY. I had to manually remove and reinstall a lot of broken stuff before command worked--I know it goes by fast but I wrote as muc broken down on paper as I could remember. then rdb. then reboot. then after 10 hours FINALLY the login greeter except the wrong one. then boot into a HIDEOUS pitch-black OS called openbox. It's like a pitch black room and the flashlight is the rightclick.

                  Apparently we nuked our display managers somehow. took forever to get lightdm to work. And budgie itself was gone as well as some necessay gnome apps.
                  then AFTER grep "fixed" all packages in TTY, I ran the same command in the UI/OS to find more broken. Once that was settled I am back in business with some minor installs.

                  Coinciding, for me, with the update, is me ripping a lot of programs out this week (for space) without considering deps. That's on me. Then I aborted a 200-package update while SYNCING Friday (accident).

                  I am whole again.. the reason this reply is so long is there might be on thing you can take away to get you further down the road while my trauma is still fresh🙂

                  edit/fixed one typo, left the rest...

                    Maasi Okay, the udisk thing can be safely ignored. Must be something other than a broken package then.

                      Maasi the gist of my post was manually uninstalling/installing half the broken packages in tty, led me to finally being able to use the grep broken command. The packages, need to run the danged command I had somehow ripped out. Somehow that diligence got me to the operating system...

                      ....as to your question, stalling out at RIT is not uncommon during update. It is 100% cured by trying it again until it sticks. Keep trying it will update.

                          brent

                          I did systemd-analyze critical-chain and it show systemd-fsck-root @584542y 2w 2d 20h 1min 49.328s +16ms in red

                          is that the problem?

                              Maasi Over my head. I defer to Justin --edit or the majority of people above my brain level who can interpret that. Red is always pay attention, I agree.

                                    Maasi I mentioned what the problem was in my last comment, it couldn't lookup DNS. Is the error the same if you update now?

                                        Justin

                                        no the DNS thing is fixed now, thank you about that.

                                        Now a new problem appeared. when I do systemd-analyze critical-chain, systemd-fsck-root.service @584542y 2w 2d 20h 1min 49.337s +17ms appears in red. could it be the problem?

                                            Maasi Unlikely. That's just a filesystem check.

                                              brent

                                              I give up. Im trying to install solus but it writes:

                                              Failed to apply format: / dev nvme0n1p2: Command '/sbin/pvcreate -ff -y /dev/nvme0n1p2' returned non-zero exit status 5
                                              Failed to apply disk strategy

                                              how do i fix it?

                                                  thank you everyone, you guys are did great. Thanks for the all replies.