Jump to content
XPEnology Community

HHawk

Member
  • Posts

    59
  • Joined

  • Last visited

Everything posted by HHawk

  1. But, if I do that; I can visit SABnzbd when typing in my browser ip-address:8080?
  2. Okay, I created a docker-compose.yml (seems indeed pretty easy) with the following: version: "2.1" services: sabnzbd: image: ghcr.io/linuxserver/sabnzbd container_name: SABnzbd environment: - PUID=1028 - PGID=100 - TZ=Europe/Amsterdam volumes: - /volume1/docker:/config - /volume1/DiskStation/Downloads/complete:/downloads - /volume1/DiskStation/Downloads/temp:/incomplete-downloads ports: - 44100:12025 restart: unless-stopped However, when I run it, I noticed straight away the following again: 2021-02-23 09:17:01,536::INFO::[SABnzbd:1427] Starting web-interface on 0.0.0.0:8080 2021-02-23 09:17:01,536::INFO::[_cplogging:216] [23/Feb/2021:09:17:01] ENGINE Bus STARTING 2021-02-23 09:17:01,639::INFO::[_cplogging:216] [23/Feb/2021:09:17:01] ENGINE Serving on http://0.0.0.0:8080 2021-02-23 09:17:01,640::INFO::[_cplogging:216] [23/Feb/2021:09:17:01] ENGINE Bus STARTED ... 2021-02-23 09:17:01,641::INFO::[panic:239] Launching browser with http://127.0.0.1:8080/sabnzbd Seems it's forcing 8080 again. What am I doing wrong?
  3. Hi Dfds, Thank you for responding, but now (for me at least) where do I add that exactly. I did read something about it, but I have no idea where to exactly add that to be honest. I did search XPEnology NAS for something like that (to add it), but could not find it. My previous build didn't use Docker at all (installed it from packages back then). I upgraded the old DSM 5.x to DSM 6.x about 2 years ago and decided to finally upgrade everything (in terms of hardware) and redo my complete setup agian, but this time with Docker. Sorry for my ignorance. Regards, HHawk //edit I searched Google for that file: docker-compose.yml. It should be located in /volume1/@docker/ however nothing is there. Only a bunch of other directories.
  4. Hi all, Been busy with this from early this morning; long story short, I managed to setup SABnzbd, Sonarr, Radarr and got them working. I could change the default ports for Sonarr and Radarr without any issues... These are all running from a XPEnology NAS with Docker. However changing the default port for SABnzbd (from 8080 to something like 13502) is becoming a real pain. Every single time I change it to a different port and restart, reboot, whatever. It will go back to port 8080. I have no clue how to force a different port. I tried a ton of things including editing the sabnzbd.ini file and change the port there, but it simply gets reset. Sidenote; if I change the HTTPS port it will work, however it's not possible for me to get a Let's Encrypt certificate on the hostname XPEnology NAS (using afraid.org DDNS service). Anyways, can someone tell me how I can change the default port for SABnzbd running through Docker? I don't want to use the default port. I think the issue is related to how SABnzbd is started from Docker: 2021-02-22 13:52:39,987::INFO::[SABnzbd:1162] Arguments = "/app/sabnzbd/SABnzbd.py" "--config-file" "/config" "--server" "0.0.0.0:8080" But I have no clue on how to change that port number (and where). Maybe someone has some advice for me or can help me? This is driving me nuts! Thanks! Regards, HHawk
  5. Thank you flyride also for your reply. Might look into a lowest "K" CPU and undervolt it. One more silly question. Will any of the processors mentioned by you be faster than my current: Intel Core i3-4130 I know it has less cores (only 2 cores), but has 4 threads but I don't the threads are used in XPEnology? Is this correct? Also the Intel Core i3-4130 has a base speed of 3,4 GHz, though this is advertised in my XPEnology as 3.7 Ghz. Wrong? Maybe this is incorrect, however it *might* be that I overclocked it a little back in the day. The current setup is (I guess) 2 years old. I don't want to drop on core speed, because (if I understood and read correctly) core speed is important on tasks like unpacking / extracting in SABnzbd for example. True? Maybe I mistaked or I have old ideas. I am currently tempted by the Intel Core i3-8350K for my future build and undervolt it. However still not 100% decided on it obviously. Might go the 9100T route or any other decent T-version. As I still need to find the time and energy to redo the complete XPEnology build, install and setup obviously. Thanks again both for your input.
  6. Thank you for your input. Highly appreciated. I will the information to good use.
  7. Error... Posted another CPU but without GPU.
  8. Due to personal circumstances, I was not able to build my new NAS. However I am out of the hospital and finally can restart this. I am ditching the RAID controller, as I will be using the onboard SATA controller. The only debate I have now is which processor to choose. Currently I have a Intel Core i3-4360 in my current NAS. I am looking for something more powerful which uses 1151 socket. I also did some reading on the forums. However I need some more information on things; I believe the maximum CPU cores is limited to 8 Threading is not supported by XPEnology Intel Turbo boost; is this used? As you can read, I did find most information on the forums. However the only thing I am not sure about is the "Turbo boos" function. Is this supported in XPEnology and does it work? Sidenote; does SSD caching nowadays work with XPEnology? I know there were issues with this in the past. And is it recommended? Or best left alone? So far I am considering the following Intel CPU's: Intel Pentium Gold G5620 - 2 cores @ 4.0 Ghz. (no turbo) Intel Core i3-8300 - 4 cores @ 3.7 Ghz. (no turbo) Intel Core i3-9350K - 4 cores @ 4.0 Ghz (4.6 Ghz. turbo) If it does not matter much, my best bet would be the G5620. Or is going for 4 full cores (i3-8300) better in terms of performance on my XPEnology NAS? I think the 9350K is overkill and to highly priced for a NAS. Thank you for your input and suggestions! As always, highly appreciated. Regards, HHawk
  9. I gave up getting this to run (either version) on either test server (R410/R710). For some reason I am unable to find the Synology. No matter what I try. I even tried different USB sticks now as a last resort, but no luck.
  10. Well retrying both again on a R710. Which uses Broadcom NetXtreme II BCM5709 Gigabit Ethernet (4 ports). This NIC is supported by both loaders, but still, the same issue. No IP, so I cannot find the Synology to install. Also tried both UEFI and Legacy BIOS, but no cigar. Strange...
  11. Okay just a follow up. I have just tried 3615, but the exact same issue. It cannot find the Synology to install. :S I will retry a few more things. But I have no clue what is wrong. Did all the necessary steps in grub.cfg. Also with 3615 the R410 does not show up as it is having an IP assigned in the router. But when I boot the same machine to (for example) Parted Magic, it receives an (dedicated) IP.
  12. @A__C Thank you for responding. Highly appreciated. The reason why I was testing 918 is because of the RAID controllers. I wanted to test it to see if they were "accepted" without errors... So probably the reason is the hardware is to old? :S I have not ordered the rest of the hardware, because I wanted to make sure it would run. Sidenote; if I would order SAS to SATA adapters; in the worst case scenario, I would still be able to run it from the (new) motherboard's onboard SATA controller, right?
  13. Okay... I decided to test a few things first, but I cannot even find my Synology, so I cannot install it at all. What I tried so far. General information: Next I followed the available tutorial for installing DS918, so I did all the USB things correctly, like setting up USB VID en PID (double checked). I also looked up both MAC addresses for the onboad LAN ports (double checked). I also tried an older single port PCIe Intel NIC I had laying around (again made sure that I have the correct MAC address). I generated a new serial for DS916+, as there is no generator for the DS918 and after searching the forums, someone in the French section said to choose DS916+. So I did this (tried 3 different serials even). The only thing I did not understand completely was the "SataPortMap" setting, however I tried various things, along with setting it to 42. However since I am using one of the mentioned controllers and disabled all onboard SATA controllers, I think a setting of only "2" or "4" should have been sufficient for 2 / 4 harddisk, right? And I only have one controller (if I install the flashed Fujitsu or the flashed Supermicro card), right? Or am I wrong here? Now after doing all of the above steps (various times with different settings, serials and RAID cards) I still cannot find my synology (not through the webbrowser, nor through the Synology Assistent). No matter what I try. It just does not find it. And yes, the cable is connection and yes the MAC addresses were correctly written in grub.conf. I also tied an old PCIe Intel NIC card, but the same story. It simply refuses to see the Synology / NAS... I did notice something weird, when Jun's loader was running / loaded, my router said the Dell R410 did not have an IP assigned to it? Apparently, something is causing that Jun's loader is not fully initialized and as a result there is no network connection and therefor I cannot find and install Synology on the machine. Anyone has an idea? Maybe I overlooked something. Other information (I could find / gather) are below If you need more information and/or details, please ask. I hope someone has some advice. Maybe/probably I did something wrong...?
  14. Hi flyride, Thank you for your detailed information/answer. I have succesfully flashed the Supermicro HBA AOC-S3008L-L8e card to a "general" LSI 9300-8i following this tutorial. Unfortunately I cannot test it at the moment. But I will try next week, before I purchase all other hardware. Maybe I will succeed? Hopefully! * crossing fingers *
  15. Hi flyride! I checked your .xls file (many thanks for that) and I have a question. I noticed the following: Not the last line in bold, please. I am planning to do a new build, as described here. However I will be using a "Supermicro HBA AOC-S3008L-L8e" RAID controller card. This is based upon LSA SAS 3008 chipset (which is supported apparently according to your .xls). Will this work with DSM 6.2.1 and DS3615? I already asked for including the drivers here, however I understand now this is not possible anymore with DSM 6.2.1? Thanks in advance. Regards
  16. Anyone who can and is willing to give some advice? I want to place the order this week, so I can (re)build my new NAS. Thanks!
  17. Hi all, Is it possible to add drivers for the Supermicro HBA AOC-S3008L-L8e (which is based on the LSI 3008 chipset)...? I don't know if this is even needed, but just wondering. Information: https://www.supermicro.com/products/accessories/addon/AOC-S3008L-L8e.cfm Drivers: https://www.supermicro.com/wftp/driver/SAS/LSI/3008/Driver/ (FreeBSD, Linux, UEFI and Windows) Firmware: https://www.supermicro.com/wftp/driver/SAS/LSI/3008/Firmware/ (both IR / IT mode firmware; no need to x-flash) Would be great if these drivers could be added? For now and future use obviously. Seems not much of a hassle?
  18. Okay, I have finally decided on my final (new) NAS setup. In bold are the changes. - Motherboard: ASRock H370M Pro4 - CPU: Intel Pentium G5600 - RAM: G.Skill Aegis F4-2400C15D-16GIS (16GB is probably overkill?) - PSU: Seasonic Focus Gold 550W - Case: Fractal Design Node 804 - CPU cooling: Corsair Hydro H55 - Network: onboard or an older Intel 4-port PCIe adapter - RAID controller: Fujitsu D2607 LSI SAS2008 (flashed to IT-mode) - Storage: 4x SAS Hitachi HGST Ultrastar He8 6TB (HUH728060AL5200) in SHR As you can see with my previous lists the harddisks changed. I also finally flashed the purchased RAID controller to LSI firmware 9211-8i in IT-mode (20.00.07.00). Sidenote; if anyone is looking to flash a Fujitsu D2607 with stock LSI firmware, look here. Very good and detailed tutorial. I am using the 4x SAS Hitachi HGST Ultrastar He8 6TB as these enterprise SAS HDD's last longer (in my experience) compared to consumer grade HDD's. Also Hitachi (even nowadays owned by Western Digital) has an excellent track record in regards to reliability. I understand I could get SATA HDD's and connect them to the motherboard, but given the above reason along with future expansion / upgrades, I decided to use a RAID controller (in IT mode ofcourse). Now I do have a few questions. Question 1 Given the fact I am using a hardware RAID controller in IT-mode, will it still be able to read SMARTCTL information in XPEnology? So when a harddisk is having issues, it will report these issues? I think it does, but I am making sure. Question 2 My current setup is based on 4x 4TB Seagate IronWolf HDD's in RAID 10. I chose this option back then because of the performance. However with a SHR setup, will performance be still good or similar. I do understand that RAID 10 is normally faster, but for downloading, unpacking, copying and backup's, etc. SHR will be sufficient right? Question 3 My current (old) NAS setup has an Intel Core i3 4130 CPU. Compared to the newer Intel Pentium G5600, I will notice a bit of an increase right? Because of a slightly higher clock speed and newer technology? Question 4 I asked this before, but just making sure. Will the above combination (motherboard, CPU, RAID controller and SAS HDD's) work without issues in XPEnology? Sorry for all the questions, but I am just making sure everything will work and perform as expected. Thank you in advance! Regards
  19. Thank you for your input. Yes, I know it has 6x onboard SATA ports, however I want to be able to upgrade with more HDD's in the future when needed. Sorry for the confusion. Should have mentioned that.
  20. Hi all, It's been quite a while since I posted something here. Anyways, since my current XPEnology NAS is a bit outdated (and moreover lacking HDD storage space), I decided to do a completely new build. It's mainly used for storage and downloading (unpacking needs to be quick) movies, series, games, etc. I will also store all of our pictures (from phones, laptop, etc.) from now on on the NAS, because I will have more space available then before. Here is what I am planning to build: - Motherboard: ASRock H370M Pro4 - CPU: Intel Pentium G5600 - RAM: G.Skill Aegis F4-2400C15D-16GIS (16GB is probably overkill?) - PSU: Seasonic Focus Gold 550W - Case: Fractal Design Node 804 - CPU cooling: Corsair Hydro H55 - RAID controller (IT-mode): Fujitsu 9211-8i D2607 LSI SAS2008 - Network: onboard or an older Intel 4-port PCIe adapter - Storage: 4x Hitachi HGST Ultrastar He6 6TB in SHR mode My current setup consists out 4x 4TB HDD's in RAID 10. So I will ditch RAID 10 in favour for SHR mode. Way more space and still fast enough for most things, I guess (no experience with SHR though). Will the above work with DSM 6.x without issues? Any other recommendations, ideas, whatsoever? Thank you in advance!
  21. Thank you both chege and IG-88 for explaining... Guess I should have checked the forums a bit better before upgrading. Anyways, will give it a new go tomorrow (after I first disabled bond, lowered MTU and disabled Jumbo Frames). Hopefully it will succeed this time... And if I understood correctly; I can redo the settings to 9000 MTU, Jumbo Frames and bond, after I upgraded to DSM 6.0, right? ...or will it still cause issues? Thanks again!
  22. Okay... Some positive news. Changing the VERSION to an older DSM-version works. I could boot to the installation procedure, selected my old DSM_DS3615xs_5967.pat file. Then it started installing and I crossed my fingers... After a minute or 2 it rebooted. I checked the screen locally and it was updating the files. Now I can enter DSM GUI again and so far everything is still working! I went to network and checked the settings there. And it says: Bond 1 - Connected LAN 1 - 1000 Mbps, Full duplex, MTU 9000 LAN 2 -- (this one is still disconnected) LAN 3 -- (this one is still disconnected) Can it really be the MTU and/or Jumbo Frame setting which caused all the problems with DSM 6.0 GUI? I find that really weird...? It should still connect right (like Sabnzbd, Couchpotato and Sonarr do)? Or am I mistaken here...? Please explain if you can... I would appreciated it. Also if I would disable the BOND, 9000 MTU and Jumbo Frames... Will DSM 6.0 with Jun's loader work? ...or will it still not work? Thanks in advance!
  23. [spoiler=]Well I am now running the Ubuntu Live USB and I followed the commands as described on your other page. - sudo -i - apt-get install mdadm lvm2 I don't want to mount the data partition, so I skipped that step... - mdadm -Ee0.swap /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 - mdadm -AU byteorder /dev/md0 /dev/sda1 /dev/sdb1 dev/sdc1 /dev/sdd1 But I cannot seem to find my Xpenology system files, for example: /etc.defaults/synoinfo.conf And/or: /etc.defaults/VERSION Am I overlooking something here... Where should I look? I am sorry if I am asking stupid questions, but I hardly have any experience with Ubuntu in general. Never mind, I found it... Sorry I am stupid. Update: well I skimmed through the synoinfo.conf file, but there was no bondX in here, only ethX and all of them were at 1500. So that wasn't the problem. Therefor I will try to downgrade now back to 5.2. Hopefully it will work...
  24. Well no dice... What I did now: - created a completely fresh USB stick with Jun's loader 6.0.1 - followed all configuration steps to the letter - switched the driver string in grub.cfg - changed VID, PID and MAC - only used one MC - disabled the trunk/bond on switch - disconnected both ports on Intel PCIe card - selected 'Force Install'-option and installed the .PAT-file - auto rebooted normally and selected option 1 from loader Waited for 10 minutes. The only thing accesable are (once again) Sabnzbd, Sonarr and Couchpotato... ...DSM GUI is not reachable at all. So I am back to square one again. Sigh. I am gonna try to downgrade now. I am completely done with DSM 6.0 and wished I never did this update... //edit Before trying to downgrade, I will run the Ubuntu Live USB stick and check the files as well.
×
×
  • Create New...