NVME question

[lev22885]

Good evening. My server with characteristics: huananzhi qd4 + xeon e5 2690v3 + 32 gb RAM samsung ecc reg + ST6000VX001 + SSD M2 970 evo plus (250 gb) (I use it for various databases and sites). At the moment I sit on proxmox and virtualize your modified bootloader with DSM through proxmox. I remember that in the middle of May I tried to boot M2 with your bootloader, but it was not visible in the system (that's when I decided to switch to proxmox). How are things now? Will the M2 work now? (I could check it myself, but I'd have to make so many backups....). Thanks for further help. 

 

// Addendum to a personal conversation @mark

 

Thank you for your response! In the post I meant to use the m2 as a cache or a full disk. I also remembered that thanks to this video - " https://www.youtube.com/watch?v=ECXDjXN4E_I&t=613s " I was able to make M2 work, kind of like on your bootloader on bare hardware without virtual machines (but with failures after DSM reboot).

 

[Peter Suh]

How will DSM work if M.2 is removed?

Is the TCRP FRIEND kernel being used?

[lev22885]

4 минуты назад, Peter Suh сказал:

How will DSM work if M.2 is removed?

Is the TCRP FRIEND kernel being used?

I don't understand the first question a little bit

 

And as for the TCRP friend, I'm using

[Peter Suh]

17 minutes ago, lev22885 said:

I don't understand the first question a little bit

 

And as for the TCRP friend, I'm using

 

Occasionally, in the case of MOBOs that ride characteristics, M.2 NVMe may cause the DSM to fail to boot when operating as bare metal.

The Asus IoT MOBO shown in my profile also has this characteristic, so I can't use M.2 NVMe.

I want to check this phenomenon.

Edited July 17, 2023 by Peter Suh

[lev22885]

12 минут назад, Peter Suh сказал:

 

Occasionally, in the case of MOBOs that ride characteristics, M.2 NVMe may cause the DSM to fail to boot when operating as bare metal.

The Asus IoT MOBO shown in my profile also has this characteristic, so I can't use M.2 NVMe.

I want to check this phenomenon.

I'm willing to help with verification, what needs to be done? ( But before that I will have to backup all my data, it may take +- a day )

[Peter Suh]

 

This is a test for you, not for me.
The choice is yours.
It's a simple test, but I don't know why you need to back up your data,
Please proceed as your time permits.

 

I can't erase the feeling that there is a mistranslation through the Russian-to-English translator in the middle.

Edited July 17, 2023 by Peter Suh

[lev22885]

43 минуты назад, Peter Suh сказал:

 

This is a test for you, not for me.
The choice is yours.
It's a simple test, but I don't know why you need to back up your data,
Please proceed as your time permits.

 

I can't erase the feeling that there is a mistranslation through the Russian-to-English translator in the middle.

You're right, I'm using a translator. 

 

Backup will have to be done, because proxmox uses its own file system, and on it already installs file systems of virtual machines and therefore testing on bare hardware my m2, all my data from it will be formatted accordingly 

 

But I'm a bit confused, what exactly do I need to test when I install dsm on my true hardware and not proxmox? 

[Peter Suh]

Is your language Thai?

I translated the following

 

สวัสดีคุณผู้ชมทุกท่านครับ สำหรับวันนี้เรามาเพิ่ม M.2 NVMe ให้กับ Xpenology Nas กันครับ ซึ่งจุดประสงค์ที่ผมเพิ่ม M.2 NVMe ลงไปก็เพื่อนำมาทำเป็น SSD Cache นั่นเองครับ โดยปกติแล้วถ้าเป็นเครื่อง Synology Nas ของแท้ทั่วไป ก็สามารถเปลี่ยนเข้าไปแล้วใช้งานได้เลยครับ แต่ถ้าเป็น Xpenology Nas เวลาเพิ่มเข้าไปแล้ว ตัว OS จะมองไม่เห็น M.2 NVMe ครับ ทั้งนี้เป็นเพราะว่าทาง Synology ได้ทำการ Fix หมายเลข Port ของ M.2 NVMe ให้เป็นหมายเลข Port ของ Synology Hardware เอาไว้ ซึ่ง Mainboard แต่ละตัวก็อาจจะมีหมายเลข Port ไม่เหมือนกันทำให้ตัว OS มองไม่เห็น M.2 NVMe นั่นเองครับ สำหรับวิธีการแก้ไขก็ตรงๆเลยครับคือทำการเปลี่ยนหมายเลข Port ของ M.2 NVMe ให้ตรงกับ Mainboard ก็จะสามารถใช้งานได้ครับ มาดูวิธีการเปลี่ยนในคลิปกันนะครับ ผิดพลาดตรงไหนต้องขออภัยด้วยนะครับ เชิญรับชมครับ.

--------------------------------------------------------------------------------------------------------------
Credit - https://blog.dateno1.com/?p=3890
--------------------------------------------------------------------------------------------------------------

Website : https://www.suteediy.com
Facebook : https://www.facebook.com/suteediyonyo...

 

-- Translate --

 

Hello all viewers. For today, let's add M.2 NVMe to Xpenology Nas. The purpose that I add M.2 NVMe to is to make SSD Cache. Normally, if it's a genuine Synology Nas machine, it can But if it is Xpenology Nas, when added, the OS will not see M.2 NVMe. This is because Synology has fixed the port number of M.2 NVMe to be the port number of Synology Hardware. Each Mainboard may have a different Port number, causing the OS to not see M.2 NVMe. will be able to use it Let's see how to change it in the clip. If there is a mistake, I apologize. Please visit.

-------------------------------------------------- -------------------------------------------------- ----------
Credit - https://blog.dateno1.com/?p=3890
-------------------------------------------------- -------------------------------------------------- ----------

