external hard drive randomly changes mount point

amaro · 2021-07-04 15:09:06

Hello everybody!

My external drive randomly changes mount point. I guess this happens after suspension. But not after every suspension. Say, once in a month.

Right now on the tabs column 'thunar' shows the 'right' path but if I click on a file it doesn't open.
At the same time on the devices column 'thunar' shows the changed path.

Here is the right path from 'thunar' tabs column

/run/media/***/TB/***/Language/

Here is the changed path from 'thunar' devices column

/run/media/***/TB1/***/Language/

Also, if I run 'fd' command in terminal using the 'right' path I get 0 results.

$ pwd
/run/media/***/TB
$ fd language

Here is the 'fstab' line

# cat /etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>

UUID=536fb205-802b-4b1b-a7f8-33773f578422  /run/media/***/TB   	ext4   	defaults,noatime		0 0

I don't know what causes it nor how to fix it. I usually unplug the device but there is probably a better way.

Any ideas on how to get it back to its original path and how to stop it from happening again are highly appreciated!
Thank you in advance!

Edit: I have just unmounted the device and unplugged it. But this time after plugging it it mounted at TB1. There must be something wrong here.

Last edited by amaro (2021-07-04 15:55:09)

seth · 2021-07-04 16:30:07

Is there a stale mount (at …/TB) when this happens?

amaro · 2021-07-04 17:31:24

I do not remember about the last time. But this time there was.
I closed all open files. Unmounted the device. Unplugged it. When I plugged it again it mounted correctly.

But I usually have several open files from that device. And the laptop goes into suspension a few times per day. And after suspension everything works fine.

Anyway, from your question I assume it's probably related to some of the open files.

seth · 2021-07-04 19:00:55

Yes, check your journal.
You're likely losing the device (eg. because of some USB issue) but it can't be umounted (because of the opened files would be a reasonable explanation) and then it gets mounted to a versioned path (by udisks)
You want to understand why the device is lost and prevent that.

amaro · 2021-07-05 04:21:00

I did

$ journalctl --since "2021-07-04 16:15:00" --until "2021-07-04 23:20:00"

I got a lot of messages. Most of them are like this

Jul 04 21:19:08 G0 org.freedesktop.thumbnails.Thumbnailer1[167596]: libpng error: Read Error
Jul 04 21:39:05 G0 org.freedesktop.thumbnails.Thumbnailer1[168237]: error: The metadata does not have a thumbnail property

But there are a bunch of 'ET4-fs' related messages.

