package base-files 7.2ubuntu5 failed to install/upgrade: unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | base-files (Ubuntu) |
Undecided
|
Unassigned | ||
Bug Description
Not sure what else happened. I just got a dialog box about this failing.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: base-files 7.2ubuntu5
ProcVersionSign
Uname: Linux 3.13.0-29-generic i686
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
Date: Sun Aug 3 16:22:49 2014
Dependencies:
DpkgTerminalLog:
Preparing to unpack .../base-
Unpacking base-files (7.2ubuntu5.1) over (7.2ubuntu5) ...
dpkg: error processing archive /var/cache/
unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected
DuplicateSignature: package:
ErrorMessage: unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected
InstallationDate: Installed on 2013-05-16 (444 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
SourcePackage: base-files
Title: package base-files 7.2ubuntu5 failed to install/upgrade: unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected
UpgradeStatus: Upgraded to trusty on 2014-05-03 (92 days ago)
| rick wilson (rickw) wrote : | #1 |
| tags: | removed: need-duplicate-check |
Ok great I will make that s3 file system attach somewhere else. Thanks
Sent from my iPad
> On Aug 4, 2014, at 1:34 AM, Steve Langasek <email address hidden> wrote:
>
> This error message indicates that you have a non-default filesystem on
> /mnt that's in a problematic state. The base-files package provides the
> /mnt directory on the filesystem, so dpkg assumes it should be able to
> unpack that directory if necessary. I think you will need to unmount
> /mnt on your system to upgrade base-files.
>
> Marking this bug as invalid, because I don't believe there's anything we
> can do in base-files to mitigate this.
>
> ** Changed in: base-files (Ubuntu)
> Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> package base-files 7.2ubuntu5 failed to install/upgrade: unable to
> stat `./mnt' (which I was about to install): Transport endpoint is not
> connected
>
> Status in “base-files” package in Ubuntu:
> Invalid
>
> Bug description:
> Not sure what else happened. I just got a dialog box about this
> failing.
>
> ProblemType: Package
> DistroRelease: Ubuntu 14.04
> Package: base-files 7.2ubuntu5
> ProcVersionSign
> Uname: Linux 3.13.0-29-generic i686
> ApportVersion: 2.14.1-0ubuntu3.2
> Architecture: i386
> Date: Sun Aug 3 16:22:49 2014
> Dependencies:
>
> DpkgTerminalLog:
> Preparing to unpack .../base-
> Unpacking base-files (7.2ubuntu5.1) over (7.2ubuntu5) ...
> dpkg: error processing archive /var/cache/
> unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected
> DuplicateSignature: package:
> ErrorMessage: unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected
> InstallationDate: Installed on 2013-05-16 (444 days ago)
> InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
> SourcePackage: base-files
> Title: package base-files 7.2ubuntu5 failed to install/upgrade: unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected
> UpgradeStatus: Upgraded to trusty on 2014-05-03 (92 days ago)
>
> To manage notifications about this bug go to:
> https:/
This error message indicates that you have a non-default filesystem on /mnt that's in a problematic state. The base-files package provides the /mnt directory on the filesystem, so dpkg assumes it should be able to unpack that directory if necessary. I think you will need to unmount /mnt on your system to upgrade base-files.
Marking this bug as invalid, because I don't believe there's anything we can do in base-files to mitigate this.