Fireball3

I'm not sure if that is the case. I used this discussion to read up on staggered-spin-up. Found this, somewhat lenghty but informative, thread. As far as I understand now, either that mentioned P11 has to be left open or some setting on the drives has to be done to keep them spun down by default. If a controller/HBA can spin down a drive, I would expect it can spin it up also. Given, those drives "boot into standby" - meaning they are running but not spinning. In the end it means the OS is in control of drive spin.

This could be possibly managed in software, but the initial, cold power-on when no OS is controlling the drive spin is the major problem. I think that power supplies should be built to deliver a "bust current" for a brief period of time. But the overall saving is probably not worth it.

I scrolled down to the HX650 where 10% values were not available. Didn't even notice the 10% headline...thanks.

Do you have a source, as a qualitative example, how the 0-20% relation is? I'm not sure if you can simply extrapolate it (linear).

A LUN is not identical to drive size. I suppose they mean the RAID volumes that can be created (out of drives with a capacity <2.2TB) can be over 2.2TB. Feel free to correct me if I'm wrong. If it was just a matter of firmware, I'm sure we would have it already on all controllers.

You will be fine if the majority of your drives are reds and green drives. I would go for the 750W PSU.

Well, it covers green drives and standard drives. Power consumption of those didn't change dramatically and 1[A] is still 1[A] on PSU side. Maybe the PSU models are not up-to-date any more but check the listed vendors products for their recent builds. Watch out for the "single rail" and the recommended [A] in the OP.

Well done! Good to know it's working. I will add that to the wiki. The steps are the same as for the H310. You could have used the toolset also. LSI P7 is the key to bypass the vendor ID mismatch as you have the possibility to override it. Later versions of sas2flsh don't offer this option.

There is an improved preclear script by bjp999. It speeds up the post read process.

Is this not enough? Why?

Hi subzero, welcome to the unRAID forums. You have the card? Why don't you try it using the H310 toolset.

For all those who want to use the P20 firmware. See this post Backup your data before updating! Report back with your experience.

Yes, that is the cause of the blue screen you see. If you read carefully through the instructions it is explained why you don't need the BIOS and what to do if you want to have it flashed. For simple passthrough you don't need to set up anything in the BIOS and without it you get faster boot times. Just noticed your flashlog. Thanks for attaching them! According tho the log, you did flash a BIOS on that card. Then I can only guess that the BIOS is not working correctly with the card? I can't tell if it's normal (blue screen) or not because I didn't flash a BIOS to my cards. How long does it take @boot until the BIOS is finished with it's init? Maybe you can speed up without the BIOS. Anyway, glad to hear it's working. Can you confirm that temps and SMART as well as spindown is correctly working in unRAID?

You need to flash the 9240-8i to an LSI 9211-8i IT See this, or this. If you use the H310 toolset you need steps 1-4 and step 5.3 (skip the others) and step 6. Make sure you understand the instructions and ask before doing something wrong.

If you have a genuine LSI card, you can download the instructions and appropriate firmware from the LSI website. What is the model number of your card? e.g. LSI SAS 9211-8i

Thanks for the heads up!

@saihtam Seems like there is no IT firmware for your card. @nightanole LSI naming scheme is pretty confusing to me. The 9200 could be an OEM card? If you have the card, try the 9201-16e firmware that you found (P20). Save a backup of your current firmware. At least you could post the card info from sas2flash.

Hi, interesting find with that Raid500! That card seems completely new in the unRAID business. You should know, that frome here, it is all experimental and there is a chance to brick the controller! I did it with an FSC D2607 that also has the SAS2008 chip but won't flash correctly to LSI9211i firmware. This could also happen to the Lenovo build - but no one can tell you that (from what i found on the net). Bricking is really the worst case scenario since most tools simply won't flash and stop with an error. In my case FSC delivered a really nasty tool but that's another story... Far more probable is that you end up with an erased ROM and can't manage to flash the LSI firmware. Then you have to revert to the Lenovo firmware. This should ideally work at any time but you know this guy, Murphy? 1. As a first step, I would go straight to the latest LSI firmware (P19) Use the tools and instructions from LSI. Make sure you capture the logs when flashing. Use the logging options! Here is how Lenovo does the flashing - they use megacli (I never used it) 2. If P19 toolset won't work, you can try the P7 (use the whole toolset, not only the firmware file!). P7 is giving you the option to override the vendor mismatch - if that's a problem with P19. Having P7 flashed you can always go to P19 since P7 will set the same vendor-ID as P19 is expecting. 3. You don't need the EFI shell. You can work with DOS bootdisk/usb drive as well. Let's deal with the PAL error if it is the case. This is you first time...well, shouldn't be a problem if you understand what you're doing. First, you should read the instructions out of this package. Just to get the idea what is happening in the whole process. Then you should be able to tailor your own toolset (if necessary). Ask you questions before doing something! I suggest you should split this topic into a new thread and come back here later with the result.

Wow...so many reallocated sectors...ah, wait it's WD... At least it did not totally black-out like mine was doing. Reallocated sector count is "near threshold". Spare sectors will soon be out - as far as I understand the SMART philosophy. While I tend to keep even those drives with low reallocated counts, in this case I would scrap it.

You need to flash the 9211-8i IT firmware. For unRAID it is not necessary to flash a BIOS. You will have faster boot times doing so. You can download the IT firmware (should be P19) from LSI. If you get the pal error, try the UEFI installer for P19 or use another mainboard to flash your cards. Hopefully your cheap copies behave like originals!

More specific (perhaps I didn't understand well) A GUI to set up server and client for rsync backups.

Yes, I second this request!

Well, the naming S3 is probably confusing because in that script you can select the option to shutdown instead of S3 sleep! Take your time, I don't know exactly when I finish to set up my backup rig.

Or use the auto_s3_sleep script on your backup machine to power down when it is idling. This will work even if the GUI has gone unresponsive. Would you mind sharing your rsync config/setup files?

Thanks for improving! Please document/comment the changes inside the script, raise the version number and then post it here. I'm far from being that experienced to tell if there are better ways of scripting - if it works it's OK. Maybe others, with the same use case, will want to test and comment on it?