You are not logged in.

#1 2019-12-27 20:26:39

zaxdan69
Member
Registered: 2016-06-04
Posts: 318

Issue with mount disks

I have 4 partitons(in different disks) which I mount them in fstab:

#Datadisk 
UUID=D47604D77604BC6C	/media/datadisk 	ntfs-3g uid=1000,gid=1000,dmask=000,fmask=000,noauto,x-systemd.automount	0	0
#datadisk2 
UUID=3A0ED42E0ED3E145	/media/datadisk2	ntfs-3g uid=1000,gid=1000,dmask=000,fmask=0000,noauto,x-systemd.automount	0	0
#datadisk3
UUID=07C5895138DD0C86	/media/datadisk3	ntfs-3g uid=1000,gid=1000,dmask=000,fmask=0000,noauto,x-systemd.automount	0	0
#gamedisk
UUID=29C167B538DD0C86	/media/gamedisk		ntfs-3g uid=1000,gid=1000,dmask=000,fmask=0000,noauto,x-systemd.automount	0	0

I was watching a movie in kodi which was on datadisk2 and I paused it and I downloaded a subtitle which I tried to save on that disk. I get an error and I realized that the disk wasn't accessible any more. I closed kodi and I tried to unmount the drive from nemo. I wasn't able to unmount it and I tried to reboot the system. Reboot hanged because there was a task about unmounting that disk which couldn't complete.
I had this same issue some times before with a different disk(gamedisk), but because those times I did an update before I thought that caused by some update which need a reboot(a reboot always fix this issue).
I don't use any other OS except windows but not often and not for long times. I don't have any such problem in windows.
I also have dublicate entries for those disks in nemo and other file managers(thunar, double commander, krusader)  which is not normal and I'm thinking that something is wrong with the mounting of those disks and mayby this is responsible for that issue.
I haven't use any other way to mount those disks, I just created the directories in /media and added the entries in fstab.  I searched in /mnt, /run/media and /run/mount and there is no entry for any of those disks. Only in /run/mount there is a utab file with these contents:

SRC=/dev/sda1 TARGET=/media/gamedisk ROOT=/ OPTS=x-systemd.automount
SRC=/dev/sdc1 TARGET=/media/datadisk2 ROOT=/ OPTS=x-systemd.automount
SRC=/dev/sdb1 TARGET=/media/datadisk3 ROOT=/ OPTS=x-systemd.automount
SRC=/dev/sdd1 TARGET=/media/datadisk ROOT=/ OPTS=x-systemd.automount
SRC=/dev/sr0 TARGET=/run/media/userarch/GParted-live ROOT=/ OPTS=uhelper=udisks2

Also there are dublicate mounts in /proc/mounts:

systemd-1 /media/datadisk autofs rw,relatime,fd=49,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=16319 0 0
systemd-1 /media/datadisk2 autofs rw,relatime,fd=50,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=16322 0 0
systemd-1 /media/datadisk3 autofs rw,relatime,fd=52,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=16324 0 0
systemd-1 /media/gamedisk autofs rw,relatime,fd=53,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=16326 0 0

/dev/sda1 /media/gamedisk fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0
tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=1227056k,mode=700,uid=1000,gid=100 0 0
gvfsd-fuse /run/user/1000/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=100 0 0
/dev/fuse /run/user/1000/doc fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=100 0 0
/dev/sdc1 /media/datadisk2 fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0
/dev/sdb1 /media/datadisk3 fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0
/dev/sdd1 /media/datadisk fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0

Offline

#2 2019-12-27 22:28:43

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,731

Re: Issue with mount disks

I don't use any other OS except windows


https://wiki.archlinux.org/index.php/Du … t_Start-Up

But also ensure the health of the disk: https://wiki.archlinux.org/index.php/Smart

Offline

#3 2019-12-28 07:19:40

zaxdan69
Member
Registered: 2016-06-04
Posts: 318

Re: Issue with mount disks

Thanks.
I know about fast startup and it's already turned off. I also have  check the health of the disks.

Offline

#4 2019-12-28 11:16:49

loqs
Member
Registered: 2014-03-06
Posts: 19,045

Re: Issue with mount disks

Please post the output of `smartctl -a` for datadisk2 and the kernel messages from the boot with the issue.

Offline

#5 2019-12-28 11:54:48

zaxdan69
Member
Registered: 2016-06-04
Posts: 318

Re: Issue with mount disks

Here is the output from smartctl:

smartctl 7.0 2018-12-30 r4883 [x86_64-linux-5.4.6-arch3-1] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Blue
Device Model:     WDC WD10EZRZ-22HTKB0
Serial Number:    WD-WCC4J7DL1SHF
LU WWN Device Id: 5 0014ee 2b9fbf845
Firmware Version: 01.01A01
User Capacity:    1.000.204.886.016 bytes [1,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Sat Dec 28 13:35:36 2019 EET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82)	Offline data collection activity
					was completed without error.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever
					been run.
