aaronwt

I would have never figured that out. I guess at some point I removed the space by accident. Thanks.

Did something happen with the cache mover on this version? I've had the same settings for years to invoke the mover at the top of the hour, either every 1 hour or two hours. But something has changed. One it doesn't seem to be trying to do it at the top of the hour any more. And two it seems to always fail. I always get a message in the log that shows this. These are from my unRAID1 and unRAID3 setups. Jul 29 07:51:01 Tower crond[1409]: failed parsing crontab for user root: */2* * * /usr/local/sbin/mover |& logger Jul 29 08:19:01 Tower3 crond[1249]: failed parsing crontab for user root: */2* * * /usr/local/sbin/mover |& logger The mover isn't running like it used to and it isn't at the top of the hour. My mover settings currently are 0 */2* * * which is supposed to be every 2 hours at the top of the hour. or I'll have it set to 0 */1* * * which is supposed to be every hour at the top of the hour. The only way I have been able to initiate the mover is by doing it manually. Did something change? Do I need to have different settings for the mover?

My old WD EADS 2TB drives have been running for years at around 50C in a closet. There have been no problems.

I thought Seagate doesn't have any drives labeled "green" any more?

There's a whole level of virtualization going on there with FUSE. What is the difference in CPU between the two machines? What are the bogomips on the machine(s) you are comparing. How much ram is in each machine? do you have the himem is dirtayable option set? My unRAID1 setup has a 2.4 Ghz(or 2.6Ghz I always forget) single core Athlon CPU, but with 4GB of memory. My unRAID2 setep has a dual core 2.8 Ghz Athlon but with 2GB of memory. Both machines have dual channel memory while I guess my N54L is only single channel since it's got only one 2GB stick. I had thought about getting another 2GB stick before I opened it up but I figured my other machine was perfectly fine with only 2GB of memory so I figured it wasn't needed.

I thought I was getting faster results to cache drive then that on my N40L but I'm at work currently and can't test for you. I will see when I get home tonight. Maybe someone else can confirm earlier. Writing to a user share which writes to the cache drive I get 50-60MB/s. Writing directly to the cache drive share and not through the user share file system I get 75-85MB/s. This was using Windows Explorer in a Windows 7 VM from one unRAID server to the N40L unRAID server. I copied a BluRay folder of a movie (34.8GB) - "2001 A Space Odyssey". The cache drive is a EADS 1.5TB green drive and the rest of the drives in the array are WD 2TB Reds. Thanks. My N54L finished the parity sync last night. Now when I write to a share that uses the cache I'm back to only 50MB/s write speeds. If I write directly to the cache drive is up to double that. Why is there such a disparity between the two? So it sounds like when I had all my drives in the array in external enclosures everything was fine. But I don't like those slow speeds to a share that uses the cache drive. Since my other unRAID setups can get much faster speeds in the same situation. I just don't understand why the N54L is so much slower.

OK, I forgot that I mostly had test data on my unRAID3 setup. I only had around 100GB of data I needed to keep, so I copied that to another location and started from scratch. I'm using a Seagate 2TB 7200 rpm drive for parity, three 5900 RPM Seagate drives for the array, and one Seagate 5900 rpm drive for the cache drive. All the drives that are in my N54L enclosure. I don't have any of my external enclosures turned on. So while it's doing the initial parity sync(I'm getting 107MB/s parity sync speeds) I'm able to copy files directly to the cache drive and I'm getting between 70MB/s and 110MB/s write rates and between 90MB/s and 110MB/s read rates. It is fluctuating alot between those speeds but it is much higher than before. I'll need to gradually add enclosures and drives to see where the copy speeds start to drop down. So my next step is to move the drive I was using as the cache drive before into a slot in the N54L to see what speeds I get. Then if that goes well, I'll need to add one enclosures after another, testing speeds after each one is added.

My BiOS is upgraded. I turned on the write cache when I had a parity and a couple of array drives inside the N54L. It made a big difference in the parity check then but I never tried it with a cache drive. Now that I have around eighteen array drives i am not going to get 100MB/s+ parity check speeds. So with the write cache on or off the speeds are the same. It's just more consistent with it off now. But with the cache drive I've tried an old 750GB WD green drive and a 1TB 7200 rpm Seagate drive. Both of these drives get much faster speeds from my first unRAID setup. The drives are fine. But for some reason my write speeds over the network aren't exceeding 50Mb/s to the cache drive. When I pick up a few more drives I'll stick some in the N54L to test it out with just a parity, cache and three array drives to see what speeds I get. But until I find some drives on sale for a great price I'll need to wait and just live with the speeds.

