Frank1940

If you have a wireless router, make sure that you have the security turned on and a secure password applied. If you haven't previously done that, you have probably already been compromised and most likely all of your computers and data have been hacked.

Full explanation of question 4: The largest hard drive has to be used as the parity drive. Thus the 3TB drive becomes the parity drive. The 1TB, 1.5TB and 2TB drives will be used as the data drives. The total data space is 5.5TB. As a point of explanation (since apparently, you posted with much research), if you add a second 3TB drive at a later date to this array, you would have 8.5TB of storage space. As I recall, there is a maximum of twenty data drives allowed. Reason for Edit: to correct my inability to add!!!! 4.5 was 5.5 and 7.5 was 8.5 Thanks to BetaQuasi and Lionelhutz for seeing my mistake.

From my reading of this thread, it would not be two releases but more than three and possibly a great many more. There are issues with the NIC's of certain Motherboards. There are issues with SATA boards. And you get software that does work with your particular SATA boards, I seem to recall that there can be spin-up issues if you want to use even the most primitive sort of power saving scheme. Depending on what you want to be able to do with your unRaid box, you might find that you can't get a configuration that will work unless you go back to 4.7. Then you have the 2GB limitation on HD size. This thing is a real minefield for anyone trying to select a software setup that will work now and allow for future expansion. I would really like some knowledgeable person to see if they could put together a matrix of software and hardware to help everyone who is attempting to use the version 5 beta. Perhaps, there is something that I am missing but I don't think I am the only one who is confused as to what combinations of hardware and software work and don't work.

LOL....i meant for the current kernel What you might not realize is that the problem is the current kernel!!! (Version 3 of the Linux kernel 'broke' the LSI drivers.) What BRiT was trying to tell you is that beta 12 is the last release where the LSI cards will work because it uses one of last releases of version 2 of the Linux kernel. according to the changelog beta 12 uses the 3.03 kernel.....beta 11 uses the 2.6.37.6 kernel and beta 13 uses the 3.1 kernel....so does this mean it was broken with the 3.1+ kernels? Yes. Sorry, I should have looked up the version of the kernel being used for each release. I have a personal opinion about this version 3 release of Linux and that is that it is looking more like Windows than ever. Meaning that there is a continuous stream of updates coming out to address various shortcomings in the code. Plus, it appears that recent releases have broken drivers and firmware for various hardware devices. Of course the ones most of us are concerned are the ones for existing SATA cards. What worries me is that if the manufacturers are the ones who will have to update the drivers and/or firmware, it may never happen if their marketing groups decide that the costs involved can not be paid back by the potential new sales of the older designed hardware. LimeTech is caught between a rock and hard spot at this point. If he decides to stay with the old kernel, the old hardware will work. However, this will mean that new hardware (with drivers and firmware designed for the new version of the kernel) will not work with this old kernel version. Read about Realtec NIC driver issues for some insight into the problems of not keeping current on kernel version. I suspect, at this point, he is playing a waiting game and hoping that some of the hardware issues and a couple of minor software (NFS problems???) are resolved in some future kernel update before releasing version 5.

LOL....i meant for the current kernel What you might not realize is that the problem is the current kernel!!! (Version 3 of the Linux kernel 'broke' the LSI drivers.) What BRiT was trying to tell you is that beta 12 is the last release where the LSI cards will work because it uses one of last releases of version 2 of the Linux kernel.

I.m running beta 14 with kernel 3.3, if anyone want to try this, feel free -> http://www.filefactory.com/file/2qlr5qxok92v/n/bzimage_rar Including samba 3.6.3- //Peter New kernel 3.3.1 and also verified that Tun/Tap and bridge is enabled as modules for OpenVPN. -K10temp is also added for sensors for AMD. http://www.filefactory.com/f/8dc509eb6d610f88/ Thanks again, Peter! I have installed the new kernel (3.3.1) on my test bed and it appears to work fine. I looked at the release notes for this version of the kernel and found that a number of NFS issues have been addressed. I am wondering if any of the people who have had NFS issues have had time to test to see if anything has been resolved by the new kernel?

