upthetoon

Thanks for the advice. I’ll do some more digging on the Ryzen options.

Why Aye man I don't think I'd be brave enough to go down the sample route Did you get your board from a UK supplier? I had a brief look at Ryzen but that only because I googled "threadripper" to see what that was all about (the last time I built an AMD PC it was many years ago with an Athlon...). I can see much more reasonably priced Ryzens now that I have a half decent look. Choosing a £150ish Ryzen, it seems quite close to a single aged xeon. https://www.cpubenchmark.net/compare/AMD-Ryzen-5-2600-vs-Intel-Xeon-E5-2650-v2/3243vs2042 This was the server I found on eBay; https://www.ebay.co.uk/itm/SUPERMICRO-6027R-E1R12L-2U-12-BAY-SERVER-1x-INTEL-XEON-E5-2650-V2-32GB-RAM/113536006486?hash=item1a6f45f956:g:g04AAOSw9z1cDk0t:rk:6:pf:0 This site seems to have a good cheap/older selection; https://www.lamicro.co.uk/servers/supermicro-rack-servers?gclid=Cj0KCQiA7briBRD7ARIsABhX8aBHyFihku6GY8LXeP3rY7a2Lw-4-pMISdqMEdKv62jbGhKCn2kcztMaAk5lEALw_wcB I'm guessing that price will rise once all the little extras like any bays/cables/splitters/PCI cards are added though. Lifting my ATX board out and replacing it with a Ryzen board and CPU would be simpler... but would it be as fun?!

I built my current server 10 years ago (i5 quad core 16GB tower) and it's starting to feel a bit of strain with the dockers I have running. I've read through quite a few build threads and like the look of the second hand server builds you see around - my server goes in a cupboard so size and noise aren't too much of an issue. The UK is not the best place to source Supermicro gear, it is less abundant and (much more) expensive. I've seen a few servers available but they are all pretty old models and I cant find much on them on the motherboards they use on the forum. Is there any reason I should be avoiding them? I could just get a newer ATX mobo and stick a i7 in there but a couple of old xeons and a bunch of smaller DIMMS looks like a lot more bang for the money? Example eBay server... Supermicro 6027R-E1R12L Superstorage Server Including: Supermicro 12 x 3.5" Bay 2U Chassis Supermicro X9DRD-7LN4F-JBOD Motherboard 1 x Intel Xeon E5-2650 V2 2.60GHz 8-Core 32GB DDR3 RAM 2 x PXS-920P-SQ Power Supplies Rack Kit

This got lost in all the replies I think. Invalid port in redirect target. Only ports 80 and 443 are supported, not 444 error anyone?

Sorry to add to the list of people with probably obvious issues but I'm having trouble getting this working too. I've been using it through the RC's and have unraid set to port 444 to avoid the clash. It was working fine before the CA change. I've followed the instructions above (thank you) and set the HTTPVAL flag to true. I'm using port 81 for the docker and have port 80 fwd to 81 in my router. I'm getting this error which I can't see is happening for anyone else... Failed authorization procedure. <redacted>.duckdns.org (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching https://<redacted>.unraid.net:444/.well-known/acme-challenge/QaX0x01RBkOvVSiPIP5VlKlhGyQDYNZXTuanOrzQ-n0: Invalid port in redirect target. Only ports 80 and 443 are supported, not 444 Startup command; root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="letsencrypt" --net="bridge" --privileged="true" -e TZ="Europe/London" -e HOST_OS="unRAID" -e "EMAIL"="<redacted>" -e "URL"="duckdns.org" -e "SUBDOMAINS"="<redacted>" -e "ONLY_SUBDOMAINS"="true" -e "DHLEVEL"="2048" -e "PUID"="99" -e "PGID"="100" -e "HTTPVAL"="true" -p 81:80/tcp -p 443:443/tcp -v "/mnt/user/appdata/letsencrypt":"/config":rw linuxserver/letsencrypt

I couldn't see an obvious way to turn off https in unraid. I changed the secure port number in unraid which I don't think is a long term solution but has done the trick for now!

Seeing the same issue on rc8q; Error response from daemon: driver failed programming external connectivity on endpoint letsencrypt (~): Error starting userland proxy: listen tcp 0.0.0.0:443: bind: address already in useError: failed to start containers: letsencrypt

Thanks, I'll do the long smart test and see if that brings up anything interesting.

That diagnostic tool is great. Thanks for offering to take a look. The new disk is WDC_WD40EZRZ-00WN9B0_WD-WCC4E7RXXNR1 - 4 TB (sdg). It's 32C. No, some of the other disks were spun down. I had a look at the troubleshooting section before and have tried setting off a long smart test from the terminal. Not 100% sure it is running. ridcully-diagnostics-20170806-1257.zip

Yeah, did a preclear on the disk which went fine. Something is up now though, I can't get smartdisk info, just says "Please wait... retrieving S.M.A.R.T. information!" . The disk is still mounted and I can copy files from it. The identity tab looks ok; SMART support: Available - device has SMART capability. SMART support: Enabled SMART overall-health: Passed Other disks are fine and a reboot hasn't fixed it.