Website : https://www.suteediy.com
Facebook : https://www.facebook.com/suteediyonyo...

 

 

FYI, this Korean blogger is someone I know.^^
https://blog.dateno1.com/?p=3890

 

There is no mention anywhere that you can run M.2 NVMe as a bootloader instead of a USB bootloader.

Again, M.2 NVMe can only be used as a cache or volume disk.

 

I already misunderstood that you have already installed the M.2 NVMe on the bare metal and tried booting the DSM.
I understand that it is still in the preparation stage.

It seems that the process of converting a virtualized disk volume to a bare metal one can only take a long time.

I hope you find more ways to enable M.2 NVMe on proxmox before you decide to switch to bare metal.

 

Is it correct that M.2 NVMe is passed through in proxmox?

 

In my hazy memory, if M.2 NVMe is an onboard type, it cannot work
It seems to work if it is a PCIe expansion type.

Or maybe vice versa.

 

I also have proxmox, but I haven't completely built a system environment for M.2 NVMe testing.
I'll take some time today to check out my proxmox system and try to help you.

[lev22885]

6 минут назад, Peter Suh сказал:

Is your language Thai?

I translated the following

 

สวัสดีคุณผู้ชมทุกท่านครับ สำหรับวันนี้เรามาเพิ่ม M.2 NVMe ให้กับ Xpenology Nas กันครับ ซึ่งจุดประสงค์ที่ผมเพิ่ม M.2 NVMe ลงไปก็เพื่อนำมาทำเป็น SSD Cache นั่นเองครับ โดยปกติแล้วถ้าเป็นเครื่อง Synology Nas ของแท้ทั่วไป ก็สามารถเปลี่ยนเข้าไปแล้วใช้งานได้เลยครับ แต่ถ้าเป็น Xpenology Nas เวลาเพิ่มเข้าไปแล้ว ตัว OS จะมองไม่เห็น M.2 NVMe ครับ ทั้งนี้เป็นเพราะว่าทาง Synology ได้ทำการ Fix หมายเลข Port ของ M.2 NVMe ให้เป็นหมายเลข Port ของ Synology Hardware เอาไว้ ซึ่ง Mainboard แต่ละตัวก็อาจจะมีหมายเลข Port ไม่เหมือนกันทำให้ตัว OS มองไม่เห็น M.2 NVMe นั่นเองครับ สำหรับวิธีการแก้ไขก็ตรงๆเลยครับคือทำการเปลี่ยนหมายเลข Port ของ M.2 NVMe ให้ตรงกับ Mainboard ก็จะสามารถใช้งานได้ครับ มาดูวิธีการเปลี่ยนในคลิปกันนะครับ ผิดพลาดตรงไหนต้องขออภัยด้วยนะครับ เชิญรับชมครับ.

--------------------------------------------------------------------------------------------------------------
Credit - https://blog.dateno1.com/?p=3890
--------------------------------------------------------------------------------------------------------------

Website : https://www.suteediy.com
Facebook : https://www.facebook.com/suteediyonyo...

 

-- Translate --

 

Hello all viewers. For today, let's add M.2 NVMe to Xpenology Nas. The purpose that I add M.2 NVMe to is to make SSD Cache. Normally, if it's a genuine Synology Nas machine, it can But if it is Xpenology Nas, when added, the OS will not see M.2 NVMe. This is because Synology has fixed the port number of M.2 NVMe to be the port number of Synology Hardware. Each Mainboard may have a different Port number, causing the OS to not see M.2 NVMe. will be able to use it Let's see how to change it in the clip. If there is a mistake, I apologize. Please visit.

-------------------------------------------------- -------------------------------------------------- ----------
Credit - https://blog.dateno1.com/?p=3890
-------------------------------------------------- -------------------------------------------------- ----------

Website : https://www.suteediy.com
Facebook : https://www.facebook.com/suteediyonyo...

 

 

FYI, this Korean blogger is someone I know.^^
https://blog.dateno1.com/?p=3890

 

There is no mention anywhere that you can run M.2 NVMe as a bootloader instead of a USB bootloader.

Again, M.2 NVMe can only be used as a cache or volume disk.

 

I already misunderstood that you have already installed the M.2 NVMe on the bare metal and tried booting the DSM.
I understand that it is still in the preparation stage.

It seems that the process of converting a virtualized disk volume to a bare metal one can only take a long time.

I hope you find more ways to enable M.2 NVMe on proxmox before you decide to switch to bare metal.

 

Is it correct that M.2 NVMe is passed through in proxmox?

 

In my hazy memory, if M.2 NVMe is an onboard type, it cannot work
It seems to work if it is a PCIe expansion type.

Or maybe vice versa.

 

I also have proxmox, but I haven't completely built a system environment for M.2 NVMe testing.
I'll take some time today to check out my proxmox system and try to help you.

Thank you for your reply. But you're a bit wrong about the language, I'm Russian:)

 

Yes, I use M2 in proxmox, but at the moment it is virtualised in DSM not as M2, but as normal sata

 

I will wait for your further advice, thanks for your help! 

[Peter Suh]

Here is the result of proxmox recognizing nvme.
The result of successful bare metal is proxmox (vm), and it is not very different.
NVMe passed through as a PCIE device and checked the PCI-E advanced options as capture.

 

 

 

 

[lev22885]

3 минуты назад, Peter Suh сказал:

Here is the result of proxmox recognizing nvme.
The result of successful bare metal is proxmox (vm), and it is not very different.
NVMe passed through as a PCIE device and checked the PCI-E advanced options as capture.

 

 

 

 

Thanks for this check, then I will try to check soon and will report back with the result