Solved xinit-1.4.1,1: checksum mismatch

I checked the installed packages for checksum discrepancies:

# pkg check -s -a
Checking all packages: 94%
xinit-1.4.1,1: checksum mismatch for /usr/local/etc/X11/xinit/xinitrc
Checking all packages: 100%


Should I worry about this ?

The whole system works well. :confused:

# freebsd-version -uk
12.1-RELEASE-p9
12.1-RELEASE-p9



Thank you.
 
Dear judd,
a re-install of that package should not hurt, just to be on the safe side. You can delete the xinit-* files in /var/cache/pkg. Then run pkg upgrade -f xinit. This should download the package xinit-1.*.txz and reinstall it. In /var/cache/pkg you will find the package with some magic number and a link without that number pointing to that file. I am not sure if there is a simpler way. But it should fix the issue.
 
Dear judd,
a re-install of that package should not hurt, just to be on the safe side. You can delete the xinit-* files in /var/cache/pkg. Then run pkg upgrade -f xinit. This should download the package xinit-1.*.txz and reinstall it. In /var/cache/pkg you will find the package with some magic number and a link without that number pointing to that file. I am not sure if there is a simpler way. But it should fix the issue.

Perfectly resolved.
I really appreciate your help and experience!

# pkg check -s -a
Checking all packages: 100%



My respects.
 
There is one thing which came into my mind. Bit errors can happen any time and that is why checksums are useful. I just worry if the bit flip has happend with the download or on your hard disk. It might make sense to scrub the pool if you are using ZFS or check the health of the disk. I do not expect any issues, it would be just to be on the safe side.
 
Just update the metadata, your metadata is outdated: pkg update -f
 
There is one thing which came into my mind. Bit errors can happen any time and that is why checksums are useful.

Yes, we agree.

I just worry if the bit flip has happend with the download or on your hard disk.

The checksum of the discharge was checked and was correct.
As for the disk, I couldn't tell you. It is a Western Digital Green 480 GB SSD that is only eight months old and I understand that there may be some problem with it.

It might make sense to scrub the pool if you are using ZFS or check the health of the disk. I do not expect any issues, it would be just to be on the safe side.

I am using ZFS.
 
Just update the metadata, your metadata is outdated: pkg update -f

Thank you for your response. :)
It didn't work out:

# pkg check -s -a
Checking all packages: 94%
xinit-1.4.1,1: checksum mismatch for /usr/local/etc/X11/xinit/xinitrc
Checking all packages: 100%
 
As for the disk, I couldn't tell you. It is a Western Digital Green 480 GB SSD that is only eight months old and I understand that there may be some problem with it.
An issue is unlikely. But if you have time you can still verify it using sysutils/smartmontools and by scrubbing the pool. The scrub takes almost no time because it runs in the background. With the speed of SSDs it finishes surprisingly fast.
 
An issue is unlikely. But if you have time you can still verify it using sysutils/smartmontools and by scrubbing the pool. The scrub takes almost no time because it runs in the background. With the speed of SSDs it finishes surprisingly fast.

# geom disk list
Geom name: ada0
Providers:
1. Name: ada0
Mediasize: 480103981056 (447G)
Sectorsize: 512
Mode: r2w2e3
descr: WDC WDS480G2G0A-00JH30


I would be grateful if you could pass me the commands for smartmontools ?
 
Dear judd,
no problem. smartctl -h gives a summary.
To read out the data run smartctl -a /dev/ada0. For a short test run smartctl -t short /dev/ada0. smartctl -a /dev/ada0 will provide a lot of messages. I think the most interesting lines are related to error counts. If I remember correctly there are a few threads about disk health. But If you are in doubt just post the result. I am not the sysutils/smartmontools guru, but there are other users with more expertise who will give their comments.
 

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

