bubbaQ

( Parity alone can not tell you anything about data integrity... you have to calculate the parity by spinning up ALL the disks, and then check the parity if you want to do that.

Could you add an Array variable for the Linux device for disk.... something like: $disks[disk1][fsDevice] => sda

Already sent it in. Speed and performance are as advertised.

If you get the Scythe "Kama-Panel", it comes with a slim-insert that is a 4-fan controller. http://www.scythe-usa.com/product/acc/015/Conpane4.html

No.

Mini-ITX, not micro-ATX.

Same as the Vertex2 Sequential Read : 200 MB/s Sequential Write : 125 MB/s Linux driver only supports it in SATA mode, not RAID.

It is not an Ocz firmware issue... it is an unRAID driver issue.

FWIW, I put the Revodrive in unRAID, and it does not see the raid as a set, but two individual drives. I've seen the same behavior with other hardware raid (i.e. on the mobo) in unRIAD.

Yup... and the reason it exists is that with sector remapping, once a sector has been remapped and a spare sector put in its logical place, you can't get back and overwrite that old sector. By using the code native to the drive, it will also overwrite the sectors marked as bad.

If you try to stop the array, and it can't stop, say, because of some open files, it ties up the UI, so you can't get to any other tabs.... which is where the utilities are (or will be) to close/kill processes so you can have a clean shutdown. Not sure how to get around that... but just something to think about. In the mean time, the next bubbaTools adds a small widget to the Array Status page, that indicated if any files are open.... seeing open files indicated there at least will give me fair warning that if I press stop, the array won't shut down.

It is possible... particularly if s2ram has a specific knowledge of your mobo. Run "s2ram -n" to see if it has your mobo in its database.

I have compiled s2ram (from the suspend-0.8 source). Note, you will have to first install libx86 for it to run. Both are in the attached zip file. If you lose your video when you resume, or have trouble getting your machine to go into or wake up from s3 sleep, you may benefit from using s2ram instead of writing the state directly to /sys/power/state. s2ram is cleaner, and does some "preparation" of the system before entering s3 suspend. suspend-utils.zip

That is my "plan B" if I can't find the other one. But none of the images I can find of it show the inside, and the openness of the backplane.

I once found a link to a 3-in-3 SATA hot swap drive cage. Now you may ask, why a 3-in-3? You gain no extra density. The reason is airflow. With the 3-in-3 spacing, the drives don't heat each other up, and you need less airflow, and thus less noise. This is for my desktop, not a server, so quiet is important. The one I found before used a 120mm fan and had a backplane that was the most open I have ever seen.... even more open than the Lian Li EX-H34. practically the whole right 2/3 (as viewed from the rear) was open. Anyway, I can't find it now... anyone have any suggestions?

Before I ever had a ZX-80, my first programming was a 32-step limit program on a TI calculator. I needed all 32 steps to find a better fractional representation for pi than 22/7 (=3.14286) .... I got 355/113 (=3.1415929)... pi=3.1415927

My mistake... I thought they were there in past versions.... that's what I get for spending too much time in my "custom" unRAID environment. And I agree with the philosophy. If you ever wrote your own multiboot partition boot loader, by poking machine code a byte at a time into the partition sector of a disk, you treat all memory space as precious.

lspci and lsusb are missing from the 5.0-beta1 distro

Actually, it is very likely the hardware. You would be AMAZED at what shortcuts HW manufacturers pull that makes their HW non-compliant with official standards (which Linux expects) and then they "fix" it in their Windows drivers.... never bothering to "fix" it in the Linux drivers. Particularly with something as low-profile as WOL. Yes, NIC and chipset manufacturers, I'm talking about you. So, if you want to blame Linux for expecting HW manufacturers to comply with standards, then that's up to you. I blame the asshat hardware manufacturers. Put a REAL Intel NIC in the system and you will likely not have a problem.

A SuperMicro SC830 or an Enlight EN-8960 would also work for me, if anyone has leads to a used one.

The "new" products are static pages .... not from the database that he whacked.

Actually, he is black, not gray ... he deleted all the products from the products pages. Compare the site now to archive.org.

This is very common. You have to save the video registers and restore them. The s2ram package will do this nicely.

"in -beta2 about to be released." :D :D

S3 suspend is dangerous. You can corrupt drives and lose your whole array messing around with it. I don't know how I can explain it differently ... S3 is not something that even can be "built-into" unRAID. It depends on way too many other variables, such as your BIOS, your PSU, your chipset, etc. The only thing unRAID can do, is include the S3 module. If it was not there, you could not do S3. unRAID has the s3 module. That's all that can be done from unRAID's perspective. Your frustration that you can't wake up your box from S3 is YOUR HARDWARE'S FAULT. Your hardware either has crappy Linux drivers, or implements the standards improperly, or any of 100 different bugs related to ACPI on Linux and S3 suspend mode. Did you try an Intel NIC, and disable the Realtek on the mobo? That's the first thing I would try.