Total time to complete Offline
data collection: 		(13200) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 150) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x3035)	SCT Status supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   130   127   021    Pre-fail  Always       -       4500
  4 Start_Stop_Count        0x0032   099   099   000    Old_age   Always       -       1235
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   088   088   000    Old_age   Always       -       9308
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       1230
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       121
193 Load_Cycle_Count        0x0032   129   129   000    Old_age   Always       -       213149
193 Load_Cycle_Count        0x0032   129   129   000    Old_age   Always       -       213149
194 Temperature_Celsius     0x0022   118   103   000    Old_age   Always       -       25
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       8
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

But how to get the kernel messages from boot with the issue? This doesn't happen all the time. Is random and happens on different disks. I rebooted the system many times after that. Now the disk works again.

Offline

#6 2019-12-28 12:01:33

loqs
Member
Registered: 2014-03-06
Posts: 19,045

Re: Issue with mount disks

Journal#Filtering_output
I would suggest filtering all kernel messages for the day the issue occurred to try and locate the correct boot then you could filter kernel messages for just that boot.

Offline

#7 2019-12-28 13:29:41

zaxdan69
Member
Registered: 2016-06-04
Posts: 318

Re: Issue with mount disks

Since this happens about 21:00, I used journalctl from 19:30 to 22:00. Here is the output:
http://ix.io/25HD

I think here is the first related line:

21:04:09 arch-desktop kernel: BUG: unable to handle page fault for address: 000000005dff6e95

EDIT:
just happened again. I'm trying to unmount it and umount command just hangs. I have dmesg running but doesn't have anything about it.

Last edited by zaxdan69 (2019-12-28 13:57:19)

Offline

#8 2019-12-28 13:56:56

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,731

Re: Issue with mount disks

Δεκ 27 19:33:30 arch-desktop smartd[717]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 116 to 117

Even  if this is the stupidsilly Fahrenheit scale, that's 47°C (in actual temperatures) - unless this is an ssd, that's too hot.

