On 2/27/2021 at 2:31 PM, casperse said:

I still havent managed to go pass version "DSM 6.2.3-25426 Update 3" if anyone have a 6.9 I would like to know how?

After I didn't get an answer if someone could already install the RC DSM 7.0 as VM, I decided to try an update from 6.2.3 to 6.2.4 (on the DS3617xs platform). The result is that I can no longer reach the DSM -> Brick.

 

Can anyone report anything different?

Big problem, need urgent help!

Due to my stupidity I tried to update my Xpenology VM from the running version DSM 6.2.3-25426 to the newest DSM 6.2.4-25556. As bootimage I use 1.03b for a DS3617. The end of the story is, the VM was no longer responsive => Brick!

I had under Unraid passthrough to the VM a DUAL Intel Nic and a LSI SAS2008 PCI-Express Fusion-MPT SAS-2 controller (LSI 9211-8i / Dell H310 HBA in IT-Mode)  to which 6x WD 6TB hard disks are connected as RAID5.

So I rebuilt the VM and reinstalled the DSM 6.2.3-25426 version, again. I now have the problem that when I passthrough the LSI controller with the 6x hard drives they show up as 6x external hard drives and no longer as RAID5.

Please help me, I don't know how to get back the RAID5. A backup is unfortunately not available, I never thought that the RAID5 could be broken by the update.

 

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' id='9'>
  <name>Xpenology - VM</name>
  <uuid>a454f1e6-fe15-df14-0475-fceadd9fb72d</uuid>
  <description>DS3617xs - File Server</description>
  <metadata>
    <vmtemplate xmlns="unraid" name="CentOS" icon="default.png" os="centos"/>
  </metadata>
  <memory unit='KiB'>4194304</memory>
  <currentMemory unit='KiB'>4194304</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>4</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='1'/>
    <vcpupin vcpu='1' cpuset='5'/>
    <vcpupin vcpu='2' cpuset='2'/>
    <vcpupin vcpu='3' cpuset='6'/>
  </cputune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-q35-3.0'>hvm</type>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough' check='none' migratable='on'>
    <topology sockets='1' dies='1' cores='2' threads='2'/>
    <cache mode='passthrough'/>
  </cpu>
  <clock offset='utc'>
    <timer name='rtc' tickpolicy='catchup'/>
    <timer name='pit' tickpolicy='delay'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/isos/synoboot.img' index='2'/>
      <backingStore/>
      <target dev='hdc' bus='usb'/>
      <boot order='1'/>
      <alias name='usb-disk2'/>
      <address type='usb' bus='0' port='2'/>
    </disk>
    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source dev='/dev/disk/by-id/ata-SanDisk_SDSSDHII120G_154682400434' index='1'/>
      <backingStore/>
      <target dev='hdd' bus='sata'/>
      <alias name='sata0-0-3'/>
      <address type='drive' controller='0' bus='0' target='0' unit='3'/>
    </disk>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <alias name='usb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <alias name='usb'/>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <alias name='usb'/>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <alias name='usb'/>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'>
      <alias name='pcie.0'/>
    </controller>
    <controller type='pci' index='1' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x10'/>
      <alias name='pci.1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='2' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='2' port='0x11'/>
      <alias name='pci.2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
    </controller>
    <controller type='pci' index='3' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='3' port='0x12'/>
      <alias name='pci.3'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
    </controller>
    <controller type='pci' index='4' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='4' port='0x13'/>
      <alias name='pci.4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
    </controller>
    <controller type='pci' index='5' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='5' port='0x14'/>
      <alias name='pci.5'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/>
    </controller>
    <controller type='pci' index='6' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='6' port='0x15'/>
      <alias name='pci.6'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/>
    </controller>
    <controller type='pci' index='7' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='7' port='0x16'/>
      <alias name='pci.7'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/>
    </controller>
    <controller type='pci' index='8' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='8' port='0x17'/>
      <alias name='pci.8'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x7'/>
    </controller>
    <controller type='pci' index='9' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='9' port='0x18'/>
      <alias name='pci.9'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='10' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='10' port='0x19'/>
      <alias name='pci.10'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x1'/>
    </controller>
    <controller type='pci' index='11' model='pcie-to-pci-bridge'>
      <model name='pcie-pci-bridge'/>
      <alias name='pci.11'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <alias name='virtio-serial0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </controller>
    <controller type='sata' index='0'>
      <alias name='ide'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='sata' index='1'>
      <alias name='sata1'/>
      <address type='pci' domain='0x0000' bus='0x0b' slot='0x01' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:24:c4:10'/>
      <source bridge='br0'/>
      <target dev='vnet0'/>
      <model type='e1000e'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/1'/>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
      <alias name='serial0'/>
    </serial>
    <console type='pty' tty='/dev/pts/1'>
      <source path='/dev/pts/1'/>
      <target type='serial' port='0'/>
      <alias name='serial0'/>
    </console>
    <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-9-Xpenology - VM/org.qemu.guest_agent.0'/>
      <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <alias name='input0'/>
      <address type='usb' bus='0' port='1'/>
    </input>
    <input type='mouse' bus='ps2'>
      <alias name='input1'/>
    </input>
    <input type='keyboard' bus='ps2'>
      <alias name='input2'/>
    </input>
    <graphics type='vnc' port='5901' autoport='yes' websocket='5701' listen='0.0.0.0' keymap='de'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <alias name='video0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/>
      </source>
      <alias name='hostdev0'/>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </hostdev>
    <memballoon model='none'/>
  </devices>
  <seclabel type='dynamic' model='dac' relabel='yes'>
    <label>+0:+100</label>
    <imagelabel>+0:+100</imagelabel>
  </seclabel>
