yanjun

open it just run this command. echo 1 > /run/synostorage/disks/nvme0n1/m2_pool_support echo 1 > /run/synostorage/disks/nvme0n1/m2_pool_support

Actually, I have been testing SA6400 for a long time, and the initial version didn't encounter many problems until I tried to migrate my main machine to SA6400. The current issue I am facing is that when I use a combination of HBA card and SAS expander, the loading process of mpt3sas causes kernel magic. I don't have many clues to solve this problem.

https://github.com/PeterSuh-Q3/rp-ext/raw/main/nvme-cache/src/nvme-cache.sh maybe this ?

Everyone knows that the DS923+ model supports using nvme hard drives as storage pools. By comparing synoinfo.conf, I found that this option is the key to enabling this feature. support_m2_pool="yes" I used sa6400 for testing, I can indeed see the nvme hard disk in the hard disk list, but when I try to add him as a storage pool, I encountered an annoying compatibility reminder, as shown below, I also Try to turn off the hard disk compatibility option through the following configuration, support_disk_compatibility="no" I also added the model and compatibility support of my corresponding hard drive to almost all files in the /var/lib/disk-compatibility directory, but the page still has a compatibility report, anyone have any better suggestions?

@fbelavenutoIs there a plan to list EPYC7002 as beta in arpl, are there any obstacles currently encountered

Where can I see this information, for example, Synology introduced epyc7002?

As far as I know, currently this model has not received the rule that it cannot develop loader. As you can see, FS6400 and 920 need the dtb file to describe the location information of the hard disk, but his dtb file has more complex information besides the hard disk. information. I tried for a long time and it didn't solve the problem. I am posting the dts file, you can try to see if you can solve it yourself based on the information in this thread. FS6400.dts

@Orphée If you have time, can you take a look at the private message?

https://github.com/jumkey/redpill-load/commit/f77ece8c33ff51d1ba11cbb8eb7de0a6269aabe6 this commit shoud fix sata boot issue.

The information you provided is too little, can you give your own environment, bare metal or virtual machine, usb or sata dom?

In fact, using sn/mac is not an os hack. We're just trying to put the right value in the right place.

Because I'm trying to solve the problem, jumkey and I have figured out how to authorize advanced media extentions for DS3622xs+ in version 7.1 before raising the need for SN/MAC. Because there is currently no valid DVA3221 SN/MAC combination. So we can't test. My purpose is to make the experience of the dsm loader closer to the original genuine Synology. Don't quite understand what problem your proposed solution really solves?

I don't mean to argue. After DSM7.1, the installation of Advanced Media Extensions has affected the normal use of DSM. I understand that the previous SN/MAC sales are not in line with the purpose of the forum. I also happily accept that my post has been migrated for violating the old rules. But if the current forum rules for DSM Serial Number should be updated after 5 years as circumstances change is a question.

It's not surprising that many people leak some real SN/MAC for reasons such as posting their own review videos. It is normal for other people to see these SN/MAC sharing.

Hello everyone, after the 7.1 version update, the real SN and MAC seems to be a mandatory configuration, because Advanced Media Extensions 2.0 needs to be verified before it can be installed. So I specially opened a post to ask everyone to share the real SN and MAC (without affecting everyone's own use). Especially models after 19 years, including but not limited to: DS3622xs+, DVA3221.