=== START OF INFORMATION SECTION ===
Model Family: WD Blue and Green SSDs
Device Model: WDC WDS480G2G0A-00JH30
Serial Number: 19391D800614
LU WWN Device Id: 5 001b44 8b146f2d2
Firmware Version: UG220400
User Capacity: 480.103.981.056 bytes [480 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-3, ACS-2 T13/2015-D revision 3
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Fri Sep 4 10:39:52 2020 -03
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x11) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 83) minutes.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
5 Reallocated_Sector_Ct 0x0032 100 100 000 Old_age Always - 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 990
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 708
165 Block_Erase_Count 0x0032 100 100 000 Old_age Always - 566
166 Minimum_PE_Cycles_TLC 0x0032 100 100 --- Old_age Always - 6
167 Max_Bad_Blocks_per_Die 0x0032 100 100 --- Old_age Always - 38
168 Maximum_PE_Cycles_TLC 0x0032 100 100 --- Old_age Always - 8
169 Total_Bad_Blocks 0x0032 100 100 --- Old_age Always - 418
170 Grown_Bad_Blocks 0x0032 100 100 --- Old_age Always - 0
171 Program_Fail_Count 0x0032 100 100 000 Old_age Always - 0
172 Erase_Fail_Count 0x0032 100 100 000 Old_age Always - 0
173 Average_PE_Cycles_TLC 0x0032 100 100 000 Old_age Always - 6
174 Unexpected_Power_Loss 0x0032 100 100 000 Old_age Always - 54
184 End-to-End_Error 0x0032 100 100 --- Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
188 Command_Timeout 0x0032 100 100 --- Old_age Always - 0
194 Temperature_Celsius 0x0022 072 051 000 Old_age Always - 28 (Min/Max 9/51)
199 UDMA_CRC_Error_Count 0x0032 100 100 --- Old_age Always - 0
230 Media_Wearout_Indicator 0x0032 100 100 000 Old_age Always - 0x013d0114013d
232 Available_Reservd_Space 0x0033 100 100 005 Pre-fail Always - 100
233 NAND_GB_Written_TLC 0x0032 100 100 --- Old_age Always - 2882
234 NAND_GB_Written_SLC 0x0032 100 100 000 Old_age Always - 7012
241 Host_Writes_GiB 0x0030 100 100 000 Old_age Offline - 3138
242 Host_Reads_GiB 0x0030 100 100 000 Old_age Offline - 1412
244 Temp_Throttle_Status 0x0032 000 100 --- Old_age Always - 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]

Selective Self-tests/Logging not supported

root@solo:/home/solo # smartctl -t short /dev/ada0
smartctl 7.1 2019-12-30 r5022 [FreeBSD 12.1-RELEASE-p9 amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Short self-test routine immediately in off-line mode".
Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful.
Testing has begun.
Please wait 2 minutes for test to complete.
Test will complete after Fri Sep 4 10:42:37 2020 -03
Use smartctl -X to abort test.
 
169 Total_Bad_Blocks 0x0032 100 100 --- Old_age Always - 418
I am not sure about the item above. But if a disk with a size of almost half of a TB as a few bad blocks might be not avoidable, it is about statistics. It might time to worry if the number is increasing.
230 Media_Wearout_Indicator 0x0032 100 100 000 Old_age Always - 0x013d0114013d
232 Available_Reservd_Space 0x0033 100 100 005 Pre-fail Always - 100
As long as there are sufficient spare blocks it should be fine. I hope I will be corrected if my statements are wrong or incomplete.
 
Sometimes, you modify a file and forget you did it.

Next time, before correcting the problem, use pkg info -l xinit to list each file. Maybe you will recall what you have done. And if not, you can copy these files somewhere and use diff(1) to find what changed after reinstalling it (providing it's the same version).
 
Sometimes, you modify a file and forget you did it.

Sure, but in my case I haven't touched anything counterproductive lately, I'm very careful about that.

And if not, you can copy these files somewhere and use diff(1) to find what changed after reinstalling it (providing it's the same version).

I'll start reading about diff, I'll write it down and I'll take it into account from now on. ?

use pkg info -l xinit

Yes, it's the same version:

% pkg info -l xinit
xinit-1.4.1,1:
/usr/local/bin/startx
/usr/local/bin/xinit
/usr/local/etc/X11/xinit/xinitrc
/usr/local/man/man1/startx.1.gz
/usr/local/man/man1/xinit.1.gz
/usr/local/share/licenses/xinit-1.4.1,1/LICENSE
/usr/local/share/licenses/xinit-1.4.1,1/MIT
/usr/local/share/licenses/xinit-1.4.1,1/catalog.mk
 
Back
Top