opentoe

Thank you! Looks real nice.

Couple of questions. Anyone else submit a drive to smartmontools.org? I've submitted a few times for a drive that is not in the database and it never gets added. I've given them all the proper information they have asked for. I've seen many drives being added since I'm on the email distro but just not the drive I've asked to add. You'll see below the "manufacture" is missing. You'd think most Western Digital drives would be in there already. Also, another questions. What does the PATH mean? What's the difference between FIRST install and RECENT install? Thanks. [WD-WCC130966733] => Array ( [TRAY_NUM] => 10 [TYPE] => SATA [DEVICE] => sdd [PATH] => 0:0:2:0 [uNRAID] => disk9 [MANUFACTURER] => [MODEL] => WDC WD4003FZEX-00Z4SA0 [sN] => WD-WCC130966733 [FW] => 01.01A01 [CAPACITY] => 4.00 TB [POWER_ON_HOURS] => 17391 [LOAD_CYCLE_COUNT] => 33 [FIRST_INSTALL_DATE] => 2015/09/18 [RECENT_INSTALL_DATE] => 2015/09/18 [LAST_SEEN_DATE] => 2016/01/09 [PURCHASE_DATE] => [NOTES] => [sTATUS] => INSTALLED [FOUND] => YES => green-on

Why such an expensive controller? Could of grabbed two 4 port controllers for less then what one of those cost, unless you didn't have the slot for it. Seems to be a nice fast card. Hard to tell what case you are using, but keep on trucking!

I believe since you will be using it in passthru mode (IT) it doesn't matter the size of the drive. The OS just needs to recognize/support the size.

Suggestion. Since we now have the entire list of tools in the gui can we add descriptions to the tools when you hover the mouse over the filename? Just for the lazy people I guess, like me.

Hi. Does the TRIM plugin work on unassigned SSD drives? I did install the plugin and the description indicates it is a CRON job using fstrim on the cache drive. Where is it adding the cron job, I may want to add my unassigned drive in there also. I checked all my cron folders and didn't see any changes but then I also do not have a cache drive. I thought I would at least see fstrim command in the /etc/cron.d folder. Jan 8 18:26:08 SUN logger: plugin: creating: /boot/config/plugins/dynamix.ssd.trim/dynamix.ssd.trim.txz - downloading from URL https://raw.githubusercontent.com/bergware/dynamix/master/archive/dynamix.ssd.trim.txz Jan 8 18:26:08 SUN logger: plugin: checking: /boot/config/plugins/dynamix.ssd.trim/dynamix.ssd.trim.txz - MD5 Jan 8 18:26:08 SUN logger: plugin: running: /boot/config/plugins/dynamix.ssd.trim/dynamix.ssd.trim.txz Jan 8 18:26:08 SUN logger: plugin: running: anonymous Jan 8 18:28:29 SUN in.telnetd[26597]: connect from 192.168.1.121 (192.168.1.121) Jan 8 18:28:34 SUN login[26598]: ROOT LOGIN on '/dev/pts/1' from 'BIGBEN' Jan 8 18:30:42 SUN emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog

It does get quite confusing since there are different methods for different cards. I've only flashed the Dell H310 cards. I think I flashed about 20 of them already. You will also read that if you flash with the DELL IT FIRMWARE, which you can download right from Dell's site and is approved by Dell the QUEUE DEPTH is very low. The Dell queue depth is 25. The LSI IT FIRMWARE is 600. Now I've used both variations of the IT firmware and have not found one or the other to perform better. I just happen to have the LSI IT FIRMWARE running since it was the last version I flashed to the cards. If you are having trouble flashing and need specifics or files themselves let me know. As I said before it has been a while since I've flashed anything but still have my notes and the files I used and once I start doing it the memory will come back.

Find the make and model of your ssd, search for the makers web site, then look up your model to see if it has native garbage collection. Here's what Samsung says about TRIM. I currently have one 840 EVO SSD drive as an "unassigned" device, but apparently it doesn't have built-in TRIM, so once again install another plugin. "Modern operating systems have enabled another form of SSD maintenance, TRIM. TRIM is a facility by which the OS can notify the SSD when data is either marked for erase or no longer valid. TRIM helps to make Garbage Collection more efficient by preparing invalid data for deletion. Remember, SSDs are new technology, so computers were built to interface with traditional hard disk technology. Hard disks are not subject to the same write/erase limitations that SSDs are – they can easily overwrite data in an existing location without erasing it first. Therefore, when the OS “deletes” data, the data does not actually go anywhere. The space in which it resides is simply marked as “free space” that may be used later. By default, because it doesn’t know it’s not working with its longtime HDD companion, the OS doesn’t let the SSD know that a particular piece of data is no longer valid and that its corresponding memory location is now free – after all, there is no reason to do so. With the introduction of SSDs, however, there is now a compelling reason to increase communication about file validity between the OS and the storage device. Enter TRIM. TRIM allows the OS to inform the SSD which data are no longer valid, allowing the SSD to skip over invalid data when performing Garbage Collection instead of moving around old data. Once a block is full of pages that all contain invalid data, that block is considered free and may be erased. The TRIM command is sent to the SSD controller automatically by the OS every time it deletes a file. As it requires OS support, not all users will be able to use native TRIM functionality. On PCs, TRIM is supported in Windows 7 or later. On Macs, TRIM is only supported for Apple’s OEM SSDs and is not supported for Samsung’s (or any other manufacturers’) aftermarket SSDs. Users of older Windows operating Systems (Windows XP, Windows Vista) may use Magician’s built-in “Performance Optimization” feature to manually pass the TRIM command to the SSD on demand (or via user-specified schedule)."

The heatsink does get quite warm to the touch also. Even at idle. If you do not notice a temp increase, then it probably dead.

When the computer boots up you'll see it being initialized. Do you see that?

Just to note in case needed. I just updated the local master browser plugin a few minutes ago and received the "defaultpagelayout" error and couldn't access the web interface. I logged into the box and rebooted from within (I needed a reboot anyway) and the error went away.

I got to be a pro at this when I upgraded my cards and also did several for other users on here on the forum for free. It was actually hard to brick a card. I still have my notes and could look them up if needed, and still have all files I used. One thing I do remember to avoid manufacture checks was to use an older version of SAS2FLSH. I do remember when using the latest version that came with P20 complained also.

I've been running Crashplan in a VM for a few months with no problems. I'm not savvy enough or have the time to constantly update files or troubleshoot why it doesn't work after an update. After the initial backup, you can drop down the memory to 1GB or even less. It is a basic Ubuntu install, auto updates and runs pretty good. I use VNCVIEWER to connect from any machine on the network. Backing up over 600GB.

Thanks for the tips! I didn't realize they updated their models. If anyone has knowledge about the above, I'm all ears! Thanks! If you aren't sure of what exactly you'll be adding slap another 200-300 watts. I still and will always recommend Seasonic as the best power supply out there. I own over 20 of them running Bitcoin miners 24/7 at around %80-%90 and not once ever had an issue. I've burnt through several brands, including Corsair's. Seasonic does make a lot of other models, including Corsair. I've checked all the Corsair models I've burnt through and none were manufactured by Seasonic. They were made by Channel Well. If you are calculating down to the AMPS and WATTS you may as well just spend the $200 on a really good 10 year warranty high watt PSU and be done with it. In the grand scheme of things $200 is pretty small and the part is very crucial. Good luck.

If you are going to purchase the Norco 4224 case I suggest make sure you try to get the updated version. Norco didn't change the model number or skus on it, but made a few changes. Each backplane (4 drives) is powered by one 4pin molex not 2. 2.5" internal hard drive tray 120mm fan board, old version only had 80mm. I removed all the noisy 80mm fans from the board and installed 3 120mm Noctua fans. Stock fan board comes with 4 80mm noisy fans with plastic grills. I flipped the fan board around so the fans were on the other side and removed the 4 80mm and installed 3 120mm. That helped with the wiring and noise, but took away the 2.5" drive plate which I don't use anyway. I did post some pictures I think in the OCD/build thread but can't find them. Here they are again. Remember the Norco SAS cables are pretty short and thick. I bought them and was able to use them, but were hard to work with in getting around corners and such. I did buy another brand that was longer and had the same spec but was much more easier to bend and work with. They were blue in color, can't remember where I got it, but they are easy to find online. Picture1 Picture2 Picture3 Picture4 Picture5 Picture6 Picture7 Picture8

The Plugins page says "built-in" in the last column for "native" plugins. There are only 2. Added plugins have a checkbox that enables a remove button. Darn. I always miss the obvious. I just noticed the Dynamax webgui plugin says "no update" and all the others say "Up-to-date". Is that for a reason?

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. Been running the latest P20 for over a 60 days with different hard drive models and sizes. I think the original P20 firmware and an older Linux kernel was a bad combo. I think once LSI/Avago performed their update and with a new kernel may have taken the issues away. It is hard to tell from a single post from a user with 4 total posts. Not saying he's wrong but it does contradict my results %100. If there was an issue I would have definitely noticed it by now. I wouldn't even try the original P20 firmware. I still recommend if someone wants to try the P20, don't get it from a packaged zip file or depository. Just grab the new one from the Avago site. Just to be on the safe side. Someone has to be a pioneer and try it, right?

I linked 2 posts. May be more though. LSI/Avago quietly fixed the P20 firmware with a new update. They still called it P20. I suggest do NOT use any of the custom or pre-packaged zip files out there since they all will probably contain the original, faulty firmware. Just download the latest P20 from the Avago site. I did confirm it is the newer firmware. I also got this from LSI/Avago's knowledge base. 20.00.00.00 OLD 20.00.04.00 NEW Question: Upgrading to firmware phase 20 (20.00.00.00) caused errors in /var/log/messages file Answer: If you upgrade to phase 20 firmware (20.00.00.00) on LSI SAS HBAs (e.g. LSISAS2004, LSISAS2008, LSISAS2308 based) then you may see this repeated many times in /var/log/messages: mpt2sas0: log_info (0x31080000): original (PL), code (0x08), sub_code (0x0000) This has been addressed by Avago and has been fixed in a newer firmware release: 20.00.04.00 (still called phase 20, or P20). This firmware can be downloaded from the Avago web site (http://www.avagotech.com). To avoid the message, you can flash the controller to an older version of firmware (e.g. phase 19), or flash to the newer firmware release 20.00.04.00 or newer (if available).

I just installed the AutoFan plugin. I think I didn't have such good luck with it previously, but need something to monitor or keep an eye on my CPU fan's RPM. Strangely I woke up this morning with the system power off. I never power it off. So I powered it back on and the bios message on the console was CPU FAN ERROR or something. I think I have the bios monitoring my fans, so if they dip too low the board itself will perform a shutdown. I'll have to see if this can monitor my CPU fan. If it can and works, then I'll turn off the bios monitor. Don't want them conflicting with one another. Or just remove AutoFan plugin and let the motherboard's built-in monitoring do it's job. It doesn't need software to work. EDIT: The AutoFan settings page does indicate STOPPED. But when I view my dashboard I see a couple fans there and their RPM's are moving up and down. After a reboot, it will indicate RUNNING, but when changing settings on the WebGUI it won't read "RUNNING" again. I also don't see all the PWM fans in my system. I've tried "detecting" on all that's there but doesn't seem to like what I have maybe. Starting to install too many plugins. Can't tell what is native or has been added. I'm sure lots of users have a lot more, I have 16 plugins.

Yes, it is confusing because many different issues are discussed here. If you want to crossflash the M1015 to LSI IT firmware, the latest is P11. Because P20 apparently has some data corruption issues, it is recommended to stay with P19! The package linked for the M1015 is not up to date because nobody worked on it. It shouldn't be a problem to take the P19 (e.g. out of the H310 package) instead of the P16. EDIT: fixed, and linked Has P20 version been confirmed "bad" by multiple users? I opted to use P20, and has been running good. I know there was a document or thread out there here about it.

I made a bootable USB stick and copied multiple versions of the LSI firmware/bios. Multiple versions of the sas2flsh utility, threw in a text based editor and whatever else I could think of so I wouldn't need anything else. That card doesn't have any BBU or on-board cache. I don't think that mode will even turn on. That's my guess.

I've noticed version 7 of the sas2flsh.exe utility works best. I fooled around with an extra H310 card I had. Also I was able to re-program the SAS address to a different address then what it originally was. Not that this matters much, but just for information. Just as long as there aren't any address conflicts should be ok. Why? Because one H310 card was "messed" up from someone at work and said he "bricked" the card. Apparently he erased everything on the card but I brought it back to life by re-flashing it and re-programming the address.

I read about the queue depth with the Dell firmware as well. I don't know if Dell updated that with their 2014 version IT firmware or not. I've used both versions of the card (Dell IT and LSI IT) and the performance was the same. I can't even remember which versions I have installed right now, but the server is operating very nicely so I won't screw it up.

I'm using the correct bios/fw but I do notice that flashing to ir is a problem comparing to flashing to it - yes I am trying older version of sas2flsh too. Do you know what the oldest sas2flsh fileversion is ? I remember getting the older version of sas2flsh from grabbing an older firmware version from 2011. There are probably over a dozen versions of that utility around. Each firmware download from Avago's site is packaged with the utility. Download some older ones and extract the utility. Dump them all on the USB stick and try them out.

Just make sure you are flashing it with the correct chipset firmware. If you aren't, you can brick the card. Once you have confirmed you do have the right firmware files, then you should be able to crossflash it. We don't normally see users asking to flash a card to IR mode, since you can't use passthru at that point but if you are getting those errors you listed above, try another version of the sas2flsh.exe utility. I have noticed that the older versions of that utility let you bypass manufacture ID conflicts and give you much better odds on flashing it successfully.