SSD

Thanks! That's what I thought but good to know for sure. Added to the "Best of the Forums", "Hail to the Chief" section here.

But the question is --- if a drive is being rebuilt, and you get a read error from one of the drives (parity or data) during the rebuild, would unRAID terminate the reconstruct of the drive? Or would it just go on to the next sector and complete the reconstruction on a best effort basis?

I agree. unRAID does not take a drive out of service for a read error - only for a write error. In this scenario (rebuilding a drive), I don't think that unRAID would stop for a read error. It would likely assume the sector were all zeros and continue on. This is just a guess. TOM IF YOU ARE READING COULD YOU CONFIRM OR DENY? INQUIRING MINDS WANT TO KNOW!

By the time I got this note, the lock had been dropped. Thanks for the instructions. I'll try it next time this happens.

I don't think I asked my question very well. I had a WINDOWS workstation copying a large file to the unRAID server. The Windows workstation crashed. The file it was writing is now locked on the unRAID server, even after the Windows workstation comes back online. I believe if I wait several hours the lock will get dropped. Is there a way to get unRAID to release to lock sooner without rebooting the unRAID server?

Occasionally I have a machine go down while writing to the unRAID server (usually to the cache disk). On reboot, the file it was writing to is frequently locked and cannot be deleted. It makes it hard to resume copying. I've tended to just ignore it and the next day find that I can delete it. Is there is a way to force a file to be closed so that it can be deleted.

A link to this thread has been added to the Best of the Forums (see link in my sig). Thanks to Tibbar and WeeboTech for providing a great "How To" that will benefit many other users! We now return to the regularly scheduled thread ...

How are your drive temps? Is there a fan on the back of the drive cage pulling air over the drives? If not and your drive temps are pushing 45-50C, I'd consider putting a high CFM fan on the back to try to pull as much air between the drives as possible. I've had some luck enlarging 80mm fan mounts to 120mm with my dremmel. 120mm fans move much more air and are also quieter.

My server is a P5B VM D0 MB, E2140 CPU with Zalman cooler, 2G GSkill Memory, 550 Watt "Mag Dog" (old Compusa brand) PSU (likely the weak link, but working fine running 15 drives!), Adaptec RAID 1430SA PCI-E 4 port SATA card, and Supermicro 8 port PCI SATA Card. Very much different from WeeboTech's supercool mini project, this is a hulking beast of a server at 27" tall and weighing close to 50 lbs I'd guess. Drives: 4x 1T (1 is parity) 5x 750G 4x 500G 2x 300G IDE (1 is cache) Total Usable (Rated) Space: 9.05T + 300G cache (not including parity) Case is an old SuperMicro SC750A. I've gone at it with a dremel numerous times as you'll see. From the front and rear. The cable is an eSata to Sata cable running to an internal drive. My best dremel job on that upper 120mm fan. Looks stock. Front cover removed - Notice dremmeling for lower fans (case was made for 3x80mm fans down there) and 2 fans attached to the hard disk cooler frontplates. There is another fan above the 2 lower ones (mounted inside). In order to mount all my drives I designed and built a custom 10 drive cage using aluminum strips and right angle pieces. Here are pictures while it was under construction and mounted inside the case. This case is cavernous inside providing lots of room for this. Closer look at the drive cage - if you look closely you'll see the edges of the three fans on the right. The zipties make it easier to remove the cage when needed. My next project is to build a custom drive cage to fit inside the upper (normal drive) area. I'll bet I can get 9 or 10 drives in there, whereas there are only 5 at the moment. There is also room above the PSU for probably 6 or so drives. If Tom allows for more expandability, and I need the space, this case can likely get close to 30 drives inside.