weirdcrap

OK sweet. As far as the price goes, is this a deal for an r510 with these specs? Or could I do better for a similar price point? I don't want to sink hundreds of dollars in a pre-owned server unless it's a smoking deal. My main requirements are 10+ bays for disks, supports at least 64GB of RAM, and obviously a solid raid controller that will play nice with Unraid if someone thinks of something better before the sale ends.

I work in an IT shop so once I get it going I will probably get it put into one of our racks here. Or if not get a small rack for my home office and start my own home lab lol. Yeah, I was curious if anyone had recent opinions of the H200, I did some searching and saw some threads on here and most people say they are fine but limited to 16 disks? Not an issue for me since the server only has 12 bays. These were posts from several years ago though.

https://www.ebay.com/itm/Dell-PowerEdge-R510-12-Bay-Server-2x2-67GHz-12-Cores-32GB-H200-12x-Trays/172577298188?hash=item282e68970c:g:21UAAOSwySlZ6O4D Are these a good deal for the hardware specs? Thinking about pulling the trigger on one and figured I would get some re-assurance and inform the community! My backup server has Marvel controllers that until the last few UnRAID versions haven't given me any issues but lately they have been really acting up. I figured rather than sink several hundred dollars into new RAID cards for not that great hardware (see VOID in my sig) I could just spend a bit more and do a whole overhaul. I will lose some space for a few disks (16 down to 12) but the 4TB disks I am swapping in should make up for the difference.

I may have just solved my irq16 issue, several restarts and USB devices plugged into ports and the front and back have not produced a new IRQ16 disabled error. I found a post on the ubuntu forums that suggested swapping PCI-E cards to different slots fixed it for one user with a Gigabyte motherboard like mine. I had to come in to work on the server today anyways as one of my drives was throwing errors at boot that got its speed downgraded from 6GBps to 3GBps so I figured what the hell I might as well try it. Originally I had two PCI-E 1x expansion cards plugged into the two 1x slots at the bottom of the board. I moved the bottom one off the 1x slot and put it into the x16 slot (I have no need for a GPU) and everything SEEMS to be happy now. IRQ16 is still what it always was according to /proc/interrupts: root@Node:/home/user# cat /proc/interrupts CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7 0: 25 0 0 0 0 0 0 0 IR-IO-APIC 2-edge timer 5: 0 0 0 0 0 0 0 0 IR-IO-APIC 5-edge parport0 8: 4 0 0 0 0 0 0 0 IR-IO-APIC 8-edge rtc0 9: 0 0 0 0 0 0 0 0 IR-IO-APIC 9-fasteoi acpi 16: 40 0 0 0 0 0 0 0 IR-IO-APIC 16-fasteoi ehci_hcd:usb1 18: 0 0 0 0 0 0 0 0 IR-IO-APIC 18-fasteoi i801_smbus 23: 38 0 0 0 0 0 0 0 IR-IO-APIC 23-fasteoi ehci_hcd:usb2 24: 0 0 0 0 0 0 0 0 DMAR-MSI 0-edge dmar0 25: 0 0 0 0 0 0 0 0 DMAR-MSI 1-edge dmar1 26: 23814 0 0 0 0 0 0 0 IR-PCI-MSI 327680-edge xhci_hcd 27: 100794 0 0 0 0 0 0 0 IR-PCI-MSI 512000-edge ahci[0000:00:1f.2] 28: 4017 0 0 0 0 0 0 0 IR-PCI-MSI 524288-edge ahci[0000:01:00.0] 29: 2511 0 0 0 0 0 0 0 IR-PCI-MSI 2097152-edge ahci[0000:04:00.0] 30: 708529 0 0 0 0 0 0 0 IR-PCI-MSI 1572864-edge eth0 NMI: 0 0 0 0 0 0 0 0 Non-maskable interrupts LOC: 140729 218526 231275 187016 186757 154390 152016 148618 Local timer interrupts SPU: 0 0 0 0 0 0 0 0 Spurious interrupts PMI: 0 0 0 0 0 0 0 0 Performance monitoring interrupts IWI: 0 0 0 0 0 0 0 0 IRQ work interrupts RTR: 0 0 0 0 0 0 0 0 APIC ICR read retries RES: 20997 7530 3206 2167 1897 1142 1148 958 Rescheduling interrupts CAL: 2144 2680 3039 2932 2581 2553 2516 2791 Function call interrupts TLB: 675 1322 1617 1496 1328 1298 1357 1577 TLB shootdowns TRM: 0 0 0 0 0 0 0 0 Thermal event interrupts THR: 0 0 0 0 0 0 0 0 Threshold APIC interrupts DFR: 0 0 0 0 0 0 0 0 Deferred Error APIC interrupts MCE: 0 0 0 0 0 0 0 0 Machine check exceptions MCP: 5 5 5 5 5 5 5 5 Machine check polls HYP: 0 0 0 0 0 0 0 0 Hypervisor callback interrupts ERR: 0 MIS: 0 PIN: 0 0 0 0 0 0 0 0 Posted-interrupt notification event NPI: 0 0 0 0 0 0 0 0 Nested posted-interrupt event PIW: 0 0 0 0 0 0 0 0 Posted-interrupt wakeup event We will see if it continues to behave itself over the next week or so. TL;DR try moving your PCI-E cards around if you have other open slots, it may resolve your issue (YMMV).

