You are not logged in.
Running fsck from the multi-user.target does not cause it to blow up, nothing suspicious in dmesg or journal either.
update: edited title since this is no longer exclusive to NTFS. will try running with the LTS kernel.
update 2: LTS kernel causes drive to crash.
Last edited by levalithan (Today 14:04:50)
Offline
Running fsck from the multi-user.target does not cause it to blow up, nothing suspicious in dmesg or journal either.
If otherwise fsck has reliably triggered the problem, can you replicate it
1. with a fresh user account
2. running a different session (eg. sway or icewm or so)
Offline
switching from qtile to bspwm, fsck works and drive doesn't seem to crash, even when booting vesktop (which will also usually reliably crash it). will compare my autostart scripts for both WMs to see what might be causing it, if anything.
edit: spoke too soon, it just crashed haha. will try on a new user account
edit 2: brand new user account has the same issue. fsck now (usually) works but opening vesktop or steam will reliably crash the disk after a certain amount of time.
Last edited by levalithan (Today 20:38:13)
Offline