I tried turning the write cache off. When I initially turned it on I only had drives in the internal drive bay, but I was only looking at speeds during a parity check. Not transfer speeds since I was transferring without a cache drive. I wish I had checked out transfer speeds earlier with a cache drive. Anyway I turned off the write caching in the BIOS. The write speeds are still on 45MB/s to 50MB/s to the cache drive. But at least they don't fluctuate alot like they did with write caching on. These write speeds are slower than I would like. I would prefer to get at least 60MB/s write speeds for when I'm ripping BD titles. So I could rip two at a time. Otherwise with the speeds I'm getting I need to only rip one. The read speeds are 75MB/s to 85MB/s from the cache and array drives so I know the network connection is capable of faster speeds, I just don't understand why the write speeds are so slow over the newtork.

What speeds are people getting to the N54L when writing to a cache drive over the network? I recently setup a cache drive and I'm only getting around 45MB/s to 50MB/s write speeds. The read speeds are OK but it seems to be writing slower than I would expect. The same cache drive in my unRAID1 setup gets write speeds of 70MB/s to 75MB/s. So I'm curious if these speeds are normal. I've tried the cache drive in a drive bay inside the 54L and also in a couple of my external enclosures. It made no difference in the speeds. Is there a setting I need to change in the BiOS to increase the speeds or is this normal?

That was the idea I had a while back. BTW there is a particular syba card that allows 4 ports on a PCIe x1 slot. It has 2 eSATA ports and 2 internal SATA ports. It's no longer available on the regular market. I found 2 on the secondary market. It worked for me. It wouldn't be the best performer, but it sure would max out ports !!! As far as the opening, there's enough room in backup of the upper metal to drill and nibble space for eSATA ports. You would need to evacuate parts to insure no shavings fall on the motherboard, but it could give you 6 or 8 ports from the x4/x1 slot. A x1 card will not work well for multiple enclosures(and least not multiple bay. multiple enclosures) In my testing the most drives I will use on a x1 card is four(which for me is one enclosure with four drives in it) and with a x4 card I don't like to exceed 16 drives(four enclosures). Although I have 17 drives in my unRAID1 attached to a rosewill card. But it is noticeably slower during the parity check because of that. I've decided to just use a 4 bay enclosure with only two drives in it for the built in eSATA port. Then I will be moving my five bay enclosure from my unRAID1 and move that to my unRAID3 while moving a 4 bay enclosure to unRAID1. Then I need to drop the cache drive on unRAID1 and I won't have a cache drive on unRAID3 either. Then I should be able to get 1 parity drive and 23 arrays drives in the setup. Although I have found the N54 is is kind of picky with my RC218 and the eSATA port. I could not use five MediaSonic enclosures and I could not use five Sans Digital enclosures. I had to use a combination of both for it to boot and see all the drives. So I'm not sure what will happen when I move over the 5 bay Sans Digital enclosure. Although I had the same issue with my unRAID2 setup. I have no idea why, but I did not have the issue with my first unRAID build.

But during a parity check or drive rebuild, it will still be accessing all the drives at the same time. Accessing one drive at a time is no problem, like when writing data to the array. I tried staggering the drives in my first unRAID setup but the difference in my use was minimal. I ended up using a cache drive with that setup. With my second unRAid setup I put all the drives in order of each enclosure. I'm not using a cache drive in that setup and have been pleased with the speed results. While the driver attempts to read the drives, I think it has to read each drive sequentially. So by ordering the drives to access the channel once every round vs accessing the channel 4 times one behind the other may alleviate contention for the channel. There was someone who did this years ago when port multipliers were new and he said it gave him a slight increase in speed. YMMV. It may not be worth it considering how you have to arrange the drives. I know when I tested PMP support using 4 drives simultaneously, I got something like 15MB/s per drive. In comparison using the silicon image, 1 drive was 120MB/s 2 drives were 60MB/s, 3 drives were 40MB/s and 4 drives were 30MB/s. There is still the option of putting the 2 eSATA brackets ports on the back of the unit after it is nibbled out. You may be able to fit 4 there. I haven't measured it. That's what I did with my old chenbro chassis years back. I currently have five eSATA ports on the back. Getting four from my Rosewill RC218. Two external on the card and then I have two more from the two internal ports running to a two port bracket. Where would another eSATA port come from? Or would I need to create an opening to run the two internal ports from the Rosewill and then stick a card in the PCI express x1 slot?

