[Bug 1509279] Re: Unable to securely remove file during wily install

[Iain Lane]

It looks like the drive had an error and was remounted read-only by the
kernel. From your syslog:

Oct 23 09:24:06 ubuntu kernel: [ 3725.082596] ata1.00: exception Emask 0x0 SAct 0x200 SErr 0x0 action 0x0
Oct 23 09:24:06 ubuntu kernel: [ 3725.082616] ata1.00: irq_stat 0x40000008
Oct 23 09:24:06 ubuntu kernel: [ 3725.082628] ata1.00: failed command: READ FPDMA QUEUED
Oct 23 09:24:06 ubuntu kernel: [ 3725.082650] ata1.00: cmd 60/08:48:b8:16:80/00:00:09:00:00/40 tag 9 ncq 4096 in
Oct 23 09:24:06 ubuntu kernel: [ 3725.082650]          res 41/40:48:ba:16:80/00:00:09:00:00/69 Emask 0x409 (media error) <F>
Oct 23 09:24:06 ubuntu kernel: [ 3725.082677] ata1.00: status: { DRDY ERR }
Oct 23 09:24:06 ubuntu kernel: [ 3725.082683] ata1.00: error: { UNC }
Oct 23 09:24:06 ubuntu kernel: [ 3725.084805] ata1.00: configured for UDMA/100
Oct 23 09:24:06 ubuntu kernel: [ 3725.084872] sd 0:0:0:0: [sda] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Oct 23 09:24:06 ubuntu kernel: [ 3725.084888] sd 0:0:0:0: [sda] tag#9 Sense Key : Medium Error [current] [descriptor] 
Oct 23 09:24:06 ubuntu kernel: [ 3725.084903] sd 0:0:0:0: [sda] tag#9 Add. Sense: Unrecovered read error - auto reallocate failed
Oct 23 09:24:06 ubuntu kernel: [ 3725.084919] sd 0:0:0:0: [sda] tag#9 CDB: Read(10) 28 00 09 80 16 b8 00 00 08 00
Oct 23 09:24:06 ubuntu kernel: [ 3725.084927] blk_update_request: I/O error, dev sda, sector 159389370
Oct 23 09:24:06 ubuntu kernel: [ 3725.084998] ata1: EH complete
Oct 23 09:24:06 ubuntu kernel: [ 3725.085092] EXT4-fs error (device sda1): __ext4_get_inode_loc:3927: inode #4987766: block 19923415: comm dpkg: unable to read itable block
Oct 23 09:24:06 ubuntu kernel: [ 3725.085481] Aborting journal on device sda1-8.
Oct 23 09:24:06 ubuntu kernel: [ 3725.085957] EXT4-fs (sda1): Remounting filesystem read-only
Oct 23 09:24:06 ubuntu kernel: [ 3725.085971] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4962: IO failure
Oct 23 09:24:06 ubuntu kernel: [ 3725.086162] EXT4-fs error (device sda1) in ext4_orphan_add:2816: IO failure
Oct 23 09:24:10 ubuntu kernel: [ 3729.304907] ata1.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x0
Oct 23 09:24:10 ubuntu kernel: [ 3729.304976] ata1.00: irq_stat 0x40000008
Oct 23 09:24:10 ubuntu kernel: [ 3729.304993] ata1.00: failed command: READ FPDMA QUEUED
Oct 23 09:24:10 ubuntu kernel: [ 3729.305016] ata1.00: cmd 60/08:c8:b8:16:80/00:00:09:00:00/40 tag 25 ncq 4096 in
Oct 23 09:24:10 ubuntu kernel: [ 3729.305016]          res 41/40:c8:ba:16:80/00:00:09:00:00/69 Emask 0x409 (media error) <F>
Oct 23 09:24:10 ubuntu kernel: [ 3729.305027] ata1.00: status: { DRDY ERR }
Oct 23 09:24:10 ubuntu kernel: [ 3729.305034] ata1.00: error: { UNC }
Oct 23 09:24:10 ubuntu kernel: [ 3729.309145] ata1.00: configured for UDMA/100
Oct 23 09:24:10 ubuntu kernel: [ 3729.309290] sd 0:0:0:0: [sda] tag#25 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Oct 23 09:24:10 ubuntu kernel: [ 3729.309303] sd 0:0:0:0: [sda] tag#25 Sense Key : Medium Error [current] [descriptor] 
Oct 23 09:24:10 ubuntu kernel: [ 3729.309315] sd 0:0:0:0: [sda] tag#25 Add. Sense: Unrecovered read error - auto reallocate failed
Oct 23 09:24:10 ubuntu kernel: [ 3729.309328] sd 0:0:0:0: [sda] tag#25 CDB: Read(10) 28 00 09 80 16 b8 00 00 08 00
Oct 23 09:24:10 ubuntu kernel: [ 3729.309335] blk_update_request: I/O error, dev sda, sector 159389370
Oct 23 09:24:10 ubuntu kernel: [ 3729.309409] ata1: EH complete
Oct 23 09:24:10 ubuntu kernel: [ 3729.309559] EXT4-fs error (device sda1): __ext4_get_inode_loc:3927: inode #4987766: block 19923415: comm dpkg: unable to read itable block
Oct 23 09:24:10 ubuntu kernel: [ 3729.359786] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4962: IO failure
Oct 23 09:24:10 ubuntu kernel: [ 3729.364736] EXT4-fs error (device sda1) in ext4_unlink:3030: IO failure

So, this seems like a bad drive to me, I'm afraid.


** Changed in: ubiquity (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1509279

Title:
  Unable to securely remove file during wily install

Status in ubiquity package in Ubuntu:
  Invalid

Bug description:
  Error during install of Wily "Unable to securely remove
  /target/usr/share/man/man8/pvdisplay.8.gz.dpkg-tmp Read only file
  system.

  The disc to which I was installing may possibly be unreliable.  If the
  symptom suggests that this might have been a disc problem then please
  mark this as invalid.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: ubiquity 2.21.37 [modified: lib/partman/automatically_partition/question]
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.365
  Date: Fri Oct 23 10:29:19 2015
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   LANGUAGE=en_GB.UTF-8
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1509279/+subscriptions