Hi, I just got a new drive so thought it would be a good time to make the move to XFS. I followed the wiki and took my next largest drive out of the global share settings and set of a rsync using nohup. It'd been killed after copying about 500GB of the 3TB drive; rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(636) [sender=3.1.2] rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at io.c(504) [generator=3.1.2] Any ideas what could have caused this to stop? Is using nohup likely to cause issues with all the output being written out?

Fantastic, thank you.

this docker is currently using the 10.0 repository, so whatever you're seeing it seems it's not that, that seems to affect 10.1 versions. currently (as in literally right at this very moment, working on moving over to 10.1) OK, thanks!

Hi, What version of MariaDB is in this docker? I think I'm seeing this issue... https://mariadb.atlassian.net/browse/MDEV-9181 Which is fixed in 10.1.11 forward. If it isn't already could this be moved up versions please?

Thanks, I'll have a look at both of those over the weekend...

thanks for the reply. I've been monitoring this for the last week after rebooting the server. It all seemed fine but now its doing the same thing. The mover ran last night and then there was only a spindown command for the parity drive. The others were all running. I used the manual spindown buttons on the gui and left for work, I'll see what its like when I get home. Is there a way of seeing what the OS thinks is active and is keeping the spindown command from being actioned?

Hi, I've tried a couple of dockers but always end up stop using them as my disks won't spin down when I do. The docker image is on the cache drive in a "non move" folder (/mnt/cache/.custom/docker). Even with no docker containers running the disks appear to spin up within a minute or two of being manually spun down and stay up. I have all disks set to spin down after 15 mins.

I'd also recently tried docker (ember media server) and plex server. I've disabled both of those and everything seems to be fine now. Full parity check with 0 errors. Not sure if its a coincidence or not.

Hi, I recently replaced a failed drive and all seemed to be good. There are no issues reported and the array/disks are all reporting healthy. No errors on a partiy check. My syslog, however, is contantly churning with this... Any ideas? Nov 1 08:32:11 Ridcully kernel: blk_update_request: I/O error, dev sdh, sector 310641831 Nov 1 08:32:11 Ridcully kernel: sd 7:0:0:0: [sdh] tag#15 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 1 08:32:11 Ridcully kernel: sd 7:0:0:0: [sdh] tag#15 CDB: opcode=0x28 28 00 12 84 04 a7 00 00 08 00 Nov 1 08:32:11 Ridcully kernel: blk_update_request: I/O error, dev sdh, sector 310641831 Nov 1 08:32:11 Ridcully kernel: sd 7:0:0:0: [sdh] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 1 08:32:11 Ridcully kernel: sd 7:0:0:0: [sdh] tag#16 CDB: opcode=0x28 28 00 12 84 04 a7 00 00 08 00 Nov 1 08:32:11 Ridcully kernel: blk_update_request: I/O error, dev sdh, sector 310641831 Nov 1 08:32:11 Ridcully kernel: sd 7:0:0:0: [sdh] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 1 08:32:11 Ridcully kernel: sd 7:0:0:0: [sdh] tag#17 CDB: opcode=0x28 28 00 12 84 04 a7 00 00 08 00 Nov 1 08:32:11 Ridcully kernel: blk_update_request: I/O error, dev sdh, sector 310641831 EDIT - the diagnostics were too large with the syslog(s) so I had to remove them. I can post portions if needed. ridcully-diagnostics-20151101-0836.zip

For reference if anyone finds this in similar circumstance, it was a chipset/SATA controller bug with the on board Marvell controller; http://lime-technology.com/forum/index.php?topic=40683.0

Thanks for your help Gary. I'm sure there's something wrong with the SATA3 ports when I use both of them for some reason. I've taken the faled drive out and re-used that port, the cache drive was then fine and the data re-build is now underway. Hopefully I'll have a fully stable server again by tomorrow! Thanks again.

Something weird is happening. I stopped the array and tried to assign the new drive. When I select it from the drop down is disappears from the list and the slot is shown as "unassigned" still. This new drive and the cache drive are both on the 2 SATA3 ports on the motherboard, the other drives are all on the regular SATA ports, I wonder if that's got anything to do with it.

I've unassigned the drive and started the array, theres another issue, thats what's thrown me. "Unmountable disk present: Cache • WDC_WD5000AAKS-22V1A0_WD-WCAWF7406431 (sdh)" The drive has a green circle but has this message.. Partition format: error " Unmountable - No file system (32) " No idea whats happened here.

No, I stopped the array, reassiged the failed drive then stated the array. Damn it. It then seemed to start a rebuild but then the 5th slot showed as disabled. It seems like I should change the assignment of disk 5 to "no device" now and start the array?

I had a 2TB array drive fail (it was a bit of a slow death with errors and then completely failed just before I added a replacement drive). I've precleared a 3TB drive (no errors or issues) and then just followed the instructions to replace the failed drive. It all seemed fine and started the data rebuild but after only a few minutes the new drive showed up as failed too. I havent physically disconnected the old drive, I'm using different SATA and power socket/cables. I've now stopped the array. The new drive appears in the list of drives... But if I select it, it does this; Diagnostics attached, help appreciated! ridcully-diagnostics-20151024-0905.zip