Fireball3

I recommend to have a look at the wiki pages before buying things! http://www.lime-technology.com/wiki/index.php?title=Hardware_Compatibility&oldid=8957#PCI_SATA_Controllers The BR10i is in the List of "not recommended" adaptors because it does not support drives >2.2TB Of course, if one can live with that restriction it's no issue. The link inside the table should provide further info regarding flashing, firmware etc.

Just 2 add my 50ct. On my both servers I was fine with a single core CPU. The one was an Intel Celeron, the other a Sempron 140. All cool on v5. With v6 I had issues -with the Celeron-System because of reduced parity check speeds. http://lime-technology.com/forum/index.php?topic=42629.msg406745#msg406745 -with the Sempron-System because of reduced network throughput. Full load on CPU and transfer speeds going down while copying to the cache drive (used to be ~100MB/sec. steady stream --> ~40-60M/sec. fluctuating) In addition to that, I have problems when streaming from my Sempron-System (which is now an X2 245e) to my Popcorn Hour C200. This seems related to the Realtek Onboard NIC (in connection with the C200). 32bit drivers on v5 apparently performed better than the 64bit ones coming with v6. LT (JonP) told me to wait for 6.2 because they will work on the samba protocol...will see. At the moment I use an additional Intel NIC in bonding mode and it seems to work (still testing). Only the Intel NIC won't "wake up on LAN". Conclusion: Use at least a dual core CPU. Try to stick with a Intel NIC. @Frank I see you're running a Sempron with Realtek NIC too. No issues so far? Especially network throughput - all steady?

Didn't check all the commands, and I trust that they are correct. There is just the one step missing, where the SAS address is set again, after the flash. Although I don't know what effect a missing SAS address will bring!?

Out of my mind: Repeat the sequence how P19 is flashed, but use the files from the P20 zip.

6300 rpm - well, if you had a quiet server previously, now you have a nice hair blower soundmachine.

Yes, by the time I put the zip together, P19 was the most recent available firmware. All my cards are still running with P19, but you can easily exchange the files with the P20 once you get the idea behind the procedure. unevent already explained it pretty well.

Hey peter, I presume you went through the readme that comes with the "H310 toolset"? Would you mind sharing your concerns, so we can improve those instructions? I know how you feel! I also read countless posts and had several unanswered questions. I decided to adapt those instructions and have all necessary files in one place after successfully flashing my 310's. All you need should be in that zip! If it is not, let me know what is unclear!

No, this is not generally valid. I have at least 2 H310 cards on different non-Dell boards running without the taping mod. If I remember correctly, the issue is related to the PCIe slot dedicated for graphic cards.

I haven't seen any comparisons what is best: DELL or LSI. All other rebranded cards (Intel, IBM) were flashed with the LSI firmware because there is no IT firmware from those vendors. The H310 procedure is derived from the IBM crossflash. It doesn't add much more effort to flash the LSI firmware. LSI firmware is proven in use by most of us but I'm sure the DELL software will do also.

I guess this is the same issue I reported some posts earlier. The problem will go away if you install the clean powerdown plugin - which I strongly recommend to do! Nevertheless, the bug you found should be taken care of.

Crossflashing the H310 is not as straightforward as with genuine LSI products. It is mandatory to flash the DELL IT firmware or you will not be able to flash the LSI firmware. In my post, I have linked to opentoe's finding. He says, the DELL IT firmware is also working with unRAID. I remember having read something about a different queue depth in the DELL firmware. Can't say if it is affecting performance in unRAID though. If unRAID shows your drives, the flashing has worked. As I explained in the how-to, if you flash the BIOS, the card will report duing POST and then you will probably see the operating mode it is in. Unfortunately there is no other benefit but it will increase boot time so I decided to skip the BIOS.

This can make a difference! Sometimes the main PCIe slot, dedicated for the use of a graphics card, can cause trouble. There might be options in the BIOS to set PCIe slot usage.

Hi levster, I'm sure you did a search on PAL error. The only options are to try another mainboard or use the UEFI method. I've never done the UEFI way but you will find instructions in the search results for "PAL error".

I will check what can be done to improve the situation in the wiki. It will still be a problem to lead people to the wiki if they just follow forum search results. I wonder if it is possible to have a post sticky on each page of a multi-sided thread?