I assume that you are referring to me. I am running a parity drive--250GB. (The last parity check was run on April 1st.) Edited on 4/7/2012 to correct wrong word (check was chance).

I used ImgBurn to create the ISO and that file was written directly into the file location (a user share) on the server as it was being compiled. I will delete a BLU-RAY file from the server later today and use ImgBurn to generate a BLU-RAY ISO on the server to see if a larger file size makes any difference. As I promised, I have generated a large file which resulted in the drive/user share being almost full. I deleted a couple of BLU-RAY Iso's and then copied a couple of DVD ISO's to bring the drive to the point of where the BLU-RAY that I was going to created would almost fill the drive. The BLU-RAY which I choose was Pirates of the Caribbean (Part 3) and I again used ImgBurn to create and store the resulting file directly on the server. The movie only ISO turned out to be 38.6GB and the drive had 78.3GB of data (1.69GB or 2% free) when the copy was done. This test bed server has only a 100Mbs NIC and it took 2hours 52 minutes to make the copy. I did check the progress periodically and the transfer rate remained reasonably consistent throughout the entire time. (The initial prediction was 2hours 45 minutes.) I can only say that I didn't have any of the issues which other people have reported. Perhaps the issue is a problem with the network rather than with actual disk transfer...

I used ImgBurn to create the ISO and that file was written directly into the file location (a user share) on the server as it was being compiled. I will delete a BLU-RAY file from the server later today and use ImgBurn to generate a BLU-RAY ISO on the server to see if a larger file size makes any difference.

Well I found that if I use teracopy I get more consistent results in being able to copy up the files. I am however no longer able to build iso files on the fly direclty to the server. Did a bit more reading and found the issue may be something to do with Samba Strict Allocate problem in that it will write a file with 0's to the size you are trying to write. Using NFS may get around the issue but it is just a pain as it is another thing to install/configure. I've got the same problem here, too. As you said, the server seems to allocate the needed space and the copy times out before it has finished. But it only happens if the target disk you are copying to is "low" at free space (20-30% free). There is a thread for this problem here: http://lime-technology.com/forum/index.php?topic=19207.0 Is there any simple way to mount a NFS share into Windows explorer to check if that would "resolve" the issue? It's just annoying if you start copying 2TB over night and at morning you see it stopped at 10% because of this error. Unfortunately, it was not what I found with my test bed. As you can see from the equipment list in my signature, I have two very small data disks so filling them up was not much of an issue. I used ImgBurn to burn DVD iso's to the server. The 80GB drive filled up first (Final tally -- 77.7 GB's used, 2.29GB free, 3% Free). Then the next group of files were written to the @0GB drive (Final tally there -- 18.2 GB's used, 1.84GB's free, 9% Free). For the complete array, the stats were: (95.9 GB used, 4.13 free, 4% Free). I deliberately did not use Windows Explorer to simply copy the files as I have TeraCopy installed. The Windows machine runs Win 7 (64 bit). While my network backbone is GigaBit, the NIC in the test bed is 100Mbs. (Makes for fast writes until all of the caches are filled!!!)

Peter ---- An interesting comment. I read it several times in an attempt to determine its meaning. Are you saying that there is an acknowledged issue in the Ver 3.3 kernel which is causing the NFS problems? Frank

I.m running beta 14 with kernel 3.3, if anyone want to try this, feel free -> http://www.filefactory.com/file/2qlr5qxok92v/n/bzimage_rar Including samba 3.6.3- //Peter Thanks, Peter. I have upgrade my test bed server to use the new kernel. I have read both Blu-ray and standard DVD iso's using both Samba and NFS with my Netgear NTV-550. I have also copied files to it using Samba from Win7. Everything is working as it should. However, I must point out that I had no problems with the earlier kernels on this very old hardware.

