Jump to content
XPEnology Community

RedPill - the new loader for 6.2.4 - Discussion


Recommended Posts

Hello everyone, today I was finally able to install a version of the new RedPill by following a couple of videos I found on the net (in the video notes I also found the link to download the image); I installed it on virtualbox (I will have to install it in baremetal mode on a special server, but first I want to see how the installation is via vm), I made (or almost) the changes described in the videos and started the machine, the machine starts as with the previous loaders, initially the router did not see it, then with the synology assistant I changed the ip (he had assigned an ip completely different from my network) now the router sees it and I authorized it to enter the lan, only that find.synology.com does not see it, even if I give it the ip address I assigned it does not find it and therefore I cannot go on. I also noticed that if I turn off the machine and reboot it reassigns the initial ip, in the videos there was an option to change in the vmx file (but it was done with vmware) and virtualbox doesn't seem to me so I don't know how and where to go to edit. I also noticed that he assigned a serial number of the machine that in the RedPill it was not possible to modify (in the previous loader yes) if I did not understand wrong with the tinycore-redpill-main everything can be done but I cannot build the loader . I remember that I read something about the identification of the diskstation but by now the discussion has reached more than 140 pages ... .. finished 15/20 pages I have to start over ..... 🙈🙈🙈!!!!! Someone can give me a hand ??? thank you

Link to comment
Share on other sites

Hello everyone, today I was finally able to install a version of the new RedPill by following a couple of videos I found on the net (in the video notes I also found the link to download the image); I installed it on virtualbox (I will have to install it in baremetal mode on a special server, but first I want to see how the installation is via vm), I made (or almost) the changes described in the videos and started the machine, the machine starts as with the previous loaders, initially the router did not see it, then with the synology assistant I changed the ip (he had assigned an ip completely different from my network) now the router sees it and I authorized it to enter the lan, only that find.synology.com does not see it, even if I give it the ip address I assigned it does not find it and therefore I cannot go on. I also noticed that if I turn off the machine and reboot it reassigns the initial ip, in the videos there was an option to change in the vmx file (but it was done with vmware) and virtualbox doesn't seem to me so I don't know how and where to go to edit. I also noticed that he assigned a serial number of the machine that in the RedPill it was not possible to modify (in the previous loader yes) if I did not understand wrong with the tinycore-redpill-main everything can be done but I cannot build the loader . I remember that I read something about the identification of the diskstation but by now the discussion has reached more than 140 pages ... .. finished 15/20 pages I have to start over ..... [emoji85][emoji85][emoji85]!!!!! Someone can give me a hand ??? thank you
If running under VirtualBox, make sure you change the network card from default NAT to bridged mode on primary LAN/WLAN Interface, then you will see the NAS in your network instead of behind NAT through you primary machines connection. That's probably why you got a strange NAT IP address by DHCP.

Skickat från min LE2113 via Tapatalk

Link to comment
Share on other sites

9 hours ago, Piteball said:

If running under VirtualBox, make sure you change the network card from default NAT to bridged mode on primary LAN/WLAN Interface, then you will see the NAS in your network instead of behind NAT through you primary machines connection. That's probably why you got a strange NAT IP address by DHCP.

Skickat från min LE2113 via Tapatalk
 

Hi Piteball, yes I did everything correct (I already knew it from the various previous loaders) however the machine starts correctly and goes online (I reach it only via syno assistant and I change the IP) but I do not reach it via browser. Let's see if I have some time today and I'm still working on it in the loader, thanks in the meantime.

Link to comment
Share on other sites

On 1/14/2022 at 5:43 PM, haydibe said:

You didn't follow the link to my signature as @pocopico suggested, did you?

 

This will download tinycore, extract the image, create a preconfigured vm to use the extracted tinycore image with usb boot. It will also add a 100gb data disk, to be attached to sata0.

 

Run these command in the shell of your Proxmox server: 



# set vm id
id=930

