KDE Partition Manager - long start time (bug solved)

I'm thinking I've stumbled accross a rather nasty bug that I am surprised I can't find posted anywhere online.
I noticed this slow drive scanning process occaisionally before when KDE Partition Manager starts, but I just figured out why it was happening.

Most of the time my network shares (NFS) are usually up. I figured out from running journalctl -f that my nfs shares were causing the long delay when starting KDE Partition Manager. I checked the time on my logs and it took KDE Partition Manager a full half hour to start while doing the logging.

I tried changing my nfs mount paramaters , but nothing made any difference in my start times. Then I removed all my nfs mount lines from fstab and bingo, instant start up time.

Here are my journal entries while kde was starting and performing the drive scan process.

Summary
 tpc@htpc1 ~ 
$ journalctl -f
-- Logs begin at Sun 2018-10-28 07:25:33 MST. --
Oct 31 15:37:58 htpc1 systemd[643]: Starting Mark boot as successful...
Oct 31 15:37:58 htpc1 systemd[643]: Started Mark boot as successful.
Oct 31 15:42:29 htpc1 plasmashell[811]: trying to show an empty dialog
Oct 31 15:42:29 htpc1 plasmashell[811]: org.kde.plasmaquick: Applet "Application Menu" loaded after 0 msec
Oct 31 15:42:29 htpc1 plasmashell[811]: org.kde.plasmaquick: Increasing score for "Application Menu" to 97
Oct 31 15:42:29 htpc1 plasmashell[811]: QObject::startTimer: Timers cannot be started from another thread
Oct 31 15:42:29 htpc1 plasmashell[811]: QObject::startTimer: Timers cannot be started from another thread
Oct 31 15:42:32 htpc1 plasmashell[811]: trying to show an empty dialog
Oct 31 15:42:32 htpc1 plasmashell[811]: QObject::startTimer: Timers cannot be started from another thread
Oct 31 15:42:32 htpc1 plasmashell[811]: QObject::startTimer: Timers cannot be started from another thread
Oct 31 15:42:34 htpc1 kwin_x11[805]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 35494, resource id: 33554565, major code: 18 (ChangeProperty), minor code: 0
Oct 31 15:42:34 htpc1 kdesu[1366]: qt.core.logging: Ignoring malformed logging rule: '’*=false’'
Oct 31 15:42:35 htpc1 kdesud[1370]: qt.core.logging: Ignoring malformed logging rule: '’*=false’'
Oct 31 15:42:35 htpc1 plasmashell[811]: QObject::startTimer: Timers cannot be started from another thread
Oct 31 15:42:37 htpc1 plasmashell[811]: KActivitiesStats( 0x55e9ae5db4a0 ) ResultModelPrivate::onResultScoreUpdated  result added: "applications:org.kde.partitionmanager.desktop" score: 13.2286 last: 1541025754 first: 1538808294
Oct 31 15:42:50 htpc1 su[1375]: (to root) htpc on pts/5
Oct 31 15:42:50 htpc1 su[1375]: pam_unix(su:session): session opened for user root by (uid=1000)
Oct 31 15:42:50 htpc1 su[1375]: pam_unix(su:session): session closed for user root
Oct 31 15:42:50 htpc1 kwin_x11[805]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 38305, resource id: 65011729, major code: 18 (ChangeProperty), minor code: 0
Oct 31 15:42:50 htpc1 su[1378]: (to root) htpc on pts/5
Oct 31 15:42:50 htpc1 su[1378]: pam_unix(su:session): session opened for user root by (uid=1000)
Oct 31 15:42:51 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner)
Oct 31 15:42:51 htpc1 systemd[1]: Mounting /media/nfs/3tb...
Oct 31 15:42:51 htpc1 kernel: FS-Cache: Loaded
Oct 31 15:42:51 htpc1 kernel: FS-Cache: Netfs 'nfs' registered for caching
Oct 31 15:42:51 htpc1 kernel: Key type dns_resolver registered
Oct 31 15:42:52 htpc1 kernel: NFS: Registering the id_resolver key type
Oct 31 15:42:52 htpc1 kernel: Key type id_resolver registered
Oct 31 15:42:52 htpc1 kernel: Key type id_legacy registered
Oct 31 15:42:55 htpc1 plasmashell[811]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 4833, resource id: 54525969, major code: 142 (Unknown), minor code: 3
Oct 31 15:42:55 htpc1 plasmashell[811]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 4864, resource id: 69206022, major code: 142 (Unknown), minor code: 3
Oct 31 15:42:55 htpc1 plasmashell[811]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 4907, resource id: 69206119, major code: 142 (Unknown), minor code: 3
Oct 31 15:42:57 htpc1 plasmashell[811]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 5022, resource id: 54525969, major code: 142 (Unknown), minor code: 3
Oct 31 15:42:59 htpc1 kwin_x11[805]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40252, resource id: 54525969, major code: 15 (QueryTree), minor code: 0
Oct 31 15:43:53 htpc1 mount[1480]: mount.nfs: Connection timed out
Oct 31 15:43:53 htpc1 systemd[1]: media-nfs-3tb.mount: Mount process exited, code=exited status=32
Oct 31 15:43:53 htpc1 systemd[1]: media-nfs-3tb.mount: Failed with result 'exit-code'.
Oct 31 15:43:53 htpc1 systemd[1]: Failed to mount /media/nfs/3tb.
Oct 31 15:43:53 htpc1 systemd[1]: media-nfs-4tb.automount: Got automount request for /media/nfs/4tb, triggered by 1467 (m_DeviceScanner)
Oct 31 15:43:53 htpc1 systemd[1]: Mounting /media/nfs/4tb...
Oct 31 15:44:11 htpc1 plasmashell[811]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 5180, resource id: 69206119, major code: 142 (Unknown), minor code: 3
Oct 31 15:44:19 htpc1 plasmashell[811]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 5371, resource id: 69206022, major code: 142 (Unknown), minor code: 3
Oct 31 15:44:24 htpc1 kwin_x11[805]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 44245, resource id: 2097152, major code: 18 (ChangeProperty), minor code: 0
Oct 31 15:44:24 htpc1 kwin_x11[805]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 44252, resource id: 2097153, major code: 18 (ChangeProperty), minor code: 0
Oct 31 15:44:39 htpc1 wpa_supplicant[628]: wlp0s26f7u4: WPA: Group rekeying completed with 92:50:ca:34:12:10 [GTK=TKIP]
Oct 31 15:44:55 htpc1 mount[1505]: mount.nfs: Connection timed out
Oct 31 15:44:55 htpc1 systemd[1]: media-nfs-4tb.mount: Mount process exited, code=exited status=32
Oct 31 15:44:55 htpc1 systemd[1]: media-nfs-4tb.mount: Failed with result 'exit-code'.
Oct 31 15:44:55 htpc1 systemd[1]: Failed to mount /media/nfs/4tb.
Oct 31 15:44:55 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner)
Oct 31 15:44:55 htpc1 systemd[1]: Mounting /media/nfs/3tb...
Oct 31 15:45:47 htpc1 plasmashell[811]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:113: ReferenceError: appIcon is not defined
Oct 31 15:45:56 htpc1 mount[1678]: mount.nfs: Connection timed out
Oct 31 15:45:56 htpc1 systemd[1]: media-nfs-3tb.mount: Mount process exited, code=exited status=32
Oct 31 15:45:56 htpc1 systemd[1]: media-nfs-3tb.mount: Failed with result 'exit-code'.
Oct 31 15:45:56 htpc1 systemd[1]: Failed to mount /media/nfs/3tb.
Oct 31 15:45:56 htpc1 systemd[1]: media-nfs-4tb.automount: Got automount request for /media/nfs/4tb, triggered by 1467 (m_DeviceScanner)
Oct 31 15:45:56 htpc1 systemd[1]: Mounting /media/nfs/4tb...
Oct 31 15:46:57 htpc1 mount[1683]: mount.nfs: Connection timed out
Oct 31 15:46:57 htpc1 systemd[1]: media-nfs-4tb.mount: Mount process exited, code=exited status=32
Oct 31 15:46:57 htpc1 systemd[1]: media-nfs-4tb.mount: Failed with result 'exit-code'.
Oct 31 15:46:57 htpc1 systemd[1]: Failed to mount /media/nfs/4tb.
Oct 31 15:46:57 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner)
Oct 31 15:46:57 htpc1 systemd[1]: Mounting /media/nfs/3tb...
Oct 31 15:47:10 htpc1 plasmashell[811]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:113: ReferenceError: appIcon is not defined
Oct 31 15:47:58 htpc1 mount[1687]: mount.nfs: Connection timed out
Oct 31 15:47:58 htpc1 systemd[1]: media-nfs-3tb.mount: Mount process exited, code=exited status=32
Oct 31 15:47:58 htpc1 systemd[1]: media-nfs-3tb.mount: Failed with result 'exit-code'.
Oct 31 15:47:58 htpc1 systemd[1]: Failed to mount /media/nfs/3tb.
Oct 31 15:47:58 htpc1 systemd[1]: media-nfs-4tb.automount: Got automount request for /media/nfs/4tb, triggered by 1467 (m_DeviceScanner)
Oct 31 15:47:58 htpc1 systemd[1]: Mounting /media/nfs/4tb...
Oct 31 15:49:00 htpc1 mount[1693]: mount.nfs: Connection timed out
Oct 31 15:49:00 htpc1 systemd[1]: media-nfs-4tb.mount: Mount process exited, code=exited status=32
Oct 31 15:49:00 htpc1 systemd[1]: media-nfs-4tb.mount: Failed with result 'exit-code'.
Oct 31 15:49:00 htpc1 systemd[1]: Failed to mount /media/nfs/4tb.
Oct 31 15:49:00 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner)
Oct 31 15:49:00 htpc1 systemd[1]: Mounting /media/nfs/3tb...
Oct 31 15:50:03 htpc1 mount[1702]: mount.nfs: Connection timed out
Oct 31 15:50:03 htpc1 systemd[1]: media-nfs-3tb.mount: Mount process exited, code=exited status=32
Oct 31 15:50:03 htpc1 systemd[1]: media-nfs-3tb.mount: Failed with result 'exit-code'.
Oct 31 15:50:03 htpc1 systemd[1]: Failed to mount /media/nfs/3tb.
Oct 31 15:50:03 htpc1 systemd[1]: media-nfs-4tb.automount: Got automount request for /media/nfs/4tb, triggered by 1467 (m_DeviceScanner)
Oct 31 15:50:03 htpc1 systemd[1]: Mounting /media/nfs/4tb...
Oct 31 15:50:21 htpc1 systemd[1]: Starting Cleanup of Temporary Directories...
Oct 31 15:50:21 htpc1 systemd[1]: Started Cleanup of Temporary Directories.
Oct 31 15:50:21 htpc1 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 31 15:50:21 htpc1 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 31 15:50:21 htpc1 kernel: audit: type=1130 audit(1541026221.574:64): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 31 15:50:21 htpc1 kernel: audit: type=1131 audit(1541026221.574:65): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 31 15:51:05 htpc1 mount[1709]: mount.nfs: Connection timed out
Oct 31 15:51:05 htpc1 systemd[1]: media-nfs-4tb.mount: Mount process exited, code=exited status=32
Oct 31 15:51:05 htpc1 systemd[1]: media-nfs-4tb.mount: Failed with result 'exit-code'.
Oct 31 15:51:05 htpc1 systemd[1]: Failed to mount /media/nfs/4tb.
Oct 31 15:51:05 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner)
Oct 31 15:51:05 htpc1 systemd[1]: Mounting /media/nfs/3tb...
Oct 31 15:52:09 htpc1 mount[1716]: mount.nfs: Connection timed out
Oct 31 15:52:09 htpc1 systemd[1]: media-nfs-3tb.mount: Mount process exited, code=exited status=32
Oct 31 15:52:09 htpc1 systemd[1]: media-nfs-3tb.mount: Failed with result 'exit-code'.
Oct 31 15:52:09 htpc1 systemd[1]: Failed to mount /media/nfs/3tb.
Oct 31 15:52:09 htpc1 systemd[1]: media-nfs-4tb.automount: Got automount request for /media/nfs/4tb, triggered by 1467 (m_DeviceScanner)
Oct 31 15:52:09 htpc1 systemd[1]: Mounting /media/nfs/4tb...
Oct 31 15:53:10 htpc1 mount[1719]: mount.nfs: Connection timed out
Oct 31 15:53:10 htpc1 systemd[1]: media-nfs-4tb.mount: Mount process exited, code=exited status=32
Oct 31 15:53:10 htpc1 systemd[1]: media-nfs-4tb.mount: Failed with result 'exit-code'.
Oct 31 15:53:10 htpc1 systemd[1]: Failed to mount /media/nfs/4tb.
Oct 31 15:53:10 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner)
Oct 31 15:53:10 htpc1 systemd[1]: Mounting /media/nfs/3tb...
Oct 31 15:54:12 htpc1 mount[1727]: mount.nfs: Connection timed out
Oct 31 15:54:12 htpc1 systemd[1]: media-nfs-3tb.mount: Mount process exited, code=exited status=32
Oct 31 15:54:12 htpc1 systemd[1]: media-nfs-3tb.mount: Failed with result 'exit-code'.
Oct 31 15:54:12 htpc1 systemd[1]: Failed to mount /media/nfs/3tb.
Oct 31 15:54:12 htpc1 systemd[1]: media-nfs-4tb.automount: Got automount request for /media/nfs/4tb, triggered by 1467 (m_DeviceScanner)
Oct 31 15:54:12 htpc1 systemd[1]: Mounting /media/nfs/4tb...
Oct 31 15:54:39 htpc1 wpa_supplicant[628]: wlp0s26f7u4: WPA: Group rekeying completed with 92:50:ca:34:12:10 [GTK=TKIP]
Oct 31 15:55:14 htpc1 mount[1735]: mount.nfs: Connection timed out
Oct 31 15:55:14 htpc1 systemd[1]: media-nfs-4tb.mount: Mount process exited, code=exited status=32
Oct 31 15:55:14 htpc1 systemd[1]: media-nfs-4tb.mount: Failed with result 'exit-code'.
Oct 31 15:55:14 htpc1 systemd[1]: Failed to mount /media/nfs/4tb.
Oct 31 15:55:14 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner)
Oct 31 15:55:14 htpc1 systemd[1]: Mounting /media/nfs/3tb...
Oct 31 15:56:15 htpc1 mount[1747]: mount.nfs: Connection timed out
Oct 31 15:56:15 htpc1 systemd[1]: media-nfs-3tb.mount: Mount process exited, code=exited status=32
Oct 31 15:56:15 htpc1 systemd[1]: media-nfs-3tb.mount: Failed with result 'exit-code'.
Oct 31 15:56:15 htpc1 systemd[1]: Failed to mount /media/nfs/3tb.
Oct 31 15:56:15 htpc1 systemd[1]: media-nfs-4tb.automount: Got automount request for /media/nfs/4tb, triggered by 1467 (m_DeviceScanner)
Oct 31 15:56:15 htpc1 systemd[1]: Mounting /media/nfs/4tb...
Oct 31 15:57:19 htpc1 mount[1754]: mount.nfs: Connection timed out
Oct 31 15:57:19 htpc1 systemd[1]: media-nfs-4tb.mount: Mount process exited, code=exited status=32
Oct 31 15:57:19 htpc1 systemd[1]: media-nfs-4tb.mount: Failed with result 'exit-code'.
Oct 31 15:57:19 htpc1 systemd[1]: Failed to mount /media/nfs/4tb.
Oct 31 15:57:19 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner)
Oct 31 15:57:19 htpc1 systemd[1]: Mounting /media/nfs/3tb...
Oct 31 15:57:52 htpc1 plasmashell[811]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:113: ReferenceError: appIcon is not defined
Oct 31 15:58:24 htpc1 mount[1761]: mount.nfs: Connection timed out
Oct 31 15:58:24 htpc1 systemd[1]: media-nfs-3tb.mount: Mount process exited, code=exited status=32
Oct 31 15:58:24 htpc1 systemd[1]: media-nfs-3tb.mount: Failed with result 'exit-code'.
Oct 31 15:58:24 htpc1 systemd[1]: Failed to mount /media/nfs/3tb.
Oct 31 15:58:24 htpc1 systemd[1]: media-nfs-4tb.automount: Got automount request for /media/nfs/4tb, triggered by 1467 (m_DeviceScanner)
Oct 31 15:58:24 htpc1 systemd[1]: Mounting /media/nfs/4tb...
Oct 31 15:59:26 htpc1 mount[1765]: mount.nfs: Connection timed out
Oct 31 15:59:26 htpc1 systemd[1]: media-nfs-4tb.mount: Mount process exited, code=exited status=32
Oct 31 15:59:26 htpc1 systemd[1]: media-nfs-4tb.mount: Failed with result 'exit-code'.
Oct 31 15:59:26 htpc1 systemd[1]: Failed to mount /media/nfs/4tb.
Oct 31 15:59:27 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner)
Oct 31 15:59:27 htpc1 systemd[1]: Mounting /media/nfs/3tb...
Oct 31 16:00:28 htpc1 mount[1775]: mount.nfs: Connection timed out
Oct 31 16:00:28 htpc1 systemd[1]: media-nfs-3tb.mount: Mount process exited, code=exited status=32
Oct 31 16:00:28 htpc1 systemd[1]: media-nfs-3tb.mount: Failed with result 'exit-code'.
Oct 31 16:00:28 htpc1 systemd[1]: Failed to mount /media/nfs/3tb.
Oct 31 16:00:28 htpc1 systemd[1]: media-nfs-4tb.automount: Got automount request for /media/nfs/4tb, triggered by 1467 (m_DeviceScanner)
Oct 31 16:00:28 htpc1 systemd[1]: Mounting /media/nfs/4tb...
Oct 31 16:01:01 htpc1 CROND[1789]: (root) CMD (run-parts /etc/cron.hourly)
Oct 31 16:01:18 htpc1 kcmshell5[1793]: qt.core.logging: Ignoring malformed logging rule: '’*=false’'
Oct 31 16:01:29 htpc1 mount[1785]: mount.nfs: Connection timed out
Oct 31 16:01:29 htpc1 systemd[1]: media-nfs-4tb.mount: Mount process exited, code=exited status=32
Oct 31 16:01:29 htpc1 systemd[1]: media-nfs-4tb.mount: Failed with result 'exit-code'.
Oct 31 16:01:29 htpc1 systemd[1]: Failed to mount /media/nfs/4tb.
Oct 31 16:01:29 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner)
Oct 31 16:01:29 htpc1 systemd[1]: Mounting /media/nfs/3tb...
Oct 31 16:02:30 htpc1 mount[1798]: mount.nfs: Connection timed out
Oct 31 16:02:30 htpc1 systemd[1]: media-nfs-3tb.mount: Mount process exited, code=exited status=32
Oct 31 16:02:30 htpc1 systemd[1]: media-nfs-3tb.mount: Failed with result 'exit-code'.
Oct 31 16:02:30 htpc1 systemd[1]: Failed to mount /media/nfs/3tb.
Oct 31 16:02:30 htpc1 systemd[1]: media-nfs-4tb.automount: Got automount request for /media/nfs/4tb, triggered by 1467 (m_DeviceScanner)
Oct 31 16:02:30 htpc1 systemd[1]: Mounting /media/nfs/4tb...
Oct 31 16:03:38 htpc1 mount[1801]: mount.nfs: Connection timed out
Oct 31 16:03:38 htpc1 systemd[1]: media-nfs-4tb.mount: Mount process exited, code=exited status=32
Oct 31 16:03:38 htpc1 systemd[1]: media-nfs-4tb.mount: Failed with result 'exit-code'.
Oct 31 16:03:38 htpc1 systemd[1]: Failed to mount /media/nfs/4tb.
Oct 31 16:03:38 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner)
Oct 31 16:03:38 htpc1 systemd[1]: Mounting /media/nfs/3tb...
Oct 31 16:04:12 htpc1 plasmashell[811]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:113: ReferenceError: appIcon is not defined
Oct 31 16:04:39 htpc1 mount[1806]: mount.nfs: Connection timed out
Oct 31 16:04:39 htpc1 systemd[1]: media-nfs-3tb.mount: Mount process exited, code=exited status=32
Oct 31 16:04:39 htpc1 systemd[1]: media-nfs-3tb.mount: Failed with result 'exit-code'.
Oct 31 16:04:39 htpc1 systemd[1]: Failed to mount /media/nfs/3tb.
Oct 31 16:04:39 htpc1 systemd[1]: media-nfs-4tb.automount: Got automount request for /media/nfs/4tb, triggered by 1467 (m_DeviceScanner)
Oct 31 16:04:39 htpc1 systemd[1]: Mounting /media/nfs/4tb...
Oct 31 16:04:39 htpc1 wpa_supplicant[628]: wlp0s26f7u4: WPA: Group rekeying completed with 92:50:ca:34:12:10 [GTK=TKIP]
Oct 31 16:05:50 htpc1 mount[1812]: mount.nfs: Connection timed out
Oct 31 16:05:50 htpc1 systemd[1]: media-nfs-4tb.mount: Mount process exited, code=exited status=32
Oct 31 16:05:50 htpc1 systemd[1]: media-nfs-4tb.mount: Failed with result 'exit-code'.
Oct 31 16:05:50 htpc1 systemd[1]: Failed to mount /media/nfs/4tb.
Oct 31 16:05:50 htpc1 systemd[1]: media-nfs-3tb.automount: Got automount request for /media/nfs/3tb, triggered by 1467 (m_DeviceScanner)
Oct 31 16:05:50 htpc1 systemd[1]: Mounting /media/nfs/3tb...
Oct 31 16:06:11 htpc1 plasmashell[811]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 8048, resource id: 69206119, major code: 142 (Unknown), minor code: 3
Oct 31 16:06:11 htpc1 plasmashell[811]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 8079, resource id: 2097169, major code: 142 (Unknown), minor code: 3
Oct 31 16:06:13 htpc1 kcmshell5[1822]: qt.core.logging: Ignoring malformed logging rule: '’*=false’'
Oct 31 16:06:13 htpc1 kcmshell5[1822]: kcmshell5 with modules ' "org.kde.kcmshell_kcm_kdeconnect" ' is already running.
Oct 31 16:06:29 htpc1 kdeconnectd[830]: kdeconnect.core: Sending onNetworkChange to  1  LinkProviders
Oct 31 16:06:29 htpc1 kdeconnectd[830]: kdeconnect.core: Broadcasting identity packet
Oct 31 16:06:51 htpc1 mount[1819]: mount.nfs: Connection timed out
Oct 31 16:06:51 htpc1 systemd[1]: media-nfs-3tb.mount: Mount process exited, code=exited status=32
Oct 31 16:06:51 htpc1 systemd[1]: media-nfs-3tb.mount: Failed with result 'exit-code'.
Oct 31 16:06:51 htpc1 systemd[1]: Failed to mount /media/nfs/3tb.
Oct 31 16:06:51 htpc1 systemd[1]: media-nfs-4tb.automount: Got automount request for /media/nfs/4tb, triggered by 1467 (m_DeviceScanner)
Oct 31 16:06:51 htpc1 systemd[1]: Mounting /media/nfs/4tb...
Oct 31 16:07:52 htpc1 mount[1826]: mount.nfs: Connection timed out
Oct 31 16:07:52 htpc1 systemd[1]: media-nfs-4tb.mount: Mount process exited, code=exited status=32
Oct 31 16:07:52 htpc1 systemd[1]: media-nfs-4tb.mount: Failed with result 'exit-code'.
Oct 31 16:07:52 htpc1 systemd[1]: Failed to mount /media/nfs/4tb.
2 Likes

Interesting, I have been using KDE partition manager yesterday and today quite a bit and have not seen this issue. Hmm.....must be something different between our systems.

1 Like

As I say I have noticed this off and on in the past , but nothing like the delay times I'm experiencing now when the nfs lines are in fstab.

There are references online to long start times if you have a floppy drive enabled in your bios, but no floppy drive installed. However, I couldnt find a single reference to this situation anywhere else though.

My nfs mounts look like this:

nfs x-systemd.automount,x-systemd.device-timeout=10,timeo=14,x-systemd.idle-timeout=1min 0 0
1 Like

Thats pretty much exactly like mine was. I tried adding the soft paramater and other things and it didnt make the least bit of difference. I uninstalled/reinstalled the program and not a damn bit better.

I found this info at the KDE Partition Manager website:

On startup, KDE Partition Manager hangs for a couple of minutes while it apparently tries to scan the floppy drive on my computer.

This happens if you have a floppy drive configured in your computer's BIOS settings but have not actually connected one. If you do not have a floppy drive check your BIOS settings and disable any floppy drives configured there to see if this makes the problem go away.

During startup, KDE Partition Manager prints some message about probing devices and that it might even crash or at least take a long time.

LibParted, a backend library KDE Partition Manager uses, has problems with systems where the Linux Device Mapper is used in a way it doesn't understand. Unfortunately it reacts to some of these situations with segmentation faults, i.e. crashes. KDE Partition Manager therefore tries to avoid these situations by using an alternative way to scan your computer for disks. If it cannot do that, however, and therefore has to rely on LibParted, it will print a message like the one mentioned. If the scanning for disks works, you can safely disregard the message.

Just to clarify. The delays only occur when the network shares are offline/unmounted and the NFS load lines are in fstab.

Maybe leave NFSes out of fstab and start them later with a service!!!! :kissing_heart:
Now that you are so close to an expert level!!

Ya I was planning on writing a systemd mount unit to test if it would avoid this issue. I love fstab more than systemd though. :sob:

Aren't they equivalent? Doesn't systemd handle the fstab entries the same as mount units?

Yes they are equivelent, but maybe KPM won't choke if its not in fstab. Who knows, I was planning on writing a mount unit to find out. Either way its not the end of the world. I use gparted as well.

The one thing about KPM that I do prefer is its easy backup of partition tables.

I just tested with mine offline to be sure. Whatever the kde partition manager scanning process does causes them all to become mounted which makes sense since that seems to be what is failing for you.

1 Like

Exactly, but If your server is offline (in my case). It just keeps retrying and retrying to mount the nfs shares until it finally reaches some retry cutoff threshold and the program finally starts properly then.

I just had a thought @dalto, could you please check if you have all these enabled.

sudo systemctl status nfs-server.service

sudo systemctl status rpcbind.service

sudo systemctl status rpcbind.socket		

sudo systemctl status NetworkManager-wait-online.service		

sudo systemctl status rpc-statd.service		
     
sudo systemctl status nfs-client.target		

Sorry, I misread this the first time. I was thinking you meant offline as unmounted. You meant that your server was literally offline.

I took my server off the network and I see the same behavior as you.

1 Like

Thank you. I dont see how no one else could have noticed this if its not unique to my setup. I searched and searched, and couldnt find anything online. I don't just post something after only reading a post or two.

People who use KDE Partition Manager + systemd automounts + NFS shares + having their NFS server offline + having the skill to actually diagnose the problem. That might be a small group. :smile:

As a side note, I only started using the KDE partition manager in the last couple of weeks. I have been using gparted forever but I find that I am actually preferring KPM. It seems to be laid out more logically.

I totally agree I actually far prefer KPM from a usability standpoint, but from a reliability standpoint I'd take gparted any day. KPM is a little too buggy to trust difficult partitioning tasks to. The last thing I want is a crash on a partition resize operation.

Indeed. I resized 5.5TB partition with KPM yesterday and after about 8 hours I was starting to get nervous. :sweat:

Ouch, I don't blame you for being nervous.

Well I guess I've got some bug reporting to do now that this is confirmed.

(edit) bug report filed:

https://bugs.kde.org/show_bug.cgi?id=400540

3 Likes

The last thing I want is a crash on a partition resize operation.

It will be a bit better in KPM 4 where there is a separate process running as root to execute commands. Even if GUI crashes, the current command will finish, so e.g. data move will be complete (althouth, if partition boundaries need to be changed after that, it won't be done). Still much easier to recover than from interrupted data move which is basically impossible to recover from.
Can anybody retest this bug with KPM from git?

There were a lot of changes which might affect it (libparted backend was replaced with sfdisk).

fstab is not used at by KPM during the scan (but maybe some of the tools like libparted could have used it...). KPM only checks whether partition is mounted during the scan, it shouldn't try to mount it.

Thank you for your attention on this matter @stikonas .

I installed kpmcore-git and partitionmanager-git. The newer version ran fine without the NFS entries in fstab. Unfortunately, when the NFS entries were returned to fstab the exact same delays were experienced when starting Partition Manager.

I can't thank you enough for your rapid response. KDE definitely has a hard working team of developers in place. Please let me know if there are any further diagnostics you would like run.

Forum kindly sponsored by