Sorry for the late reply. Have been busy lately. I have never done it on a linux machine, but it should be the same. Just grab the right files.

I have updated my 5.0.6 server and of course installed dynamix. Having trouble to get the server to sleep/shutdown. This is what I captured with the debug option. I noticed that I hadn't installed the powerdown plugin and did it right away. That send the server right into sleep/powerdown - flawless timing . Is there an issue with the stock powerdown command or is it a dynamix issue? If necessary, I can deinstall the powerdown plugin again. Jan 7 10:01:10 Tuerke s3_sleep: ---------------------------------------------- Jan 7 10:01:10 Tuerke s3_sleep: command-args=-q Jan 7 10:01:10 Tuerke s3_sleep: action mode=sleep Jan 7 10:01:10 Tuerke s3_sleep: check disks status=no Jan 7 10:01:10 Tuerke s3_sleep: check network activity=no Jan 7 10:01:10 Tuerke s3_sleep: check active devices=no Jan 7 10:01:10 Tuerke s3_sleep: check local login=no Jan 7 10:01:10 Tuerke s3_sleep: check remote login=no Jan 7 10:01:10 Tuerke s3_sleep: version=3.0.1 Jan 7 10:01:10 Tuerke s3_sleep: ---------------------------------------------- Jan 7 10:01:10 Tuerke s3_sleep: included disks=sdb sdc sdd sde sdf sdg sdh sdi sdj sdk Jan 7 10:01:10 Tuerke s3_sleep: excluded disks=sda Jan 7 10:01:10 Tuerke s3_sleep: ---------------------------------------------- Jan 7 10:01:10 Tuerke s3_sleep: killing s3_sleep process 3672 Jan 7 10:01:10 Tuerke s3_sleep: ---------------------------------------------- Jan 7 10:01:10 Tuerke s3_sleep: command-args=-C 2 -h 00 -h 17 -h 18 -h 19 -h 20 -h 21 -h 22 -h 23 -a -m 15 -n -e eth0 -N 12500 -i 192.168.178.150 -i 192.168.178.153 -l -L -D 1 Jan 7 10:01:10 Tuerke s3_sleep: action mode=shutdown Jan 7 10:01:10 Tuerke s3_sleep: check disks status=yes Jan 7 10:01:10 Tuerke s3_sleep: check network activity=yes Jan 7 10:01:10 Tuerke s3_sleep: check active devices=192.168.178.150 192.168.178.153 Jan 7 10:01:10 Tuerke s3_sleep: check local login=yes Jan 7 10:01:10 Tuerke s3_sleep: check remote login=yes Jan 7 10:01:10 Tuerke s3_sleep: version=3.0.1 Jan 7 10:01:10 Tuerke s3_sleep: ---------------------------------------------- Jan 7 10:01:10 Tuerke s3_sleep: included disks=sdb sdc sdd sde sdf sdg sdh sdi sdj sdk Jan 7 10:01:10 Tuerke s3_sleep: excluded disks=sda Jan 7 10:01:10 Tuerke s3_sleep: ---------------------------------------------- Jan 7 10:01:10 Tuerke s3_sleep: s3_sleep process ID 16658 started, To terminate it, type: s3_sleep -q Jan 7 10:01:10 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:01:10 Tuerke s3_sleep: Extra delay period running: 15 minute(s) Jan 7 10:02:10 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:02:10 Tuerke s3_sleep: Extra delay period running: 14 minute(s) Jan 7 10:03:10 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:03:10 Tuerke s3_sleep: Extra delay period running: 13 minute(s) Jan 7 10:04:11 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:04:11 Tuerke s3_sleep: Extra delay period running: 12 minute(s) Jan 7 10:05:11 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:05:11 Tuerke s3_sleep: Extra delay period running: 11 minute(s) Jan 7 10:06:11 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:06:11 Tuerke s3_sleep: Extra delay period running: 10 minute(s) Jan 7 10:07:11 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:07:11 Tuerke s3_sleep: Extra delay period running: 9 minute(s) Jan 7 10:08:11 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:08:11 Tuerke s3_sleep: Extra delay period running: 8 minute(s) Jan 7 10:09:11 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:09:11 Tuerke s3_sleep: Extra delay period running: 7 minute(s) Jan 7 10:10:11 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:10:11 Tuerke s3_sleep: Extra delay period running: 6 minute(s) Jan 7 10:11:11 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:11:11 Tuerke s3_sleep: Extra delay period running: 5 minute(s) Jan 7 10:12:11 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:12:11 Tuerke s3_sleep: Extra delay period running: 4 minute(s) Jan 7 10:13:11 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:13:11 Tuerke s3_sleep: Extra delay period running: 3 minute(s) Jan 7 10:14:11 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:14:11 Tuerke s3_sleep: Extra delay period running: 2 minute(s) Jan 7 10:15:11 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:15:11 Tuerke s3_sleep: Extra delay period running: 1 minute(s) Jan 7 10:16:11 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:16:11 Tuerke s3_sleep: Extra delay period running: 0 minute(s) Jan 7 10:16:11 Tuerke s3_sleep: Initialize TCP activity counter Jan 7 10:17:11 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:17:11 Tuerke s3_sleep: Check TCP/SSH/TTY/IP activity Jan 7 10:17:17 Tuerke s3_sleep: Communication state is idle Jan 7 10:17:17 Tuerke s3_sleep: Shutdown system now Jan 7 10:17:17 Tuerke s3_sleep: System woken-up. Reset timers Jan 7 10:18:17 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:18:17 Tuerke s3_sleep: Extra delay period running: 15 minute(s) Jan 7 10:19:17 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:19:17 Tuerke s3_sleep: Extra delay period running: 14 minute(s) Jan 7 10:20:17 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:20:17 Tuerke s3_sleep: Extra delay period running: 13 minute(s) Jan 7 10:21:17 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:21:17 Tuerke s3_sleep: Extra delay period running: 12 minute(s) Jan 7 10:22:17 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:22:17 Tuerke s3_sleep: Extra delay period running: 11 minute(s) Jan 7 10:23:17 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:23:17 Tuerke s3_sleep: Extra delay period running: 10 minute(s) Jan 7 10:24:17 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:24:17 Tuerke s3_sleep: Extra delay period running: 9 minute(s) Jan 7 10:25:17 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:25:17 Tuerke s3_sleep: Extra delay period running: 8 minute(s) Jan 7 10:26:17 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:26:17 Tuerke s3_sleep: Extra delay period running: 7 minute(s) Jan 7 10:27:17 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:27:17 Tuerke s3_sleep: Extra delay period running: 6 minute(s) Jan 7 10:28:17 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:28:17 Tuerke s3_sleep: Extra delay period running: 5 minute(s) Jan 7 10:29:17 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:29:17 Tuerke s3_sleep: Extra delay period running: 4 minute(s) Jan 7 10:30:17 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:30:17 Tuerke s3_sleep: Extra delay period running: 3 minute(s) Jan 7 10:31:17 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:31:17 Tuerke s3_sleep: Extra delay period running: 2 minute(s) Jan 7 10:32:17 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:32:17 Tuerke s3_sleep: Extra delay period running: 1 minute(s) Jan 7 10:33:17 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:33:17 Tuerke s3_sleep: Extra delay period running: 0 minute(s) Jan 7 10:33:17 Tuerke s3_sleep: Initialize TCP activity counter Jan 7 10:33:46 Tuerke emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin install https://github.com/dlandon/powerdown/raw/master/powerdown-x86_64.plg Jan 7 10:33:47 Tuerke logger: plugin: creating: /boot/config/plugins/powerdown/powerdown-2015.12.18.tgz - downloading from URL https://github.com/dlandon/powerdown/raw/master/powerdown-2015.12.18.tgz Jan 7 10:33:47 Tuerke logger: plugin: checking: /boot/config/plugins/powerdown/powerdown-2015.12.18.tgz - MD5 Jan 7 10:33:47 Tuerke logger: plugin: creating: /boot/packages/powerdown-2.18-noarch-unRAID.tgz - downloading from URL https://github.com/dlandon/powerdown/raw/master/powerdown-2.18-noarch-unRAID.tgz Jan 7 10:33:48 Tuerke logger: plugin: checking: /boot/packages/powerdown-2.18-noarch-unRAID.tgz - MD5 Jan 7 10:33:48 Tuerke logger: plugin: running: /boot/packages/powerdown-2.18-noarch-unRAID.tgz Jan 7 10:33:48 Tuerke init: Re-reading inittab Jan 7 10:33:48 Tuerke logger: plugin: running: anonymous Jan 7 10:33:48 Tuerke logger: plugin: creating: /boot/config/plugins/powerdown/powerdown.conf - from INLINE content Jan 7 10:34:04 Tuerke emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin checkall Jan 7 10:34:18 Tuerke s3_sleep: All monitored HDDs are spun down Jan 7 10:34:18 Tuerke s3_sleep: Check TCP/SSH/TTY/IP activity Jan 7 10:34:24 Tuerke s3_sleep: Communication state is idle Jan 7 10:34:24 Tuerke s3_sleep: Shutdown system now Jan 7 10:34:24 Tuerke powerdown[11499]: Powerdown initiated Jan 7 10:34:24 Tuerke powerdown[11505]: Powerdown V2.18 Jan 7 10:34:24 Tuerke rc.unRAID[11509][11513]: Processing /etc/rc.d/rc.unRAID.d/ kill services scripts. Jan 7 10:34:24 Tuerke rc.unRAID[11517][11521]: Processing /etc/rc.d/rc.unRAID.d/ kill scripts. Jan 7 10:34:24 Tuerke powerdown[11525]: Initiating Shutdown with '' Jan 7 10:34:24 Tuerke shutdown[11526]: shutting down for system halt