Tom. when you post up 5b15, could you please list the hardware incompatibilities that you are aware of. This bit of information will save a lot of questions in the new beta thread and help reduce the FUD factor that many people seem to have in using beta software. FUD = Fear, Uncertainty, Doubt (This technique was first used by IBM salesmen when IBM's customers were first beginning to attach non IBM equipment to their mainframes.)

I am also running WIN7 Home Premium 64 bit. I have noticed the same behavior on a share that is mapped as a networked drive showing as 'disconnected'. (As a note of full disclosure, this Share Drive is on my FreeNAS server--- I am waiting for ver 5 to come out of beta before purchasing a license.) This particular share is actually an Address Book database that can be accessed from several different computers on my home network. However, I have observed that even if the mapped drive is shown as disconnected in Windows Explorer, the database program can still open the files without any problem. In fact, I just checked the shared drive status in Windows Explorer and found the drive disconnected. I closed Window explorer and open the database on that shared drive with the address book program without an issue. I reopened Windows Explorer and the shared drive was still shown as disconnected. Previous experience with this situation has shown that clicking on the disconnected drive in Windows Explorer will always connected it. I really suspect that it is a problem in Window Explorer not getting the state of the shared drives correct and not refreshing its cache properly. Do try to see if your program has access to the shared drive when it is shown as disconnected. My experience has shown that it will be available and ready for use.

The side fan blowing inward is intended to be an attempt to cool hot running video cards. Since unRAID has little to no video output, that flow is unneeded. Blowing air in at the side provides little or no additional air flow over your drives. In fact, it probably decreases that needed air flow. I would try reversing that side fan to exhaust air from the case and see if it forces more air flow over your drives to reduce their temperature.

Oh my goodness, here is one that is even cheaper! http://www.amazon.com/ATI-Rage-8MB-Video-Card/dp/B000G6U2W4/ref=pd_sim_e_1 Probably not suitable for modern graphics requirements but it should work fine for the text only display that unRAID uses

In the same vein, look for a local shop that still builds and repairs computers. They often end up with computers that can't be repaired and are left when the shop sells the previous owner a new computer. The shop will often 'recycle' the usable parts and you can often find items like PCI video cards for $10 to $15.

I would suggest that you open up the case and carefully inspect everything inside for dirt and dust clogging up the the CPU cooler and the power supply. Make sure that all case fans, filters, etc. are clean and nothing is blocking the air flow.

How do you expect to move 220GB of files into 650MB of space?

You need to post more spec's on the UPS. Look for the label and see what the current draw is. Multiply that value by 110. If the product is not 600 (watts/Volt-amperes), it probably does not have enough power to spin up all the drives and shut unRaid down. Second issue is that unRaid is very particular about the protocol on the USB buss. Only a few UPS brands (and not all models even with those brands) will work with it. But you have to check the volt-ampere rating before you even get to that issue.

As a point of information, Linux Kernel 3.3 rc5 posted up last weekend. One of the fixes was a floating point error which occurred in the 32 bit version running on 64 processors. With the current state of flux in the version 3 of the Linux Kernel, you might understand the reluctance of LimeTech to release ver 5.

What would be the advantage of doing this? It seems to me that moving files( data) without a very good reason is nothing but a real opportunity to introduction errors and data corruption. My philosophy is to never fix something that ain't broke...

I did find a post which did say if a file is corrupted so that it can't be opened to generate the thumbnail, it will crash Windows Explorer! It might be well to turn off this 'feature' in Windows---- Control Panel, System, Advance System Settings, Performance--Settings, Visual Effects, Uncheck 'Show Thumbnails instead of Icons'.

I am wondering if Windows Explorer is scanning the entire file system on the server for some reason before it mounts it for use. I know it scans USB keys and asks if you want to 'play' media files every time you plug a key in. Other item to consider: Is windows attempting to index all of the files on the server? (See Control Panel, Indexing Options) I see the same problem on my FreeNAS server where I have a lot more files than I do on my unRAID test bed. Just some food for thought...

What is the meaning your question? Which Media Player are you using? Are you trying to setup your media player? I assume from your statement--"I can access NFS shares vie my media player like this:" --- that you have actually access the unRaid NFS share by manually entering the mounting info. I guess I am trying to say if you want help, you will have to provide the forum with a lot more information.