JonathanM

Did you preclear the drives and check smart reports before you added the drives to the array? Do you still have the old drives with the data on them? Next time you boot the array and it starts the parity check, let it run for a couple minutes, then capture the syslog, zip it up, and attach it to your post.

There are no errors shown here that aren't expected at this point. The super.dat errors are there because you haven't defined an array yet, and every time the web interface is accessed, it reloads the unraid driver so it can detect hot swapped drives. In short, nothing wrong, nothing to see here, move along. In the future, if you need to attach a syslog, zip it up and attach it. Even REALLY huge syslogs zip into fairly tiny packages, because of all the repeated text. Also, I know dynamix is pretty and all, but I really recommend getting the basic array functions all working before making changes and putting addons into the equation. Dynamix is not authored or supported by Lime Technology, so if you have any issues, chances are the first troubleshooting step is going to be "remove all addons and try again".

And won't be, since unraid hasn't been rebooted. It won't recreate the info we need until you shutdown, and restart the system. What you need to do is restart, then copy data until you get the error. Then you need to extract the syslog, zip it up, and post it here.

New flash drive. Tom will issue a license based on the GUID you enter into the web form. He must be able to find you as a current customer based on the email you submit.

Kingston reader discussion. http://lime-technology.com/forum/index.php?topic=27163.0 and here http://lime-technology.com/forum/index.php?topic=6185.0

Hmm. For some reason I thought this was the correct one. http://www.amazon.com/Kingston-Flash-Reader-MobileLite-Multi-card/dp/B00536WFTA

I hazily remember reading that the G3 wouldn't work for some reason, and I couldn't find any reasonably priced G2's. Mind sharing the link for a $7 G2?

Can anyone comment on USB 3.0 support in this release?

They may act differently however. Some scripts may assume things that are no longer true with 64 bit. Max performance from changing the memory allocated for specific items for example. Free memory is going to have to be evaluated a little differently now.

Can you give us some idea of how long you are going to keep this offer open? I don't mean the exact expiration, just an idea. Weeks? Months? Until version 6 is final? Until demand falls? I'm definitely going to be adding a key for testing, but I don't have one I want to commit yet. Ideally I want to find a SD reader to license, but I haven't investigated what's working and has unique GUID's recently.

Try editing the plugin file with a text editor, and replace the bad location with http://slackpack.ludost.net/packages/13.37/mysql-5.5.30-i486-1gds.txz Dunno if it will work, but it's worth a try.

I think it should be possible using smb-extra.conf, but I've never done it, so I can't help with details. autumnwalker is right, in that you can't do it with the stock web gui. If it's possible at all, it's going to involve manually setting it up.

I don't remember that specific set of conditions being addressed here before, but my gut instinct is that you could dd the drive from the old to the new, set a new config, tell unraid parity is already valid, and do a parity check just to be sure. HOWEVER... since I would recommend doing a parity check before you started messing with it, and a parity check afterwards, my gut instinct is that you would be better off temporarily putting a portable fan blowing on the server and going through with a normal rebuild, parity check before and after, and call it a day (or 3) How does the array handle a normal monthly check? If you are stressing it with normal activities, perhaps you need to rethink the entire thing. It would really suck to cook the server because a drive failed and it went into degraded mode, which spins up all the drives for any data activity.

Looks like you have a bad cable, switch, or ethernet card. 93K dropped packets???

utorrent is uPnP, as many torrent clients are. Whether it's a risk you can deal with is up to you. Private trackers generally require an open incoming port, whether manually forwarded or uPnP. So if you are running a torrent client and want to be "connectable", you will need that port open. It's only as risky as the coding in the torrent client you choose. If there is a vulnerability in that specific torrent client, you could get hacked.

In general, you just need to make sure that you don't forward any ports to the unraid box. Home routers pretty much block any unsolicited outside traffic by default, you shouldn't need to really do anything. The exception is uPnP, if that is enabled on the router, and you have a uPnP aware application, it can request port forwarding dynamically.

That looks like someone may be trying to hack in to your server. Unraid is not meant to be exposed to the internet, it needs to be behind a router, with no ports forwarded unless you know exactly what you are doing. How is your unraid box connected to your network? Scratch that, after thinking a little more on it, that may be an add-on trying to send mail, and failing. Do you have any notification add-on's installed?

As long as you can get the drives physically mounted in that little case, and cooled properly, I see no reason why you can't do what you want (slow parity protected storage) with that system. I just didn't want you to think you were going to be able to do all the whiz bang add-on high speed storage stuff that you see some of the people on here talking about. Your first post started in on the add-on stuff you were downloading and installing, so I wondered if your goals were realistic. So what response do you get from the browser on another machine on your network if you type http://192.168.1.113 into the address line? Can you ping that ip from another machine on the network?

I think we are getting the cart before the horse here. I'm not sure what you expect to accomplish with what you've got, but right now all I see in your syslog is a 2TB drive (parity) a 750GB and a 500GB drive for data. That won't even net you 2TB of protected space. First, what exactly do you want this machine to do for you? 10+ year old hardware is going to be extremely limited as to what it can accomplish with current drives, even running its best. As to why you aren't getting a network connection, are you sure the on board ethernet is turned on in the BIOS? I didn't find any sign of a working network card in your syslog.

Not dangerous, just a pain in the tail. They will add up in every backup, since there will be new content there every time. You could end up with a HUGE backup.

Unraid will partition and format the drives for you when you include them in the array. Currently that will be a reiserfs format, but in the upcoming year there may be other options available, depending on which way Tom decides to go. Any brand new drives should be fully tested before you populate unraid with them, Joe L.'s preclear script is a dandy way to do that. You don't HAVE to use it, but it's highly recommended. After the array has parity calculated and is fault tolerant, any added drives must be cleared one way or the other. You can clear them using the unraid interface, which will keep your array offline while it completes, or you can use the preclear script to prepare the drive for a much more rapid addition, the array will only be offline for a few minutes while it is formatted. Either way clearing takes many hours. If you are ok with not keeping backups while you transfer data, you could build the array with all your empty drives, copy a few drives to the protected array, preferably with a file copy utility that checksums and tests like teracopy. After you have a couple of your existing data drives successfully copied over, you could add those drives physically to the box, and start the preclear process on those while you are copying more drives. After the preclear is done, add those drives to the protected array, and move more of your old drives into place to preclear. I hope you have a beefy system to support all those spindles.

How much of a performance boost do you actually see when you invoke it?

An unraid array with 2-4TB, 2-3TB, and 2-2TB drives will have 14TB of space. So you have a little more breathing room than you thought. I've got to ask this, how much of that 26TB of data is irreplaceable, and how much is important to you? How much is currently backed up elsewhere? All the drive juggling that you are planning to do will be a magnet for murphy's law to bite you hard if you don't have backups. I think your best bet is to scrounge a second box and take your time migrating and organizing.

I'm pretty sure it's the responsibility of the originator of the copy to handle cleanup correctly. Perhaps you are using a file manager that can cleanly continue a partial transfer if you resume it, so it assumes you may want to continue the copy later? Try using a different file manager, or use the command line and see if the behaviour changes.

You are running a server, and yes, it is a lot of stress, so we want to find out whether the drive is up to the challenge BEFORE you rely on it to keep your data safe. Preclear is designed to work the drive from end to end, just like unraid will if there is a problem with another drive and it's needed to participate in the rebuild process. It will only cause an issue with the drive if it's marginal to begin with. Reading and writing is what the drive is designed to do. As long as it is kept happy with normal voltage and temperatures, it should read and write for as long as requested without errors. If it fails, we want to know sooner rather than later.