ruepel

Members
  • Posts

    12
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

ruepel's Achievements

Noob

Noob (1/14)

0

Reputation

  1. hi there, after a couple of weeks of backing up and switching drives around I am still stuck with a RO drive in my array. Fix Common Issues tells me that disk3 is mounted read only. btrfs scrub of disk3 results in it being aborted after a few hours. SMART looks good on all the drives. What I have tried so far: backup up disk and test files on backup: worked resilver disk in place: worked mount array in production environment: worked for a couple of hours and then failed again (edited) Dec 3 17:01:06 X kernel: BTRFS warning (device dm-2): dm-2 checksum verify failed on 8243588595712 wanted 0x20266073 found 0x54c99e5c level 0 Dec 3 17:01:06 X kernel: BTRFS: error (device dm-2) in __btrfs_free_extent:3095: errno=-5 IO failure Dec 3 17:01:06 X kernel: BTRFS info (device dm-2): forced readonly Dec 3 17:01:06 X kernel: BTRFS: error (device dm-2) in btrfs_run_delayed_refs:2144: errno=-5 IO failure Dec 3 17:01:07 X kernel: BTRFS warning (device dm-2): failed setting block group ro: -30 Dec 4 04:40:25 X kernel: BTRFS error (device dm-2): parent transid verify failed on 865140736 wanted 133651 found 130063 Dec 4 04:40:27 X kernel: BTRFS error (device dm-2): error loading props for ino 194637 (root 5): -5 Dec 4 04:40:31 X kernel: BTRFS error (device dm-2): parent transid verify failed on 865140736 wanted 133651 found 130063 Dec 4 05:31:02 X kernel: BTRFS warning (device dm-2): csum failed root 5 ino 568257 off 0 csum 0xe9a722c6 expected csum 0x00000000 mirror 1 Dec 4 05:31:05 X kernel: BTRFS error (device dm-2): bdev /dev/mapper/md3 errs: wr 0, rd 0, flush 0, corrupt 4455, gen 0 Dec 4 05:31:12 X kernel: verify_parent_transid: 92 callbacks suppressed Dec 4 05:31:12 X kernel: BTRFS error (device dm-2): parent transid verify failed on 940867584 wanted 133651 found 130308 Dec 4 05:31:12 X kernel: btrfs_lookup_bio_sums: 92 callbacks suppressed Dec 4 05:31:12 X kernel: BTRFS info (device dm-2): no csum found for inode 568263 start 0 Dec 4 05:31:12 X kernel: BTRFS error (device dm-2): parent transid verify failed on 940867584 wanted 133651 found 130308 Dec 4 05:31:12 X kernel: BTRFS info (device dm-2): no csum found for inode 568263 start 4096 Dec 4 05:31:13 X kernel: BTRFS error (device dm-2): bdev /dev/mapper/md3 errs: wr 0, rd 0, flush 0, corrupt 4472, gen 0 Dec 4 05:31:13 X kernel: BTRFS warning (device dm-2): csum failed root 5 ino 568262 off 0 csum 0x95a1df60 expected csum 0x00000000 mirror 1 Dec 4 05:31:13 X kernel: BTRFS error (device dm-2): bdev /dev/mapper/md3 errs: wr 0, rd 0, flush 0, corrupt 4473, gen 0 Dec 4 05:31:36 X kernel: verify_parent_transid: 62 callbacks suppressed Dec 4 05:31:36 X kernel: BTRFS error (device dm-2): parent transid verify failed on 841433088 wanted 133651 found 130013 Dec 4 05:31:36 X kernel: btrfs_lookup_bio_sums: 62 callbacks suppressed All I can gleam from the log is dm-2 which I'm sure is disk3 or /dev/mapper/md3 throws btrfs errors and I don't quite know why. Granted the drive is 99% full (ie. has 250GB space left) but others are at 120GB or 90GB even and those disks don't have any problems. Has anyone any idea what might cause this issue? Is it the drive that is broken or is it the data on the drive? vulcan-diagnostics-20211204-1251.zip
  2. will do as soon as it happens again -- rebooted the server earlier without saving the diagnostic file first I guess we can close this thread and continue in @digitalformula's thread: https://forums.unraid.net/topic/81481-shares-disappearing-still-happening/
  3. will do as soon as it happens again -- rebooted the server earlier without saving the diagnostic file first
  4. i'm having the same issue. Let me guess, you perform a few file operations via nfs and suddenly the FS /mnt/user/ + /mnt/user0 disappears without a warning. @limetechIf it is a kernel issue when can we expect a solution/fix/rollback?
  5. could someone please take a look at this? it is still an issue and very, very annoying. thank you!
  6. still seeing the error. this time moving files in Dolphin resulted in nfsd crashing. I really hope, someone can help me. file management in the unraid console is no fun. Interesting observation: SMB shares weren't affected at all. this is part of the log when it happended: Jun 20 14:50:47 vulcan rpcbind[38947]: connect from 10.10.10.207 to getport/addr(nlockmgr) Jun 20 15:02:10 vulcan rpcbind[43080]: connect from 10.10.10.207 to getport/addr(nlockmgr) Jun 20 15:02:10 vulcan rpcbind[43081]: connect from 127.0.0.1 to getport/addr(status) Jun 20 15:02:10 vulcan rpcbind[43082]: connect from 127.0.0.1 to getport/addr(status) Jun 20 15:03:11 vulcan rpcbind[43751]: connect from 10.10.10.207 to getport/addr(nlockmgr) Jun 20 15:04:01 vulcan kernel: shfs[44161]: segfault at 10 ip 0000151606ddb381 sp 00001515d57adc10 error 4 in libfuse.so.2.9.9[151606dd7000+18000] Jun 20 15:04:01 vulcan kernel: Code: e8 94 cb ff ff 8b 83 cc 00 00 00 85 c0 0f 85 4e 01 00 00 4c 89 e6 48 89 df 4c 8d 7c 24 60 e8 b6 db ff ff 48 89 ef 48 8b 40 20 <4c> 8b 60 10 e8 36 c4 ff ff 45 31 c0 48 8d 4c 24 18 31 d2 4c 89 e6 Jun 20 15:04:01 vulcan kernel: ------------[ cut here ]------------ Jun 20 15:04:01 vulcan kernel: nfsd: non-standard errno: -103 Jun 20 15:04:01 vulcan kernel: WARNING: CPU: 3 PID: 7295 at fs/nfsd/nfsproc.c:820 nfserrno+0x44/0x4a [nfsd] Jun 20 15:04:01 vulcan kernel: Modules linked in: xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat nf_nat_ipv6 xt_nat iptable_mangle ip6table_filter ip6_tables vhost_net tun vhost tap veth ipt_MASQUERADE iptable_nat nf_nat_ipv4 iptable_filter ip_tables nf_nat dm_crypt algif_skcipher af_alg dm_mod dax nfsd lockd grace sunrpc md_mod ipmi_devintf bonding netxen_nic tg3 sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd glue_helper ipmi_ssif i2c_core intel_cstate intel_uncore acpi_power_meter intel_rapl_perf ahci libahci wmi megaraid_sas button ipmi_si pcc_cpufreq [last unloaded: netxen_nic] Jun 20 15:04:01 vulcan kernel: CPU: 3 PID: 7295 Comm: nfsd Not tainted 4.19.41-Unraid #1 Jun 20 15:04:01 vulcan kernel: Hardware name: Dell Inc. PowerEdge R520/051XDX, BIOS 2.5.1 02/08/2018 Jun 20 15:04:01 vulcan kernel: RIP: 0010:nfserrno+0x44/0x4a [nfsd] Jun 20 15:04:01 vulcan kernel: Code: c0 48 83 f8 22 75 e2 80 3d a7 06 01 00 00 bb 00 00 00 05 75 17 89 fe 48 c7 c7 bb a9 16 a0 c6 05 90 06 01 00 01 e8 02 f6 ee e0 <0f> 0b 89 d8 5b c3 48 83 ec 18 31 c9 ba ff 07 00 00 65 48 8b 04 25 Jun 20 15:04:01 vulcan kernel: RSP: 0018:ffffc90003bb7e20 EFLAGS: 00010282 Jun 20 15:04:01 vulcan kernel: RAX: 0000000000000000 RBX: 0000000005000000 RCX: 0000000000000007 Jun 20 15:04:01 vulcan kernel: RDX: 0000000000000006 RSI: ffff88881f6564f0 RDI: ffff88881f6564f0 Jun 20 15:04:01 vulcan kernel: RBP: ffffc90003bb7e50 R08: 0000000000000003 R09: 0000000000020300 Jun 20 15:04:01 vulcan kernel: R10: 000000000000063b R11: 0000000000020990 R12: ffff888675796018 Jun 20 15:04:01 vulcan kernel: R13: ffffffffa016a4d0 R14: 000000000000001c R15: ffffffffa016a220 Jun 20 15:04:01 vulcan kernel: FS: 0000000000000000(0000) GS:ffff88881f640000(0000) knlGS:0000000000000000 Jun 20 15:04:01 vulcan kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 20 15:04:01 vulcan kernel: CR2: 000014568cf72d00 CR3: 0000000001e0a005 CR4: 00000000000626e0 Jun 20 15:04:01 vulcan kernel: Call Trace: Jun 20 15:04:01 vulcan kernel: fill_post_wcc+0x69/0x122 [nfsd] Jun 20 15:04:01 vulcan kernel: nfsd3_proc_rmdir+0x6e/0x96 [nfsd] Jun 20 15:04:01 vulcan kernel: nfsd_dispatch+0xb4/0x169 [nfsd] Jun 20 15:04:01 vulcan kernel: svc_process+0x4fc/0x6b6 [sunrpc] Jun 20 15:04:01 vulcan kernel: ? nfsd_destroy+0x48/0x48 [nfsd] Jun 20 15:04:01 vulcan kernel: nfsd+0xeb/0x142 [nfsd] Jun 20 15:04:01 vulcan kernel: kthread+0x10b/0x113 Jun 20 15:04:01 vulcan kernel: ? kthread_park+0x71/0x71 Jun 20 15:04:01 vulcan kernel: ret_from_fork+0x35/0x40 Jun 20 15:04:01 vulcan kernel: ---[ end trace fdda59ca4cc54630 ]--- Jun 20 15:04:52 vulcan emhttpd: req (2): startState=STARTED&file=&optionCorrect=correct&csrf_token=****************&cmdStop=Stop Jun 20 15:04:52 vulcan kernel: mdcmd (59): nocheck cancel Jun 20 15:04:53 vulcan emhttpd: Spinning up all drives... Jun 20 15:04:53 vulcan emhttpd: shcmd (12791): /usr/sbin/hdparm -S0 /dev/sdj Jun 20 15:04:53 vulcan kernel: mdcmd (60): spinup 0 Jun 20 15:04:53 vulcan kernel: mdcmd (61): spinup 1 Jun 20 15:04:53 vulcan kernel: mdcmd (62): spinup 2 Jun 20 15:04:53 vulcan kernel: mdcmd (63): spinup 3 Jun 20 15:04:53 vulcan kernel: mdcmd (64): spinup 4 Jun 20 15:04:53 vulcan kernel: mdcmd (65): spinup 5 Jun 20 15:04:53 vulcan kernel: mdcmd (66): spinup 6 Jun 20 15:04:53 vulcan kernel: mdcmd (67): spinup 29 Jun 20 15:04:53 vulcan root: Jun 20 15:04:53 vulcan root: /dev/sdj: Jun 20 15:04:53 vulcan root: setting standby to 0 (off) Jun 20 15:04:56 vulcan emhttpd: Stopping services... Jun 20 15:04:56 vulcan emhttpd: shcmd (12793): /etc/rc.d/rc.libvirt stop Jun 20 15:04:56 vulcan root: Domain 5cc43df6-aaa3-0d66-e14a-fb15375bf33c is being shutdown Jun 20 15:04:56 vulcan root: Jun 20 15:05:57 vulcan root: Waiting on VMs to shutdown............................................................
  7. hi! My unraid server runs on 6.6.7 and my client is a Manjaro desktop with a wired connection to the server. I have mounted the shares with autofs and it works flawlessly via NFS ... except when it doesn't. Sometimes, seemingly randomly, the entire file sharing would crash and all the shares are gone. Only a system reboot off the unraid system will bring them back. I have noticed that it only occurs when working on files in the file explorer pcmanfm and I believe ranger. It seems something borks up when moving, copying, or deleting files. It doesn't happen all the time. Most of the time I can perform file operations in pcmanfm or ranger without a problem. I have no idea whether it is client or server related. I hope the diagnostic file might help. Thanks for helping! vulcan-diagnostics-20190505-1735.zip
  8. Hi I seem to have a problem with nfs that I don't know how to troubleshoot. I have a media share on my Unraid system (6.6.3) that I am mounting via nfs on my plex server. That machine also does a few other things for me like importing music via beets. I have tried the following version 192.168.1.2:/mnt/user/media /mnt/media nfs defaults 0 0 192.168.1.2:/mnt/user/media /mnt/media nfs noatime,nodiratime 0 0 192.168.1.2:/mnt/user/media /mnt/media nfs defaults,intr,rw,vers=4,timeo=15,auto,async,nofail,bg 0 0 none of them actually resolve the issues. Plex is constantly rescanning the files and readding them to the library causing rebuilds of the metadata. Beets would oftentimes report stale file handles, and transcodes via ffmpeg would stop because of stale file handles. I have left the "tuneable" at default of 330 but experimented with a value of 0 to see if it would make difference but it didn't. I have also checked if the files on the server have been modified or accessed. None of the files that are reported to the plex server as "new" or "changed" have been created, changed, or accessed during my testing. That is files that have been in the library before and are reported to plex as new/changed. My /etc/exports file reads: "/mnt/user/media" -async,no_subtree_check,fsid=100 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) Do you have any idea what might cause those stale file handles and how I can get rid of them/ troubleshoot them more? One workaround right is to mount the shares with CIFS which works fine but I would like to use NFS if I could. thank you for your help!
  9. I can second that @MarkUK. My server has been running for 10 days on version 6.6.3 with mild nfs and smb traffic without any problems.
  10. I have had similiar issues after upgrading to 6.6.0 in that /mnt/user disappeared several times. This is the logfile from last night. It seems it has something to do with the NFSd process. Maybe it will help the team with trouble shooting. I have reverted back to 6.5.3 in the meantime since I need a stable system to work with. Sep 28 00:26:36 vulcan kernel: WARNING: CPU: 18 PID: 25036 at fs/nfsd/nfsproc.c:817 nfserrno+0x44/0x4a [nfsd] Sep 28 00:26:36 vulcan kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_REJECT xt_nat ebtable_filter ebtables veth ip6table_filter ip6_tables vhost_net tun vhost tap ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat dm_crypt algif_skcipher af_alg dm_mod dax nfsd lockd grace sunrpc md_mod ipmi_devintf bonding netxen_nic tg3 sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd ipmi_ssif glue_helper intel_cstate i2c_core intel_uncore intel_rapl_perf ahci libahci megaraid_sas wmi acpi_power_meter pcc_cpufreq button ipmi_si [last unloaded: netxen_nic] Sep 28 00:26:36 vulcan kernel: CPU: 18 PID: 25036 Comm: nfsd Not tainted 4.18.8-unRAID #1 Sep 28 00:26:36 vulcan kernel: Hardware name: Dell Inc. PowerEdge R520/051XDX, BIOS 2.5.1 02/08/2018 Sep 28 00:26:36 vulcan kernel: RIP: 0010:nfserrno+0x44/0x4a [nfsd] Sep 28 00:26:36 vulcan kernel: Code: c0 48 83 f8 22 75 e2 80 3d b3 06 01 00 00 bb 00 00 00 05 75 17 89 fe 48 c7 c7 3b 5a 17 a0 c6 05 9c 06 01 00 01 e8 8a 2c ee e0 <0f> 0b 89 d8 5b c3 48 83 ec 18 31 c9 ba ff 07 00 00 65 48 8b 04 25 Sep 28 00:26:36 vulcan kernel: RSP: 0018:ffffc90003b9bdc0 EFLAGS: 00010282 Sep 28 00:26:36 vulcan kernel: RAX: 0000000000000000 RBX: 0000000005000000 RCX: 0000000000000007 Sep 28 00:26:36 vulcan kernel: RDX: 0000000000000000 RSI: ffff88041fa56470 RDI: ffff88041fa56470 Sep 28 00:26:36 vulcan kernel: RBP: ffffc90003b9be10 R08: 0000000000000003 R09: ffff88082ff91c00 Sep 28 00:26:36 vulcan kernel: R10: 0000000000000679 R11: 0000000000021668 R12: ffff88081ac82808 Sep 28 00:26:36 vulcan kernel: R13: 00000000abf82000 R14: ffff88081ac82968 R15: 0000000000000100 Sep 28 00:26:36 vulcan kernel: FS: 0000000000000000(0000) GS:ffff88041fa40000(0000) knlGS:0000000000000000 Sep 28 00:26:36 vulcan kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 28 00:26:36 vulcan kernel: CR2: 00007f5daaef9010 CR3: 0000000001e0a004 CR4: 00000000000626e0 Sep 28 00:26:36 vulcan kernel: Call Trace: Sep 28 00:26:36 vulcan kernel: nfsd_open+0x15e/0x17c [nfsd] Sep 28 00:26:36 vulcan kernel: nfsd_read+0x45/0xec [nfsd] Sep 28 00:26:36 vulcan kernel: nfsd3_proc_read+0x95/0xda [nfsd] Sep 28 00:26:36 vulcan kernel: nfsd_dispatch+0xb4/0x169 [nfsd] Sep 28 00:26:36 vulcan kernel: svc_process+0x4b5/0x666 [sunrpc] Sep 28 00:26:36 vulcan kernel: ? nfsd_destroy+0x48/0x48 [nfsd] Sep 28 00:26:36 vulcan kernel: nfsd+0xeb/0x142 [nfsd] Sep 28 00:26:36 vulcan kernel: kthread+0x10b/0x113 Sep 28 00:26:36 vulcan kernel: ? kthread_flush_work_fn+0x9/0x9 Sep 28 00:26:36 vulcan kernel: ret_from_fork+0x35/0x40 Sep 28 00:26:36 vulcan kernel: ---[ end trace 59856c68d508e506 ]--- Sep 28 00:32:55 vulcan rpc.mountd[25039]: Cannot export /mnt/user/media, possibly unsupported filesystem or fsid= required Sep 28 00:40:30 vulcan kernel: perf: interrupt took too long (4923 > 4918), lowering kernel.perf_event_max_sample_rate to 40000 Sep 28 01:00:16 vulcan crond[2440]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Sep 28 02:00:16 vulcan crond[2440]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Sep 28 03:00:16 vulcan crond[2440]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Sep 28 03:25:02 vulcan rpc.mountd[25039]: Cannot export /mnt/user/Downloads, possibly unsupported filesystem or fsid= required
  11. I dug a little deeper and found that my gpu is in it's IOMMU group which is good I guess. But how do I pass that group through to my plex container, so I can have the encoding and decoding happen on the graphics card?
  12. hi, I'm confused. I have downloaded the Dev Tools plugin to manage GCC etc. and I have downloaded the latest NVIDIA driver but whenever I try to run the file it gives me the following message: kernel source path '/lib/modules/4.14.40-unRAID/source' is incorrect I have the latest Unraid 6.5.2 installed. What am I supposed to do? Edit: In case this is useful. The server is a Dell R520 with 32 GB RAM, 2xIntel E5-2430, and a NVIDIA GTX 1050 which is being detected and can be passed through to a VM. But I need it for my Plex container.