limetech

Right, that's a pain. Updated the README.md file.

https://github.com/limetech/webGui Let's give this a try. For you non-coders, you can monitor and download the "latest". For you coders, you can fork the repository and send me pull requests if you want to work on it. The "merge window" will last until the documentation is done and then I'll release 5.0 and move on to updating slackware, the kernel, and other components. Let's try and keep this thread on-topic. Thank you!

Yes of course. Also you can send me an email at [email protected] or at [email protected]. This happens from time-to-time with Hotmail and I have not figured out the pattern yet.

We have been having problems lately sending to Hotmail, and other Microsoft email addresses. For example, sometimes Hotmail treats email from lime-technology.com as spam and completely deletes it. Sometimes our email ends up in your spam folder; sometimes it's delivered normally. I'd like to request that you to go to your Hotmail account "Options/More options/Safe and blocked senders/Safe senders" and add "lime-technology.com" to your list of "Safe senders and domains".

Will do.

Take a look at the home page - I'm not sure it's turned out exactly like I envisioned... what do you think? http://lime-technology.com/

I'd like to request permission from anyone interested to put a picture of your server build (along with your forum member name) on one of our website pages. The picture should be a 460x300 png file. If interested, post it in this thread. Thanks, TomM

In your scenario that would work perfectly. Your scenario is really based on folder permissions not by user authentication. Unraid gives the option to add multi users with different levels of access (since learning about the issue, im using the word "option" loosely). The limitation in your point, is that there can be many users (as in physical people using the server) however only two options/folder views are applied to all physical users. Happy to give an example if that helps. simply put your confusing authentication vs authorization. Please provide an example because your use of terms "folder permission" and "authentication vs. authorization" are very confusing to me

It took a long time to figure out what was really happening, including looking at a lot of code in samba. The windows "bug", imho, is that it should not offer a login username/password dialog prompt when a server returns an "unauthorized" error as a result of trying to browse a Private share; I don't know why Windows does this and you can make it happen with a windows server so it's not strictly a samba compatibility issue. Here's another confusing behavior: Let's say your windows logon name is "larry" with password "1234" and you have created an unRaid user named "larry" with password "5678". You next click on 'tower' and then click on a Public share - guess what? Windows will ask you to enter a password(!). Why? Because on samba side, it sees that "larry" is a valid name, so it now tries to validate the password, which fails (the windows connection sends the user name "mypc\larry" along with your windows password which is encrypted). It reports this failure to windows so windows ask you for your (unRaid-side) password which you have to enter correctly or no shares for you!

