You are not logged in.
Pages: 1
Hello,
when I try to pacman -Syu I cant, I get the message that a version of openjpeg, namly "openjpeg2-2.5.0-3", with a lot of files related to it are already in existance.
52 Packages are missing and can't be updated.
Is there a way to remove said package from the update queue via pacman?
Do I have to rm every called file that is blocking the update manually?
I'm kind of lost. Please help
EDIT:
I must have had lost my battery during an update.
...And once a whole while ago, I tried to manually remove the openjpeg package by renaming it, but then renamining it again. That must have been the root of the problem.
Last edited by Baboon9 (2023-09-29 03:44:11)
Offline
https://wiki.archlinux.org/title/Pacman … )%22_error
Something you need to ask yourself generally, why or how are these files in place without pacman knowing about that. And you might be facing disk corruption and should first check the SMART status of your device (run a long test, wait for the elapsed time, post the output of smartctl -a)
Maybe also post the actual output you are getting so we can give you more targeted advice: https://wiki.archlinux.org/title/List_o … n_services
These are the things you should do, for the literal answer to your question, that would constitute a partial update which is explicitly unsupported and might run you into a bunch of more trouble: https://wiki.archlinux.org/title/System … nsupported
Last edited by V1del (2023-09-28 14:45:33)
Offline
I redirected stdout to a textfile, removed some lines manually, cutted out the file paths, directed that in a new file and then mved all files in a tmp file.
Now I could have had my update.
Here is the ouput of $ smartctl -a sda -d ata
#################################smartctl test run###############
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.5.3-arch1-1] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, [url=http://www.smartmontools.org]www.smartmontools.org[/url]
=== START OF INFORMATION SECTION ===
Model Family: Samsung based SSDs
Device Model: Samsung SSD 850 PRO 256GB
Serial Number: S39KNX0J687645J
LU WWN Device Id: 5 002538 d421679d1
Firmware Version: EXM04B6Q
User Capacity: 256.060.514.304 bytes [256 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
TRIM Command: Available
Device is: In smartctl database 7.3/5528
ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4c
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Thu Sep 28 23:30:09 2023 CEST
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: ( 0) seconds.
Offline data collection
capabilities: (0x53) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
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: ( 133) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
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 0x0033 100 100 010 Pre-fail Always - 0
9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 2633
12 Power_Cycle_Count 0x0032 098 098 000 Old_age Always - 1781
177 Wear_Leveling_Count 0x0013 099 099 000 Pre-fail Always - 30
179 Used_Rsvd_Blk_Cnt_Tot 0x0013 100 100 010 Pre-fail Always - 0
181 Program_Fail_Cnt_Total 0x0032 100 100 010 Old_age Always - 0
182 Erase_Fail_Count_Total 0x0032 100 100 010 Old_age Always - 0
183 Runtime_Bad_Block 0x0013 100 100 010 Pre-fail Always - 0
187 Uncorrectable_Error_Cnt 0x0032 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0032 068 044 000 Old_age Always - 32
195 ECC_Error_Rate 0x001a 200 200 000 Old_age Always - 0
199 CRC_Error_Count 0x003e 100 100 000 Old_age Always - 0
235 POR_Recovery_Count 0x0012 099 099 000 Old_age Always - 82
241 Total_LBAs_Written 0x0032 099 099 000 Old_age Always - 10046204918
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 2316 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
255 0 65535 Read_scanning was never started
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
The above only provides legacy SMART information - try 'smartctl -x' for more
############################################################################################The Test just took a few seconds....?
Everything should be up and running again. Thanks V1del
Last edited by V1del (2023-09-28 23:41:46)
Offline
The test command will return immediately, but the drive will test itself for the remainder of the time which should be 2 mins for a short one and 133 minutes on a long one. That said from these values things do generally look fine, did you ever crash/power outage during an update or so?
In any case please mark as [SOLVED] by editing the title in your first post. And please wrap command outputs in [ code ] tags like I did for you now in the future, it makes longer outputs more readable.
Last edited by V1del (2023-09-28 23:42:31)
Offline
Pages: 1