$ journalctl --since "2021-07-04 16:15:00" --until "2021-07-04 23:20:00" | grep EXT4
Jul 04 16:47:48 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-vym: error -5 reading directory block
Jul 04 16:47:48 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-vym: error -5 reading directory block
Jul 04 16:47:48 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-vym: error -5 reading directory block
Jul 04 16:47:48 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-vym: error -5 reading directory block
Jul 04 16:47:48 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-vym: error -5 reading directory block
Jul 04 16:47:48 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-vym: error -5 reading directory block
Jul 04 16:47:48 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-vym: error -5 reading directory block
Jul 04 16:47:48 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-vym: error -5 reading directory block
Jul 04 16:47:48 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-vym: error -5 reading directory block
Jul 04 16:47:48 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-vym: error -5 reading directory block
Jul 04 16:48:23 G0 kernel: EXT4-fs warning: 4 callbacks suppressed
Jul 04 16:48:23 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm gvfsd-recent: error -5 reading directory block
Jul 04 16:48:26 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm gvfsd-recent: error -5 reading directory block
Jul 04 16:48:37 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-vym: error -5 reading directory block
Jul 04 16:48:37 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-vym: error -5 reading directory block
Jul 04 16:48:37 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-vym: error -5 reading directory block
Jul 04 16:48:37 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-vym: error -5 reading directory block
Jul 04 16:48:37 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-vym: error -5 reading directory block
Jul 04 16:48:37 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-vym: error -5 reading directory block
Jul 04 16:48:37 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-vym: error -5 reading directory block
Jul 04 16:48:37 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-vym: error -5 reading directory block
Jul 04 16:48:37 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-vym: error -5 reading directory block
Jul 04 16:48:37 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-vym: error -5 reading directory block
Jul 04 16:48:49 G0 kernel: EXT4-fs warning: 2 callbacks suppressed
Jul 04 16:48:49 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm gvfsd-recent: error -5 reading directory block
Jul 04 16:48:49 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm gvfsd-recent: error -5 reading directory block
Jul 04 17:15:43 G0 kernel: EXT4-fs (sdc1): warning: maximal mount count reached, running e2fsck is recommended
Jul 04 17:15:43 G0 kernel: EXT4-fs (sdc1): recovery complete
Jul 04 17:15:43 G0 kernel: EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null)
Jul 04 17:18:38 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:18:38 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:18:38 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:18:38 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:18:38 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:18:38 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:18:52 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:18:52 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:18:52 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:18:52 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:18:52 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:18:52 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:19:15 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:19:15 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:19:15 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:19:15 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:19:15 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:19:15 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:19:31 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:19:31 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:19:31 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:19:31 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:19:31 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:19:31 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:23:06 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:23:06 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:23:06 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:23:06 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:23:06 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:23:06 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:24:24 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:24:24 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:24:24 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:24:24 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:24:24 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:24:24 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 17:32:07 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm trizen: error -5 reading directory block
Jul 04 17:32:07 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm trizen: error -5 reading directory block
Jul 04 17:32:09 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pacman: error -5 reading directory block
Jul 04 17:33:04 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm youtube-dl: error -5 reading directory block
Jul 04 17:33:04 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm youtube-dl: error -5 reading directory block
Jul 04 17:33:04 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm youtube-dl: error -5 reading directory block
Jul 04 17:33:04 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm youtube-dl: error -5 reading directory block
Jul 04 17:33:04 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm youtube-dl: error -5 reading directory block
Jul 04 17:33:04 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm youtube-dl: error -5 reading directory block
Jul 04 17:33:04 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm youtube-dl: error -5 reading directory block
Jul 04 17:33:04 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm youtube-dl: error -5 reading directory block
Jul 04 17:33:04 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm youtube-dl: error -5 reading directory block
Jul 04 17:33:04 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm youtube-dl: error -5 reading directory block
Jul 04 17:36:27 G0 kernel: EXT4-fs warning: 2 callbacks suppressed
Jul 04 17:36:27 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm bash: error -5 reading directory block
Jul 04 17:36:30 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm mpv: error -5 reading directory block
Jul 04 17:36:30 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm mpv: error -5 reading directory block
Jul 04 17:36:30 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm mpv: error -5 reading directory block
Jul 04 17:36:30 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm mpv: error -5 reading directory block
Jul 04 17:36:30 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm mpv: error -5 reading directory block
Jul 04 17:44:37 G0 kernel: EXT4-fs error (device sdb1): __ext4_find_entry:1530: inode #26216633: comm mupdf: reading directory lblock 0
Jul 04 17:44:37 G0 kernel: EXT4-fs error (device sdb1): __ext4_find_entry:1530: inode #26216633: comm mupdf: reading directory lblock 0
Jul 04 18:03:38 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 18:03:38 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 18:03:38 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 18:03:38 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 18:03:38 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 18:03:38 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm fd: error -5 reading directory block
Jul 04 18:31:27 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-chromium: error -5 reading directory block
Jul 04 18:31:28 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-chromium: error -5 reading directory block
Jul 04 18:31:28 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-chromium: error -5 reading directory block
Jul 04 18:31:28 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-chromium: error -5 reading directory block
Jul 04 18:31:28 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-chromium: error -5 reading directory block
Jul 04 18:31:28 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-chromium: error -5 reading directory block
Jul 04 18:31:28 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-chromium: error -5 reading directory block
Jul 04 18:31:28 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-chromium: error -5 reading directory block
Jul 04 18:31:28 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-chromium: error -5 reading directory block
Jul 04 18:31:28 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-chromium: error -5 reading directory block
Jul 04 18:31:35 G0 kernel: EXT4-fs warning: 2 callbacks suppressed
Jul 04 18:31:35 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm gvfsd-recent: error -5 reading directory block
Jul 04 18:31:36 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm gvfsd-recent: error -5 reading directory block
Jul 04 18:37:57 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-chromium: error -5 reading directory block
Jul 04 18:37:57 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-chromium: error -5 reading directory block
Jul 04 18:37:57 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-chromium: error -5 reading directory block
Jul 04 18:37:57 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-chromium: error -5 reading directory block
Jul 04 18:37:57 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-chromium: error -5 reading directory block
Jul 04 18:37:57 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-chromium: error -5 reading directory block
Jul 04 18:37:57 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-chromium: error -5 reading directory block
Jul 04 18:37:57 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-chromium: error -5 reading directory block
Jul 04 18:37:57 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-chromium: error -5 reading directory block
Jul 04 18:37:57 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-chromium: error -5 reading directory block
Jul 04 18:38:12 G0 kernel: EXT4-fs warning: 2 callbacks suppressed
Jul 04 18:38:12 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm gvfsd-recent: error -5 reading directory block
Jul 04 18:38:14 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm gvfsd-recent: error -5 reading directory block
Jul 04 18:45:51 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-Thunar: error -5 reading directory block
Jul 04 18:45:51 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-Thunar: error -5 reading directory block
Jul 04 18:45:51 G0 kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:997: inode #26216633: lblock 0: comm pool-Thunar: error -5 reading directory block
Jul 04 18:45:51 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm Thunar: error -5 reading directory block
Jul 04 18:45:51 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm Thunar: error -5 reading directory block
Jul 04 18:45:51 G0 kernel: EXT4-fs error (device sdb1): __ext4_find_entry:1530: inode #34209793: comm Thunar: reading directory lblock 0
Jul 04 18:45:51 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-Thunar: error -5 reading directory block
Jul 04 18:45:51 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-Thunar: error -5 reading directory block
Jul 04 18:45:51 G0 kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:997: inode #26216633: lblock 0: comm pool-Thunar: error -5 reading directory block
Jul 04 18:46:18 G0 kernel: EXT4-fs (sdc1): warning: maximal mount count reached, running e2fsck is recommended
Jul 04 18:46:18 G0 kernel: EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null)
Jul 04 18:47:55 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-Thunar: error -5 reading directory block
Jul 04 18:47:55 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-Thunar: error -5 reading directory block
Jul 04 18:47:55 G0 kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:997: inode #26216633: lblock 0: comm pool-Thunar: error -5 reading directory block
Jul 04 18:47:55 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm Thunar: error -5 reading directory block
Jul 04 18:47:55 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm Thunar: error -5 reading directory block
Jul 04 18:47:55 G0 kernel: EXT4-fs error (device sdb1): __ext4_find_entry:1530: inode #34209793: comm Thunar: reading directory lblock 0
Jul 04 18:47:55 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-Thunar: error -5 reading directory block
Jul 04 18:47:55 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-Thunar: error -5 reading directory block
Jul 04 18:47:55 G0 kernel: EXT4-fs warning (device sdb1): htree_dirblock_to_tree:997: inode #26216633: lblock 0: comm pool-Thunar: error -5 reading directory block
Jul 04 18:47:59 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-Thunar: error -5 reading directory block
Jul 04 18:47:59 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-Thunar: error -5 reading directory block
Jul 04 18:48:02 G0 kernel: EXT4-fs (sde1): warning: maximal mount count reached, running e2fsck is recommended
Jul 04 18:48:03 G0 kernel: EXT4-fs (sde1): mounted filesystem with ordered data mode. Opts: (null)
Jul 04 18:57:03 G0 kernel: EXT4-fs warning: 6 callbacks suppressed
Jul 04 18:57:03 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm pool-Thunar: error -5 reading directory block
Jul 04 19:00:09 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm spacefm: error -5 reading directory block
Jul 04 19:00:09 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm spacefm: error -5 reading directory block
Jul 04 19:06:38 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm Thunar: error -5 reading directory block
Jul 04 19:13:28 G0 kernel: EXT4-fs warning (device sdb1): dx_probe:761: inode #2: lblock 0: comm lsof: error -5 reading directory block
Jul 04 19:25:11 G0 kernel: EXT4-fs (sdb1): warning: maximal mount count reached, running e2fsck is recommended
Jul 04 19:25:11 G0 kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)

They are mostly warnings. But there are two error messages.
My guess is the issue is related to those two errors which are some files opened with 'mupdf'.

Jul 04 17:44:37 G0 kernel: EXT4-fs error (device sdb1): __ext4_find_entry:1530: inode #26216633: comm mupdf: reading directory lblock 0
Jul 04 17:44:37 G0 kernel: EXT4-fs error (device sdb1): __ext4_find_entry:1530: inode #26216633: comm mupdf: reading directory lblock 0

I also saw some warnings that e2fsck is needed.
I did

# tune2fs -l /dev/sdb1 | grep -E 'Mount|Max'
Mount count:              253
Maximum mount count:      31

# e2fsck /dev/sdb1
e2fsck 1.46.2 (28-Feb-2021)
TB has been mounted 253 times without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
TB: 162352/61054976 files (2.7% non-contiguous), 121698468/244190208 blocks

# tune2fs -l /dev/sdb1 | grep -E 'Mount|Max'
Mount count:              0
Maximum mount count:      31

What else can be done?

seth · 2021-07-05 14:20:24

The e2fsck situation is expectable since you uncleanly release the device over and over again. So are the various FS errors (because the FS is dirty)
What's most interesting is the (complete) part of the journal around an S3 cycle that leads to this condition.

amaro · 2021-07-06 02:54:01

seth wrote:

What's most interesting is the (complete) part of the journal around an S3 cycle that leads to this condition.

seth, I have to admit the meaning of this is a mystery to me.
I know all the words but I cannot figure out what 'around an S3 cycle' refers to.
Would you mind deciphering it?

seth · 2021-07-06 05:23:53

Hehe, sorry.
S3 is system sleep "suspend to ram", https://en.wikipedia.org/wiki/Advanced_ … wer_states
So the momen where you suspect to lose the device.

Arch Linux

#1 2021-07-04 15:09:06

external hard drive randomly changes mount point

#2 2021-07-04 16:30:07

Re: external hard drive randomly changes mount point

#3 2021-07-04 17:31:24

Re: external hard drive randomly changes mount point

#4 2021-07-04 19:00:55

Re: external hard drive randomly changes mount point

#5 2021-07-05 04:21:00

Re: external hard drive randomly changes mount point

#6 2021-07-05 14:20:24

Re: external hard drive randomly changes mount point

#7 2021-07-06 02:54:01

Re: external hard drive randomly changes mount point

#8 2021-07-06 05:23:53

Re: external hard drive randomly changes mount point

Board footer