djvas335
-
Posts
161 -
Joined
-
Last visited
-
Days Won
2
Posts posted by djvas335
-
-
Thanks for replying, I checked the link however I did not find the relevant information, can you please point the relevant section ?
What I need is to add some options to the mlx4_core driver like this, I am not sure how to do this, is this to be done at loader creation ? Or this can be done directly from DSM ?
options mlx4_core roce_mode=2
5 hours ago, Peter Suh said: -
Hi, Peter, how can we pass parameters for kernel modules, I tried using modprobe.d however this did not work, I need to set some parameters for mlx4_core driver to be applied at boottime
-
Hi guys, sorry for hijacking the thread, but can this be built for microserver gen10+ with ilo5 ? Thanks in advance
On 6/10/2023 at 9:46 AM, armanism said:ams for DSM 7.2 ds3622xs+
-
Наверное просто плохая или не подходящая память
37 minutes ago, level001 said:Подскажите при добавлении памяти надо переконфигурировать arpl ?
Ставлю 2 планки по 4 уходит в перезагрузку при загрузке dsm 7.1 , биос ее видит.
Ставлю старые планки 2+1 всё нормально грузится.
Просто новый arpl 1 хочет больше 4 памяти. И он тоже 4+4 не грузит dsm.
1+2 ecc 4+4 non ecc.
-
If you are using tcrp, then you need to choose friend, so that friend can update your setup when you change firmware and leave it on that boot option
On 6/27/2023 at 8:59 PM, TemplarB said:Update. I've decided to go cardinally and after saving last User_config.json and checking it (unsure why but it lacked e.g. serial number and had a different vid/pid even despite I haven't moved sd-card) and run all commands from this tutorial:
Namely:
./rploader.sh clean ./rploader.sh update ./rploader.sh fullupgrade ./rploader.sh identifyusb ./rploader.sh serialgen DS3622xs+ ./rploader.sh satamap ./rploader.sh build ds3622xsp-7.2.0-64570
While I haven't specified "withfriend" it added it at the end according to thhe log.
I rebooted and chose in GRUB last option (something with friend) It worked to the final message ("loading kexec...") no errors
I opened Synology Assistant and it found the "recoverable" (no surprises, I rebuilt with new serial, so it is new). It has only one option "recover" I pressed it, it says "installing DSM" quickly goes from 0 to 100% and writes "restarting in 10:00" and counts down. Meanwhile the server reboots and I choose 1st option in GRUB (load USB, Verbose)
it shows that "booting the kernel." like usual. However
Synology Assistant does NOT initially sees it and later goes back to option "recover"
- 1
-
Just friend, with friend no postupdate necessary
9 hours ago, freddie said:hello I've Already do that, you say to install and after install running from TC friend ? with postupdate or not, so I'll try this and tell if it work or not
-
18 minutes ago, freddie said:
It's an HP Pro 3500 séries Intel i3-2xxx <= IDK the number, but it's still working with the update 0, but I downloaded the update 1 :
synology_broadwellnk_3622xs+.pat. Tue, 13 Jun 2023 14:26:42 GMT. 24.16MB. on archive Synology and After the update with this file my NAS doesn't work.
-
You need to run friend once or do a postupdate from tinycore
-
What is your hardware ?
1 hour ago, freddie said:Hello I have latest 0.9.4.9c on github with New install on USB stick with empty SSD and it doesn't work
I try this morning and it won't work I don't know what to do ? If anyone have a solution pour welcome !
-
Please clarify issue you need help with
2 hours ago, linhvk said:Please help how to solve this issue?
-
I had an issue like this, building fresh latest loader seems to have fixed it
30 minutes ago, freddie said:hello, I do run ./rploader.sh postupdate ds3622xsp-7.2.0-64570 and he found the U1, I agreed twice and when i restart with usb boot, nothing always recuperable (recovery) and now telnet services activated for diagnostics !! where i do wrong ??
and booting with TCRP friend my ip changed and my card network doesn't working !
-
Yepp also baremetal Microserver Gen8
4 minutes ago, eDonkey said:The same here on BareMetal HP Micro G8.
-
I had same message after upgrade, however my system just booted up with no issue
On 6/27/2023 at 9:28 AM, Biocef said: -
-
Please also note the systems are different, storage3 is a microserver gen10 Plus and storage7 is microserver gen8, you can see that mlx4 is not running at full pciex speed on storage7 because of cpu bus limitation.
3 minutes ago, Peter Suh said:Using the vanilla mlx_compat.ko was effective in getting rid of the noise, but the loading of mlx4_ib.ko seems to be missing. In addition, the log indicates that the speed is also reduced without the loading of this module.
After figuring out the characteristics of this module file a little more, let's find out how. -
I removed mlx4_core.ko and mlx4_en.ko
4 minutes ago, Peter Suh said:Specifically which ko files did you remove to remove the mlx4 module?
-
storage3 is a system where I removed mlx4 from all-modules so its using internal DSM driver, storage7 is running mshell with no changes
7 minutes ago, Peter Suh said:How did storage3 load the module?
-
However something is still missing, please see screenshot from system running without mlx4 in all-modules, please note the part with mlx4_ib, its missing from screenshot from storage7
30 minutes ago, Peter Suh said: -
-
Update to a latest version of the loader, clean the loader and build the loader again, better do it from scratch, after that just go to the new IP and do a recover system, the friend will update the bootloader and the system should boot normally, if it asks to install new dsm, latest loader is dsm7.2.0 update 1 so you will have to download and update your system after latest loader rebuild
- 1
-
I will test later today, I need to build an additional system for testing as other systems are running in production as of now, also please note that mshell build requires partition size expansion as default partition size of tcrp is not sufficient for the mshell to build the loader.
2 hours ago, Peter Suh said:There is one thing different from the last test with you.
The link below is a place where vanilla modules related to mlx4 are kept.
https://github.com/PeterSuh-Q3/arpl-modules/tree/main/vanilla/broadwellnk-4.4.302In addition to mlx4_en.ko and mlx4_core.ko , we have confirmed that mlx_compat.ko has additional dependencies.
Have you tried the added version as a vanilla module up to mlx_compat.ko with MSHELL?
Could you please confirm that this test also shows the logs you are concerned about? -
But I do not want to exclude the module mlx4 from loading in DSM, I want that the mlx4 module included in all-modules in the loader do not load so that the module included in DSM loads, the mlx4 included in the all-modules does not work and crashes my system when I access after the system started up. So what I want is for the vanilla mlx4 driver in DSM take over from the mlx4 included in the all-modules pack.
7 hours ago, pocopico said:Since we are using gnu tar to extract the modules at boot or at loader creation the exclusion of some modules is not a very difficult task.If you want to specify a module to be excluded from DSM you can add modprobe.blacklist=mlx4 at your linux command line.
I will include that in the next release of the HTML Builder.
How we identify the module that actually cause KPs is the most difficult part cause you have to read the KP message.
-
Actually I did give feedback that modules worked but there was some log noise before driver load if you remember we had a conversation on that, I now built the new loader using HTML builder and had issues again with the mlx4 driver thus my forum message, I overcame this for now by removing the mlx4 driver from the tgz and copying the rebuilt tgz via scp to its final location after the loader is built and rebuilding the loader again.
13 hours ago, Peter Suh said:Currently, this mlx4 has been removed from the DDSML method of MSHELL for TCRP.
In this removed state, the built-in modules (vanilla modules) already included in DSM are used instead.It has already been reflected in M SHELL by yourrequest a while ago, What other problems are there?
I didn't have your last feedback, so I asked another user with the same nic to test it. There was nothing wrong with his feedback.
In addition, if the user wants to exclude modules with additional issues,
I am considering using modprobe.blacklist in MSHELL's DDSML method using modprobe.
-
Please can something be done with modules which crash system on startup when affected hardware is present ? The all-modules is creating issues each time the loader is recreated, is there an option to remove drivers which cause problems from it ? For me I need to remove the mlx4 driver as it crashes my system on startup. Any suggestions for this ?
- 1
Network no longer reachable after update
in General Installation Questions/Discussions (non-hardware specific)
Posted
The address which appears there is not the same address that the DSM will have, just run synology assistant to find which is the ip address being acquired by the DSM