That is most likely a waste of time and bandwidth as your system would contain exactly that.
In my opinion - no.
What could be an idea, is to schedule - at regular intervals - a copy of your package list and personal configuration - just as a precautionary measure - just an example [root tip] [Utililty Script] Backup configuration and package list and if you want to make sure no systemfiles has been altered outside package sync you could look towards these pages
yeah well, I just wanted to be sure the system is still fine.
I noticed yesterday too late that my root partition was full, that’s why my updates kept failing. I cleared up space by removing a backup from the root partition.
Now I just want to be sure that nothing in my root partition was corrupted or deleted while there was no space left in the root partition.
-Dkk will perform on the repos, what is available, not what you have.
Something more like what OP is asking for might be
pacman -Qkk | grep -v '0 altered files'
Though I fear what this will mean for people looking at the output.
Its likely there willl be ‘modified’ files or ‘mismatched time’ etc that is ignorable.
Well, the single Dk
pacman -Dk
will report big goofs like missing dependencies… though that will likely only happen if someone did -Rdd manually.
If you think in terms of sfc or dism on Windows, then no. It is not an fixed state os image. It’s more fluid. Best guess is just rerun the upgrade.
The problem with such a check is that the database doesn’t match exactly every file, since they get modified and you get a lot of false positives with pacman -Qkk for example. SteamOS for example made the root readonly and therefore such a check is valid, since no files will be modfied directly, but on an overlay.
“Nuke it from orbit – it’s the only way to be sure.”
– Adapted from Aliens (1986)
Well, short of doing that, if /home is on a separate partition I’d probably perform a fresh install; and/or use the method suggested by @linux-aarhus in post#5 to restore configurations that I specifically wanted to keep. After a decade of faithful service; and noting your other post which might indicate the possibility of other issues, a reinstall is certainly another way to be sure.
I think you need to specify --sha256sum to actually check the contents of the files, like to detect if it is corrupted. Without it it’s more like a metadata audit.
This tool is for pure Arch Linux. If you runs it on Manjaro, you will get some mismatched checksums, for example all Manjaro Kernels and some Manjaro packages (they copy from Arch packages and are modified by Manjaro team).
yes i saw that, i had 5 packages that had warnings. I wonder why is this so? Should not manjaro modify the mtree also if they modify a file, so all matches again.
For quick checks, fsck can scan your filesystem and pacman -Syu grabs the latest updates, potentially fixing corrupted files. If things feel more serious, consider an Arch live USB for deeper checks. Just remember, backups are your friend!
Unless you’re facing specific problems, Manjaro usually handles things well. But if something’s wonky, hit the web for solutions specific to your symptoms. No need to reinvent the wheel!
Prevention is key, though. Regular updates and keeping an eye on logs can save you headaches later. Happy rolling