-
Posts
1132 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by optiman
-
-
Thanks Joe! I didn't know that, and feel much better now.
I haven't changed it so this is good.
My expectation is that if the monthly check runs and IF there are errors, I will be given the choice to review and decide what to do. I hope it works that way.
I haven't had any errors in a long time (knock on wood) so I have no experience and don't know what to expect.
-
You can uncheck it. Just uncheck it and then click start parity and the goto syslog and it will say NOCORRECT.
I'm aware of the manual process. However, I have my config setup to it runs the Parity check monthly (like most do), which starts automatically and it will write the correction automatically. You cannot uncheck the box and expect it to remain unchecked, which is my concern and therefore the request for Tom to change this for future releases.
-
I just tired to uncheck the box, then hit Refresh, and it was checked again. it looks like you cannot uncheck at all.
I guess we all better pray that this does't bit us on the back side.
Tom - please correct this in the next release, and for sure in the Final.
-
In any case, I would prefer it to NOT correct, as once parity is modified it is not possible to get back to where it was... (if checked you are always trusting your data disks, even potentially if they have failed)
I agree. I'm sure that part way through the 5.0 development cycle, the default was set to 'Not Correct' but Tom decided to change it back.
I'm very wary of the possibility that I boot the machine up and, before I have any chance for user interaction, it is starting to overwrite my parity data. I know that it has been stated that it is nearly always the parity disk which is wrong, but I'm afraid of falling into the few percent gap where that is not the case. I believe that the user should always have overriding control of any correction procedure.
I agree too. And thanks Joe for confirming. We should all ask that Tom change that back so that the box is not checked and we have the option to accept the corrections or not.
-
so with this RC version, should I leave the box checked that says Write Corrections to Parity Disk, on the main page?
Mine is checked and I have it setup to run a parity check once a month. In the past, it was recommended to leave that unchecked incase the parity disk itself had the issue.
Just looking for a recommendation now that we are up to v5 RC8.
Thanks
Anyone want to offer your choice of setting here?
-
so with this RC version, should I leave the box checked that says Write Corrections to Parity Disk, on the main page?
Mine is checked and I have it setup to run a parity check once a month. In the past, it was recommended to leave that unchecked incase the parity disk itself had the issue.
Just looking for a recommendation now that we are up to v5 RC8.
Thanks
-
Tried that and got
Warning: wildcards not supported in HTTP. HTTP request sent, awaiting response... 404 Not Found 2012-09-24 16:56:10 ERROR 404: Not Found.
Sorry, my bad: wget can't use wildcards with http. I meant to give the ftp link:
wget ftp://ftp.osuosl.org/pub/slackware/slackware-current/slackware/n/samba-*.txz
Anyway, glad to hear you found it, and that it seems to fix the problem. Until Tom packs the new samba in the next build, you can put one "installpkg /PATH-TO/samba-3.6.8-i486-1.txz" line in your GO script, BEFORE the line that starts emhttp.
(I'll go fix the link in my previous post)
Thanks for the new samba info Barzija!
Can you please confirm where to put the file? Would I put in \boot\packages\samba-3.6.8-i486-1.txz
Then just add the line to the GO file, installpkg /PATH-TO/samba-3.6.8-i486-1.txz
I want to try this new version as well. I had a issue where I wasn't able to delete some files from my pc or imac using SMB. However, I did find a workaround. I had to share it as a AFP and then connect with my imac. I was then able to delete the files. It seems that this issue was directly related to the samba version included with the current RC.
-
I'm not sure if the right people have noticed it but there is a very real problem with RC8 detailed here: http://lime-technology.com/forum/index.php?topic=22647.0
wow, that looks to be serious. That said, I don't seem to have that problem. I don't have any tmp files to delete, and I'm running win7 64bit as my main client, connecting via SMB shares. I have deleted files and they remain gone, and no tmp files. Could it be a plugin issue and not directly related to RC8?
What is the easist way to confirm if you are impacted by this issue, just incase I'm missing something?
-
Now I get SG_IO: bad/missing sense data, sb.. on my console
I'm getting the same error on my console. Nothing shows up in the log. I did not have this on RC5.
I just checked and I do not have this error message on my console and I'm running RC8. Could it be specific to your hardware?
-
the log icon is missing because it points to the wrong place and the plugin hasn't been fixed yet. Another poster, a few pages back in this thread, discovered this, and even fixed it with a command, but it didn't hold up to a reboot. We need the guy who wrote the plugin to fix it.
-
OK found the log viewer sorry about that was staring me in face been long day and kids have been driving me nuts once i got home from work lol.
Where can I find the option to start the mover manually so I can set a move of the files off me cache drive manually cant seem to locate it.
It may be time for some much needed sleep lol
Settings --> Share Settings --> button at the bottom
-
The whole issue is likely to be null anyway if tom updates the kernel to the newly released kernel. I believe the debug flag has been reset on the latest kernels.
I have just installed the latest build, rc8a, with the new kernel and the error messages are still there.
what a bummer... I will be upgrading tonight and was hoping this was going to get resolved.
-
@Tom, can we see update of following part in the next build?
Netatalk to version 3.0
Samba to version 3.6.8
//Peter
+1
-
where did you see this post? I don't find it in the Announcement section, where it should be. WTF?
-
due to the email notification syslog bugs, my syslog rotates about every 2 days, meaning I now have syslog1, syslog2, etc. The only fix is to uninstall SF email notification. I might do that anyway, given it doesn't work like the old version did with unmenu. Having a half ass plugin is lame. It doesn't even tell you when the server is running a Parity check.
I appreciate all the effort, but doing a half ass job and leaving like this is joke. I wish had the skills to fix it myself. I would even pay a fee for solid wokring plugins.
WTF!
-
bummer - sure hope the guys supporting this would release an updated version that fixes this
-
This was annoying me so I looked at the path for the broken log icon and it was pointing to
/plugins/simpleFeatures.logViewer/images/logs.png
That directory is actually in /usr/local/emhttp/
When I looked on my server, this file (and folder actually) wasn't there. I decided to copy another icon to this location and it worked fine. I used this command to steal an icon from elsewhere (you could choose any other icon you prefer, but this icon is used for logs elsewhere):
cp /usr/local/emhttp/plugins/webGui/images/default.png /usr/local/emhttp/plugins/simpleFeatures.logViewer/images/logs.png
You may need to manually create the images subdirectory first. Note that I haven't rebooted yet to see if this will persist, and I wouldn't be surprised if it doesn't actually.
Should be an easy fix for the next version of the plugin.
I just tried and I would need to create the directory. Let me know if works after a reboot and I'll do the same.
Thanks for your reply! At least we know now that it's simply pointing to the wrong path and not a big deal.
-
What we need is an update from Tom or Joe, so we know they are still alive and with us, even if there is nothing great to report right now. Silence leads people to jump to conclusions, and those are normally not positive.
I actually think v5 is very solid, and I've always received excellent support. Perhaps they are just on vacation, which we all should do from time to time.
Tom - you still with us?
-
From what I can tell yes. For future reference, when posting code or command like that, use the code button at the top of the post box. It wraps the code in [ code ] [ /code ] so it formats properly.
Like I mentioned earlier, you can run that in telnet by copying like you did, and right click in telnet to paste. It will add the cron now, otherwise it will not be added until you reboot.
Speeding ant, may I suggest you add that to the OP until you get a chance to rewrite the email script? Would allow users to continue to use the add on and not spam their syslog. Not a solution but a band-aid for the interim.
Thanks again, after adding these cron jobs, my syslog is very short and clean. It's almost seems too short.
Thanks! man, I didn't notice that it went off the screen when I did the copy/paste. Let me try that again.
here is my go file;
#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp &
# /boot/unmenu/uu
# cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c
unraid_notify start
sed -i '/Scheduled Parity Check/d' /var/spool/cron/crontabs/root
sed -i '/cron=\"\"/d' /var/spool/cron/crontabs/root
crontab -l > /tmp/log; echo '#Remove ioctl error from syslog' >> /tmp/log; echo '* */1 * * * sed -e "/.*sending\ ioctl.*/d" -e "/.*callbacks\ suppressed.*/d" -e "/.*last\ message.*/d" /var/log/syslog >tmp && mv tmp /var/log/syslog' >>/tmp/log; crontab /tmp/log; rm /tmp/log
I just checked my syslog and you all are correct, the syslog doesn't update after making the change to the go file. It is nice and short, but not updating after the inital boot. I had to comment out that cronjob and it's now updating again. Of course we have tons of the stupid errors clogging up the syslog now, but at least I have a log again.
We need the SF email thing fixed, full stop.
By the way, it doesn't work that good anyway. Before with unread email notificy, I would get updates when a parity check was running, now I get nothing but the "Tower is OK" emails.
I too would like to konw if I kill the email notiify, would apc email notifications still work, or would that kill that too?
-
You can check to see if it is where SF is looking for it for starters. I haven't paid attention honestly, ill see if its missing for me. All in all a minor quibble
how do I check to see where SF is looking for it? The file I put put in my \boot\extras directory is simpleFeatures.log.viewer-1.0.5-i486-1.tgz
Is that the same version / file that you have?
the log icon still isn't showing up... anyone else have this problem?
-
for NON-apc UPS's you have to change the cable type from 'smart' to 'usb' i believe.
I'm not sure, but I think you would only use Smart if you have a APC SmartUps ups. My Apc ups is a BackUps model and my settings is set to usb. At the end of the day, you don't get anything extra from a SmartUps vs a BackUps from what I can tell. The plugin does what it does if it works at all.
-
Telnet into the server, and type
ls -l /usr/local/emhttp/plugins/simpleFeatures/icons/page_white_text.png
If it comes back with the permission/info for the file, it exists where it should be, else it with say "file or directory does not exist"
You could try refreshing the cache for your browser:
Windows: ctrl + F5
Mac/Apple: Apple + R or command + R
Linux: F5
Do that when on the simple features page
thanks. I did that and got this back,
-rwxrwxrwx 1 root root 342 2012-04-30 16:02 /usr/local/emhttp/plugins/simpleFeatures/icons/page_white_text.png*
so I guess the file is there.
Refreshing the IE page didn't work. I even tried Chrome and Safari. The icon just doesn't show up.
now what?
-
You can check to see if it is where SF is looking for it for starters. I haven't paid attention honestly, ill see if its missing for me. All in all a minor quibble
how do I check to see where SF is looking for it? The file I put put in my \boot\extras directory is simpleFeatures.log.viewer-1.0.5-i486-1.tgz
Is that the same version / file that you have?
-
NoWould this be tied to the AFP TimeShare that I created?
No.Better question, is this anything to worry about?
Then, be happy.My server seems happy.
Thanks! Just wanted to confirm. I feel better knowing it's not a issue.
"SimpleFeatures" Plugin - Version 1.0.11
in User Customizations
Posted
Perhaps I'm missing something, but for those that already have the SF installed, all we need to do is REPLACE the /boot/extra/*.plg files with the new ones and reboot, correct? No need to delete anything and I don't want to loose my configuration data for Email Notifiy, so I'm planning to leave my file /boot/config/simplefeatures.cfg file alone.
Or did I miss something re the instructions? I am planning to upgrade to the new files tonight, so please let me know if my above plan won't work.
Thanks!