Checksum mismatch

Help Section
1

I want to do the same check as I did on FreeBSD, so here at nomadBSD it will be different, as I use an HDD:

# geom disk list
Geom name: da0
Providers:
1. Name: da0.sched.
   Mediasize: 250059350016 (233G)
   Sectorsize: 512
   Mode: r2w2e8
   descr: Samsung G2 Portable
   lunname: JMicron USB to ATA/ATAPI bridge
   lunid: JMicron USB to ATA/ATAPI bridge
   ident: 00000011E09310C000D6
   rotationrate: unknown
   fwsectors: 63
   fwheads: 255

I checked the installed packages for checksum discrepancies:

# pkg check -s -a
Checking all packages:   8%
dsbautostart-1.2: checksum mismatch for /usr/local/bin/dsbautostart
dsbautostart-1.2: checksum mismatch for /usr/local/share/applications/dsbautostart.desktop
Checking all packages:   8%
dsbbatmon-1.0.6: checksum mismatch for /usr/local/bin/dsbbatmon
Checking all packages:   8%
dsbdriverd-0.6.1: checksum mismatch for /usr/local/etc/rc.d/dsbdriverd
dsbdriverd-0.6.1: checksum mismatch for /usr/local/libexec/dsbdriverd
dsbdriverd-0.6.1: checksum mismatch for /usr/local/share/dsbdriverd/drivers.db
Checking all packages:   8%
dsblogoutmgr-1.3.2: checksum mismatch for /usr/local/bin/dsblogoutmgr
Checking all packages:   8%
dsbmc-1.0: checksum mismatch for /usr/local/bin/dsbmc
Checking all packages:   9%
dsbmc-cli-0.4: checksum mismatch for /usr/local/bin/dsbmc-cli
dsbmc-cli-0.4: checksum mismatch for /usr/local/man/man1/dsbmc-cli.1.gz
Checking all packages:   9%
dsbmixer-1.4: checksum mismatch for /usr/local/bin/dsbmixer
dsbmixer-1.4: checksum mismatch for /usr/local/libexec/dsbmixer_backend
Checking all packages:  10%
encodings-1.0.5,1: missing file /usr/local/share/fonts/encodings/encodings.dir
Checking all packages:  42%
libexo-0.12.11: missing file /usr/local/share/applications/exo-file-manager.desktop
libexo-0.12.11: missing file /usr/local/share/applications/exo-mail-reader.desktop
libexo-0.12.11: missing file /usr/local/share/applications/exo-preferred-applications.desktop
libexo-0.12.11: missing file /usr/local/share/applications/exo-terminal-emulator.desktop
libexo-0.12.11: missing file /usr/local/share/applications/exo-web-browser.desktop
Checking all packages:  43%
libfm-1.3.1: missing file /usr/local/share/applications/libfm-pref-apps.desktop
Checking all packages:  64%
nvidia-driver-440.100: checksum mismatch for /boot/modules/nvidia-modeset.ko
nvidia-driver-440.100: checksum mismatch for /boot/modules/nvidia.ko
Checking all packages:  74%
plank-0.11.89: missing file /usr/local/bin/plank
plank-0.11.89: missing file /usr/local/man/man1/plank.1.gz
Checking all packages:  85%
slim-1.3.6_21: missing file /usr/local/bin/slim
slim-1.3.6_21: missing file /usr/local/man/man1/slim.1.gz
Checking all packages:  96%
xinit-1.4.1,1: checksum mismatch for /usr/local/etc/X11/xinit/xinitrc
Checking all packages: 100%

Should I worry about this ?

I can’t perform the smartctl test because being a record usb, smartmontools won’t let me or i don’t know how to do it … ¿?

# smartctl -a /dev/da0
smartctl 7.1 2019-12-30 r5022 [FreeBSD 12.1-RELEASE-p6 amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/da0: Unknown USB bridge [0x04e8:0x6031 (0x000)]
Please specify device type with the -d option.

Use smartctl -h to get a usage summary

I hope I’m not disturbing anyone.
Nomad works well, this is simply to inform me a little about software and hardware.
:slight_smile:

2

Hi @judd,

No. The DSB tools have been installed via pkg (to register them), but we installed them over the existing installation from upstream. And we removed some files which are not needed.

I quote Wikipedia

For example, few external drives connected via USB and FireWire correctly send S.M.A.R.T. data over those interfaces. With so many ways to connect a hard drive (SCSI, Fibre Channel, ATA, SATA, SAS, SSA, and so on), it is difficult to predict whether S.M.A.R.T. reports will function correctly in a given system.

Even with a hard drive and interface that implements the specification, the computer’s operating system may not see the S.M.A.R.T. information because the drive and interface are encapsulated in a lower layer.

1 Like
3

I understand, thank you very much and very kindly for your time. :slight_smile: