求助!!!!更新6.10.2后所有共享中的文件夹都消失了


Go to solution Solved by marc126,

Recommended Posts

在系统更新里更新完6.10.2之后,点开共享里面所有文件夹都消失了,只剩下了docker和vm虚拟机也都打不开了,只剩下了lxc文件夹,虽然我可以手动挂载磁盘内的docker.img文件,但是之前我设置的所有东西都丢失了 。我尝试过替换flash设备里的config文件夹,和回滚到6.10.1,还是一点用都没有。1574544473_QQ20220528132312.thumb.png.7f2a7a9429d2c1cf2bc4b4a81b7daf06.png

之后我又尝试手动创建新的共享文件夹,但是当我移动磁盘里的system文件夹时又提示我可用空间不足(此时我的cache和两块硬盘的可用空间都远大于docker.img文件的占用空间。

下面是我创建了Downloads文件夹,Movies文件夹等新共享文件夹之后日志里面的报错,请问各位大佬我该怎么恢复我之前的配置呢

May 28 13:25:40 AlexStation sshd[32604]: Failed password for root from 43.156.66.251 port 42390 ssh2
May 28 13:25:40 AlexStation emhttpd: error: share_luks_status, 6158: Operation not supported (95): getxattr: /mnt/user/Downloads
May 28 13:25:40 AlexStation emhttpd: error: share_luks_status, 6158: Operation not supported (95): getxattr: /mnt/user/Movies
May 28 13:25:40 AlexStation emhttpd: error: share_luks_status, 6158: Operation not supported (95): getxattr: /mnt/user/appdata
May 28 13:25:40 AlexStation emhttpd: error: share_luks_status, 6158: Operation not supported (95): getxattr: /mnt/user/lxc
May 28 13:25:40 AlexStation emhttpd: error: share_luks_status, 6158: Operation not supported (95): getxattr: /mnt/user/system
May 28 13:25:40 AlexStation emhttpd: error: share_luks_status, 6158: Operation not supported (95): getxattr: /mnt/user/杂七杂八
May 28 13:25:41 AlexStation sshd[32604]: Received disconnect from 43.156.66.251 port 42390:11: Bye Bye [preauth]
May 28 13:25:41 AlexStation sshd[32604]: Disconnected from authenticating user root 43.156.66.251 port 42390 [preauth]

alexstation-diagnostics-20220528-1318.zip

Link to comment
  • 2 weeks later...
  • 1 month later...
3 minutes ago, Peelson said:

@ich777 hi~ we found a issue of lxc plugin.When I update to unraid 6.10.2,I lost all of my shares after a normal reboot.Dockers and vms are not working anymore...It resolved by removing lxc plugin.

Have you yet updated the plugin to version 2022.07.12?

 

A little bit of background information would be helpful…

Which path have you choosen for LXC?

Can you provide the Diagnostics?

Link to comment
On 6/1/2022 at 3:35 PM, marc126 said:

我升级到6.10.2后,再安装好LXC插件,一切正常使用,但是一旦重启就出现楼主一样的问题(共享只有LXC目录)。

 

删除LXC插件再重启,就恢复正常了。

 

应该是LXC插件问题

@alexmercer I would not describe this as a solution because if you want to use the LXC plugin it's definitely not solved...

 

What path did you choose for LXC?

 

EDIT: As described in the plugin, please don't use the FUSE file path /mnt/user/... use the real path instead, for example /mnt/cache/lxc or /mnt/disk1/lxc or on whatever disk your lxc share is on.

 

 

**The following is not related to LXC but please also give this attention**

 

EDIT2: From what I see in your syslog, your i915 module crashed after activating it:

May 28 13:00:27 AlexStation kernel: i915 0000:00:02.0: drm_WARN_ON(!IS_PLATFORM(dev_priv, INTEL_SKYLAKE) && !IS_PLATFORM(dev_priv, INTEL_KABYLAKE))
May 28 13:00:27 AlexStation kernel: WARNING: CPU: 2 PID: 3893 at drivers/gpu/drm/i915/intel_pch.c:61 intel_pch_type+0x560/0x9d2 [i915]
May 28 13:00:27 AlexStation kernel: Modules linked in: i915(+) iosf_mbi i2c_algo_bit ttm drm_kms_helper drm intel_gtt agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops efivarfs ip6table_filter ip6_tables iptable_filter ip_tables x_tables bonding e1000e r8169 realtek x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel nvme crypto_simd cryptd rapl intel_cstate intel_uncore i2c_i801 i2c_smbus i2c_core nvme_core ahci libahci fan thermal video backlight acpi_pad button [last unloaded: e1000e]
May 28 13:00:27 AlexStation kernel: CPU: 2 PID: 3893 Comm: modprobe Tainted: G     U            5.15.43-Unraid #1
May 28 13:00:27 AlexStation kernel: Hardware name: BIOSTAR Group GAMING H170T/GAMING H170T, BIOS 5.12 09/17/2021
May 28 13:00:27 AlexStation kernel: RIP: 0010:intel_pch_type+0x560/0x9d2 [i915]
May 28 13:00:27 AlexStation kernel: Code: 4c 8b 67 50 4d 85 e4 75 03 4c 8b 27 e8 38 7c 10 e1 48 c7 c1 0a b1 58 a0 4c 89 e2 48 c7 c7 9d ae 58 a0 48 89 c6 e8 93 80 3c e1 <0f> 0b b8 04 00 00 00 e9 62 04 00 00 48 85 ff 74 04 48 8b 7f 08 48
May 28 13:00:27 AlexStation kernel: RSP: 0018:ffffc9000397fb80 EFLAGS: 00010282
May 28 13:00:27 AlexStation kernel: RAX: 0000000000000000 RBX: ffff88814b520000 RCX: 0000000000000027
May 28 13:00:27 AlexStation kernel: RDX: 0000000000000003 RSI: ffffc9000397fa08 RDI: ffff888267d1c510
May 28 13:00:27 AlexStation kernel: RBP: 000000000018a100 R08: ffffffff822b4e28 R09: 0000000000000000
May 28 13:00:27 AlexStation kernel: R10: 000000000000005c R11: 0000000000000210 R12: ffff8881010503e0
May 28 13:00:27 AlexStation kernel: R13: ffff88810018a144 R14: ffff88814b526bb0 R15: ffff88814b5207d0
May 28 13:00:27 AlexStation kernel: FS:  0000152660836740(0000) GS:ffff888267d00000(0000) knlGS:0000000000000000
May 28 13:00:27 AlexStation kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 28 13:00:27 AlexStation kernel: CR2: 000015266066f000 CR3: 0000000106062003 CR4: 00000000003706e0
May 28 13:00:27 AlexStation kernel: Call Trace:
May 28 13:00:27 AlexStation kernel: <TASK>
May 28 13:00:27 AlexStation kernel: intel_detect_pch+0x7a/0x1e2 [i915]
May 28 13:00:27 AlexStation kernel: i915_driver_probe+0x27e/0xb81 [i915]
May 28 13:00:27 AlexStation kernel: ? _raw_spin_unlock_irqrestore+0x19/0x1b
May 28 13:00:27 AlexStation kernel: local_pci_probe+0x44/0x85
May 28 13:00:27 AlexStation kernel: pci_device_probe+0x145/0x197
May 28 13:00:27 AlexStation kernel: really_probe+0x11e/0x2e8
May 28 13:00:27 AlexStation kernel: __driver_probe_device+0x91/0xc0
May 28 13:00:27 AlexStation kernel: driver_probe_device+0x1e/0x73
May 28 13:00:27 AlexStation kernel: __driver_attach+0xb1/0xc5
May 28 13:00:27 AlexStation kernel: ? __device_attach_driver+0x85/0x85
May 28 13:00:27 AlexStation kernel: bus_for_each_dev+0x74/0xa9
May 28 13:00:27 AlexStation kernel: bus_add_driver+0x108/0x1b9
May 28 13:00:27 AlexStation kernel: driver_register+0x9e/0xd7
May 28 13:00:27 AlexStation kernel: i915_init+0x20/0x8f [i915]
May 28 13:00:27 AlexStation kernel: ? 0xffffffffa068f000
May 28 13:00:27 AlexStation kernel: do_one_initcall+0x78/0x178
May 28 13:00:27 AlexStation kernel: ? do_init_module+0x23/0x1f9
May 28 13:00:27 AlexStation kernel: ? kmem_cache_alloc_trace+0x11f/0x146
May 28 13:00:27 AlexStation kernel: do_init_module+0x4b/0x1f9
May 28 13:00:27 AlexStation kernel: __do_sys_init_module+0xb6/0xf5
May 28 13:00:27 AlexStation kernel: do_syscall_64+0x83/0xa5
May 28 13:00:27 AlexStation kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae
May 28 13:00:27 AlexStation kernel: RIP: 0033:0x15266096d18a
May 28 13:00:27 AlexStation kernel: Code: 48 8b 0d e1 7c 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d ae 7c 0c 00 f7 d8 64 89 01 48
May 28 13:00:27 AlexStation kernel: RSP: 002b:00007ffd5867e578 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
May 28 13:00:27 AlexStation kernel: RAX: ffffffffffffffda RBX: 00000000004293a0 RCX: 000015266096d18a
May 28 13:00:27 AlexStation kernel: RDX: 0000000000428780 RSI: 00000000004705d0 RDI: 00001526601ff010
May 28 13:00:27 AlexStation kernel: RBP: 00001526601ff010 R08: 0000000000000007 R09: 0000000000428330
May 28 13:00:27 AlexStation kernel: R10: 0000000000000001 R11: 0000000000000246 R12: 0000000000428780
May 28 13:00:27 AlexStation kernel: R13: 0000000000000000 R14: 00000000004294b0 R15: 00000000004293a0
May 28 13:00:27 AlexStation kernel: </TASK>
May 28 13:00:27 AlexStation kernel: ---[ end trace d4df3113f797b978 ]---

 

Maybe try to disable VT-d in your BIOS if you don't need it, this might solves this issue.

 

 

EDIT3: Please remove this entry from your go file if you got the Intel-GPU-TOP or Intel-GVT-g plugin installed:

#Setup drivers for hardware transcoding in Plex
modprobe i915
***line removed***
chmod 0777 /dev/dri/*

May I also ask why you got the GVT-g plugin installed? You have no VMs installed where you make use of it, it would be better to stick to the Intel-GPU-TOP plugin if you only want to use your iGPU for transcoding for Plex.

 

 

EDIT4: Please also consider upgrading to 6.10.3 because this is the latest version. I can only tell that I've also use LXC on a daily basis on my server and I've rebooted multiple times and have no issue whatsoever, not on my test server and not on my productive server (I use on both of the machines "/mnt/cache/lxc" as a path in the LXC settings) :

grafik.thumb.png.a996c34ecfd0065e3daf97898e284356.png

Link to comment
13 minutes ago, Peelson said:

not yet

What path have you choosen for LXC?

Please keep in mind that I never recommend that you don‘t use the FUSE path /mnt/user/… always use the real path like /mnt/cache/… or /mnt/diskX/… (like described on the plugin configuration page).

Link to comment
  • 2 weeks later...
On 7/12/2022 at 11:39 PM, ich777 said:

What path have you choosen for LXC?

Please keep in mind that I never recommend that you don‘t use the FUSE path /mnt/user/… always use the real path like /mnt/cache/… or /mnt/diskX/… (like described on the plugin configuration page).

I‘m sure I used /mnt/cache/...

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.