kociubin
-
Posts
26 -
Joined
-
Last visited
Posts posted by kociubin
-
-
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?
-
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
-
2
-
-
On 10/17/2022 at 12:03 PM, Dreadnought said:
I have a valid SN for DS3622xs+ too which is offically working within the synology account but ARPL is complaining that this SN is invalid too.
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.
-
On 10/15/2022 at 3:19 PM, mcdull said:
Thanks for your information, but I have the same mac and sn when mirgating from a working DSM 7 of TinyCore RedPill Loader. I am also using Proxmox as well, should I start up another vm and put back all hdd?
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.
-
18 hours ago, mcdull said:
May I have a quick question? is this loader blocking quickconnect or transcoding service?
I have a valid serial number and mac under vm but cannot get either to work. with the TinyCore RedPill Loader I have no such issue. Thanks.
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.
-
2 hours ago, rcached said:
Drives seem to run a bit hot (in the 40s) but that is likely due to the case design, and nothing a hardware mod cannot fix.
Install fancontrol to improve your temps. Go back a few pages in this thread for instructions.
-
55 minutes ago, kociubin said:
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.
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.
-
1
-
-
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.
-
5 minutes ago, Nunyafb Izness said:
In a word YES I have been working on what i did and exactly how so even NOOBS such as myself can do it. If you want I can pm you my rough notes and you can send me questions while I finish cleaning up my notes. This includes installing the fancontrol.
I will attempt it today. It would be great if you could post your notes here for everyone to see.
-
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.
-
1 hour ago, richv31 said:
OK, this is what I did to get the terramaster nas running on 6.2.2. This is for a fresh install only. It may work for an upgrade but I have not tried it. Create a usb drive with 1.04b (setup your VID/PID, serial, mac, etc). Then download the extra.lzma that real3x created (that excludes the updated graphics driver modules that Jun included in 1.04b) and replace the one in the second partition on the usb drive with it. DO NOT delete the extra2.lzma from the USB drive as others have suggested. If you do, the system will not boot for install. Plug the usb, boot the system with a clean HDD (e.g. no synology partitions exist) and install the 6.2.2 update 4 pat file. I have this running on Terramaster F2-220, F4-220 and a qnap-453be. I recall reading somewhere in the tutorials that the J1800/J1900 cpus do not work with the updated i915 drivers )in 1.04b) for 918 installs.
Finally, if you attempt to use the vanilla 1.04b on these machines, they will boot up fine for install, but once the install is completed they will disappear from the network. seemingly the issue is with the updated graphics driver that causes issues in loading the realtek network driver.
I am waiting to try IG-88s new drivers but for the moment the above is working for me.
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.
-
3 hours ago, IG-88 said:
what was not working?
918+?
there are differences in the kernel of 6.2.2 that make most of the additional drivers useless
when updating to 6.2.2 it needs a new extra.lzma with new drivers (or hardware that is supported by dsm by default)
for 3615/17 it was released mid december, for 918+ is a new version nearly ready, not perfect but better then the one already available, intel and realtek nic drivers in recent version
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.
-
On 12/28/2019 at 12:45 PM, richv31 said:
yeah, I have 6.2.2-24922-4, clean install, /dev/dri present
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
-
10 hours ago, richv31 said:
I have 918+ 6.2.2 update 4 running smoothly on this NAS. I used the fancontrol binary from kociubin's post above, setup as a boot task and it's all performing as expected. Thx
Can you confirm which version you successfully upgraded to? Was it 6.2.2-24922-4 ? Any issues booting or issues with ethernet?
Thanks
-
2 hours ago, tdse13 said:
Thank you. Your program is working but I cannot experience any decrease in temperature. My setup is for 3615xs with the v1.02b loader.
Docker is not a problem. It is running on my Terramaster F2-220 without problems. However, I do not have any idea about compiling. I am able to install the gcc container but I would need some instruction on how to build the program.
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.
-
5 hours ago, tdse13 said:
Thank you for your support. Unfortunately, Compuman's versions in posts 65 and 66 do not work for me: -ash: ./fancontrol: No such file or directory
I have never compiled anything myself. Could you please give me a hint or a link for a guide. Thank you.
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.
-
1 hour ago, tdse13 said:
Neither ./fancontrol 1 1 37 255 nor ./fancontrol 1 0 30 255 produce any output at all.
1) How did you compile the binary? I did not compile it at all but used the file "fancontrol"
2) Are you running it as root? Make sure you are. Yes, as root
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>
In my version I do not see the option <test_temp>
Usage:
fancontrol
fancontrol <debug> <setpoint> <pwminit> <interval> <overheat> <pwmmin> <kp> <ki> <imax> <kd>
Arguments must be specified in order. Arguments that are not
specified will take their default value.
debug Enable (1) or disable (0) debug logs (default: 0)
setpoint Target maximum hard drive operating temperature in
degrees Celsius (default: 37)
pwminit Initial PWM value to write (default: 128)
interval How often we poll for temperatures in seconds (default: 10)
overheat Overheat temperature threshold in degrees Celsius above
which we drive the fans at maximum speed (default: 50)
pwmmin Never drive the fans below this PWM value (default: 80)
kp Proportional coefficient (default: 1.0)
ki Integral coefficient (default: 0.0)
imax Maximum integral value (default: 10.0)
kd Derivative coefficient (default: 0.0)
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++.
-
53 minutes ago, tdse13 said:
Thank you. I get the following output:
maxtemp = 46, error = -209.000000, pout = -209.000000, iout = 0.000000, dout = -0.000000, pwmtemp = 80.000000, pwm = 80
maxtemp = 46, error = -209.000000, pout = -209.000000, iout = 0.000000, dout = 0.000000, pwmtemp = 80.000000, pwm = 80
maxtemp = 46, error = -209.000000, pout = -209.000000, iout = 0.000000, dout = 0.000000, pwmtemp = 80.000000, pwm = 80
maxtemp = 47, error = -208.000000, pout = -208.000000, iout = 0.000000, dout = 0.000000, pwmtemp = 80.000000, pwm = 80
And I cannot hear any difference in the speed of the fan.The temperature reading corresponds to second hard drive.
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 = 80Few 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
-
6 hours ago, tdse13 said:
Thank you for your reply. Unfortunately, the program does not work. ./fancontrol -h shows the options, ./fancontrol starts but nothing happens. Only ctrl. -x returns to the prompt. Any idea what is wrong on my side? Thank you.
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.
-
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.
-
On 6/10/2019 at 3:19 AM, compuman said:
I found a method to use "free space on internal USB stick" like DataStore without change the USB policy, so with ONE solution I solve two problem:
-external USB stick on USB2 port no more needed
-external USB HDD on USB3 port works in VM XPEnology like always (share by default like usbshare1 and usbshare2)
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.
-
On 8/16/2018 at 2:41 PM, ZerOneX said:
Guys, quick question for the ones that has the cable....
It is possible, through a BIOS setup, to change the USB port to boot the pendrive with the bootloader?
Yes. You can pick which USB or IDE drive to boot from.
-
1
-
-
1 hour ago, compuman said:
this link not work for me
Try this:
-
3 hours ago, compuman said:
so we need the VGA cable?
i found someone with 12p female -> 15p vga female
some other 12p male -> 15p vga female
what one is the correct one
can someone link a "correct one" to buy?
Try this one:
Automated RedPill Loader (ARPL)
in Loaders
Posted
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!!