Please help with VHDX in hyper-v

[burabaika]

hello!

I created VM in hyper-v, started the VM, the 25.12.1 bootloader recognized the image, formatted it, compiled it with sa6400 and DSM 7.3.

After logging into the web interface, the Sinology utility says there are no disks.

What's the secret?
How do I get DSM to recognize this disk for system installation?

[github-actions]

请填写以下信息.
Please fill in the following information.

Install ENV: (You can find it in the boot interface.)

• DMI:
• CPU:
• NIC: (pid & vid)

RR version: (You can find it in the update menu.)

• RR:
• addons:
• modules:
• lkms:

DSM:

• model:
• version:

Issue:

logs:

(## 因为 log中存在 SN/MAC 等一些敏感信息, 当提供完整文件时请自行抹除他们, 当然你也可以发送到我的邮箱. ##)
(## Because the log contains some sensitive information such as SN/MAC, please delete them when providing the complete file. Of course, you can also send it to my email. ##)
...

(请先看一下#173、#175、#226 的内容)
(Plz review the content of #173, #175, #226 first)
...

(如果你只是说 XXX 不能用, 什么详细信息也不提供, 我也只能说感谢你的反馈.)
(If you just say XXX doesn't work without providing any details, I can only say thank you for your feedback.)
...

[burabaika]

                                                                                            Welcome to RR v25.12.1                                                                                                 
                                                                                                                                                                                       Sat Jan 10 08:31:39 UTC 2026
                                                                                         Boot Type: [UEFI] [VMBUS DoM]

Model: SA6400(epyc7002)
Version: 7.3(86009)
Kernel: custom
LKM: prod
MEV: hyperv
DMI: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 12/03/2020
CPU: 11th Gen Intel(R) Core(TM) i5-11400F @ 2.60GHz
MEM: 3921 MB
Cmdline:
withefi earlyprintk syno_hw_version=SA6400 console=ttyS0,115200n8 consoleblank=600 split_lock_detect=off netif_num=2 pid=0x0001 earlycon=uart8250,io,0x3f8,115200n8 R965c5742-f485-493d-9752-9355f04=00:15:5d:00:02:0b mac2=001132a496f6 mac1=001132a496f5 sn=2350W8RWWE7VH modprobe.blacklist=evbug,cdc_ether pcie_aspm=off rootwait nowatchdog vid=0x46f4 loglevel=15 HddHotplug=1 skip_vender_mac_interfaces=0,1 panic=5 vender_format_version=2 log_buf_len=32M root=/dev/md0 syno_ttyS1=serial,0x2f8 syno_ttyS0=serial,0x3f8 mev=hyperv

Reboot to boot directly in DSM
root@rr:/opt/rr#

[burabaika]

logs.tar.gz

[wjz304]

Hyper-V 目前只支持 直通 磁盘控制器，所以只适用于 server版本的 Hyper-V。

当然我有一个半成品的工具 https://github.com/RROrg/rr-tools， 但是它尚不稳定

[burabaika]

Yeah, I see, for the not-so-smart - how do I use it if I don't even have the system installed? (((

[burabaika]

see my disk, sdb

root@rr:/opt/rr# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 3.5G 0 disk
|-sda1 8:1 0 50M 0 part /mnt/p1
|-sda2 8:2 0 50M 0 part /mnt/p2
`-sda3 8:3 0 3.4G 0 part /mnt/p3
sdb 8:16 0 60G 0 disk

root@rr:/opt/rr# /root/forcemount -c -l 0 -n 1 /dev/sdb
mdadm: cannot open /dev/sdbp5: No such file or directory
Failed to create RAID array

where i'm wrong?

He adds p5 to the disk name for some reason, that's probably why?