You are not logged in.
Pages: 1
I have two problems which I think are closely related.
1) My projects are stored in another disk which i mount to /mnt/Projects to access them.
Now sometimes, randomly, while modifying some specific file, whether it be deleting or updating, the program modifying just gets stuck.
If i save it using the text editor, it gets stuck on the saving file dialog. Same thing happens while deleting, whether it be from a code editor, rm command or the file manager.
I have to force unmount the disk with umount -l and restart the computer, which later results in the file being corrupted.
The filesystem of that disk is ntfs.
Now the second problem,
Sometimes while shutting down, my computer gets stuck on some screen with text, which seem to be some kind of terminal.
Whenever it occurs, the pc shutdowns after a few minutes while outputting things like: waiting for process to exit or smth.
Usually I see this text at the cursor when this happens: "Connection to X server lost" or "GLIB Critical process ID 3 not found".
Now, the second problem occurs VERY VERY frequently when i have my disks mounted, and the problem one occurs.
And sometime all i need is to have my disks mounted, and the problem 2 will occur whether or not the 1st problem occurs.
What do I do?
Offline
* Is that an internal or external disk?
For the latter try to disable https://wiki.archlinux.org/title/Power_ … utosuspend - "usbcore.autosuspend=-1"
nb. that userspace powermanagement services like TLP can and will override this at runtime and you'll have to change the configuration there (as well)
* Is there a parallel windows installation?
3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
Offline
The article says ntfs-3g has a safeguard which prevents read-write mounting of hibernated fs. And I am not even mounting my windows drive. Is there any explanation for that?
Edit (Additional):
The Disk is a internal nvme ssd. Yes there's a parallel windows installation and I have just disabled fast-start with "powercfg /H off" as stated in the article.
Am I missing something? Because this happened again and one of my files stopped existing after I forced shutdown after it being stuck on the console after i clicked shutdown.
I used journalctl to see the log and it was stating that it was unmounting the filesystem, then after a min or so the umount timed out and that was the last log.
Last edited by d3vl4k5hy4 (Yesterday 12:27:47)
Offline
And are you using ntfs-3g?
Either way, the ramifications of fast-start go way beyond this, disabling it is entirely not optional.
I used journalctl to see the log and it was stating that it was unmounting the filesystem, then after a min or so the umount timed out and that was the last log.
https://wiki.archlinux.org/title/Kernel_parameters
Post the journal.
As for nvme's a common issue is APST, https://wiki.archlinux.org/title/Solid_ … leshooting
Offline
Journal: https://pastebin.com/x84UvPnm
Had happened when I stopped working on my project, closed vscodium and shutted down.
The file I had created and wrote in was gone.
Last edited by d3vl4k5hy4 (Yesterday 15:58:53)
Offline
Please don't copy and paste out of a pager (notice the stale newlines in your journal)
You're using ntfs3, not ntfs-3g (yes, it's confusing) and
Jul 27 14:59:50 devmachine kernel: ntfs3(sda1): Volume contains 2 bad blocks in 2 fragments.need to check
sudo smartctl -a /dev/sdaOther than tha
Jul 27 15:35:47 devmachine kernel: ------------[ cut here ]------------
Jul 27 15:35:47 devmachine kernel: kernel BUG at fs/iomap/buffered-io.c:1061!
Jul 27 15:35:47 devmachine kernel: Oops: invalid opcode: 0000 [#1] SMP NOPTI
Jul 27 15:35:47 devmachine kernel: CPU: 0 UID: 1000 PID: 12018 Comm: cmake Tainted: G OE 7.1.3-arch2-2 #1 PREEMPT(full) cf81b9d1a4a39be4b5e92e0c1c96594e14e8e6
c8
Jul 27 15:35:47 devmachine kernel: Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
Jul 27 15:35:47 devmachine kernel: Hardware name: ASUS System Product Name/PRIME B550M-A WIFI II, BIOS 2803 04/27/2022
Jul 27 15:35:47 devmachine kernel: RIP: 0010:iomap_write_end+0x1c8/0x1e0
Jul 27 15:35:47 devmachine kernel: Code: 8b 03 48 c1 e8 03 83 e0 01 74 10 e9 b4 fe ff ff 0f 0b eb 83 0f 0b e9 5a ff ff ff 4c 8b 74 24 18 e9 1e ff ff ff 4c 89 74 24 18 <0f> 0b
0f 0b 31 c0 e9 0e ff ff ff 66 90 66 66 2e 0f 1f 84 00 00 00
Jul 27 15:35:47 devmachine kernel: RSP: 0018:ffffcadbc7b6fb60 EFLAGS: 00010297
Jul 27 15:35:47 devmachine kernel: RAX: 0000000000000040 RBX: fffff916c556cdc0 RCX: fffff916c556cdc0
Jul 27 15:35:47 devmachine kernel: RDX: 0000000000000fc0 RSI: 0000000000000096 RDI: ffff898495536fc0
Jul 27 15:35:47 devmachine kernel: RBP: 0000000000000096 R08: ffffcadbc7b6fbd8 R09: 0000000000000000
Jul 27 15:35:47 devmachine kernel: R10: ffffcadbc7b6fdc0 R11: ffff8983cb989bc0 R12: 0000000000000000
Jul 27 15:35:47 devmachine kernel: R13: ffff89844710fa68 R14: 0000000000000096 R15: 0000000000000000
Jul 27 15:35:47 devmachine kernel: FS: 00007eff69d0fb40(0000) GS:ffff8988a4351000(0000) knlGS:0000000000000000
Jul 27 15:35:47 devmachine kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 27 15:35:47 devmachine kernel: CR2: 00005654abefba78 CR3: 000000010a0cd000 CR4: 0000000000f50ef0
Jul 27 15:35:47 devmachine kernel: PKRU: 55555554
Jul 27 15:35:47 devmachine kernel: Call Trace:
Jul 27 15:35:47 devmachine kernel: <TASK>
Jul 27 15:35:47 devmachine kernel: iomap_file_buffered_write+0x23f/0x450
Jul 27 15:35:47 devmachine kernel: ntfs_file_write_iter+0x803/0xb10 [ntfs3 589b3e1406eaeed71a92a1ae4cb388faed3be29e]
Jul 27 15:35:47 devmachine kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Jul 27 15:35:47 devmachine kernel: ? do_syscall_64+0xaa/0x660
Jul 27 15:35:47 devmachine kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Jul 27 15:35:47 devmachine kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Jul 27 15:35:47 devmachine kernel: ? security_file_permission+0x48/0x130
Jul 27 15:35:47 devmachine kernel: vfs_write+0x281/0x570
Jul 27 15:35:47 devmachine kernel: ksys_write+0x7b/0x110
Jul 27 15:35:47 devmachine kernel: do_syscall_64+0xaa/0x660
Jul 27 15:35:47 devmachine kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Jul 27 15:35:47 devmachine kernel: ? ksys_write+0x7b/0x110
Jul 27 15:35:47 devmachine kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Jul 27 15:35:47 devmachine kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Jul 27 15:35:47 devmachine kernel: ? do_syscall_64+0x5f/0x660
Jul 27 15:35:47 devmachine kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Jul 27 15:35:47 devmachine kernel: ? exc_page_fault+0x90/0x1f0
Jul 27 15:35:47 devmachine kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e
Jul 27 15:35:47 devmachine kernel: RIP: 0033:0x7eff6aa9405e
Jul 27 15:35:47 devmachine kernel: Code: 4d 89 d8 e8 84 bf 00 00 4c 8b 5d f8 41 8b 93 08 03 00 00 59 5e 48 83 f8 fc 74 11 c9 c3 0f 1f 80 00 00 00 00 48 8b 45 10 0f 05 <c9> c3
83 e2 39 83 fa 08 75 e7 e8 03 ff ff ff 0f 1f 00 f3 0f 1e fa
Jul 27 15:35:47 devmachine kernel: RSP: 002b:00007ffe26b30dd0 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
Jul 27 15:35:47 devmachine kernel: RAX: ffffffffffffffda RBX: 0000000000000096 RCX: 00007eff6aa9405e
Jul 27 15:35:47 devmachine kernel: RDX: 0000000000000096 RSI: 00005654abeef6d0 RDI: 0000000000000004
Jul 27 15:35:47 devmachine kernel: RBP: 00007ffe26b30de0 R08: 0000000000000000 R09: 0000000000000000
Jul 27 15:35:47 devmachine kernel: R10: 0000000000000000 R11: 0000000000000202 R12: 00005654abeef6d0
Jul 27 15:35:47 devmachine kernel: R13: 0000000000000096 R14: 0000000000000004 R15: 47e93c6a1e4b6723
Jul 27 15:35:47 devmachine kernel: </TASK>
Jul 27 15:35:47 devmachine kernel: Modules linked in: ntfs3 rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device algif_hash algif_skcipher af_alg bnep vfat fat snd_hda_code
c_alc662 amd_atl snd_hda_codec_realtek_lib mt7921e snd_hda_codec_nvhdmi snd_hda_codec_generic snd_hda_codec_hdmi mt7921_common intel_rapl_msr intel_rapl_common mt792x_lib snd_hda_intel mt76_connac_lib snd_hda_co
dec mt76 ucsi_ccg kvm_amd typec_ucsi snd_hda_core mac80211 roles snd_intel_dspcfg nvidia_drm(OE) btusb typec kvm snd_intel_sdw_acpi snd_hwdep btmtk thunderbolt irqbypass r8169 snd_pcm btrtl asus_armoury nvidia_m
odeset(OE) cfg80211 btbcm realtek snd_timer aesni_intel btintel firmware_attributes_class eeepc_wmi drm_ttm_helper snd phy_package asus_wmi gf128mul libarc4 ee1004 ttm mdio_devres bluetooth soundcore sparse_keym
ap rapl libphy video rfkill pcspkr wmi_bmof sp5100_tco mdio_bus ccp mousedev joydev k10temp i2c_nvidia_gpu i2c_piix4 i2c_smbus gpio_amdpt gpio_generic mac_hid nvidia_uvm(OE) nvidia(OE) aead i2c_dev pkcs8_key_par
ser ntsync crypto_user zram
Jul 27 15:35:47 devmachine kernel: 842_decompress 842_compress lz4hc_compress lz4_compress nvme nvme_core nvme_keyring nvme_auth wmi
Jul 27 15:35:47 devmachine kernel: ---[ end trace 0000000000000000 ]---but there're no HW errors logged.
No idea whether it's lost in the copypasta, but
lsblk -f; mount to illustrate what's mounted where and whether the nvme is actually relevant here.
Troublesome mount seems
Jul 27 16:19:39 devmachine systemd[1]: Unmounting /mnt/Projects...
Jul 27 16:21:09 devmachine systemd[1]: mnt-Projects.mount: Unmounting timed out. Terminating.
Jul 27 16:22:40 devmachine systemd[1]: mnt-Projects.mount: Mount process timed out. Killing.
Jul 27 16:22:40 devmachine systemd[1]: mnt-Projects.mount: Killing process 19260 (umount) with signal SIGKILL.This might also just be a bug in ntfs3 (don't ignore the bad blocks on sda, though!) so you could still test ntfs-3g
Offline
Jul 27 14:59:18 devmachine kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
Jul 27 14:59:18 devmachine kernel: PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000fffff]
Jul 27 14:59:18 devmachine kernel: PM: hibernation: Registered nosave memory: [mem 0x09d1f000-0x09ffffff]
Jul 27 14:59:18 devmachine kernel: PM: hibernation: Registered nosave memory: [mem 0x0a200000-0x0a20dfff]
Jul 27 14:59:18 devmachine kernel: PM: hibernation: Registered nosave memory: [mem 0x0b000000-0x0b01ffff]
Jul 27 14:59:18 devmachine kernel: PM: hibernation: Registered nosave memory: [mem 0xa8ad3000-0xa8ad3fff]
Jul 27 14:59:18 devmachine kernel: PM: hibernation: Registered nosave memory: [mem 0xa8b45000-0xa8b45fff]
Jul 27 14:59:18 devmachine kernel: PM: hibernation: Registered nosave memory: [mem 0xc42f0000-0xc43e3fff]
Jul 27 14:59:18 devmachine kernel: PM: hibernation: Registered nosave memory: [mem 0xc53ae000-0xc53aefff]
Jul 27 14:59:18 devmachine kernel: PM: hibernation: Registered nosave memory: [mem 0xc87e3000-0xcbbfefff]
Jul 27 14:59:18 devmachine kernel: PM: hibernation: Registered nosave memory: [mem 0xcd000000-0xffffffff]
Jul 27 14:59:18 devmachine kernel: [gap 0xd0000000-0xfe9fffff] available for PCI devices
Jul 27 14:59:18 devmachine kernel: Booting paravirtualized kernel on bare hardwareJul 27 15:35:51 devmachine kernel: TwoTriangles[12076]: segfault at 0 ip 0000000041ac4f41 sp 00007fff1694f128 error 4 in memfd:/.glXXXXXX[1f41,41ac3000+2000] likely on CPU 2 (core 2, socket 0)Jul 27 14:59:18 devmachine systemd[1]: Mounting Kernel Configuration File System...
Jul 27 14:59:18 devmachine systemd[1]: Load Kernel Module drm skipped, unmet condition check ConditionKernelModuleLoaded=!drm
Jul 27 14:59:18 devmachine systemd[1]: Load Kernel Module fuse skipped, unmet condition check ConditionKernelModuleLoaded=!fuse
Jul 27 14:59:18 devmachine systemd[1]: Mounting FUSE Control File System...
Jul 27 14:59:18 devmachine systemd[1]: File System Check on Root Device skipped, unmet condition check ConditionPathIsReadWrite=!/
Jul 27 14:59:18 devmachine systemd[1]: Clear Stale Hibernate Storage Info skipped, unmet condition check ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
Jul 27 14:59:18 devmachine systemd[1]: Starting Journal Service...
Jul 27 14:59:18 devmachine systemd[1]: Starting Load Kernel Modules...
Jul 27 14:59:18 devmachine systemd[1]: TPM PCR Machine ID Measurement skipped, unmet condition check ConditionSecurity=measured-os
Jul 27 14:59:18 devmachine systemd[1]: TPM PCR OS Separator skipped, unmet condition check ConditionSecurity=measured-os
Jul 27 14:59:18 devmachine systemd[1]: Starting Remount Root and Kernel File Systems...
Jul 27 14:59:18 devmachine systemd[1]: Early TPM SRK Setup skipped, unmet condition check ConditionSecurity=measured-os
Jul 27 14:59:18 devmachine systemd[1]: TPM PCR NvPCR Initialization Separator skipped, unmet condition check ConditionPathExists=/etc/initrd-release
Jul 27 14:59:18 devmachine systemd[1]: Reached target Local Encrypted Volumes.
Jul 27 14:59:18 devmachine systemd[1]: TPM NvPCR Product ID Measurement skipped, unmet condition check ConditionSecurity=measured-os
Jul 27 14:59:18 devmachine systemd[1]: Starting Load udev Rules from Credentials...
Jul 27 14:59:18 devmachine systemd[1]: Starting Coldplug All udev Devices...
Jul 27 14:59:18 devmachine systemd[1]: Finished Create List of Static Device Nodes.
Jul 27 14:59:18 devmachine kernel: EXT4-fs (sdc2): re-mounted b552ffc4-68a3-43ee-bb18-b6676c28d269.
Jul 27 14:59:18 devmachine systemd-journald[396]: Collecting audit messages is disabled.
Jul 27 14:59:18 devmachine systemd[1]: Mounted Huge Pages File System.
Jul 27 14:59:18 devmachine systemd[1]: Mounted POSIX Message Queue File System.
Jul 27 14:59:18 devmachine systemd[1]: Mounted Kernel Debug File System.
Jul 27 14:59:18 devmachine systemd[1]: Mounted Kernel Trace File System.
Jul 27 14:59:18 devmachine systemd[1]: Mounted Kernel Configuration File System.
Jul 27 14:59:18 devmachine systemd[1]: Mounted FUSE Control File System.
Jul 27 14:59:18 devmachine systemd[1]: Finished Remount Root and Kernel File Systems.
Jul 27 14:59:18 devmachine systemd[1]: Finished Load udev Rules from Credentials.
Jul 27 14:59:18 devmachine systemd[1]: Rebuild Hardware Database skipped, no trigger condition checks were met.
Jul 27 14:59:18 devmachine systemd[1]: Starting Load/Save OS Random Seed...
Jul 27 14:59:18 devmachine systemd[1]: Starting Create Static Device Nodes in /dev gracefully...
Jul 27 14:59:18 devmachine systemd[1]: TPM SRK Setup skipped, unmet condition check ConditionSecurity=measured-os
Jul 27 14:59:18 devmachine kernel: Asymmetric key parser 'pkcs8' registered
Jul 27 14:59:18 devmachine kernel: i2c_dev: i2c /dev entries driver
Jul 27 14:59:18 devmachine systemd-journald[396]: Journal startedJul 27 14:59:50 devmachine kernel: ntfs3(sda1): Volume contains 2 bad blocks in 2 fragments.Jul 27 16:00:33 devmachine kernel: RIP: 0010:iomap_write_end+0x1c8/0x1e0 Unmounting /boot...
Jul 27 16:19:39 devmachine systemd[1]: Unmounting /mnt/Data1...
Jul 27 16:19:39 devmachine systemd[1]: Unmounting /mnt/Games...
Jul 27 16:19:39 devmachine systemd[1]: Unmounting /mnt/Projects...
Jul 27 16:19:39 devmachine systemd[1]: Unmounting /mnt/Windows...
Jul 27 16:19:39 devmachine systemd[1]: Unmounting Temporary Directory /tmp...
Jul 27 16:19:39 devmachine systemd[1]: proc-sys-fs-binfmt_misc.mount: Deactivated successfully.
Jul 27 16:19:39 devmachine systemd[1]: tmp.mount: Deactivated successfully.
Jul 27 16:19:39 devmachine systemd[1]: Unmounted Temporary Directory /tmp.
Jul 27 16:19:39 devmachine systemd[1]: Stopped target Swaps.
Jul 27 16:19:39 devmachine systemd[1]: Deactivating swap /dev/disk/by-diskseq/5...
Jul 27 16:19:39 devmachine systemd[1]: boot.mount: Deactivated successfully.
Jul 27 16:19:39 devmachine systemd[1]: Unmounted /boot.
Jul 27 16:19:39 devmachine systemd[1]: dev-disk-by\x2ddiskseq-5.swap: Deactivated successfully.
Jul 27 16:19:39 devmachine systemd[1]: Deactivated swap /dev/disk/by-diskseq/5.
Jul 27 16:19:39 devmachine systemd[1]: dev-zram0.swap: Deactivated successfully.
Jul 27 16:19:39 devmachine systemd[1]: Deactivated swap Compressed Swap on /dev/zram0.
Jul 27 16:19:39 devmachine systemd[1]: systemd-fsck@dev-disk-by\x2duuid-C706\x2d7E91.service: Deactivated successfully.
Jul 27 16:19:39 devmachine systemd[1]: Stopped File System Check on /dev/disk/by-uuid/C706-7E91.
Jul 27 16:19:39 devmachine systemd[1]: Removed slice Slice /system/systemd-fsck.
Jul 27 16:19:39 devmachine systemd[1]: Stopping Create swap on /dev/zram0...
Jul 27 16:19:39 devmachine kernel: zram0: detected capacity change from 24479744 to 0
Jul 27 16:19:39 devmachine systemd[1]: mnt-Data1.mount: Deactivated successfully.
Jul 27 16:19:39 devmachine systemd[1]: Unmounted /mnt/Data1.
Jul 27 16:19:39 devmachine systemd[1]: mnt-Windows.mount: Deactivated successfully.
Jul 27 16:19:39 devmachine systemd[1]: Unmounted /mnt/Windows.
Jul 27 16:19:39 devmachine systemd[1]: mnt-Games.mount: Deactivated successfully.
Jul 27 16:19:39 devmachine systemd[1]: Unmounted /mnt/Games.
Jul 27 16:19:39 devmachine systemd[1]: systemd-zram-setup@zram0.service: Deactivated successfully.
Jul 27 16:19:39 devmachine systemd[1]: Stopped Create swap on /dev/zram0.
Jul 27 16:19:39 devmachine systemd[1]: Removed slice Slice /system/systemd-zram-setup.
Jul 27 16:21:09 devmachine systemd[1]: mnt-Projects.mount: Unmounting timed out. Terminating.
Jul 27 16:22:40 devmachine systemd[1]: mnt-Projects.mount: Mount process timed out. Killing.
Jul 27 16:22:40 devmachine systemd[1]: mnt-Projects.mount: Killing process 19260 (umount) with signal SIGKILL.just the Projects mount point couldn't be unmounted.
Last edited by aminepro (Yesterday 22:08:09)
Offline
how did I not see seth reply until now, more than half hour of delay. (ah cause I didn't refresh the page)
to not waste it all:
why there are many unmet conditions, are they relevant? I'll research the meaning of that.
read/writing errors "devmachine kernel: RIP: 0010:iomap_write_end+0x1c8/0x1e0" , file system is corrupted "Volume contains 2 bad blocks in 2 fragments."
and something hibernation related, maybe the hibernation would lead to corrupted file system
Last edited by aminepro (Yesterday 17:14:08)
Offline
@aminepro, pPlease use [code][/code] tags, not "quote" tags. Edit your post in this regard.
drm and fuse are already loaded, measured-os isn't supported, the root partition early on not writable and no hibernation image present
Offline
Happened yesterday again. this is the log: https://pastebin.com/VC6q9xvB
Will send other logs u asked with smartctl thing later.
Offline
@seth I think the problem is mostly related to what drive is being written to. I use a script to mount and dismount all of my additional drives.
It is:
```
mount /dev/nvme0n1p3 /mnt/Windows
mount /dev/sda1 /mnt/Data1
mount /dev/nvme0n1p5 /mnt/Projects
mount /dev/sdb1 /mnt/Games
```
And the drives other than Projects werent written to. This has happened before with the games drive when I was installing with Steam, it showed some disk read/write errors in steam and I couldnt shutdown that time either.
I fixed it with using chkdsk in windows tho. It seems it only happens when the drive have been written to sometime during the boot.
Here's the smartctl thing:
https://pastebin.com/PYj0rSNL
What I am I supposed to do now?
EDIT:
You're using ntfs3, not ntfs-3g
But I have ntfs-3g installed tho.
Last edited by d3vl4k5hy4 (Today 05:56:06)
Offline
Please don't copy and paste out of a pager (notice the stale newlines in your journal)
but there're actually no indications of any immediate mount IO problems in the latest journal.
Offline
@seth what can i do?
also
Please don't copy and paste out of a pager (notice the stale newlines in your journal)
What does that mean?
Offline
Cross-talk…
That's not the output of "mount"
Iff the troublesome partition is (always) nvme0n1p5 and iff windows fast-start (still) is disabled resp. you rebooted both OS after disabling it (that's not meant as a joke) and ifff those errors remain w/ ntfs-3g see the linked nvme troubleshooting, disable APST and in doubt use the software IOMMU.
But I have ntfs-3g installed tho.
Unless you also tell mount to use it, that's irrelevant.
Also see https://wiki.archlinux.org/title/Udisks … ed_drivers (GUI tools will typically use udisks)
183 Runtime_Bad_Block 0x0032 097 097 000 Old_age Always - 3
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 16
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 16https://wiki.archlinux.org/title/Badblocks
Keep a very close eye on those numbers and also
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0and make sure those don't move resp. prepare for the disk to die.
Eg. this line break isn't supposed to be there
Jul 28 06:20:12 devmachine kernel: efi: ACPI=0xc8cb4000 ACPI 2.0=0xc8cb4014 TPMFinalLog=0xca396000 SMBIOS=0xcb9f2000 SMBIOS 3.0=0xcb9f1000 MEMATTR=0xc541c018 ESRT=0xc53aef18 INITRD=0xbf372b18 RNG=0xc8c92c18 TPME
ventLog=0xc8b93018 You can upload the journal directly using
sudo journalctl -b | curl -s -H "Accept: application/json, */*" --upload-file - 'https://paste.c-net.org/'Offline
Iff the troublesome partition is (always) nvme0n1p5
Its not always nvme0n1, had happened with sdb1 itself, and i think it didnt happen after i did chkdsk.
Imma use ntfs-3g as `ntfs-3g /dev/nvem0n1pX /mnt/xyz`, Is this the correct way to mount with ntfs-3g? And I'll disable APST whatever that is and check if it works. Thanks tho.
Additional stuff:
Whenever the shutdown stuck thingy happens, my ps shuts down after like 5-10 mins after outputting some stuff.
Like doing this doing that, waiting from this process or that process.
And IIRC has happened even when I did not mount anything. Is there anything else that could be causing this, @seth?
Thanks tho,
EDIT:
Also is it okay to unmount after mounting with ntfs-3g command?
Last edited by d3vl4k5hy4 (Today 07:15:42)
Offline
Depending on what your actual processes/services are doing and for what reason they might remain active on any given device this can happen regardless of the FS. Best would be to get the journal of a boot where you had the unmounting failure and stuck processes with e.g.
sudo journalctl -b-1 | curl -s -H "Accept: application/json, */*" --upload-file - 'https://paste.c-net.org/'for the boot prior to your current one and so forth. umount should be fine after having done the mount with ntfs-3g directly. once it's clear which driver takes care of the mount, umount will do the relevant unmounting sequence of whatever driver is registered as the holder of a particular mount.
While you definitely should be weary of the general disk health state as given by the smartctl output, if you only disabled fast-start now and had potential FS corruption on the disk in question it might be a good idea to run a chkdsk on said disk from Windows, to make sure the filesystem is in a generally consistent state. While ntfs-3g has a bit more leeway in which kind of errors it "accepts" if your disk is in such a state that the FS integrity isn't guaranteed you should run a chkdsk on the disk in question from Windows.
Offline
The failure to umount on shutdown is one thing, the intermittent OOPS (#6) is a different beast that cannot be explained by "process refuses to die so filesystem fails to umount"
Offline
Pages: 1