dlandon

My router is a WINS server if that is the question.

Add settings to the SMB settings to enable Samba as a WINS server, or set IP address for another WINS server on the network. WINS server settings would be mutually exclusive. Samba on unRAID cannot be a WINS server and also use another WINS server. For Samba to be a WINS server: [global] wins support = yes For Samba to use another WINS server: [global] wins server = 192.168.1.1 Using a WINS server on a Windows network can improve Windows browsing and network name resolution.

Done. Illegal characters in file names are now skipped on appdata/CA Backups/any additional excluded folders. Still performed everywhere else Done. Old results deleted prior to beginning a new scan (btw, if all those dupes were within the a CA Backup folder, then you've done backups to more than one disk. Switch the destination to user folders since you're on 6.2 Done.. The disks the file(s) are on are itemized now Not done. Thought about it (and ran the extended test a couple times) and decided that this is going to need an HTML readmore or something on the results, as limiting the results to an arbitrary number isn't fair to other users (and unfortunately AD is something of an edge case here). And I don't want to force those users to fix the first 10 errors, and then have to re-run the tests (takes my server 2 hours to run through the nearly 1M files) to see if there are any more.... I'll get around to it, but not on this round of update Nice job! I have a feeling the duplicate files are left over from my conversion of disk at a time from ReiserFS to XFS. I don't think I did it properly back then. My data has also progressed from v4.x to 6.2, so something along the way might have gotten botched. Thank you for a tremendous utility to check this stuff. I would not do anything with AD. I don't think it is used enough to warrant the investment of your time.

There's just no satisfying you is there Curious though what container its from... I can be a PITA at times. I'm a stickler for detail. Does it show? MineOS: /mnt/user/appdata/minecraftos/archive/hexxit/server-hexxit_2016-06-12_14:20:46.tar.gz /mnt/user/appdata/minecraftos/backup/hexxit/rdiff-backup-data/access_control_lists.2016-06-12T14:20:29Z.snapshot /mnt/user/appdata/minecraftos/backup/hexxit/rdiff-backup-data/current_mirror.2016-06-12T14:20:29Z.data /mnt/user/appdata/minecraftos/backup/hexxit/rdiff-backup-data/error_log.2016-06-12T14:20:29Z.data /mnt/user/appdata/minecraftos/backup/hexxit/rdiff-backup-data/extended_attributes.2016-06-12T14:20:29Z.snapshot /mnt/user/appdata/minecraftos/backup/hexxit/rdiff-backup-data/file_statistics.2016-06-12T14:20:29Z.data.gz /mnt/user/appdata/minecraftos/backup/hexxit/rdiff-backup-data/mirror_metadata.2016-06-12T14:20:29Z.snapshot.gz /mnt/user/appdata/minecraftos/backup/hexxit/rdiff-backup-data/session_statistics.2016-06-12T14:20:29Z.data

I had them as cumulative so that you could go back and reference the old results, but since I always have to force problems to happen, I've never really given it a second thought to re-running it a few times in succession. Painless for me to delete the prior results. Will add it in to the changes for the posts above. Look for it tomorrow ish. But in the meantime, you can delete /tmp/fix.common.problems/extendedLog Thanks. That would be much better to start fresh each time. I couldn't believe the issues I had with duplicate files. It was pages and pages of them. I don't know where that came from. Suggestion: You are looking in the appdata folder for characters that Windows doesn't like. In my case I think FCP was complaining about the ':' character. That folder is hidden and used by Dockers that are Linux based. That folder shouldn't even be browsed or manipulated by Windows. Can that one be skipped for that check?

Not sure where to go with this, but I ran extended tests and to my surprise I have a lot of duplicate files. I am addressing the issues and re-starting the test to see more, but the results are cumulative and don't clear between tests. Is there a way to clear the previous results so I can start a new test fresh?

I would check all your SMB settings and share permissions.

The preferred way to do this is to use the User Scripts plugin and set up a script and then set it to run daily.

Having an issue with Network Settings on Dynamix bleeding edge. I start with IP address assignment and Default gateway both set to automatic. I change the IP address assignment to static and the IP address assignment and Default gateway both change to static. I apply the settings and both are set to static. I change the IP address assignment to automatic and the Default gateway stays at static. I change it to automatic and apply the changes and it's fine. I think the gateway should follow the IP address assignment when changed and not stay in a previous setting. Kind of a minor issue, but if the gateway is not set right, Dockers will show needing an update because they can't phone home and other things will be a problem because unRAID can't reach the internet.

See Settings -> Notification Settings -> Notification display This setting can be either "Detailed" (old style of displaying notifications) or "Summarized" (new style to show clickable counters) Ok. I get it. I didn't see the new setting. Thanks.

I'm using bleeding edge Dynamix and when I look at the SystemProfile -> Ethernet I am seeing 5 occurrences of the bond0 information. It appears to be 5 copies of the same information. I have 4 VLANs and I suspect that the bond0 information is showing for the br0, br.1, br.2, br.3, and br.4.

Have you changed the emhttp port from the default of 80? Also, the builtin powerdown path is /usr/local/sbin/powerdown.

If I change the opacity and make the background less transparent. Would that help? Probably. What I have trouble with is the contrast between the characters and the background. If you change the opacity, that would probably help. I have a blue/green color deficiency so lighter colors in that spectrum that are close in hue are difficult for me to discern. Hopefully I am describing this so you can understand. That worked. It appears that the gui messages are going away on their own without me clearing them though. Is this expected behavior? Yes it is intended behavior when viewing (opening) notifications from counters in the header, they disappear as soon as another page is opened. Only in detailed view they stay open continuously. What is detailed view?

If I change the opacity and make the background less transparent. Would that help? Probably. What I have trouble with is the contrast between the characters and the background. If you change the opacity, that would probably help. I have a blue/green color deficiency so lighter colors in that spectrum that are close in hue are difficult for me to discern. Hopefully I am describing this so you can understand. That worked. It appears that the gui messages are going away on their own without me clearing them though. Is this expected behavior?

There are some settings in the Settings->Unassigned Devices related to SMB permissons. Check those. Click on 'Help' and read the settings configuration.

If I change the opacity and make the background less transparent. Would that help? Probably. What I have trouble with is the contrast between the characters and the background. If you change the opacity, that would probably help. I have a blue/green color deficiency so lighter colors in that spectrum that are close in hue are difficult for me to discern. Hopefully I am describing this so you can understand.

For those of us with color vision issues, can the text in the notifications in the Dynamix bleeding edge be changed to increase the readability? The text is a bit hard for me to read with the transparent background.

Sounds like the wife is a keeper. Don't mess up.

Ok, so that will print that line to the logger daemon so we can see it in the syslog? Yes. That will tell you if the unmount script is what's causing the unmount. If you see it in the log, save the log and post it so we can see if the shares are unmounting at the wrong time.

My last update was made in a bit of a rush and I did not handle a new configuration parameter very well that was added. Those that updated would see the message because POWERDOWN was undefined. Once you re-write the configuration file, the new parameter will get written and all will be well again.

As a quick test, put the following in your unmount script so you can see if it is being executed when you don't expect it. logger "My unmount script is running..."

Sep 19 22:30:42 Node kernel: ------------[ cut here ]------------ Sep 19 22:30:42 Node kernel: WARNING: CPU: 0 PID: 27309 at ./arch/x86/include/asm/thread_info.h:236 SyS_rt_sigsuspend+0x8f/0x9e() Sep 19 22:30:42 Node kernel: Modules linked in: xt_nat veth xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables vhost_net tun vhost macvtap macvlan ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod x86_pkg_temp_thermal coretemp kvm_intel kvm r8169 i2c_i801 i2c_core ahci libahci mii Sep 19 22:30:42 Node kernel: CPU: 0 PID: 27309 Comm: Threadpool work Not tainted 4.4.19-unRAID #1 Sep 19 22:30:42 Node kernel: Hardware name: Gigabyte Technology Co., Ltd. B85M-DS3H-A/B85M-DS3H-A, BIOS F2 08/10/2015 Sep 19 22:30:42 Node kernel: 0000000000000000 ffff8803c77ebee0 ffffffff8136a68e 0000000000000000 Sep 19 22:30:42 Node kernel: 00000000000000ec ffff8803c77ebf18 ffffffff8104a39a ffffffff81055502 Sep 19 22:30:42 Node kernel: fffffffffffffdfe 0000000000014f98 000000000000000d 000000000000a0b7 Sep 19 22:30:42 Node kernel: Call Trace: Sep 19 22:30:42 Node kernel: [<ffffffff8136a68e>] dump_stack+0x61/0x7e Sep 19 22:30:42 Node kernel: [<ffffffff8104a39a>] warn_slowpath_common+0x8f/0xa8 Sep 19 22:30:42 Node kernel: [<ffffffff81055502>] ? SyS_rt_sigsuspend+0x8f/0x9e Sep 19 22:30:42 Node kernel: [<ffffffff8104a457>] warn_slowpath_null+0x15/0x17 Sep 19 22:30:42 Node kernel: [<ffffffff81055502>] SyS_rt_sigsuspend+0x8f/0x9e Sep 19 22:30:42 Node kernel: [<ffffffff81620a2e>] entry_SYSCALL_64_fastpath+0x12/0x6d Sep 19 22:30:42 Node kernel: ---[ end trace 753ae045f3fb133e ]--- This: x86_pkg_temp_thermal coretemp kvm_intel kvm r8169 i2c_i801 i2c_core ahci libahci mii But I don't know that much about these faults. Reardless, I don't think is is good.

You have some things going on in your syslog that don't look good: Sep 18 10:41:42 Node kernel: python[17518]: segfault at 2b043cd61ff8 ip 00002b0438283d9b sp 00002b043cd62000 error 6 in libpython2.7.so.1.0[2b0438214000+341000] Sep 18 10:41:44 Node kernel: python[10080]: segfault at 2afc522c9ff8 ip 00002afc4a04fd9b sp 00002afc522ca000 error 6 in libpython2.7.so.1.0[2afc49fe0000+341000] Sep 18 10:41:45 Node kernel: python[10132]: segfault at 2b4ffcbecff8 ip 00002b4ff494f57f sp 00002b4ffcbed000 error 6 in libpython2.7.so.1.0[2b4ff48ed000+341000] Sep 18 10:41:47 Node kernel: python[10207]: segfault at 2ac0a7019ff8 ip 00002ac09ed9fd9b sp 00002ac0a701a000 error 6 in libpython2.7.so.1.0[2ac09ed30000+341000] Sep 18 10:41:48 Node kernel: python[10268]: segfault at 2afc2b390ff8 ip 00002afc2310957f sp 00002afc2b391000 error 6 in libpython2.7.so.1.0[2afc230a7000+341000] and Sep 19 22:30:42 Node kernel: ------------[ cut here ]------------ Sep 19 22:30:42 Node kernel: WARNING: CPU: 0 PID: 27309 at ./arch/x86/include/asm/thread_info.h:236 SyS_rt_sigsuspend+0x8f/0x9e() Sep 19 22:30:42 Node kernel: Modules linked in: xt_nat veth xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables vhost_net tun vhost macvtap macvlan ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod x86_pkg_temp_thermal coretemp kvm_intel kvm r8169 i2c_i801 i2c_core ahci libahci mii Sep 19 22:30:42 Node kernel: CPU: 0 PID: 27309 Comm: Threadpool work Not tainted 4.4.19-unRAID #1 Sep 19 22:30:42 Node kernel: Hardware name: Gigabyte Technology Co., Ltd. B85M-DS3H-A/B85M-DS3H-A, BIOS F2 08/10/2015 Sep 19 22:30:42 Node kernel: 0000000000000000 ffff8803c77ebee0 ffffffff8136a68e 0000000000000000 Sep 19 22:30:42 Node kernel: 00000000000000ec ffff8803c77ebf18 ffffffff8104a39a ffffffff81055502 Sep 19 22:30:42 Node kernel: fffffffffffffdfe 0000000000014f98 000000000000000d 000000000000a0b7 Sep 19 22:30:42 Node kernel: Call Trace: Sep 19 22:30:42 Node kernel: [<ffffffff8136a68e>] dump_stack+0x61/0x7e Sep 19 22:30:42 Node kernel: [<ffffffff8104a39a>] warn_slowpath_common+0x8f/0xa8 Sep 19 22:30:42 Node kernel: [<ffffffff81055502>] ? SyS_rt_sigsuspend+0x8f/0x9e Sep 19 22:30:42 Node kernel: [<ffffffff8104a457>] warn_slowpath_null+0x15/0x17 Sep 19 22:30:42 Node kernel: [<ffffffff81055502>] SyS_rt_sigsuspend+0x8f/0x9e Sep 19 22:30:42 Node kernel: [<ffffffff81620a2e>] entry_SYSCALL_64_fastpath+0x12/0x6d Sep 19 22:30:42 Node kernel: ---[ end trace 753ae045f3fb133e ]--- I'mm not very good at these things, but python is segfaulting and it appears your cpu is overheating.

The user scripts are triggered on array events disks_mounted and unmounting_disks. There are other array operations that will cause these events - such as stopping the array. The events just don't randomly happen.

I also get the same and line 60 as well. Go to the tweaks page and make a change, then save it. That will fix the problem.