</domain>

 

 

THE PROBLEM WAS FIXED!!!

 

Since no one answers me here I have taken the matter into my own hands. 

 

Tutorials are certainly all useful, but finally the easiest way is to delete the system partitions (2.4GB Linux RAID1 members: sda1, sdb1, sdc1, ... , sdx1) of all installed hard disks, with an linux live image, if you have performed an update and the system is no longer bootable. Then simply use an unused synoboot.img and the system is migrated without touching the data partitions.

 

Disadvantage is that all installed apps, configurations and settings have to be reinstalled of course. For my case i'm happy that no data is lost.

 

Thanks anyway for all the information written down here. Would only wish for the future that the community would answer a bit more active.

 

 

 

 

 

Edited August 11, 20214 yr by WowaDriver
THE PROBLEM WAS FIXED!!!

Happy to hear you found a solution! 🙂

No answers normally means that no one knows the answer to your question😞

 

You are using Unraid as a baremetal for running a Synology NAS with 5 passthrough drives.

 

My setup is much simpler just a small partition for the Synology apps 100G

And a VM disc for some photo data that I can mirror to the Unraid drives as a backup

So I can restore easily when a upgrade fails (Using the VM backup app)

Edited August 15, 20214 yr by casperse

Hello.  Just wanted to update this since I had to wipe and redo my install of xpenology and share what I learned.

 

Most is the same from my original post at:

 

 

 

except for some updates and things I tried:

 

3615xs

 

- My hardware is the same as before but on version 6.9.2 of unraid.

- Changed machine to Q35-5.1.  Kept it at SeaBIOS

- Because this is a new install, I rebuilt the synoboot from scratchexcept I kept the same s/n and mac in the grub. Verison 1.03b of the bootloader

- Also created a minimum 5GB vdisk using SATA and qcow (didn't test different type)

- STILL had to manually change the network model/card to "e1000e"  (still the big one)

- Installed version 6.2.3-25426.  Tried 6.2.4 and that just didn't work at all and that wouldn't boot.  Once in 6.2.3 I couldn't manually update to the minor updates -2 or -3.  Every time I uploaded the files, it would say it was "corrupt".  Tried to manually update to 6.2.4 and same thing.

 

So far everything is working.  I'll update if I find something that doesn't.

 

Hope this helps anyone that's still trying to do this in unraid.

 

Good luck.

 

 

Just a quick FYI for anyone getting the error 13 failed to install. I was able to fix it by changing my primary vdisk bus type to USB. 

Hi Everyone

 

I am looking into the new loader "Redpill" that seems to work with the DSM 7?

Have anyone had any success using this on Unraid?

This build should be "easy" to get working 7.0.1-42218

 

https://xpenology.com/forum/topic/53817-redpill-tinycore-loader/?tab=comments#comment-257525

 

Would be cool if we could create a working guide to get this working

I would love to have the new Photo application running in a small VM on Unraid

 

https://github.com/pocopico/tinycore-redpill

 

Edited March 30, 20224 yr by casperse

There is a tutorial here:

But I haven't tried it...

Updating to the new v7.0.0.0 Beta 2 breaks my Xponology have anyone found a fix?