My Mobo is a Gigabyte B85M-DS3H-A with an i7-4770. According to UnRAID my USB chipsets are both Intel 8 Series C220 based: IOMMU group 3: [8086:8c31] 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) IOMMU group 5: [8086:8c2d] 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) I currently only have a USB keyboard and my APC UPS plugged into two of the back USB2.0 ports.

Nope, everytime I plug a USB device into the front USB 3.0 ports I see the irq 16 disabled message. I hardly ever plug in USB devices to this server anymore so I kind of forgot about it lol. What usb chipset do you have? When I go into work tomorrow I will run dmesg on the server and figure out what I have and see if they are related.

1. You issue the mounting commands from UnRAID via terminal/ssh. Once I had my commands for mounting figured out I turned them into a user script that Squid's plugin can run on the server for me. 2. I use two one for radarr and another for sonarr. There is no reason you couldn't use a single remote mount point that I can think of.

--Yes I believe you need to reboot for the CLI tools you install to be available. --Key pair creation is a simple task and you can find instructions everywhere. The most important thing is to not set a passphrase to protect the key, if you do the script will fail to mount your directories because I am not aware of an easy way to pass a key passphrase to ssh as part of it's calling argument. --Yes the mount points all operate from within UnRAID. You may be able to mount directly in the docker container, I have never tried. Fairly certain you will lose any customizations you make to the docker when you update though. I honestly never modify anything in the dockers themselves.

-You install SSHFS from the Unraid nerd pack plugin: https://lime-technology.com/forums/topic/35866-unraid-6-nerdpack-cli-tools-iftop-iotop-screen-kbd-etc/ -The command I provided above needs to be run at array start and stop. If your SSHFS share isn't unmounted when stopping the array or powering down it will cause your system to hang. I use one script that mounts my SSHFS remote dirs at array start and another to unmount them at array stop. Squid's excellent user script plugin is perfect for this: https://lime-technology.com/forums/topic/48286-plugin-ca-user-scripts/ My mount script is just this (copy the line and change the path for however many directories): #! /bin/bash sshfs [email protected]:/remotePath/ /localPath/ -o StrictHostKeyChecking=no -o allow_other -o Compression=no -o IdentityFile=/mnt/cache/.watch/rsaKeyName Unmount just looks like this (copy the line and change the path for however many directories): #! /bin/bash logger "My unmount script is running..." umount /my/local/folder/path umount /my/local/folder/path2 -You need to have the folder already created IIRC. SSHFS essentially mounts the remote system's path inside of the local folder. -identity file is your SSH private key file used to authenticate to the remote system without the need for user input. You need to have already generated your ssh key pair and added your public key to the remote system's authorized_keys folder. The file path is just a path you choose to store the key file at. It needs to be somewhere outside of your array like inside a hidden dotted directory so the mover doesn't mess with it (like /mnt/cache/.mykeyfolder/mykey)

This and I am now seeing the below error in the syslog: Aug 16 16:10:44 Node sshd[12542]: rexec line 110: Deprecated option UsePrivilegeSeparation

Snip. Nevermind.