# create image directory, download and uncomporess
mkdir -p /var/lib/vz/images/${id}
curl --location https://github.com/pocopico/tinycore-redpill/raw/main/tinycore-redpill.v0.4.4.img.gz --output /var/lib/vz/images/${id}/tinycore-redpill.img.gz
gzip --decompress /var/lib/vz/images/${id}/tinycore-redpill.img.gz --keep

# create vm
qm create ${id} \
  --args "-device 'qemu-xhci,addr=0x18' -drive 'id=synoboot,file=/var/lib/vz/images/${id}/tinycore-redpill.img,if=none,format=raw' -device 'usb-storage,drive=synoboot'" \
  --cores 2 \
  --cpu host \
  --machine q35 \
  --memory 2048 \
  --name DSM \
  --net0 virtio,bridge=vmbr0 \
  --numa 0 \
  --onboot 0 \
  --ostype l26 \
  --scsihw virtio-scsi-pci \
  --sata0 local-lvm:vm-${id}-disk-0,discard=on,size=100G,ssd=1 \
  --sockets 1 \
  --serial0 socket \
  --serial1 socket \
  --tablet 1

# create disk for sata0
pvesm alloc local-lvm ${id} vm-${id}-disk-0 100G

Make sure to change the value for id from 930 to an id of your choosing.

 

If you want a bigger data disk, just change 100G to how much G you want. Once the vm is created, the settings can be changed in the Proxmox frontend later.

 

A valid user_config.json for q35 machine looks something like this. The vid and pid are correct if usb-boot is used (the commands above exactly do that).

The SataPortMap and DiskIdxMap are valid for the q35 machine type - the values are not valid for i440fx machine type.



{
    "extra_cmdline": {
        "vid": "0x46f4",
        "pid": "0x0001",
        "sn": "1510LWN123456",
        "mac1": "00123456789A",
        "SasIdxMap": "0",
        "SataPortMap": "66",
        "DiskIdxMap": "0600"
    },
    "synoinfo": {
        "internalportcfg": "0xffff",
        "maxdisks": "16"
    },
    "ramdisk_copy": {}
}

 

 

I've probably tried this a dozen times now, set PVE commands into a script, and for the life of me, I can't get this thing to finish booting into network discovery. 

 

Once it reaches the boot line "[    0.000000] console [ttyS0] enabled, bootconsole disabled" , it just sits there, CPU's at 50%, memory at 7%, no network, no disk activity. Just out to lunch. Longest I've waited is currently 20mins. Nothing.

 

it's almost as if it's not finding either the SATA or NET for OS startup, both using VIRTIO.

 

Bootlog attached. Any help?

 

 

*EDIT*** FIGURED IT OUT. Had CPU="HOST" instead of "KVM64", which is what worked for my 6.2 DSM

 

Edited by auTONYmous
Link to comment
Share on other sites

6 minutes ago, auTONYmous said:

I've probably tried this a dozen times now, set PVE commands into a script, and for the life of me, I can't get this thing to finish booting into network discovery. 

 

I messed up the --args command on the one you tried to use. Please use the fixed command from here:

 

It's painful that obsolete/wrong content can not be deleted or at least fixed after a period of time. Such type of content is better suited for a wiki than forum post anyway.

Link to comment
Share on other sites

All good with manual update from DSM 7.0.1-42218 to Update 2 version (skipped update 1)

 

image.png.3a3d43e9e2ce76ec56e7539159c568a1.png

 

Setup : HP GEN8 - Xeon 1265L V2 \ 10 GB ram \ 256 GB ssd

ESXI 7.0U2 \ VM with 4 cores and 6gb of ram \

Repill Loader bromolow 7.0.1-42218 \ mptsas - vmw_pvscsi - vmxnet3 drivers added in loader.

 

Edited by spikexp31
Link to comment
Share on other sites

В 15.01.2022 в 23:33, haydibe сказал:

# set vm id id=930

 

