Jump to content
XPEnology Community

kociubin

Member
  • Posts

    26
  • Joined

  • Last visited

Everything posted by kociubin

  1. For what it's worth, I was able to upgrade from ARPL v1.1-beta2a running DSM 7.1 to arpl-i18l running 7.2-64561. It was surprisingly painless. I followed the instructions below to "Switch between versions of arpl (manually, full) (Any version)" https://github.com/wjz304/arpl-i18n/blob/main/guide.md This installed the latest arpl-i18l and allowed me to install 7.2-64561. The only issue I had was that for some reason the DSM install didn't want to accept my downloaded "DSM_DS3622xs+_64561.pat" and I had to tell it to download the latest from Synology (which worked). I'm using: DS3622xs+ Nice work wjz304!!
  2. Is it bad to enable all of the modules? Will it negatively affect performance or uptime? The reason why I ask... I had some issues with recent upgrades where USB drive stopped working. I tried to enable relevant modules but it was getting time-consuming and ineffective. Then I enabled all modules and everything seems to work fine now. Is this a bad idea?
  3. I successfully upgraded my ProxMox installation to Beta2. I simply replaced the existing boot drive with the beta2 image. I booted it up. Re-configured using the same parameters as before. I then rebooted the whole VM and it booted right into DSM (i.e. no migration or repair needed). Everything worked flawlessly first time around. Thank you
  4. Same thing with me. When I tried to add the Serial Number using a menu item ARPL would complain that it's invalid. I had to manually put the SN/MAC in the config file. Everything worked this way.
  5. This is what I did. I created another new ProxMox VM with real Serial Number/MAC. I then imported the configuration from my old VM. My setup was pretty simple so it didn't take more than 15 minutes. It's worth a shot. It worked for me.
  6. FWIW, I also have a real serial and mac. I'm able to use quickconnect just fine. My goal was to get email notifications working. I intially started out with an auto-generated serial number/mac. This was on a working system. I then changed the SN/MAC to a real one. But no matter what I tried notifications just wouldn't work. So I started over and recreated my NAS using a real SN/MAC, re-imported settings and only then notifications started to work. I'm running ProxMox so this was pretty easy to do. It might be worth a shot. I think you need a real SN/MAC configured in the loader when the DSM boots up for the first time. This was certainly needed in my case to get notifications working.
  7. Install fancontrol to improve your temps. Go back a few pages in this thread for instructions.
  8. I was able to get transcoding to work. I used v0.13.3 extras from this thread: "Driver extension jun 1.03b/1.04b for DSM6.2.3 for 918+ / 3615xs / 3617xs" Everything works now including hardware transcoding inside plex.
  9. I decided to just pull the trigger and apply the upgrade to 6.2.3. I was able to upgrade directly from "DSM 6.2.1-23824 Update 6" to: 6.2.3-25426. I didn't have to do any additional tweaks. I simply upgraded from the UI and 10 minutes later my NAS was back up and running 6.2.3. Everything appears to work OK so far. I noticed that I lost hardware transcoding (i.e. no /dev/dri device) but I don't care.
  10. I will attempt it today. It would be great if you could post your notes here for everyone to see.
  11. Has anyone tried the latest 6.2.3-25426 with our F4-220? As per some other threads support for the Realtek r8168 chip should be included so it may just work out of the box.
  12. Thanks for clarifying. I did a "vanilla" upgrade (did not use a different extra2.lzma). I might give this another shot but for now I'm waiting for the rebuild/repair to finish. It's taking forever.
  13. With 6.2.2 my NAS would attempt to startup and then promptly stop working with a black screen. I could not connect to the web GUI nor ping it. I don't know if the whole system was crashing or if it was only the ethernet that would stop working.
  14. For the benefit of others who might try upgrading to 6.2.2-24922-4.... DON'T. It bricked my system and I spent 5 hours recovering. The raid is still repairing. I went back to 6.2.1-23824
  15. Can you confirm which version you successfully upgraded to? Was it 6.2.2-24922-4 ? Any issues booting or issues with ethernet? Thanks
  16. What do you mean by "program is working?" Can you hear the fan speed changing? If that's the case then you will probably need to experiment more with the parameters.
  17. You can try the one I compiled for DS918+, Loader: 1.04b, DSM 6.2.1-23824 Update 6. See attached. If it doesn't work, your best bet is to research how to use docker with Synology. Then you would download a docker image with g++ and use that to compile the source code. There are some hints in this thread of how to compile it but learning docker is a pretty big topic. You'll need to research that on your own. fancontrol
  18. Look at Compuman's posts 65 and 66 in this thread. He created another version of fan control with an additional <test_temp> parameter. Give that version a try. If it's still not working then I suggest you build your own binary using a Docker image with G++.
  19. The binary may be working for you... Here is what my output looks like. I know it's working for me because I can hear the fan changing speeds. ./fancontrol 1 1 37 255 maxtemp = 39, error = -216.000000, pout = -216.000000, iout = 0.000000, dout = -0.000000, pwmtemp = 80.000000, pwm = 80 maxtemp = 38, error = -217.000000, pout = -217.000000, iout = 0.000000, dout = -0.000000, pwmtemp = 80.000000, pwm = 80 maxtemp = 37, error = -218.000000, pout = -218.000000, iout = 0.000000, dout = -0.000000, pwmtemp = 80.000000, pwm = 80 Few questions: 1) How did you compile the binary? 2) Are you running it as root? Make sure you are. 3) Check your parameters. <test_temp> determines if you're monitoring the CPU or DISKs. <debug> <test_temp> <pwminit> <setpoint> <interval> <overheat> <pwmmin> <kp> <ki> <imax> <kd> If you want to monitor disks, try this and listen to the fan: ./fancontrol 1 0 30 255
  20. Try turning the debug flag on. You should see some output after a few seconds.. For example: fancontrol 1 37 255 Also, with the above command, you should hear the fan start up at high RPM when you run the command.
  21. For those thinking of using this Terramaster box with VMware ESXi, my advice is DON'T WASTE YOUR TIME. There are too many issues and the setup is not robust enough even for home use. Here are some serious issues: Hardware pass-through for disks is not fully working. This means that even if you get the drives to show up in Synology (this requires some command line hackery), S.M.A.R.T. info will not be readable by synology. This is a critical warning system that's too important to give up (IMHO) I couldn't get all 4 of my drives to show up in Synology. No matter what I tried only 3 of them were accessible. Booting ESXi 6.7 from a USB stick resulted in various settings to be lost after a reboot. I was able to work around it by installing ESXi on a real SSD drive but that sacrifices one of your slots. There is a 10-20% performance hit in reading/writing from disks After spending about 10 hours on this, I'm going back to bare metal. Although this sounded like a good idea, it's not workable for me in practice.
  22. This is very cool. 1) Can you share more details for how to use the "free space on internal USB stick" ? 2) Have you been able to improve the read/write performance of your setup? This is the only reason why I'm hesitating to do this.
  23. Yes. You can pick which USB or IDE drive to boot from.
  24. Try this: https://www.aliexpress.com/item/12P-to-15P-VGA-Female-D-Sub-Adapter-12Pin-15Pin-VGA-connector-length-150mm-short-cable/32808546166.html
  25. Try this one: https://www.aliexpress.com/snapshot/0.html?spm=a2g0s.9042647.0.0.623c4c4dpI7kWO&amp;orderId=93461400283237&amp;productId=32808546166
×
×
  • Create New...