limetech

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.

You can download the slackware package from an Italian site here: http://www.slacky.eu/index.php?option=com_content&task=view&id=4759&Itemid=56 I haven't tried this - but if you get it to install but it complains of missing libraries, let me know

It's not possible to build packages from source using just the unRAID OS Flash & I couldn't find any pre-build Slackware package for hamachi VPN. We'll look into building a package after the next release.