I would like to PM you my diagnistics files. Is that OK for you?

Same here, Smart UPS750 with USB cable.

P20 is the latest firmware from LSI/Avago that you can flash on that card! http://www.avagotech.com/products/server-storage/host-bus-adapters/sas-9211-8i#downloads Can't think of a test you could do to see if the card is "well". If the firmware update is going well, it is a good sign. Run a parity check with your old setup and check again with the fully populated new controller. If there are no differences there is another good sign. Crosscheck new writes to the array by comparing checksums. Have a backup.

Some technical data about the 6/i I remember having seen a comparison of 6/i and 6/iR that I'd like to link here, but can't find it at the moment. Here is a discussion about the 6/i. Edit Another discussion with no result.

Ehm, check the labels on the card! The 6/iR has also E2K-UCS-61-(B) written on it. How can you say you have the Perc 6/i? Anyway, there are differences between the 6/i and the 6/iR. I flashed the 6/iR and can provide the files to do so. I found this about flashing the 6/i. Can't say if it will work, but might be a hot trail. Edit: May be a dead end after all, because they are talking about a plain firmware upgrade and not flashing IT firmware...

Hi SnackMaster, yes, I did successfully flash a PERC 6iR E2K-UCS-61-(B). I'm not sure if this is the same card you have! I remember having examined the differences but forgot it again. Anyway, I flashed that card but refrained from using it since it doesn't support drives with capacities > 2.2TB. If you have the E2K-UCS-61 card, I can look for the tools I used. But first make sure you have the right card.

Never tried to preclear that many drives at once. You (your rig) have enough resources to do that?

Assumption - can't tell if there was a driver change with the newer kernels used in v6. IMHO the numbers of posts is irrelevant. He solved his issue by going back to V19. Far more interesting is the fact that he is running FreeNAS and not unRAID. Like I already mentioned, it's hard to track down the changes as the versioning of LSI/Avago is not easy to find. Yes, it's appreciated! I will edit my post and link to your feedback above. If somebody else is running the P20.00.04: please report your experience!

I'm not sure about it! This guy mentioned the firmware version 20.0.04 to be problematic with FreeNAS. Can't say how it works with unRAID. Finding a changelog for the firmware is hard and I can't tell if upgrading to 20.xx is worth the hassle. I've read somewhere that there is also a firmware specific driver - at least for Windows it is the case. This means if you update to P20 they recommend to update the driver also. I don't think that the unRAID driver is updated frequently (if at all) so it will always be a risk to update to a new firmware. The new firmware might run flawless with FreeNAS or Win but not necessarily with unRAID (or vice versa). Therefore stay with P19 on a productive system as it is known working with unRAID. If you have time to test P20, your welcome to do so and share your results with the community.