package login 1:4.11.1+dfsg1-2ubuntu1 failed to install/upgrade: unable to make backup link of './usr/bin/faillog' before installing new version: Input/output error

Bug #2008507 reported by brando smi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
shadow (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Not too sure what had happened.

ProblemType: Package
DistroRelease: Ubuntu 22.10
Package: login 1:4.11.1+dfsg1-2ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Architecture: amd64
Date: Fri Feb 24 16:25:41 2023
Df:

ErrorMessage: unable to make backup link of './usr/bin/faillog' before installing new version: Input/output error
PythonDetails: N/A
SourcePackage: shadow
Title: package login 1:4.11.1+dfsg1-2ubuntu1 failed to install/upgrade: unable to make backup link of './usr/bin/faillog' before installing new version: Input/output error
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
brando smi (microboujie) wrote :
Revision history for this message
Seth Arnold (seth-arnold) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment to this bug report it seems that there may be a problem with your hardware. I'd recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck!

Changed in shadow (Ubuntu):
status: New → Invalid
importance: Undecided → Low
tags: added: hardware-error
Revision history for this message
Seth Arnold (seth-arnold) wrote :

Hello, note the following lines from your dmesg:

[ 3.791052] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 3.791095] ata3.00: BMDMA stat 0x65
[ 3.791116] ata3.00: failed command: READ DMA
[ 3.791137] ata3.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in
                        res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
[ 3.791202] ata3.00: status: { DRDY ERR }
[ 3.791222] ata3.00: error: { ABRT }
[ 3.793984] ata3.00: configured for UDMA/133
[ 3.794009] ata3: EH complete
[ 3.806999] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 3.807047] ata3.00: BMDMA stat 0x65
[ 3.807068] ata3.00: failed command: READ DMA
[ 3.807089] ata3.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in
                        res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
[ 3.807154] ata3.00: status: { DRDY ERR }
[ 3.807174] ata3.00: error: { ABRT }
[ 3.809935] ata3.00: configured for UDMA/133
[ 3.809961] ata3: EH complete

There's lots of these in your logs -- they indicate failure communicating with the hard drive. This could be failing hard drive, bad cables, bad power supply, bad motherboard, etc.

I suggest making backups if you don't already have some -- do not overwrite old backups, you may need those. Then troubleshoot or replace etc.

Thanks

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.