djvas335
-
Posts
161 -
Joined
-
Last visited
-
Days Won
2
Posts posted by djvas335
-
-
Then just leave iommu disabled and issue solved
-
The best way if you have access to your data is backup your data and then recreate the raid and volume, do not play with it, you can have bad consequences.
-
Can you post your user_config.json after loader build ?
-
How is your controller setup in bios ? AHCI Mode ?
-
This is because of new all-modules integration where the problematic mlx4 driver is now bundled, I had to build my own all-modules to overcome this issue for my systems, I run connect-x3 40gb
3 hours ago, crurer said:Hi,
I'll report a BUG in rev. 0.9.4.9b when using tinycore-redpill-uefi.v0.9.4.9.img with DSM 7.1.1-42962 Update 1 running as DS3615xs. Same behaiving when I've tried another model i.e. 3622xs+.
I'm using a FSC D3222-B1x Mainboard with I5-4460 + 16GB RAM. 8x 4TB WD red + LSI 9211-4i IT mode. As soon I connect a Mellanox ConnectX-3 10GB FC to one of the PCIe slots the system is shutting down (no reboot) when the system load seems finished to access the webui.
I can confirm with older rev. i.e. 0.9.3.x the system is running fine as expected. It really costs me some time to analyze the issue.
cheers Chris
-
I have below error when trying to build latest loader and DSM
[#] Verifying /home/tc/redpill-load/custom/extensions/disks/ds3622xsp_64570/install.sh file... [ERR]
[!] Checksum mismatch - expected 63d8722edb9c5f7cb7160bead82e2909bb977a1aad96dff74f39629fde03c3bf but computed d1f4003ea029a2f44db3c105e04f245a87e6c0d0b1685ff237d2278b55e43481*** Process will exit ***
-
1
-
-
Just use below steps with latest loader version
./rploader.sh update now
./rploader.sh fullupgrade now
./rploader.sh serialgen DS3622xs+
./rploader.sh identifyusb now
./rploader.sh satamap now - pay attention, here you need to answer "yes" twice
./rploader.sh build ds3622xsp-7.2.0-64570
On 6/18/2023 at 8:08 PM, s3urat said:How?
I can't get anything past a fairly old TCRP version working on my Microserver Gen10. It just doesn't detect any disks connected to the Marvell controller.
-
Actually DSM 7.2 final was released on 22 May 2023, I am running it on several servers with latest loader, did not see any stability issues.
-
1
-
-
Latest tinycore with dsm 7.2 ds3622xs works with no issues on microserver gen7, gen8, gen10 and gen10 plus, I have tested those myself.
-
1
-
-
I am running it on several n40l and on n54l with no issues, disable c1 in bios and do not use friend option to boot
-
3 hours ago, ozef said:
Hello,
when you say go through web interface, you mean there is like arpl a web access on TCRP ? If so can you provide the url with the port please ?
Just load the tinycore and go to it's dhcp address no custom port necessary
-
10 minutes ago, Peter Suh said:
By any chance, what physical error does that log message cause?
After that message, it seems that mlx4_core has entered the normal loading phase?I did not see any issues with this for now, just trying to avoid possible issues that can creep up in the future
-
1 hour ago, Peter Suh said:
thanks for the test
Integration module pack of mellanox mlx4 (probably connectX-3) will keep the status quo including vanilla modules (mlx4_core.ko, mlx4_en.ko).
I expected it to initialize and load itself in Junior mode, but it's a pity.I think I will buy mellanox connectX-3 in the near future.
After that point, I'll try to see if more fine-tuning or testing is possible.
Yesterday, I confirmed several platforms that I already have, the Intel X540-T2 (ixgbe) should work as a vanilla module.
(broadwell, broadwellnk, v1000, epyc7002, etc.)Thanks to you, it gave me an opportunity to further research the need for vanilla modules in XPE.
Have a nice day.
As it's not working in junior mode can I ask that you please keep the mlx4 module out of the all-modules integration pack for now ? You can add it later when it will be working better. The reason I am asking for this are those errors in dmesg about unknown symbol backport dependency.
-
2 hours ago, Peter Suh said:
keep igb active(It would be good to unplug the igb nic cable.),
Instead, please confirm that mlx4 is given an IP on Synology Assist and operates. After that, please check dmesg one more time in the same way.I did the test, I erased the hdd's to also be able to make an install test and recompiled the loader, unplugged igb and rebooted the server, after reboot during the install phase, the mellanox card did not initialize, ie no lights on the cards, no system in synology assistant, replugged igb and installed DSM via igb, system started without issue and Mellanox card is available however there is someting about unknown symbol backport in dmesg, attached below.
-
1
-
-
1 hour ago, Peter Suh said:
If you can, may I ask you to take one last test?
As mentioned, I ported mlx4's vanilla driver to the all-modules integration pack, replacing the compiled module.
What is shown in the capture is not the DS3622xs+ with DSM installed
This is /lib/modules of Junior level before DSM installation.
The files you checked with me in DSM will be confirmed.
You only need to build 7.2-64561 one more time from the M SHELL menu without any manipulation.
It would be best to turn off the igb nic,
Can you test the DSM installation process with the IP address given to mlx4?Sure, I can test, however I can't disable the IGB because of the particularities of my setup, ie I can't access mellanox nic directly because it's on another network switch which I do not have direct access to and is only used for the storage network, please tell me if you still want me to do the test without disabling the igb nic
-
5 minutes ago, Peter Suh said:
This content alone is sufficient.
Your prediction was correct. Congratulations.
A second case was identified where a vanilla module was sufficient for a 10G NIC.
Intel ixgbe was the same case.
ARPL fabio's method used the method of copying the vanilla driver as it is and including it as a module of XPE.
In the case of mlx4, it seems that the same method should be used.
That way, you can install DSM with just mlx4 without the help of additional modules like igb.
I will spread it to redfill developers and fix the module.
thank youThank you very much for your time and support, I really appreciate this
-
1
-
-
21 minutes ago, Peter Suh said:
Removed mlx4_core.ko and mlx4_en.ko, the way you initially wanted, from the all-modules integration pack as shown below.
Please remove the # comment in my.sh LINE 293 as it was.
custom_config.json will be automatically restored in the same way that it refers to all-modules as before.If the log shows that you deleted all-modules , that's OK.
It will probably be the last try.
Please test.Success, the system started up and working properly, below screen with dmesg with correct driver, do you maybe need some additional information ?
-
1
-
-
4 minutes ago, Peter Suh said:
The explanation isn't clear.
The igb I added worked, but can this mean that mlx4 is showing the same message as the capture from dmesg?Let me explain better, I added your igb entry on line 2490 and rebuilt the loader, after restart the system shows as not installed, I even tried to upload the dsm installation file and after reboot it still shows as not installed in Synology Assistant
-
50 minutes ago, Peter Suh said:
We prepared igb.ko for use with DS3622xs+.
to LINE 4290 in custom_config.json like below
Please add this again.
"PeterSuh-Q3.igb": "https://raw.githubusercontent.com/PeterSuh-Q3/rp-ext/master/igb/rpext-index.json",
Rebuilding the loader is OK if you see the message below in the log.
I followed your instructions and got a corresponding entry in the log however my device still shows as not installed, I added the entry on line 2490 by the way
-
27 minutes ago, Peter Suh said:
Since igb already has vanilla modules, it seems to work without installing all-modules like my T1700.
As in the caption below
Comment out LINE 293 of my.sh with #.
Delete LINE 2490 in custom_config.json.
Can this be done with the vi editor?Modification to persist modified custom_config.json .
Once you have finished editing, build DS3622xs+ 7.2 again from the menu.Determination of whether the all-modules integration pack has been correctly removed is successful if only misc and nvme-cache are mentioned in the Removing model exts directories at the end of the loader's build log as shown below and all-modules are not present.
There is nothing to delete because it has never been added.
I have changed the files according to instructions and rebuilt the loader, however after the restart the system is now listed as not installed in Synology Assistant
-
3 hours ago, Peter Suh said:
That's too bad.
Then it's time to remove all-modules pack and test with only the vanilla modules you want.
But there are many things to prepare.
I will explain in advance because it would be good to increase your understanding of the vanilla driver (module) and proceed with this task.
I heard @wjz304's opinion about using the vanilla module alone, but the lack of compatibility makes it less likely that many devices will be supported.
This part is helped by the modified XPE module.
First, I completely removed all-modules, an integrated module pack of TCRP, and applied it to my DELL T1700 with only vanilla modules.Fortunately, in my case, the built-in e1000e and the separate e1000e are dually installed, and both work within the vanilla module.
I don't have a Mellanox nic, but I have it in place to verify vanilla status.
It looks like you already have another nic installed besides the mlx4, don't you?
Let's check in advance which nic is prepared with which PID/VID with the command below.
Please let me know the result.
lspci -vnn | grep 0200]
lspci -v | grep KernelYes I have igb, please see below screen
-
7 hours ago, Peter Suh said:
First, we removed mlx4_en.ko, which is a problem with the first test.
Distribution of the removed integration module pack is complete.
https://github.com/PeterSuh-Q3/arpl-modules/releases/tag/v1.2
Build DS3622xs+ 7.2-64561 from the M SHELL menu.
M SHELL does not recommend the command method.
Your menu interface should look like below.
In the menu, if EUDEV is selected first, switch to DDSML.
If you use it in your already built TCRP, user_config.json is referenced as it is.
There is nothing to modify on the menu, just proceed with the DS3622xs+ 7.2-64561 build.
If the problem persists in this process, we will prepare for the second test by removing mlx4_core.ko.
Instead, a separate NIC is required.I have managed to build a loader using M Shell, same issue please see below screens
-
8 minutes ago, pocopico said:
Download latest release and use the TCRP Web builder
I need to use mshell we are trying to diagnose an issue with the mlx4 driver
-
I am having diffculty compiling the loader using mshell, I am getting this error
Mounting /dev/sdb1 to localdiskp1
/dev/sdb2 localdiskp2
cp: error writing 'localdiskp1/zImage': No space left on device
Modify Jot Menu entry
I also see that my partition table is different than yours, my sdx1 is smaller than yours, I am using latest tcrp image version tinycore-redpill-uefi.v0.9.4.6.img, can you maybe point to an image with correct partition layout please ?
Is there a list of supported 8/9/10/11/12 Gen Motherboards for DSM 7.x?
in DSM 7.x
Posted
If you can, use a microserver gen10 plus, its stable and no issues