Julez

Modified to delist the PSU.

The SeaSonic PSU yes. The LSI controller no.

Sorry for the late reply, yes it is.

Does not include shipping costs. All shipping will be from 61550 in the United States. Please PM if interested. RAID Controller: $50 - LSI SAS 9211-4i with box and 1 SAS/SATA break out cable (Originally purchased 12/4/2013 used for a RAID 1 mirror for an ESXi datastore) https://www.dropbox.com/s/6k7tt8oqbwdixkv/IMG_4149%20%282%29%20%281280x832%29.jpg?dl=0 https://www.dropbox.com/s/iqgeu4d6fuvr91v/IMG_4150%20%282%29%20%281280x841%29.jpg?dl=0 No photo of the PSU itself, just the box right now.

Thanks for playing, all items sold.

Added pricing for the last few items. Shipping not included in the listed pricing.

SOLD- 3 x Seagate ST3000DM001 3TB drives

Thanks Whaler, I appreciate it!

Sold - 2 x Western Digital WD6401AALS 640GB black drives

Updated sold all 8gig Kingston Unbuffered ECC DIMMs.

PM sent, I have no problem shipping as long as you have no problem paying for shipping

Updated. Cages and SuperMicro controller sold.

Decided to part the system out instead of selling it as a whole.

Complete set of photos: https://www.dropbox.com/sh/0ywjbdaun45okzh/AADMImc6tJdyUG7gVwpXJRNRa?dl=0 Not factored in to price, shipping from Peoria, IL. US All prices in USD. Paypal accepted and recommended unless local pickup. Motherboard: SOLD - $90 - SuperMicro X9SCL+-F with box, documentation and various SATA cables that came with the motherboard. CPU: SOLD - $100 - Intel Xeon E3-1220V2 with box and stock cooler. Memory: SOLD- 4 x 8GB (32GB) Kingston Unbuffered ECC 1333mhz DDR3 Drives: SOLD- 3 x Seagate ST3000DM001 3TB drives SOLD- 2 x Western Digital WD6401AALS 640GB black drives SAS/SATA Controllers: SOLD- SuperMicro AOC-SAS2LP-MV8 with box and 2 SAS/SATA break out cables Drive cages: SOLD- 2 x iStarUSA BPU-350SATA-Black (side note on this, I think there was a model change mid way, the trays are the same, but the cage design was switched up at some point, they look the same from the front minus the lights being green vs blue and being on opposite sides, the power connectors and sata connectors are also different on the back) I had built it to work with VMware ESXi so the motherboard and the LSI controller are actually on the VMware HCL, the SuperMicro SAS/SATA controller is not, but I had used it strictly as a SATA passthru for drives. The original build consisted of ESXi 5.1, the 2 640GB drives was my ESXi datastore for the VMs. One of the VMs was UnRAID for the media server portion.

Thanks for the info and clarifying that! Sure enough, that did the trick I appreciate it.

I had read in another thread you were only supposed to run reiserfsck against /dev/mdx rather than /dev/sdx? My cache shows as /dev/sdb or /dev/sdb1. Is that not the case?

I had a failed drive that I replaced after swapping the parity drive with a larger parity drive doing the swap with the failed drive. I've run reiserfsck --check against all 3 of my data drives and parity has also checked out ok, parity had a bunch of errors and then rebuilt itself, but when I attempt to run chown -R nobody:users /mnt/cache/apps I still seem to be getting a read-only file system error.

Nevermind apparently it does and I'm an idiot Feel free to bury this thread.

I read a couple of threads including this one with the same title. http://lime-technology.com/forum/index.php?topic=33612.0 Pretty standard setup, cache drive, has apps folder that's cache only. Using Sabnzbd. When I issue the mover script it says it skips the apps folder, which is fine. But up until about a couple weeks ago it was using the mover on folders under sabnzbd completed directory to move to array drives. I don't recall ever having sabnzbd having those completed folders in the root of the cache drive to get moved to the array. Am I batshit crazy in thinking it was working this way previously? I for the life of me can't figure out what I've changed short of updating apps.

I will say this, Sandisk Cruzer Fit drives make great USB ESXi boot drives and UnRAID USB drives.

gary's right create a small VMDK and on that VM pass through the USB drive with UnRAID. I think I'm still using the old method where you have Plop installed on the VMDK and then from Plop it loads UnRAID from the USB. I think there's a better way of doing it now, but someone else will have to chime in for that. This was the thread I learned from the most when I fired up UnRAID on ESXi - http://lime-technology.com/forum/index.php?topic=14695.0 I stuck with the latest version of ESXi 5.1 strictly because it's not worth messing with ESXi 5.5 since you can't update the VM Hardware anyway. If you go with ESXi 5.5 and update the VM Hardware the VM becomes a pain in the ass to manage from a hardware standpoint (mainly because VMware wants you to manage the ESX hosts with vCenter Server's web GUI). I use an LSI raid controller on the VMware HCL for my ESXi datastores as I don't really want to mix my UnRAID storage with my VM storage, and my VM datastores are just on a mirrored set of drives. I've also been known to use a Synology NAS new NFS shares for VM datastores as well, but that's really neither here nor there.

I've actually confirmed that it's a sabnz problem. Again I'm not sure why, because it was working properly before the drive filled up. But sabnz is dumping the temp directory into the root rather than using it's completed folder for the temp directory. When I get home from work I'll have to see if the schedule for the mover is running or not, the manual run of the mover script seems to still move all the data properly, it's just that temp location isn't the right location.

No, the cache disk is not part of the array disks, it wouldn't exactly be a cache disk at that point, it'd just be another array disk. So I have several shares that are set to NOT use the cache disk ever. Then my apps share is set to ONLY use the cache disk. I have sabnz as an app. I used to think that when a download completed it was just held in the completed folder of the sabnz directory, then when the mover script ran, it would relocate the content to the proper on array-off cache share. What I think it's doing (and I could be wrong, but I'm not sure yet) is that sabnz when complete rather than using the completed directory it's using the root directory followed by the proper share name. I don't think it's the mover script that's actually moving the completed movie to the root of the cache disk the more I think about it.

I was half way through writing a response about the mover script moving data from the completed directory of Sabnz to the share, but created that share back on the Cache drive instead of using the existing on the array drives. However, I manually ran the mover and it removed those temp share from the cache. I guess I just never realized that there was a temp share on the cache outside of the sabnz directory. So I think I'm good now I guess I'm just not sure if the scheduling is working for the mover. I'll wait and see again to see what happens tonight.

Thanks, I went ahead and went that route, all seems to be fine currently. Just need to make sure the mover works this evening.