But during a parity check or drive rebuild, it will still be accessing all the drives at the same time. Accessing one drive at a time is no problem, like when writing data to the array. I tried staggering the drives in my first unRAID setup but the difference in my use was minimal. I ended up using a cache drive with that setup. With my second unRAid setup I put all the drives in order of each enclosure. I'm not using a cache drive in that setup and have been pleased with the speed results.

I just started using my eSATA ports on my N54L. From my Rosewill RC218 it is fine since that uses FIS–based (frame information structure) switching. But from what I've read it seems that the built in eSATA port uses Command-based switching so it can only access one drive at a time, not concurrently like with FIS based switching. I was wondering why things were going so slow with the four bay enclosure I connected. With four drives on the eSATA port it really slows things down if all drives are going to be accessed concurrently like during a parity check in unRAID. With one drive of course it's fine, and two drives is not bad, but once you get to three drives it really slows things down. So if I decide to use the built in eSATA port in the future, I will limit it to two drives at the most. Then I will need to take a 5 Bay enclosure from my unRAID1 to use with my unRAID3 to connect to the RC-218. Then I should be able to hit the max of 23 drives in the array. I'll have to see though how much things slow down with two drives on the built in eSata port. When I was clearing one 2TB drive it was going at just under 3 minutes for each percent. When I tried two 2TB drives that increased to around 4.5 minutes for each percent. So I'm not sure what speeds I will get from a parity check.

I guess I should have waited before I started clearing two drives on my unRAID3. At least I was able to put rc16c on my unRAID1 and unRAID2.

Here are a couple of pics of it.

If you can find an HP Proliant Microserver on sale or with rebate you can get a prebuilt system. The N54L I got was around $240 after rebate. It has a dual core cpu and 2GB of memory. Four removable hard drive bays and you can add a fith one. Plus it has an eSATA port and if you intsall the modified BIOS you can attach a port multiplier enclosure to be able to expand the system by four more drives. And you can expand it farther by opening up the case and adding a card to the system. In mine that gives me the capacity for sixteen more drives in addition to the four from the eSATA port and the five internal.

Is there a process where a fee can be paid and I can switch a couple of pro keys to some newer, faster, smaller, USB flash drives? My first two pro keys went on some small, for the time, usb flash drives. But they are also very slow and not small by todays standards. The two new Pro keys, I just purchased, will go on some very tiny flash drives that barely stick out of the USB port. Plus they are many times faster than my older USB flash drives. Just wondering if there is a way to pay some kind of transfer fee, so I could buy a couple of these Newer San Disk flash drives to use on my first two unRAID setups too. Then I can just trash the old, slow, USB flash drives I've used for the last 2.5 years.

I'll need to take some tomorrow.

Yes I have all five of the enclosures, but I'm short several 2TB drives to fill all of them. When I tested the system to see if it would see all of the drives I used some old 1TB and 750GB drives.

I finally got my N54L setup completed today. I put in a Rosewill RC218 port multiplier card. So I tested it by connecting four, 4 bay enclosures to the Rosewill card and one, 4 bay, enclosure to the eSata port. All twenty external drives came up in unRAID. Plus I have a drive connected to the on board sata port. So this should work with up to twenty five drives connected to my N54L. Now I just need to get a pro license setup for my N54L and I can start off with five drives internally and fifteen drives in four of the external enclosures.

Yes i see this share size issue now on my unRAID1 setup. I have fourteen shares with 23 array drives. With rc15a, the shares showed the free space as all that was available in the array. Now, with rc16b, they show completely different numbers which I guess represent the free space from only the drives the shares are on.

duh... :-[ now I understand... I don't typically go to the share tab. I see it shows the free space listed. I have no idea what mine showed before I switched to rc16b. I'll need to get an imgae of it on my unRAID1 setup. That has a bunch of shares all spanning multiple discs.

OK. I installed rc16b on my unRAID2 and unRAID3. My unRAID2 has 23 data drives with content from one share spread across all of them. The free space numbers are not showing any issues for me. I am not using any Add Ons. EDIT: Maybe I am confused about this. I just reread the above posts. My free space is shown for each drive, which is what I expect it to show. This has been the case for all rc5x versions I have used and also for 4.7. But it sounded like one of the posts expected the free space on one drive to show the total free space of the share? That makes no sense to me Or am I miss reading it?

All my shares are on multiple disks. I don't recall seeing a free space issue with rc15a. I'm getting ready to try out rc16b on my unRAID3.