Hello, try this instruction but bootloader freeze..

 

 Booting `RedPill DS3615xs v7.0.1-42218 (USB, Verbose)'

Loading Linux...
Loading initramfs...
Starting kernel with USB boot
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 3.10.108 (root@build13) (gcc version 7.5.0 (GCC) ) #42218 SMP Mon Oct 18 19:15:14 CST 2021
[    0.000000] Command line: BOOT_IMAGE=/zImage withefi earlyprintk syno_hw_version=DS3615xs console=ttyS0,115200n8 netif_num=1 pid=0x0001 earlycon=uart8250,io,0x3f8,115200n8 syno_port_thaw=1 SasIdxMap=0 mac1=00123456789A sn=1510LWN123456 vid=0x46f4 elevator=elevator loglevel=15 HddHotplug=0 DiskIdxMap=0600 syno_hdd_detect=0 vender_format_version=2 syno_hdd_powerup_seq=0 log_buf_len=32M root=/dev/md0 SataPortMap=66
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000] e820: BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000007ffd4fff] usable
[    0.000000] BIOS-e820: [mem 0x000000007ffd5000-0x000000007fffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000b0000000-0x00000000bfffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
[    0.000000] Early serial console at I/O port 0x3f8 (options '115200n')
[    0.000000] bootconsole [uart0] enabled
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] SMBIOS 2.8 present.
[    0.000000] DMI: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
[    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.000000] e820: last_pfn = 0x7ffd5 max_arch_pfn = 0x400000000
[    0.000000] MTRR default type: write-back
[    0.000000] MTRR fixed ranges enabled:
[    0.000000]   00000-9FFFF write-back
[    0.000000]   A0000-BFFFF uncachable
[    0.000000]   C0000-FFFFF write-protect
[    0.000000] MTRR variable ranges enabled:
[    0.000000]   0 base 0C0000000 mask FC0000000 uncachable
[    0.000000]   1 disabled
[    0.000000]   2 disabled
[    0.000000]   3 disabled
[    0.000000]   4 disabled
[    0.000000]   5 disabled
[    0.000000]   6 disabled
[    0.000000]   7 disabled
[    0.000000] found SMP MP-table at [mem 0x000f5a60-0x000f5a6f] mapped at [ffff8800000f5a60]
[    0.000000] Base memory trampoline at [ffff880000099000] 99000 size 24576
[    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
[    0.000000]  [mem 0x00000000-0x000fffff] page 4k
[    0.000000] BRK [0x01b2c000, 0x01b2cfff] PGTABLE
[    0.000000] BRK [0x01b2d000, 0x01b2dfff] PGTABLE
[    0.000000] BRK [0x01b2e000, 0x01b2efff] PGTABLE
[    0.000000] init_memory_mapping: [mem 0x7fc00000-0x7fdfffff]
[    0.000000]  [mem 0x7fc00000-0x7fdfffff] page 2M
[    0.000000] BRK [0x01b2f000, 0x01b2ffff] PGTABLE
[    0.000000] init_memory_mapping: [mem 0x7c000000-0x7fbfffff]
[    0.000000]  [mem 0x7c000000-0x7fbfffff] page 2M
[    0.000000] init_memory_mapping: [mem 0x00100000-0x7bffffff]
[    0.000000]  [mem 0x00100000-0x001fffff] page 4k
[    0.000000]  [mem 0x00200000-0x7bffffff] page 2M
[    0.000000] init_memory_mapping: [mem 0x7fe00000-0x7ffd4fff]
[    0.000000]  [mem 0x7fe00000-0x7ffd4fff] page 4k
[    0.000000] BRK [0x01b30000, 0x01b30fff] PGTABLE
[    0.000000] log_buf_len: 33554432
[    0.000000] early log buf free: 1044904(99%)
[    0.000000] RAMDISK: [mem 0x35af7000-0x36d72fff]
[    0.000000] ACPI: RSDP 0x00000000000F5890 00014 (v00 BOCHS )
[    0.000000] ACPI: RSDT 0x000000007FFE4AC0 0003C (v01 BOCHS  BXPC     00000001 BXPC 00000001)
[    0.000000] ACPI: FACP 0x000000007FFE47E6 000F4 (v03 BOCHS  BXPC     00000001 BXPC 00000001)
[    0.000000] ACPI: DSDT 0x000000007FFDF040 057A6 (v01 BOCHS  BXPC     00000001 BXPC 00000001)
[    0.000000] ACPI: FACS 0x000000007FFDF000 00040
[    0.000000] ACPI: APIC 0x000000007FFE48DA 00080 (v01 BOCHS  BXPC     00000001 BXPC 00000001)
[    0.000000] ACPI: SSDT 0x000000007FFE495A 000CA (v01 BOCHS  VMGENID  00000001 BXPC 00000001)
[    0.000000] ACPI: HPET 0x000000007FFE4A24 00038 (v01 BOCHS  BXPC     00000001 BXPC 00000001)
[    0.000000] ACPI: MCFG 0x000000007FFE4A5C 0003C (v01 BOCHS  BXPC     00000001 BXPC 00000001)
[    0.000000] ACPI: WAET 0x000000007FFE4A98 00028 (v01 BOCHS  BXPC     00000001 BXPC 00000001)
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000]  [ffffea0000000000-ffffea0001bfffff] PMD -> [ffff88007b600000-ffff88007d1fffff] on node 0
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
[    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x00001000-0x0009efff]
[    0.000000]   node   0: [mem 0x00100000-0x7ffd4fff]
[    0.000000] On node 0 totalpages: 524147
[    0.000000]   DMA zone: 56 pages used for memmap
[    0.000000]   DMA zone: 21 pages reserved
[    0.000000]   DMA zone: 3998 pages, LIFO batch:0
[    0.000000]   DMA32 zone: 7112 pages used for memmap
[    0.000000]   DMA32 zone: 520149 pages, LIFO batch:31
[    0.000000] ACPI: PM-Timer IO Port: 0x608
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
[    0.000000] ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
[    0.000000] IOAPIC[0]: apic_id 0, version 17, address 0xfec00000, GSI 0-23
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
[    0.000000] ACPI: IRQ0 used by override.
[    0.000000] ACPI: IRQ2 used by override.
[    0.000000] ACPI: IRQ5 used by override.
[    0.000000] ACPI: IRQ9 used by override.
[    0.000000] ACPI: IRQ10 used by override.
[    0.000000] ACPI: IRQ11 used by override.
[    0.000000] Using ACPI (MADT) for SMP configuration information
[    0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[    0.000000] smpboot: Allowing 2 CPUs, 0 hotplug CPUs
[    0.000000] nr_irqs_gsi: 40
[    0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
[    0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
[    0.000000] PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
[    0.000000] e820: [mem 0xc0000000-0xfed1bfff] available for PCI devices
[    0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1
[    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88007dc00000 s80704 r8192 d21696 u1048576
[    0.000000] pcpu-alloc: s80704 r8192 d21696 u1048576 alloc=1*2097152
[    0.000000] pcpu-alloc: [0] 0 1 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 516958
[    0.000000] Kernel command line: BOOT_IMAGE=/zImage withefi earlyprintk syno_hw_version=DS3615xs console=ttyS0,115200n8 netif_num=1 pid=0x0001 earlycon=uart8250,io,0x3f8,115200n8 syno_port_thaw=1 SasIdxMap=0 mac1=00123456789A sn=1510LWN123456 vid=0x46f4 elevator=elevator loglevel=15 HddHotplug=0 DiskIdxMap=0600 syno_hdd_detect=0 vender_format_version=2 syno_hdd_powerup_seq=0 log_buf_len=32M root=/dev/md0 SataPortMap=66
[    0.000000] Synology Hardware Version: DS3615xs-j
[    0.000000] Internal netif num: 1
[    0.000000] Mac1: 00123456789A
[    0.000000] Serial Number: 1510LWN123456
[    0.000000] Disk Index Map: 0600
[    0.000000] Vender format version: 2
[    0.000000] Power on seq num: 0
[    0.000000] Sata Port Map: 66
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
[    0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
[    0.000000] Memory: 2001272k/2096980k available (4820k kernel code, 392k absent, 95316k reserved, 4065k data, 828k init)
[    0.000000] Kernel/User page tables isolation: disabled
[    0.000000] Hierarchical RCU implementation.
[    0.000000]  CONFIG_RCU_FANOUT set to non-default value of 32
[    0.000000]  RCU dyntick-idle grace-period acceleration is enabled.
[    0.000000]  RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2.
[    0.000000] NR_IRQS:4352 nr_irqs:512 16
[    0.000000] Console: colour dummy device 80x25
[    0.000000] console [ttyS0] enabled, bootconsole disabled

 

What do you advise?

Edited by Bender
Link to comment
Share on other sites

Wow, i wasnt aware of new development! still using 6.1 on my HP gen 8 and 1.03b loader (3615xs)

 

This thread is huge, is there a loader that i can downnload to test, want to try 6.2.4 , since i need a new surveilance station, and not compatible anymore with 6.1.3

I have an HP Gen 8, with ESXI

 

thnx for info!!

Link to comment
Share on other sites

1 hour ago, NoFate said:

Wow, i wasnt aware of new development! still using 6.1 on my HP gen 8 and 1.03b loader (3615xs)

 

This thread is huge, is there a loader that i can downnload to test, want to try 6.2.4 , since i need a new surveilance station, and not compatible anymore with 6.1.3

I have an HP Gen 8, with ESXI

 

thnx for info!!

NoFate go to the tinycore thread. That is the best/easiest way to start.

 

Link to comment
Share on other sites

On 10/28/2021 at 2:15 AM, dreamtek said:

In proxmox with a HD5xx or HD6xx IGPU passthrough,this question can be solved.

The problem is opengl(which syno used to accelerate the facedetect) only use a i915 device with addr 00:02,and the default addr of proxmox passthrogh is 00:10.

So you can manually edit it in args: -device vfio-pci,host=00:02.0,addr=0x02,x-igd-opregion=on.

Remenber the i915 driver blacklist and vfio options in /etc/modprobe.d/vfio.conf must be done first.Or it will be a freeze on proxmox host,shutdown the autorun of DSM VM first before do above!

Thanks @dreamtek

 

I tried this on my proxmox build . 

Ensuring the i915 device was passed through with address 00:02 , but it still does not seem to function , is a genuine serial number / Mac required ?

I'm using GVT-g passthrough , I have validated that HW acceleration / transcoding / Quicksync works with Plex etc.

 

Wondering do I need to passthrough the entire igpu or should Mediated Device passthrough (Intel GTV-g) work ?

 

lspci -nnk

150392805-e0300fc8-106b-4f45-9d48-596119

 

150394244-38319580-b682-45c7-8e1b-83665d

/dev/dri/

150393084-e33787fb-b6b6-4d3d-98bb-d006a0

 

I do see this line in the output , however Quicksync seems to work ?

150393333-db3c0a8d-4874-46b0-b412-c1477e

 

Link to comment
Share on other sites

I just found this topic, I thought DSM 7 (or 6.2.4) was still impossible, then I looked into the update topic and I saw that people successfully installed DSM 7 on their NAS using RedPill.

I have a baremetal system that runs Juns loader v1.04b (DS918+). I have an Intel Pentium G4560 with 5 disks installed. Can I use RedPill loader to install DSM 7?

And if so, will I be able to keep my DSM settings and docker containers etc.

 

I searched already on this site and on Google but could not find a proper tutorial on how to do this, is there anyone here that can help?

Link to comment
Share on other sites

1 hour ago, miicker said:

I just found this topic, I thought DSM 7 (or 6.2.4) was still impossible, then I looked into the update topic and I saw that people successfully installed DSM 7 on their NAS using RedPill.

I have a baremetal system that runs Juns loader v1.04b (DS918+). I have an Intel Pentium G4560 with 5 disks installed. Can I use RedPill loader to install DSM 7?

And if so, will I be able to keep my DSM settings and docker containers etc.

 

I searched already on this site and on Google but could not find a proper tutorial on how to do this, is there anyone here that can help?

Go ahead and try it out, it's completely experimental and unsupported. However as you have noticed some people have actually gotten it to work mostly, except for some instability using docker containers.

Link to comment
Share on other sites

1 hour ago, Piteball said:

Go ahead and try it out, it's completely experimental and unsupported. However as you have noticed some people have actually gotten it to work mostly, except for some instability using docker containers.

 

I could try it out, but a rather have some more certainty before I lose 12TB of data :) 

Link to comment
Share on other sites

1 hour ago, miicker said:

 

I could try it out, but a rather have some more certainty before I lose 12TB of data :) 

It's quite impossible to give any assurances in current state. I'm actually trying it out using Tinycore Loader, however not so much luck getting the drives on the LSI 9211-8i to show up, even though mpt3sas was detected and me running rploader satamap, so I will probably have to either play around with satamap settings or connect to serialport using IPMI on the Supermicro mainboard to see what's not happening.

Link to comment
Share on other sites

I encountered an issue when trying to pass-trough HDD on DSM7. After fresh red-pill DS3615xs installation I followed the Proxmox

documentation to mount two 4TB HDDs to the VM via shell commands

 

qm set 999 -scsi0 /dev/disk/by-id/ata-WDC_WD40EFAX-XXXXXXX_WD-WXXXXXXXXX31
qm set 999 -scsi1 /dev/disk/by-id/ata-WDC_WD40EFAX-XXXXXXX_WD-WXXXXXXXXXN2

 

after booting I see the drives in Synology Storage manager but I can't create a storage volume

See screenshot for error "disk_reason_template_0"1702715401_TemplateError.thumb.PNG.c0e1bf823c305211b3f57879e01ce8cf.PNG

But the storage manager clearly see's both of them

 

Any idea how to fix this?

 

Disks.PNG

Edited by myswe
Link to comment
Share on other sites

6 hours ago, myswe said:

I encountered an issue when trying to pass-trough HDD on DSM7. After fresh red-pill DS3615xs installation I followed the Proxmox

documentation to mount two 4TB HDDs to the VM via shell commands

 

qm set 999 -scsi0 /dev/disk/by-id/ata-WDC_WD40EFAX-XXXXXXX_WD-WXXXXXXXXX31
qm set 999 -scsi1 /dev/disk/by-id/ata-WDC_WD40EFAX-XXXXXXX_WD-WXXXXXXXXXN2

 

after booting I see the drives in Synology Storage manager but I can't create a storage volume

See screenshot for error "disk_reason_template_0"1702715401_TemplateError.thumb.PNG.c0e1bf823c305211b3f57879e01ce8cf.PNG

But the storage manager clearly see's both of them

 

Any idea how to fix this?

 

Disks.PNG


 

hi, i passthrough 4 drives without problems but with SATA.

this is my config line:

 

sata1: /dev/disk/by-id/ata-WDC_WD60EFRX-68MYMN1_WD-XxXxXxXxXx,backup=0,serial=WD-XxXxXxXxXx,size=5860522584K

Link to comment
Share on other sites

4 hours ago, dodo-dk said:


 

hi, i passthrough 4 drives without problems but with SATA.

this is my config line:

 

sata1: /dev/disk/by-id/ata-WDC_WD60EFRX-68MYMN1_WD-XxXxXxXxXx,backup=0,serial=WD-XxXxXxXxXx,size=5860522584K

 

Yes SATA seems to be working flawlessly, I wonder if it has performance impact.

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...