Bug 477590

Created attachment 163517 [details]
Screenshot of notifications

SUMMARY
Running 6.7-rc2 kernel last week (Sunday Nov 19) had no problems. Upgrade to 6.7-rc3 today and reboot showed many "Filesystem is not responding, Filesystem mounted at xxx is not responding" messages. Tried older kernel from last week that worked and it doesn't, so it seems kernel has nothing to do with problem. 
Operating System: 
KDE neon 5.27
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11
Kernel Version: 6.7-rc3 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 570 Series
Manufacturer: ASUS
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Boot system, after KDE desktop shows, in about 9 seconds, the notifications of many "Filesystem not responding" messages appear.
2. Open Dolphin. All filesystems seems to be mounted and OK.
3. Reboot, same notifications appear.

OBSERVED RESULT
No ill effects are appareant. Everything works as before, as all mounted filesystems are fine in Dolphin. This is a 2+ year old install that never had this experience. I compile and update to the lastest kernel every week. Reverting to older kernels that didn't have this problem doesn't change anything.


EXPECTED RESULT
No "false" notifications of "Filesystem not responding" on boot.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: KDE neon 5.27
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11

ADDITIONAL INFORMATION : Attached