The interesting bit looks like

Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.mount: Mounting timed out. Terminating.
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.mount: Mount process exited, code=killed, status=15/TERM
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.mount: Failed with result 'timeout'.
Δεκ 27 21:15:23 arch-desktop systemd[1]: Failed to mount /media/datadisk2.
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.automount: Got automount request for /media/datadisk2, triggered by 151253 (gvfs-udisks2-vo)
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.mount: Found left-over process 150161 (mount.ntfs-3g) in control group while starting unit. Ignoring.
Δεκ 27 21:15:23 arch-desktop systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Δεκ 27 21:15:23 arch-desktop systemd[1]: Mounting /media/datadisk2...
Δεκ 27 21:15:23 arch-desktop mount[151591]: Failed to write lock '/dev/sdc1': Ο πόρος είναι προσωρινά μη διαθέσιμος
Δεκ 27 21:15:23 arch-desktop mount[151591]: Error opening '/dev/sdc1': Ο πόρος είναι προσωρινά μη διαθέσιμος
Δεκ 27 21:15:23 arch-desktop mount[151591]: Failed to mount '/dev/sdc1': Ο πόρος είναι προσωρινά μη διαθέσιμος
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.mount: Mount process exited, code=exited, status=18/n/a
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.mount: Failed with result 'exit-code'.
Δεκ 27 21:15:23 arch-desktop systemd[1]: Failed to mount /media/datadisk2.
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.automount: Got automount request for /media/datadisk2, triggered by 151253 (gvfs-udisks2-vo)
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.mount: Found left-over process 150161 (mount.ntfs-3g) in control group while starting unit. Ignoring.
Δεκ 27 21:15:23 arch-desktop systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Δεκ 27 21:15:23 arch-desktop systemd[1]: Mounting /media/datadisk2...
Δεκ 27 21:15:23 arch-desktop mount[151595]: Failed to write lock '/dev/sdc1': Ο πόρος είναι προσωρινά μη διαθέσιμος
Δεκ 27 21:15:23 arch-desktop mount[151595]: Error opening '/dev/sdc1': Ο πόρος είναι προσωρινά μη διαθέσιμος
Δεκ 27 21:15:23 arch-desktop mount[151595]: Failed to mount '/dev/sdc1': Ο πόρος είναι προσωρινά μη διαθέσιμος
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.mount: Mount process exited, code=exited, status=18/n/a
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.mount: Failed with result 'exit-code'.
Δεκ 27 21:15:23 arch-desktop systemd[1]: Failed to mount /media/datadisk2.
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.automount: Got automount request for /media/datadisk2, triggered by 151083 (gnome-pie)
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.mount: Found left-over process 150161 (mount.ntfs-3g) in control group while starting unit. Ignoring.
Δεκ 27 21:15:23 arch-desktop systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Δεκ 27 21:15:23 arch-desktop systemd[1]: Mounting /media/datadisk2...
Δεκ 27 21:15:23 arch-desktop mount[151597]: Failed to write lock '/dev/sdc1': Ο πόρος είναι προσωρινά μη διαθέσιμος
Δεκ 27 21:15:23 arch-desktop mount[151597]: Error opening '/dev/sdc1': Ο πόρος είναι προσωρινά μη διαθέσιμος
Δεκ 27 21:15:23 arch-desktop mount[151597]: Failed to mount '/dev/sdc1': Ο πόρος είναι προσωρινά μη διαθέσιμος
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.mount: Mount process exited, code=exited, status=18/n/a
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.mount: Failed with result 'exit-code'.
Δεκ 27 21:15:23 arch-desktop systemd[1]: Failed to mount /media/datadisk2.
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.automount: Got automount request for /media/datadisk2, triggered by 151253 (gvfs-udisks2-vo)
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.mount: Found left-over process 150161 (mount.ntfs-3g) in control group while starting unit. Ignoring.
Δεκ 27 21:15:23 arch-desktop systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Δεκ 27 21:15:23 arch-desktop systemd[1]: Mounting /media/datadisk2...
Δεκ 27 21:15:23 arch-desktop mount[151601]: Failed to write lock '/dev/sdc1': Ο πόρος είναι προσωρινά μη διαθέσιμος
Δεκ 27 21:15:23 arch-desktop mount[151601]: Error opening '/dev/sdc1': Ο πόρος είναι προσωρινά μη διαθέσιμος
Δεκ 27 21:15:23 arch-desktop mount[151601]: Failed to mount '/dev/sdc1': Ο πόρος είναι προσωρινά μη διαθέσιμος
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.mount: Mount process exited, code=exited, status=18/n/a
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.mount: Failed with result 'exit-code'.
Δεκ 27 21:15:23 arch-desktop systemd[1]: Failed to mount /media/datadisk2.
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.automount: Got automount request for /media/datadisk2, triggered by 151083 (gnome-pie)
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.mount: Found left-over process 150161 (mount.ntfs-3g) in control group while starting unit. Ignoring.
Δεκ 27 21:15:23 arch-desktop systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Δεκ 27 21:15:23 arch-desktop systemd[1]: Mounting /media/datadisk2...
Δεκ 27 21:15:23 arch-desktop mount[151603]: Failed to write lock '/dev/sdc1': Ο πόρος είναι προσωρινά μη διαθέσιμος
Δεκ 27 21:15:23 arch-desktop mount[151603]: Error opening '/dev/sdc1': Ο πόρος είναι προσωρινά μη διαθέσιμος
Δεκ 27 21:15:23 arch-desktop mount[151603]: Failed to mount '/dev/sdc1': Ο πόρος είναι προσωρινά μη διαθέσιμος
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.mount: Mount process exited, code=exited, status=18/n/a
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.mount: Failed with result 'exit-code'.
Δεκ 27 21:15:23 arch-desktop systemd[1]: Failed to mount /media/datadisk2.
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.automount: Got automount request for /media/datadisk2, triggered by 151083 (gnome-pie)
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.mount: Start request repeated too quickly.
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.mount: Failed with result 'exit-code'.
Δεκ 27 21:15:23 arch-desktop systemd[1]: Failed to mount /media/datadisk2.
Δεκ 27 21:15:23 arch-desktop systemd[1]: media-datadisk2.automount: Failed with result 'mount-start-limit-hit'.
dead language teacher wrote:

Ο πόρος είναι προσωρινά μη διαθέσιμος
means
The resource is temporarily unavailable

Fuse loses track at some point for several disks, but the umount/automount cycles make me feel like there's either some power saving or undercurrent at play…
Does this happen periodically or is it maybe rather related to high system load (eg. watching an x265 encoded movie)?

The situation also seems to be cleared after the reboot (as suggested in OP) and the drives are sanely accessed.

Offline

#9 2019-12-28 14:03:45

zaxdan69
Member
Registered: 2016-06-04
Posts: 318

Re: Issue with mount disks

It just happens again now(I edited my previous answer). I had kodi opened but I didn't play anything. The only thing I did was to plug in a usb tv tuner which doesn't work to test something and unplug it afterworks because still didn't work. Then I connected a usb stick to copy a file and I found that the disk has lost connection again.

EDIT:
Because I want to avoid use windows, I switched to Linux Mint, to test for some days and see if the issue exist there too.

Last edited by zaxdan69 (2019-12-30 11:37:16)

Offline

Board footer

Powered by FluxBB