Today the power went out and I had not yet set up a UPS for my omv. In these cases, what are the appropriate checks to be carried out to check that there have been no problems deriving from the sudden shutdown of the system?
sudden shutdown of the system
-
- OMV 4.x
- nicovon
-
-
Which platform are you on? amd64 or arm?
-
Which platform are you on? amd64 or arm?
amd64
-
On armbian there is a tool to check the integrity of packages.
You can check the output of dpkg --verify
https://manpages.debian.org/stretch/dpkg/dpkg.1.en.html -
On armbian there is a tool to check the integrity of packages.
You can check the output of dpkg --verify
https://manpages.debian.org/stretch/dpkg/dpkg.1.en.htmlThanks. I was thinking of a tool equivalent to the Windows scandisk..
-
-
On armbian there is a tool to check the integrity of packages.
You can check the output of dpkg --verify
https://manpages.debian.org/stretch/dpkg/dpkg.1.en.htmlCode
Alles anzeigenroot@omv:~# dpkg --verify ??5?????? c /etc/cron-apt/config ??5?????? c /etc/default/wsdd ??5?????? c /etc/watchdog.conf ??5?????? c /etc/default/monit ??5?????? c /etc/monit/monitrc ??5?????? c /etc/ntp.conf ??5?????? c /etc/collectd/collectd.conf ??5?????? c /etc/default/smartmontools ??5?????? c /etc/smartd.conf ??5?????? /var/lib/smartmontools/drivedb/drivedb.h ??5?????? c /etc/cron.daily/mdadm ??5?????? c /etc/avahi/avahi-daemon.conf ??5?????? c /etc/default/avahi-daemon ??5?????? c /etc/issue ??5?????? c /etc/default/acpid ??5?????? c /etc/systemd/logind.conf ??5?????? c /etc/default/rrdcached root@omv:~#
-
on which partition should I run the command? I believe that I cannot execute the command because the partition is mounted and I cannot unmount it.
-
The output of dpkg --verify looks fine. If everything is working as expected, I would think the shutdown has not caused any problems.
on which partition should I run the command?
You could run it on the data drives.
To check the root fs with fsck look at this site below "How to Run fsck on Linux Root Partition" -
-
Code
Alles anzeigenroot@omv:~# dpkg --verify ??5?????? c /etc/cron-apt/config ??5?????? c /etc/default/wsdd ??5?????? c /etc/watchdog.conf ??5?????? c /etc/default/monit ??5?????? c /etc/monit/monitrc ??5?????? c /etc/ntp.conf ??5?????? c /etc/collectd/collectd.conf ??5?????? c /etc/default/smartmontools ??5?????? c /etc/smartd.conf ??5?????? /var/lib/smartmontools/drivedb/drivedb.h ??5?????? c /etc/cron.daily/mdadm ??5?????? c /etc/avahi/avahi-daemon.conf ??5?????? c /etc/default/avahi-daemon ??5?????? c /etc/issue ??5?????? c /etc/default/acpid ??5?????? c /etc/systemd/logind.conf ??5?????? c /etc/default/rrdcached root@omv:~#
@macom what about the output of the dpkg command? Do you notice anything abnormal?
-
The output of dpkg --verify looks fine.
Only files changed that are likely to be changed.
-
Only files changed that are likely to be changed.
I apologize. I hadn't read your answer in the hurry. I got scared because of those question marks. By the way what does "??5?????? c" mean?
-
The d shows that the md5sum check failed on these files. Which is ok, as they are configuration files. Would be a problem if any other files would show up,
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!