It's not as bad as you are thinking it is. You only need to add user names for those wanting access to Private shares or wanting write access to Secure shares, everyone else will have "guest" access (by "guest" I mean not as user name "guest" but anonymous access). Actually it's better NOT to have a user name "guest" because that will confuse AFP when/if you use that (LOL that's another story). Sorry, these are not unRaid-specific issues. Ok, to be exact, you don't have to use your windows login name. You can use any name that's defined on the unRaid side. You just have to make sure that the very first access to any share on the server results in you correctly entering that user name/password in the dialog box. Having done that once, your Windows PC will "remember" those credentials for future access to the same server and you won't have to enter the username/password again. Let me give you an operational example. Let's say your windows PC netbios name is "mypc" and your windows login name is "larry". Further let's say your server netbios name is "tower" and you have a single user defined on unRaid side named "curly". Now you open Network and click on "tower" and a window opens showing all the shares. In this state, if you now click on a "public" share, what happens behind the scenes is windows tries to authenticate with the server as user "mypc\larry". On unRaid side, samba (linux smb protocol module) will check if "larry" exists. In this case no, so samba will check if user "mypc" exists, in this case also no. So samba will now see that "guest" access is enabled for the server, so it will reply to Windows with "success" but on the samba side, will associate any further access with the "nobody" user on the linux side. Meanwhile, Windows stores the fact that it successfully connected with user "mypc\larry" in its own credentials cache. Now, after above, you click on a Private share where the only unRaid user with access is "curly". Samba will see the request to the share as user "larry" and tell Windows that the connection is unauthorized (because larry is not in the list of users for the Private share). Windows sees this and presents you with a username/password dialog box. So you enter "curly" as the user. But now Windows sees that you already have a connection to the server as user "larry" and it DOES NOT ALLOW multiple connections to the same server via different user names. This is a well-known limitation/bug in Windows. Some people get around it, e.g., by connecting to the sever using the IP address in order to fool windows into thinking it's a different server. To get above to work, you would close any windows that might have a previous connection to the first public share, then open a command window and type "net use * /delete". That command closes all current server connections. Now click on your Private share and enter "curly" user name it will work this time. Same scenario, but this time after opening Network and clicking on "tower" you happen to click on a Private share first. You get the dialog box and login as "curly" and everything works. Now you click on a Public share and it still works (because on unRaid side all user names are accepted for Public shares). So you see the behavior can be quite different and confusing depending on what you click on after clicking on the server. Now you also know why it's easier to just use the same user names.

This is a known Windows "issue" that is really hard to explain, so for now I'll just tell you how to get around it. What is the log-on name you use for your PC? I'm going to bet it's not "alex". Maybe it's "Alex" or "alex smith" or some other name entirely. Whatever it is, create that same user in your unRaid server, and define whatever secure or private share access you want under that user name. Then close all windows that might be connected to the server and either reboot the windows PC or open a command window and type "net use * /delete" command. Now when you browse shares on the unRaid server it will work, except if the password you assigned when you created your unRaid user does not match your windows logon password, Windows will prompt you to enter the password (that you specified in the unRaid server). If you use the same password in both places you will not get this prompt.

Yes, we'll do that as soon as the next batch arrives.

After you enter username 'alex' and password, and click 'ok' do you get another box that says why access is denied?

Yes. For international, we're mailing them in a normal envelope with a USPS "First Class International" stamp which costs $1.10, so no customs, VAT, etc., but it's not trackable.

http://lime-technology.com/limetech-gear/ The size is 2.5" x 0.5". It's a "domed label" custom made by Maveric Label (highly recommended btw). The background is black, the lettering is "chrome" and the limes are, well, green.

The first set of badges has been mailed. I had no idea there would be such an interest and we have run out of badges. It will take about 10 days to get the next batch. Thanks to everyone who ordered and tossed in a few extra bucks, we very much appreciate it!

You want case badges? Sure I can send out case badges. http://lime-technology.com/limetech-gear/

Virtually all key orders are processed the same day they are received, 99% within 24 hours. Registration keys are sent as a 256-byte binary attachment to an email. Sometimes email servers and/or clients treat these kinds of email as "spam". Please check your spam folder if you have not received your key after 24 hours. We have been having issues sending to Hotmail email addresses. Even though we have never "spammed" any of our customers, and never even send out things like "newsletters" or "offers", Microsoft has seen fit to blacklist the "lime-technology.com" domain. We are looking into this to try and determine why this is happening. For now, please use an email address other than Hotmail, or add "lime-technology.com" to your list of trusted domains. If you have more questions, please post in this thread.

This starts a new method of reporting Issues with a release... Issue Reporting Instructions To report a Defect or request an Enhancement, first please browse this board for a similar report or request. If you are sure your issue is unique, please follow this procedure: [*]Click on the New Topic icon. [*]In the Subject field, type a one-line summary of the issue. [*]Select the proper Message icon in the drop-down list. [*]If you are reporting a Defect, please include a system log if possible. Please note, that some topics may be moved or merged by the Moderators. Message icons: Defect report (thumbs down) Defect solved (thumbs up) Enhancement request (light bulb)

Anything posted here must be unRAID-related. Do not post your grandma's china collection, or an old ReadyNAS box. Any inappropriate post may be deleted without warning. If you are in the business of manufacturing unRAID servers, send me an email and we can discuss OEM pricing and other services we can provide to you, including a board in the Vendor Forum. Each sale offer must contain: Product description, including part numbers, and condition (new, used, etc). Cost of product, with clearly specified currency, and Payment options (PayPal, etc). Postage cost, type, estimated delivery time and any other geographical limitations -or- Point of origin, estimated weight and available shipping carriers (USPS, UPS, Fed-EX, Royal Mail, etc). unRAID is used all around the world. Please clearly state your country of origin. USE AT YOUR OWN RISK. All transactions are the responsibility of the people involved. Lime Technology shall in no way be held liable or responsible for any representation posted here. Lime Technology shall in no way mediate or remedy any issue arising from either party.

When starting a new topic, please include the version of unRAID OS you are running. Also, almost all issues will require a system log to help diagnose the problem. There are multiple ways to obtain the system log: You can type "//tower/log/syslog" in your browser address bar (if you changed the name of your server, use that name instead of 'tower'). Then select/copy/paste the text, put into a txt file, and attach to your post. Via the console or telnet session, you can type this command: cp /var/log/syslog /boot/syslog.txt The file 'syslog.txt' will now show up in the 'flash' share under My Network Places (or Network), where you can attach to your post. In cases where the system hangs, you can set up a system log monitoring telnet session by typing this command: tail -f /var/log/syslog Messages will get displayed in your telnet window as they are generated. If the system hangs, please select/copy/paste the contents of your telnet window, put into a txt file, and attach to your post. Note: If possible, please upgrade to the latest stable release to see if this solves the problem.

Thank you. Will there be any indication the unrecoverable error was experienced? There will be the original error posted in the system log, but otherwise no. In looking at the code & thinking about this, we should increment the 'Sync Errors' counter when this happens (as we do for errors detected during Parity Check). This will be in the next release.

The reconstruct will continue.

If array parity is valid, then for an unrecoverable... Write error: the drive is 'disabled' but parity is updated (so that drive contents can be reconstructed); Read error: block is 'reconstructed' by reading all other drives plus parity. Result is then re-written to bad block (if this subsequent write fails then see 'write error' case above). If array parity is not valid, then all unrecoverable errors are 'passed up' to the caller - this will result in originating application getting an I/O error, or possible loss of data if we're talking about a cache flush write. A future feature would be to disable all write-behind, from Samba all the way to the driver, if array parity is not valid. But this would really slow down writes.

Related to this, something we're constantly asked is, "can you increase the number of disks in the array to X?" Many have asked for an X of 20, some 24. What we are going to do is create a Pro-only feature that raises the array width max up to 32, but also includes the ability to configure a "Q-parity" drive (like RAID-6). This drive will have similar size restriction as Parity drive, that is, just be larger or same size as any data disk. In this system (as in a RAID-6 system), there will be two redundancy disks, "P" which is the ordinary XOR parity, and "Q" which is a Reed-Solomon code. This will allow unRAID to recover from any 2 disk errors, with minimal performance impact.