Arch Linux

jaystrictor

Member

Registered: 2013-05-11

Posts: 9

NTFS filesystem mount: Connection timed out

Hi.
A few weeks ago, mounting NTFS partitions stopped working:

[root ~]# mount /dev/sda2 /mnt
mount: /mnt: filesystem mounted, but mount(8) failed: Connection timed out

There is nothing mounted under /mnt after this command returns.
Furthermore, it takes exactly 30 seconds:

[root ~]# time ntfs-3g /dev/sda2 /mnt
mount: /mnt: filesystem mounted, but mount(8) failed: Connection timed out

real	0m29.700s
user	0m0.110s
sys	0m0.753s
[root ~]#

But the NTFS filesystem is not corrupt:

[root ~]# ntfsls /dev/sda2
hiberfil.sys
Program Files (x86)
...

This happens to several distinct NTFS partition, both on local harddrives and on a USB stick.
Can anyone help, or show me how to dig into this problem further?

linux: 3.8.11-1
ntfs-3g: 2013.1.13-2
systemd: 203-2
gvfs: 1.16.1-1
fuse: 2.9.2-1
udisks2: 2.1.0-1
util-linux: 2.23-1

Jay

Last edited by jaystrictor (2013-05-11 15:44:49)

satanselbow

Member

Registered: 2011-06-15

Posts: 538

Re: NTFS filesystem mount: Connection timed out

Mounting directly to /mnt doesn't look like a good idea (neither logically nor practically) Create a sub folder and try that as the mount point.

# mkdir -p /mnt/my-external-drive
# mount /dev/sda2 /mnt/my-external-drive

Having a read of the wiki will shed more light on the subject too

jaystrictor

Member

Registered: 2013-05-11

Posts: 9

Re: NTFS filesystem mount: Connection timed out

The problem persists independent of the mount point.

The wiki does not seem to help. I did not find anything related there.

What really annoys me is the fact that the error message seems to not occur anywhere else, (at least when googling for it).

filesystem mounted, but mount(8) failed: Connection timed out

jaystrictor

Member

Registered: 2013-05-11

Posts: 9

Re: NTFS filesystem mount: Connection timed out

The problem is gone since the last 'pacman -Syu' on 2013-06-10.

konsgn

Member

Registered: 2014-04-22

Posts: 1

Re: NTFS filesystem mount: Connection timed out

Ok, I am having the same problem with my current set up, in addition to a bunch of other problems on the lenovo s230U. It seems there are no good bios versions yet that work well with linux.

anyway, systemd gives me an error at boot that says connection timed out:

systemctl status systemd-remount-fs.service

Produces:

● systemd-remount-fs.service - Remount Root and Kernel File Systems
   Loaded: loaded (/usr/lib/systemd/system/systemd-remount-fs.service; static)
   Active: failed (Result: exit-code) since Tue 2014-04-22 09:10:39 EDT; 23min ago
     Docs: man:systemd-remount-fs.service(8)
           http://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
  Process: 142 ExecStart=/usr/lib/systemd/systemd-remount-fs (code=exited, status=1/FAILURE)
 Main PID: 142 (code=exited, status=1/FAILURE)

Apr 22 09:10:09 arch systemd[1]: Starting Remount Root and Kernel File Systems...
Apr 22 09:10:39 arch systemd-remount-fs[142]: mount: /: filesystem mounted, but mount(8) failed: Connection timed out
Apr 22 09:10:39 arch systemd[1]: systemd-remount-fs.service: main process exited, code=exited, status=1/FAILURE
Apr 22 09:10:39 arch systemd[1]: Failed to start Remount Root and Kernel File Systems.
Apr 22 09:10:39 arch systemd[1]: Unit systemd-remount-fs.service entered failed state.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

Additionaly:

sudo mount -v -t ntfs-3g /dev/sdc1 /media/Kondrive/

produces the following after 30 seconds:

mount: /media/Kondrive: filesystem mounted, but mount(8) failed: Connection timed out

I tried downgrading util-linux but that didn't help,
also upgrading doesn't help.

Is there a better way to watch the mount program run? It seems like verbose doesn't help at all.

What package is the mount command related to? which should I try downgrading?

The annoying part about this is that nothing unique happened to cause it to break. It happened days after the last system update and I only tried updating it again after it started failing.

Any ideas?