madburg

Totally forgot one can check the status of a disk... arghhh. In the mean time i was preparing a test bench to figure this out. I found my backup SAS LSI card and a 146GB SATA drive to speed the test up and get to the bottom of this. So my thought was preclear the 146GB drive, verify (-t), reboot, verify once again (-t). I assumed this would pass and then move the drive from onboard SATA to the SAS card and verify signature again; this is where I though I may see something. Much to my surprise preclearing the 146GB drive and verifying (-t) right after instantly issues a "NOT precleared" for the drive. I am using the following command "preclear_disk.sh -W -M 4 /dev/sdb" My testbench desktop, which is the one I have been preclearing with for a long time is a Foxconn C51XEM2AA- 8EKRS2H (AMD nforce 590 chipset). unRAID loads 'sata_nv' for storage driver and 'forcedeth' for ethernet driver. So this would explain why every drive I have precleared from this MB and moved off to my production server never worked (no signature). Only thing I can think of is possibly the sata driver (for nforce chipset) is not working nicely or something is unaccounted for in the logic for setting of the signature when this chipset is used. Is that possible Joe L.? Would this be something you would like to look/work through off-line (PM's). The rig is up and I can run anything you require. Screenshot attached. I actually ran preclears several time with various unRAID builds (v5's and v6b3 for the hell of it) other command lines just in case, signature is just never found in any of the attempts. Let me know Joe L. Thanks.

Originally (years ago) I purchase many 2 TB drives and precleared them all, slowly as I needed them I added them to the unRAID server, unRAID always cleared them, never picked up the signature set by preclear. I had no idea why at the time and didn't have any more drive to figure it out. It was long ago between pre-clearing them and adding them in. Well I just picked up (2) 3TB drives. I just finished pre-clearing them and added them to my unRAID 5.0.4 production server, unRAID is clearing them (v1.14) once again, it did not pick up the signature. So only thing I can think of is this. Originally when I first started with unRAID I would preclear drives on the same server with the array up and running. Stopping the array and adding the newly pre-cleared drive(s) worked (signature detected). Once I purchased all those other 2 TB drive to have on hand and now these latest (2) 3 TB drives I have been pre-clearing them from another server. Once the preclear finished I would shut that server down, followed by shutting down the production server, moving the drives to the production server. Powering up the production server and adding the disks to the array. And the signature is not read. So I do know how this all works but it almost seems like running a preclear on a different server than where they will be added to the array is not working... My understanding is the signature written to disk is not hardware specific.. so lost as to why it is not working. The desktop I preclear from is an old AMD desktop MB (SATA MB ports), the prod server is an Intel Server MB (SAS controllers) with Xeon proc.

unRAID v6 Beta 3, lastest preclear script. (1) 3TB Hard drive installed (SATA MB) to test, no other hard drives installed, so array is not started Low memory utilization until writing zero's At Step 2 of 10 - Copying Zeros to remainder of disk to clear it (97% Done) 'Free- l' while at this step above (via screen) total used free shared buffers cached Mem: 8170244 7931528 238716 0 7207300 426780 Low: 8170244 7931528 238716 High: 0 0 0 -/+ buffers/cache: 297448 7872796 Swap: 0 0 0

