trick.tar

.

I think I found the reason.

I had some files in /root and /home/plex/scripts/ but I found they were all gone after a reboot. Only empty directories were left. I searched online quickly and read some about array stop/start, so instead I just rebooted the system again. But before doing that, I created an empty file in those directoreis to see if it goes missing again. After another reboot, to my surprise, this time I even found the 'scripts' directory went missing under the 'plex' folder. How can this happen? Why files / directories disappear every time I reboot? root@Tower:/home/plex/scripts# ls root@Tower:/home/plex/scripts# touch test root@Tower:/home/plex/scripts# ls test root@Tower:/home/plex/scripts# cd ~ root@Tower:~# touch test root@Tower:~# ls mdcmd@ test root@Tower:~# Broadcast message from root@Tower (Mon Feb 28 09:33:55 2022): The system is going down for reboot NOW! Session was closed Linux 5.10.28-Unraid. root@Tower:~# ls mdcmd@ root@Tower:~# cd ../home/plex/ root@Tower:/home/plex# ls root@Tower:/home/plex# ls root@Tower:/home/plex# ls So you get what I mean with this. First reboot: just files were gone. empty directories were left. created empty test files in those directories. Second reboot: the empty directories were gone. Newly created files also went missing.

Oooh it needed 6.10 even with the force probe trick. I didn't know that. Thank you so much for the clarification! Hope you have a great day!

Thanks for your reply! I just attached that file.

Hi, I'm using Unraid 6.9.2 with Intel 12th gen 12600k which has UHD 770. After searching quite a while, I found a method saying about i915.force_probe=4680 and followed the instruction but it didn't work. In the syslog, below is all that looks about i915 (also attached full syslog) Starts with: Feb 23 04:07:33 Tower kernel: Linux version 5.10.28-Unraid (root@Develop) (gcc (GCC) 9.3.0, GNU ld version 2.33.1-slack15) #1 SMP Wed Apr 7 08:23:18 PDT 2021 Feb 23 04:07:33 Tower kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot i915.force_probe=4680 Feb 23 04:07:33 Tower kernel: x86/split lock detection: warning about user-space split_locks Feb 23 04:07:33 Tower kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Feb 23 04:07:33 Tower kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Feb 23 04:07:33 Tower kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Feb 23 04:07:33 Tower kernel: x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers' Feb 23 04:07:33 Tower kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Feb 23 04:07:33 Tower kernel: x86/fpu: xstate_offset[9]: 832, xstate_sizes[9]: 8 Feb 23 04:07:33 Tower kernel: x86/fpu: Enabled xstate features 0x207, context size is 840 bytes, using 'compacted' format. Feb 23 04:07:33 Tower kernel: BIOS-provided physical RAM map: omitted Feb 23 04:07:33 Tower kernel: percpu: Embedded 45 pages/cpu s145240 r8192 d30888 u262144 Feb 23 04:07:33 Tower kernel: pcpu-alloc: s145240 r8192 d30888 u262144 alloc=1*2097152 Feb 23 04:07:33 Tower kernel: pcpu-alloc: [0] 00 01 02 03 04 05 06 07 [0] 08 09 10 11 12 13 14 15 Feb 23 04:07:33 Tower kernel: Built 1 zonelists, mobility grouping on. Total pages: 8205059 Feb 23 04:07:33 Tower kernel: Policy zone: Normal Feb 23 04:07:33 Tower kernel: Kernel command line: BOOT_IMAGE=/bzimage initrd=/bzroot i915.force_probe=4680 Feb 23 04:07:33 Tower kernel: Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes, linear) Feb 23 04:07:33 Tower kernel: Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear) Feb 23 04:07:33 Tower kernel: mem auto-init: stack:off, heap alloc:off, heap free:off In BIOS it's set to use 'IGD'. I tried the other one 'PEG' but no difference. I tried using intel_gpu_top plugin with no luck. Along with this, I cannot boot into GUI mode, it just blinks a single underscore character after lots of messages that appear when you boot in the default mode. I also tried putting nomodeset into syslinux but didn't work. I just ignored it and decided not to use that mode at first, but it seems it's somehow related to this one too. (being not able to utilize iGPU). I thought it might be solved when the RC3 comes out but since no one was complaing about this, I might be the only one with this problem so I came up with idea that it might not be solved in RC3 and that is why I'm posting this.