5

Today I have tried to update the package lists and I have encountered strange error 

$ sudo apt-get update
...
Ign http://archive.ubuntu.com saucy-security/universe Translation-en_US
Ign http://archive.ubuntu.com saucy-proposed/main Translation-en_US
Ign http://archive.ubuntu.com saucy-proposed/restricted Translation-en_US
Ign http://archive.ubuntu.com saucy-proposed/universe Translation-en_US
Fetched 496 kB in 38s (13.0 kB/s)
E: Unable to change to (unreachable)// - chdir (2: No such file or directory)

What should I change now ? Something in /etc/apt/sources.list ?

Improve this question
7
  • Please see this, bugs.launchpad.net/ubuntu/+source/apt/+bug/771780
    – Masroor
    Nov 7, 2013 at 1:35
  • Can you help me on what should I do in this situation ?
    – Patryk
    Nov 7, 2013 at 1:49
  • Is that Saucy installed or Beta version?
    – Braiam
    Nov 7, 2013 at 1:52
  • Does not look like I can of much assistance. The only advice we find there is something in the line of not detaching your drive while updating a system. Did you do something like that? If the answer is yes, do you want to try reattaching the drive and running update again? Good luck.
    – Masroor
    Nov 7, 2013 at 1:54
  • @Braiam That's Saucy installed.
    – Patryk
    Nov 7, 2013 at 12:08

4 Answers 4

Reset to default
11

I got this error message every time I ran sudo apt-get update with an encrypted home directory, while I was in my home directory.

If I cd'd to / first, the error went away.

(Ubuntu Server 13.10)

Improve this answer
4
  • 1
    I found my self in a removable disk that I had ejected. Changing into my home folder got me going again. This put me on the right path (literally).
    – Daniel
    Feb 11, 2014 at 23:32
  • This worked for me on 14.04 Server
    – Dennis
    Aug 15, 2014 at 13:12
  • Worked for me, but I would like to understand why. Do you have pointers that may explain this?
    – Zaccharie Ramzi
    May 20, 2019 at 9:07
  • @ZaccharieRamzi probably the directory isn't accessible by root (for encryption reasons) or some other user that the apt-get process setuids to.
    – Barry Kelly
    May 20, 2019 at 9:19
3

I had this happen today. It was because my current directory was mounted with sshfs. I don't know if it would occur with any FUSE file system or just sshfs, but the answer was to just get out of that directory. That is:

cd
sudo apt-get update
Improve this answer
1
  • That worked for me.
    – Igor V.
    Feb 28, 2017 at 10:11
3

Reinstalling libapt-pkg helped .

sudo apt-get install --reinstall libapt-pkg4.12
Improve this answer
0

Had the same issue when my current dir was a cluster fs. https://pve.proxmox.com/wiki/Proxmox_Cluster_File_System_(pmxcfs) change your current directory to a folder with a different file system. e.g. cd /

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .