package login 1:4.1.5.1-1ubuntu9 failed to install/upgrade: unable to securely remove '/etc/securetty.dpkg-new': Read-only file system

Bug #1479628 reported by Luis Echenique
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
shadow (Ubuntu)
Invalid
Low
Unassigned

Bug Description

core2duo e8500
ubuntu 14.04.2
/boot y / en ssd
/home, /var, /tmp y swap en hdd

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: login 1:4.1.5.1-1ubuntu9
ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14
Uname: Linux 3.16.0-45-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Thu Jul 30 02:01:45 2015
DpkgTerminalLog:
 Preparing to unpack .../login_1%3a4.1.5.1-1ubuntu9.1_amd64.deb ...
 Unpacking login (1:4.1.5.1-1ubuntu9.1) over (1:4.1.5.1-1ubuntu9) ...
 dpkg: error processing archive /var/cache/apt/archives/login_1%3a4.1.5.1-1ubuntu9.1_amd64.deb (--unpack):
  unable to securely remove '/etc/securetty.dpkg-new': Read-only file system
DuplicateSignature: package:login:1:4.1.5.1-1ubuntu9:unable to securely remove '/etc/securetty.dpkg-new': Read-only file system
ErrorMessage: unable to securely remove '/etc/securetty.dpkg-new': Read-only file system
InstallationDate: Installed on 2015-07-12 (17 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: shadow
Title: package login 1:4.1.5.1-1ubuntu9 failed to install/upgrade: unable to securely remove '/etc/securetty.dpkg-new': Read-only file system
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Luis Echenique (echeniqueluis) wrote :
tags: removed: need-duplicate-check
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 :

The following messages from your dmesg look like trouble..

[ 6196.836017] ata1: lost interrupt (Status 0x50)
[ 6196.836036] ata1.01: exception Emask 0x50 SAct 0x0 SErr 0x40d0802 action 0x0 frozen
[ 6196.836041] ata1.01: SError: { RecovComm HostInt PHYRdyChg CommWake 10B8B DevExch }
[ 6196.836044] ata1.01: failed command: READ DMA
[ 6196.836050] ata1.01: cmd c8/00:10:c0:63:e4/00:00:00:00:00/f2 tag 0 dma 8192 in
[ 6196.836050] res 40/00:00:00:4f:c2/00:00:00:00:00/10 Emask 0x54 (ATA bus error)
[ 6196.836052] ata1.01: status: { DRDY }
[ 6196.836060] ata1.00: hard resetting link
[ 6197.560013] ata1.01: hard resetting link
[ 6198.440053] ata1.00: SATA link down (SStatus 0 SControl 300)
[ 6198.440065] ata1.01: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 6198.505935] ata1.01: configured for UDMA/100
[ 6198.507485] ata1.01: device reported invalid CHS sector 0
[ 6198.507492] ata1: EH complete

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.