Yes and no; Yes it is 64 bit but it has newer modules (I'm not referring to xmail, etc.), and the newer kernel is understandable but a lot of code changes, so it could lead to skewed results. Hate to pollute this thread about all this, if you want to fork these posts of my here please do.

Interesting as whenever anyone states memory issues, and thats why we just want a 64 bit version of unRAID that is LIKE the 32bit 5 version of unRAID with no other bells and whistles, bunch of people jump all over on what memory issues? But since we can't get a 64 bit counterpart its really hard to show a before and after.

Well unfortunately my parity check is longer, "kernel: md: sync done. time=44969sec" 12.49 hrs What I noticed was the last TB in the new parity drive (4TB) took the additional 2 hrs to complete, largest data drives are 3TB, so even after all data drives completed their reads, it still took this additional amount (which I previously didn't have, as the parity drive was a 3TB drive) guess thats how it goes. Go big go long So taking the last 2 hours out of the equations (If the parity drive was a 3TB drive), would put the parity check at 10hrs, which is the same amount of time I had with the 250GB drive installed and running a parity check. Surprisingly as the script showed a bump of 27MB from the previous Best bang for the buck to the new one. I also decide to take a deeper look at my green drives, the 2TB units are 5940 rpm, and the 3TB units are 5700 rpm (all drives are Hitachi)

I upgrade by 7200prm 3TB parity to a 7200rpm 4TB parity drive, removed my 250GB drive altogether and replace it with the previous parity drive. This broke the 100MB barrier for my system. In my original post I forgot to mention unRAID runs virtualized, 4GB Ram reservation, 16port LSI controller with an lsi expander hanging off 2 of the ports. I have a mixture of drives, Data: (7) 2TB green drives, (7) 3TB green drives, (1) 2TB 7200rpm / Parity 4TB 7200rpm / Cache 2TB 7200rpm I do wish the script ran a test with the default unRAID values first to see the difference. Tunables Report from unRAID Tunables Tester v2.2 by Pauven NOTE: Use the smallest set of values that produce good results. Larger values increase server memory use, and may cause stability issues with unRAID, especially if you have any add-ons or plug-ins installed. Test | num_stripes | write_limit | sync_window | Speed --- FULLY AUTOMATIC TEST PASS 1 (Rough - 20 Sample Points @ 3min Duration)--- 1 | 1408 | 768 | 512 | 100.3 MB/s 2 | 1536 | 768 | 640 | 108.1 MB/s 3 | 1664 | 768 | 768 | 109.4 MB/s 4 | 1920 | 896 | 896 | 110.8 MB/s 5 | 2176 | 1024 | 1024 | 111.4 MB/s 6 | 2560 | 1152 | 1152 | 111.7 MB/s 7 | 2816 | 1280 | 1280 | 112.0 MB/s 8 | 3072 | 1408 | 1408 | 112.0 MB/s 9 | 3328 | 1536 | 1536 | 112.1 MB/s 10 | 3584 | 1664 | 1664 | 112.2 MB/s 11 | 3968 | 1792 | 1792 | 111.9 MB/s 12 | 4224 | 1920 | 1920 | 111.9 MB/s 13 | 4480 | 2048 | 2048 | 111.9 MB/s 14 | 4736 | 2176 | 2176 | 112.1 MB/s 15 | 5120 | 2304 | 2304 | 111.8 MB/s 16 | 5376 | 2432 | 2432 | 112.0 MB/s 17 | 5632 | 2560 | 2560 | 112.1 MB/s 18 | 5888 | 2688 | 2688 | 112.1 MB/s 19 | 6144 | 2816 | 2816 | 111.9 MB/s 20 | 6528 | 2944 | 2944 | 111.9 MB/s --- Targeting Fastest Result of md_sync_window 1664 bytes for Final Pass --- --- FULLY AUTOMATIC TEST PASS 2 (Final - 16 Sample Points @ 4min Duration)--- 21 | 3424 | 1544 | 1544 | 112.1 MB/s 22 | 3448 | 1552 | 1552 | 112.0 MB/s 23 | 3464 | 1560 | 1560 | 112.2 MB/s 24 | 3480 | 1568 | 1568 | 112.1 MB/s 25 | 3496 | 1576 | 1576 | 112.2 MB/s 26 | 3520 | 1584 | 1584 | 112.2 MB/s 27 | 3536 | 1592 | 1592 | 112.0 MB/s 28 | 3552 | 1600 | 1600 | 112.1 MB/s 29 | 3568 | 1608 | 1608 | 112.1 MB/s 30 | 3584 | 1616 | 1616 | 112.1 MB/s 31 | 3608 | 1624 | 1624 | 112.1 MB/s 32 | 3624 | 1632 | 1632 | 112.1 MB/s 33 | 3640 | 1640 | 1640 | 112.1 MB/s 34 | 3656 | 1648 | 1648 | 112.0 MB/s 35 | 3680 | 1656 | 1656 | 112.0 MB/s 36 | 3696 | 1664 | 1664 | 112.0 MB/s Completed: 2 Hrs 8 Min 17 Sec. Best Bang for the Buck: Test 5 with a speed of 111.4 MB/s Tunable (md_num_stripes): 2176 Tunable (md_write_limit): 1024 Tunable (md_sync_window): 1024 These settings will consume 153MB of RAM on your hardware. Unthrottled values for your server came from Test 23 with a speed of 112.2 MB/s Tunable (md_num_stripes): 3464 Tunable (md_write_limit): 1560 Tunable (md_sync_window): 1560 These settings will consume 243MB of RAM on your hardware. This is 153MB more than your current utilization of 90MB. NOTE: Adding additional drives will increase memory consumption. In unRAID, go to Settings > Disk Settings to set your chosen parameter values. Again thanks for all the work. I will run a parity check to see if its less than 10 hours (which is what I had with the 250GB drive in the array previously) previous results with 250GB drive and 3TB parity drive (all else was the same) and v2.0 of the script back then: Tunables Report from unRAID Tunables Tester v2.0 by Pauven NOTE: Use the smallest set of values that produce good results. Larger values increase server memory use, and may cause stability issues with unRAID, especially if you have any add-ons or plug-ins installed. Test | num_stripes | write_limit | sync_window | Speed --- FULLY AUTOMATIC TEST PASS 1 (Rough - 20 Sample Points @ 3min Duration)--- 1 | 1408 | 768 | 512 | 84.4 MB/s 2 | 1536 | 768 | 640 | 82.4 MB/s 3 | 1664 | 768 | 768 | 84.7 MB/s 4 | 1920 | 896 | 896 | 84.9 MB/s 5 | 2176 | 1024 | 1024 | 85.0 MB/s 6 | 2560 | 1152 | 1152 | 84.8 MB/s 7 | 2816 | 1280 | 1280 | 84.9 MB/s 8 | 3072 | 1408 | 1408 | 85.0 MB/s 9 | 3328 | 1536 | 1536 | 84.9 MB/s 10 | 3584 | 1664 | 1664 | 85.0 MB/s 11 | 3968 | 1792 | 1792 | 85.0 MB/s 12 | 4224 | 1920 | 1920 | 84.4 MB/s 13 | 4480 | 2048 | 2048 | 84.9 MB/s 14 | 4736 | 2176 | 2176 | 85.0 MB/s 15 | 5120 | 2304 | 2304 | 84.8 MB/s 16 | 5376 | 2432 | 2432 | 85.0 MB/s 17 | 5632 | 2560 | 2560 | 84.9 MB/s 18 | 5888 | 2688 | 2688 | 85.0 MB/s 19 | 6144 | 2816 | 2816 | 85.0 MB/s 20 | 6528 | 2944 | 2944 | 85.0 MB/s --- Targeting Fastest Result of md_sync_window 1024 bytes for Medium Pass --- --- FULLY AUTOMATIC TEST PASS 2 (Final - 16 Sample Points @ 4min Duration)--- 21 | 2008 | 904 | 904 | 84.8 MB/s 22 | 2024 | 912 | 912 | 84.8 MB/s 23 | 2040 | 920 | 920 | 84.7 MB/s 24 | 2056 | 928 | 928 | 84.7 MB/s 25 | 2080 | 936 | 936 | 82.9 MB/s 26 | 2096 | 944 | 944 | 84.7 MB/s 27 | 2112 | 952 | 952 | 84.8 MB/s 28 | 2128 | 960 | 960 | 84.3 MB/s 29 | 2144 | 968 | 968 | 84.4 MB/s 30 | 2168 | 976 | 976 | 84.8 MB/s 31 | 2184 | 984 | 984 | 84.2 MB/s 32 | 2200 | 992 | 992 | 84.9 MB/s 33 | 2216 | 1000 | 1000 | 84.8 MB/s 34 | 2240 | 1008 | 1008 | 84.7 MB/s 35 | 2256 | 1016 | 1016 | 84.7 MB/s 36 | 2272 | 1024 | 1024 | 73.7 MB/s Completed: 2 Hrs 8 Min 12 Sec. Best Bang for the Buck: Test 1 with a speed of 84.4 MB/s Tunable (md_num_stripes): 1408 Tunable (md_write_limit): 768 Tunable (md_sync_window): 512 These settings will consume 99MB of RAM on your hardware. Unthrottled values for your server came from Test 32 with a speed of 84.9 MB/s Tunable (md_num_stripes): 2200 Tunable (md_write_limit): 992 Tunable (md_sync_window): 992 These settings will consume 154MB of RAM on your hardware. This is 64MB more than your current utilization of 90MB. NOTE: Adding additional drives will increase memory consumption. In unRAID, go to Settings > Disk Settings to set your chosen parameter values. P.S. I always have NCQ enabled

Here you go Pauven, some data for your hard work. Tunables Report from unRAID Tunables Tester v2.0 by Pauven NOTE: Use the smallest set of values that produce good results. Larger values increase server memory use, and may cause stability issues with unRAID, especially if you have any add-ons or plug-ins installed. Test | num_stripes | write_limit | sync_window | Speed --- FULLY AUTOMATIC TEST PASS 1 (Rough - 20 Sample Points @ 3min Duration)--- 1 | 1408 | 768 | 512 | 84.4 MB/s 2 | 1536 | 768 | 640 | 82.4 MB/s 3 | 1664 | 768 | 768 | 84.7 MB/s 4 | 1920 | 896 | 896 | 84.9 MB/s 5 | 2176 | 1024 | 1024 | 85.0 MB/s 6 | 2560 | 1152 | 1152 | 84.8 MB/s 7 | 2816 | 1280 | 1280 | 84.9 MB/s 8 | 3072 | 1408 | 1408 | 85.0 MB/s 9 | 3328 | 1536 | 1536 | 84.9 MB/s 10 | 3584 | 1664 | 1664 | 85.0 MB/s 11 | 3968 | 1792 | 1792 | 85.0 MB/s 12 | 4224 | 1920 | 1920 | 84.4 MB/s 13 | 4480 | 2048 | 2048 | 84.9 MB/s 14 | 4736 | 2176 | 2176 | 85.0 MB/s 15 | 5120 | 2304 | 2304 | 84.8 MB/s 16 | 5376 | 2432 | 2432 | 85.0 MB/s 17 | 5632 | 2560 | 2560 | 84.9 MB/s 18 | 5888 | 2688 | 2688 | 85.0 MB/s 19 | 6144 | 2816 | 2816 | 85.0 MB/s 20 | 6528 | 2944 | 2944 | 85.0 MB/s --- Targeting Fastest Result of md_sync_window 1024 bytes for Medium Pass --- --- FULLY AUTOMATIC TEST PASS 2 (Final - 16 Sample Points @ 4min Duration)--- 21 | 2008 | 904 | 904 | 84.8 MB/s 22 | 2024 | 912 | 912 | 84.8 MB/s 23 | 2040 | 920 | 920 | 84.7 MB/s 24 | 2056 | 928 | 928 | 84.7 MB/s 25 | 2080 | 936 | 936 | 82.9 MB/s 26 | 2096 | 944 | 944 | 84.7 MB/s 27 | 2112 | 952 | 952 | 84.8 MB/s 28 | 2128 | 960 | 960 | 84.3 MB/s 29 | 2144 | 968 | 968 | 84.4 MB/s 30 | 2168 | 976 | 976 | 84.8 MB/s 31 | 2184 | 984 | 984 | 84.2 MB/s 32 | 2200 | 992 | 992 | 84.9 MB/s 33 | 2216 | 1000 | 1000 | 84.8 MB/s 34 | 2240 | 1008 | 1008 | 84.7 MB/s 35 | 2256 | 1016 | 1016 | 84.7 MB/s 36 | 2272 | 1024 | 1024 | 73.7 MB/s Completed: 2 Hrs 8 Min 12 Sec. Best Bang for the Buck: Test 1 with a speed of 84.4 MB/s Tunable (md_num_stripes): 1408 Tunable (md_write_limit): 768 Tunable (md_sync_window): 512 These settings will consume 99MB of RAM on your hardware. Unthrottled values for your server came from Test 32 with a speed of 84.9 MB/s Tunable (md_num_stripes): 2200 Tunable (md_write_limit): 992 Tunable (md_sync_window): 992 These settings will consume 154MB of RAM on your hardware. This is 64MB more than your current utilization of 90MB. NOTE: Adding additional drives will increase memory consumption. In unRAID, go to Settings > Disk Settings to set your chosen parameter values.

Sorry for the off-topic guys, tried to PM but didn't work. @Patilan, glad your back Can you help me out in following post? or through PM. http://lime-technology.com/forum/index.php?topic=29024.0 Thanks!

That's strange, that is what windows will label the card, so no issue there. Which package exactly did you DL and use, just to be sure.

Right so this is an issue many have. In order to setup one OR more cards, one must be able to enter the bios configuration of the SAS controller (on many MBs it will not enter the sas config if you have USB sticks connected, when you hit CTRL+C it states entering configuration but it will not). One cards bios, controls all the cards global config. If you go in the global config, I believe it ALT+N (it will state on the bottom of the screen what the key strokes are) this is where you enable/disable cards and wach cards boot order (0 = first card). varies statement have been made on this; I can tell you my version, at least one card should be enabled, all cards should have their bios and FW flashed. Then it's up to you to configure if you want it to initialize the drives and enable the ports. Some feel its a long process and prefer unRaid does it. I don't agree and too lengthy to explain right now. I will update the OP one day, as I have new scripts to make the process fast/easier and UEFI support and P16 firmware packaged just haven't posted yet. Have been test all sorts of stuff and it stability. You can then enter each cards config and setup drive spinup delays, timeouts, etc. and if one or more are in IR mode, then raid volumes. As an example my first card is in IT mode and have a RAID 10 volume for my ESXi datastore. My other 4 port card with an expander hanging off it (taking up 2 ports off the LSI card) for a total of 24 drives to unRAID.

Ok, try the following, power off the server , remove ALL USB sticks from server. Cold boot, and hit CTRL-C at LSI post. Post your results.

When you cold boot your server at the LSi post can't you hit CTRL-C and does it enter the LSI configuration or does it bypass and just boot your server?

Yes, IF you selected to disable them from a boot order or left out the BIO's flash.

Congrats! glad all worked out.