Maybe I am misunderstanding how I should be doing this but I assumed I would be using $DEVICE for my use case. Would what I have outlined below be possible with the scripting capabilities available in UD? Totally hypothetical example to illustrate what I am trying to accomplish: I have a flash drive (/dev/sdg let's say) and it has three partitions: sdg1, sdg2, and sdg3 all of which it needs to boot correctly and load the OS on it. I want to be able to simply give the image file a name (hardcoded in the script, or use the sdg1 part label, or w/e works). Then every time I plug the drive in the script beeps, removes the old image, takes an entirely new image (using DD or whatever you recommend) of /dev/sdg, and then beeps twice when it is finished. The resulting image is saved to my /mnt/user/Backups share. That would be the gist of how I want this to work. Ideally, it should be so basic that it would simply work for most drives and use cases, the only thing I would need to change would be the per-image labels if they were to be hard coded into the script.

Is it possible to take the example backup script and change it so that I get a full image of any disk I plug in that has the script enabled? I want to use it for backing up bootable USBs that may contain persistent data I want to archive. I haven't had any luck finding a ready made example I could use yet.

Running UnRAID 6.3.3 I have been replacing older/slower 2TB drives with new 4TB drives in my backup array and dropping the 2TB drives from the array altogether. Up until recently, I had only been running one parity disk so I never had to deal with this before. I was looking online to see if there was any existing documentation that mentioned the shrink array procedures for dual parity arrays, but I could not find any concrete information. I found a link in the FAQ that makes it sound like messing with disk assignments and what not becomes a bit more complicated when dual parity is involved. Do all the procedures listed on the Shrink Array wiki work the same if the array has dual parity drives? Or will I have to drop the second parity drive like that FAQ mentions before I start removing disks and reassigning slots?

I actually have a 10 disk server built in an 804, it works great. I like that: -I can store the SSDs up in the front panel of the case -It has built in fan filters to help keep the insides dust free -It supports large after market CPU coolers like the Cryorig H7 -as someone who's old server is built in a massive Antec 1200 v3 with 20 drives in it that thing is massive, heavy, and unwieldy to carry, even with two people. This thing spreads the weight out throughout the case and is nice and compact. My one complaint is the second cage full of drives is right over the power supply and with a standard sized power supply I barely have enough clearance to get all the drives connected. I am in the market to find a "stout" power supply that will make it not quite so tight.

You were right, I did leave one browser window open I totally forgot about. That's what I get for checking on the server from so many other servers on the network. Now that I fixed that CSRF error my ghost device is gone as well. I guess it had something to do with the browser session I had left open on the other machine.

@trurlThat disk has been unplugged for hours and is sitting on my desk at home so it should not still be showing in UD, that's why I was concerned about it. Thanks for the info about it being a part of UnRAID, I was not aware it was so heavily integrated. I did see some bits about having the controlr app installed with the associated plugin which I did have but have already uninstalled and it did not fix the issue. @SquidCome to think of it I may have a browser open on a machine in the server room I was using on Friday, that is probably the cause of the wrong csrf_token error.

I am still having this issue, though mine all show wrong csrf_token instead of missing. Hopefully someone can help me out. Running UnRAID 6.3.2 and as far as I know I was running the latest UD and preclear, I had CA AutoUpdate setup for the plugins to run weekly. I came in to the office last night to hook up a drive and setup a file copy to run over night. I hooked up a usb 3.0 external wd passport drive to the front port of the server and noticed a kernel panic flash across the screen and then the power light went out and the server rebooted. On booting and loading the UnRAID OS with the drive still plugged in UnRAID crashed again. I shut the server off, unplugged it, let it sit for five minutes, plugged it back in and it booted fine. When I looked at the log it was getting hit every five seconds with wrong csrf_token errors from both the preclear plugin and UD. I found some other threads were people saw clearing their browsers and uninstalling re-installing fixed it so I tried that, but the issue persisted. I use Chrome mainly if that makes a difference. I decided to uninstall it for the time being so the logs wouldn't fill up because I didn't want to work on it in the middle of the night. I unplugged the drive, cleared the /boot/ directory of any files folders I found relating to the plugins and rebooted the server. Even with the plugins uninstalled I am still seeing the UD section on my Main tab with a phantom disk for the USB hard drive listed as /dev/sda (see attached snippet). I checked and fdisk -l does not show a /dev/sda at all so the underlying Linux kernel does not see the drive still. Diagnostics are attached, you can see in the log that as soon as I attempt to re-install UD my log immediately starts getting wrong csrf_token errors again. I would prefer to be able to keep UD and preclear so I would appreciate some help in fixing whatever happened. node-diagnostics-20170305-1011.zip

Makes sense, I did some digging in my documents and found my chart from the speedtest I ran. Thanks for your help.

got home from work and checked on it and now it seems to be hovering around ~70MB/s.

With the dissk moved and your tunable settings I am now seeing roughly ~105MB/s during parity check. Do you think I can push it any faster with my setup? I'm happy with where it is now but faster is always better right?

Small update, I was slightly off on the disk numbers. The disk numbers before my juggling were: Motherboard (6 ports/6 used): 4x data 1x SSD cache 1x 2TB hot spare SAS2LP (8 ports/7 used): 6x data 1x parity SASLP (8 ports/6 used): 6x data IOCrest IO-PCE9215-4I (4 ports/2 used): 2x data I moved one data disk off the old SASLP card for a layout of: Motherboard (6 ports/6 used): 4x data 1x SSD cache 1x 2TB hot spare SAS2LP (8 ports/8 used): 7x data 1x parity SASLP (8 ports/5 used): 5x data IOCrest IO-PCE9215-4I (4 ports/2 used): 2x data Should I load the fifth drive from the SASLP on to the IOCrest card in the PCI-E 2.0 x1 slot or leave it? I haven't messed with the tuneables yet, server currently half together on my office floor. I could also off load drives onto a second 1x card I have (I still have an open PCI-E 2.0 1x slot). I seem to recall reading somewhere that unlike PCI slots, PCI-E slots each have their own dedicated bandwidth?

The old configuration I believe had 6 disks on the saslp, 6 on the mobo, and 4 on a pcie x1 sata card. Sorry I didn't flesh the specs out better I copy pasted what I had in another thread from last month. Those parity speed numbers for the old setup are from memory and I don't know if I have any screenshots or anything to back those numbers up (they may be exaggerated.) Yes the SAS2LP is in the x16 and the SASLP is on the x4. I will juggle some drives around and see how that does, then apply the new tunable numbers. Sent from my Nexus 6P using Tapatalk

I recently made some substantial hardware changes to my second UnRAID backup machine and since doing so my array speeds have been slower than what they used to be. My array consists of a mix of 2TB disks and a single 4TB parity drive. System Specifications Old specs: Mobo: ASROCK 880GMLE-FX CPU: AMD FX-6300 Black Edition RAM: 8GB (2x 4GB) Corsair Ballistix DDR3 Storage Cards: SuperMicro AOC-SASLP-MV8 Total Drives: 16 x 2TB (1 Parity x 15 data) Drives were all mounted in CoolerMaster 4x3 bay expanders where each drive had an individual power and SATA connection. PCI/PCIE Layout: 1x PCIE x1<----- IOCrest IO-PCE9215-4I 1x PCIE x16 <---- SuperMicro Card 2x PCI <----- Graphics Card my new specs: Mobo: ASUS M5A97 R2.0 CPU: AMD FX-6300 Black Edition RAM: 16GB (4x 4GB) Corsair Ballistix DDR3 Storage Cards: -SuperMicro AOC-SASLP-MV8 6x drives -SuperMicro AOC-SAS2LP-MV8 6x drives -SYBA SI-PEX40064 aka. IOCrest IO-PCE9215-4I 2x Other six drives are connected directly to motherboard. Total Drives: 19 x 2TB 1 x 4TB (1 4TB Parity x 19 2TB data) These are all in NORCO SS-500 5-Bay SATA / SAS Hot Swap Rack Module with individual SATA connections per drive and shared power from 2x molex connectors per bay. PCI/PCIE Layout: 1 x PCIe 2.0 x16 (blue) <---- SuperMicro Card x6 disks (all 2TB) 1 x PCIe 2.0 x16 (x4 mode, black) <---- SuperMicro Card x6 disks (all 2TB) 1 x PCIe 2.0 x1 <----- Empty 1 x PCIe 2.0 x1 <----- IOCrest IO-PCE9215-4I card x2 disks (all 2TB last 6 on Mobo). 2 x PCI <----- One Empty, one PCI Nvidia GTX200 series Graphics Card The parity drive, cache drive, and a few random array disks are all on the motherboard ports. I used the Disk Speed test script to test my disks and none of them are reporting terribly slow speeds (sdb & sdh are USB disks): 1) Before the hardware changes my array writes and parity checks were maxing out around ~112MB/s which is awesome and where I want to get it back to. 2) After the hardware changes and before I messed with the disk tuneable settings at all I was lucky to see over ~50MB/s (usually closer to ~30MB/s) during parity operations. 3) After applying some 'sane' numbers from the UnRAID wiki my speeds have improved but are still not up to where they used to be. Now I consistently see speeds around ~70MB/s during parity operations. The two tuneables I modified are: md_num_stripes: 2048 md_sync_window: 1024 Should I still use Pauven's tunables script to get a better idea of what my numbers should be? I see Johnny.Black has some advice for those of us who use SAS2LP cards. Is his advice still recommended as well? I also see Squid links to some discussions here that mention some issues with different drive sizes? I haven't flashed any updated firmware to any of them and INT13 is disabled on both cards. I haven't had a chance to read through all of the various discussions I am linking to, I am hoping someone with way more knowledge of this issue will be able to pop in and help me much quicker than it would take for me to read through all the different discussions and pages upon pages of replies. Edit: forgot to get to the point: So bottom line is, should I continue to mess with my tunables? Any recommended values? Should I try something else first?

Everything completed without issue this time.