Jump to content
XPEnology Community
  • 0

Migrating Baremetal to ESXi - Passthrough HDDs or Controller?


WiteWulf

Question

I'm contemplating migrating moving my baremetal install on an HP Gen8 Microserver to ESXi (ESXi because I use it at work and am more familiar with it than Proxmox).

 

It seems pretty simple: just replace the xpenology USB boot stick I'm currently using with an ESXi boot stick, create a VM for DSM with a virtual boot image, pass through the existing disks and boot it up. DSM will do the "I've detected disks from another server, do you want to migrate?" thing, and I'm done, right?

 

My main question before I do this is: given that I'm running the SATA controller on the Gen8 in AHCI mode (ie. no "hardware" RAID), should I pass through the controller to the VM, or the individual disks in Raw Disk Mode? Is there any performance benefit to either?

 

The disks (4x3TB) are full with DSM data, obviously, so I'll not be able to use that set of disks for any other ESXi guests, but I'm considering getting an HBA at some point to add some extra storage.

Link to comment
Share on other sites

Recommended Posts

  • 0

Thanks for the response @Peter Suh

 

I've rebuilt the loader with blank entries as described for SataPortMap and DiskIdxMap in user_config.json

{
  "extra_cmdline": {
    "pid": "0xa4a5",
    "vid": "0x0525",
    "sn": "XXXXXXXXXXXX",
    "mac1": "XXXXXXXXXXXX",
    "SataPortMap": "",
    "DiskIdxMap": ""
  },
  "synoinfo": {
          "internalportcfg" : "0xffff",
          "maxdisks" : "16",
          "support_bde_internal_10g" : "no",
          "support_disk_compatibility" : "no",
          "support_memory_compatibility" : "no"

},
  "ramdisk_copy": {
    
}
}


The web UI is once again offering to recover (which I've not tried yet).

 

On the command line:

SynologyNAS> dmesg | grep -i hpsa
[   20.445717] HP HPSA Driver (v 3.4.14-0)
[   20.447285] hpsa 0000:0b:00.0: MSI-X capable controller
[   20.451250] hpsa 0000:0b:00.0: Logical aborts not supported
[   20.452414] hpsa 0000:0b:00.0: HP SSD Smart Path aborts not supported
[   20.487388] scsi host30: hpsa
[   20.495158] hpsa 0000:0b:00.0: scsi 30:0:0:0: added Direct-Access     ATA      WDC WD30EFRX-68E PHYS DRV SSDSmartPathCap- En- Exp=1
[   20.497690] hpsa 0000:0b:00.0: scsi 30:0:1:0: added Direct-Access     ATA      WDC WD30EFRX-68E PHYS DRV SSDSmartPathCap- En- Exp=1
[   20.500025] hpsa 0000:0b:00.0: scsi 30:0:2:0: added Direct-Access     ATA      WDC WD30EFRX-68E PHYS DRV SSDSmartPathCap- En- Exp=1
[   20.502359] hpsa 0000:0b:00.0: scsi 30:0:3:0: added Direct-Access     ATA      WDC WD30EFRX-68N PHYS DRV SSDSmartPathCap- En- Exp=1
[   20.504692] hpsa 0000:0b:00.0: scsi 30:0:4:0: masked Enclosure         PMCSIERA SRCv8x6G         enclosure SSDSmartPathCap- En- Exp=0
[   20.507063] hpsa 0000:0b:00.0: scsi 30:3:0:0: added RAID              HP       P222             controller SSDSmartPathCap- En- Exp=1

 

All disks seen...

 

SynologyNAS> fdisk -l
Disk /dev/synoboot: 1024 MB, 1073741824 bytes, 2097152 sectors
130 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device       Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/synoboot1 *  0,32,33     6,62,56           2048     100351      98304 48.0M 83 Linux
/dev/synoboot2    6,62,57     15,205,62       100352     253951     153600 75.0M 83 Linux
/dev/synoboot3    15,205,63   130,138,8       253952    2097151    1843200  900M 83 Linux
fdisk: device has more than 2^32 sectors, can't use all of them
Disk /dev/sdae: 2048 GB, 2199023255040 bytes, 4294967295 sectors
267349 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device   Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sdae1    0,0,1       1023,254,63          1 4294967295 4294967295 2047G ee EFI GPT
fdisk: device has more than 2^32 sectors, can't use all of them
Disk /dev/sdaf: 2048 GB, 2199023255040 bytes, 4294967295 sectors
267349 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device   Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sdaf1    0,0,1       1023,254,63          1 4294967295 4294967295 2047G ee EFI GPT
fdisk: device has more than 2^32 sectors, can't use all of them
Disk /dev/sdag: 2048 GB, 2199023255040 bytes, 4294967295 sectors
267349 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device   Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sdag1    0,0,1       1023,254,63          1 4294967295 4294967295 2047G ee EFI GPT
fdisk: device has more than 2^32 sectors, can't use all of them
Disk /dev/sdah: 2048 GB, 2199023255040 bytes, 4294967295 sectors
267349 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device   Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sdah1    0,0,1       1023,254,63          1 4294967295 4294967295 2047G ee EFI GPT
Disk /dev/md0: 2431 MB, 2549940224 bytes, 4980352 sectors
622544 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1: 2047 MB, 2147418112 bytes, 4194176 sectors
524272 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/md1 doesn't contain a valid partition table

But naming looks weird ¯\_(ツ)_/¯ 

 

Clicking "Recover" in the web UI reboots the VM and brings me back to the same page. It's still stuck in a recovery loop.

Link to comment
Share on other sites

  • 0
31 minutes ago, WiteWulf said:

Thanks for the response @Peter Suh

 

I've rebuilt the loader with blank entries as described for SataPortMap and DiskIdxMap in user_config.json

{
  "extra_cmdline": {
    "pid": "0xa4a5",
    "vid": "0x0525",
    "sn": "XXXXXXXXXXXX",
    "mac1": "XXXXXXXXXXXX",
    "SataPortMap": "",
    "DiskIdxMap": ""
  },
  "synoinfo": {
          "internalportcfg" : "0xffff",
          "maxdisks" : "16",
          "support_bde_internal_10g" : "no",
          "support_disk_compatibility" : "no",
          "support_memory_compatibility" : "no"

},
  "ramdisk_copy": {
    
}
}


The web UI is once again offering to recover (which I've not tried yet).

 

On the command line:

SynologyNAS> dmesg | grep -i hpsa
[   20.445717] HP HPSA Driver (v 3.4.14-0)
[   20.447285] hpsa 0000:0b:00.0: MSI-X capable controller
[   20.451250] hpsa 0000:0b:00.0: Logical aborts not supported
[   20.452414] hpsa 0000:0b:00.0: HP SSD Smart Path aborts not supported
[   20.487388] scsi host30: hpsa
[   20.495158] hpsa 0000:0b:00.0: scsi 30:0:0:0: added Direct-Access     ATA      WDC WD30EFRX-68E PHYS DRV SSDSmartPathCap- En- Exp=1
[   20.497690] hpsa 0000:0b:00.0: scsi 30:0:1:0: added Direct-Access     ATA      WDC WD30EFRX-68E PHYS DRV SSDSmartPathCap- En- Exp=1
[   20.500025] hpsa 0000:0b:00.0: scsi 30:0:2:0: added Direct-Access     ATA      WDC WD30EFRX-68E PHYS DRV SSDSmartPathCap- En- Exp=1
[   20.502359] hpsa 0000:0b:00.0: scsi 30:0:3:0: added Direct-Access     ATA      WDC WD30EFRX-68N PHYS DRV SSDSmartPathCap- En- Exp=1
[   20.504692] hpsa 0000:0b:00.0: scsi 30:0:4:0: masked Enclosure         PMCSIERA SRCv8x6G         enclosure SSDSmartPathCap- En- Exp=0
[   20.507063] hpsa 0000:0b:00.0: scsi 30:3:0:0: added RAID              HP       P222             controller SSDSmartPathCap- En- Exp=1

 

All disks seen...

 

SynologyNAS> fdisk -l
Disk /dev/synoboot: 1024 MB, 1073741824 bytes, 2097152 sectors
130 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device       Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/synoboot1 *  0,32,33     6,62,56           2048     100351      98304 48.0M 83 Linux
/dev/synoboot2    6,62,57     15,205,62       100352     253951     153600 75.0M 83 Linux
/dev/synoboot3    15,205,63   130,138,8       253952    2097151    1843200  900M 83 Linux
fdisk: device has more than 2^32 sectors, can't use all of them
Disk /dev/sdae: 2048 GB, 2199023255040 bytes, 4294967295 sectors
267349 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device   Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sdae1    0,0,1       1023,254,63          1 4294967295 4294967295 2047G ee EFI GPT
fdisk: device has more than 2^32 sectors, can't use all of them
Disk /dev/sdaf: 2048 GB, 2199023255040 bytes, 4294967295 sectors
267349 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device   Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sdaf1    0,0,1       1023,254,63          1 4294967295 4294967295 2047G ee EFI GPT
fdisk: device has more than 2^32 sectors, can't use all of them
Disk /dev/sdag: 2048 GB, 2199023255040 bytes, 4294967295 sectors
267349 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device   Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sdag1    0,0,1       1023,254,63          1 4294967295 4294967295 2047G ee EFI GPT
fdisk: device has more than 2^32 sectors, can't use all of them
Disk /dev/sdah: 2048 GB, 2199023255040 bytes, 4294967295 sectors
267349 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device   Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sdah1    0,0,1       1023,254,63          1 4294967295 4294967295 2047G ee EFI GPT
Disk /dev/md0: 2431 MB, 2549940224 bytes, 4980352 sectors
622544 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1: 2047 MB, 2147418112 bytes, 4194176 sectors
524272 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/md1 doesn't contain a valid partition table

But naming looks weird ¯\_(ツ)_/¯ 

 

Clicking "Recover" in the web UI reboots the VM and brings me back to the same page. It's still stuck in a recovery loop.

 

SynologyNAS>
Looks like I'll have to check the junior log at the prompt.
You will be able to check the currently installed version.
Please run the command as below and report the result.

 

cat /var/log/*rc*

Link to comment
Share on other sites

  • 0
51 minutes ago, WiteWulf said:

Thanks for the response @Peter Suh

 

I've rebuilt the loader with blank entries as described for SataPortMap and DiskIdxMap in user_config.json

{
  "extra_cmdline": {
    "pid": "0xa4a5",
    "vid": "0x0525",
    "sn": "XXXXXXXXXXXX",
    "mac1": "XXXXXXXXXXXX",
    "SataPortMap": "",
    "DiskIdxMap": ""
  },
  "synoinfo": {
          "internalportcfg" : "0xffff",
          "maxdisks" : "16",
          "support_bde_internal_10g" : "no",
          "support_disk_compatibility" : "no",
          "support_memory_compatibility" : "no"

},
  "ramdisk_copy": {
    
}
}


The web UI is once again offering to recover (which I've not tried yet).

 

On the command line:

SynologyNAS> dmesg | grep -i hpsa
[   20.445717] HP HPSA Driver (v 3.4.14-0)
[   20.447285] hpsa 0000:0b:00.0: MSI-X capable controller
[   20.451250] hpsa 0000:0b:00.0: Logical aborts not supported
[   20.452414] hpsa 0000:0b:00.0: HP SSD Smart Path aborts not supported
[   20.487388] scsi host30: hpsa
[   20.495158] hpsa 0000:0b:00.0: scsi 30:0:0:0: added Direct-Access     ATA      WDC WD30EFRX-68E PHYS DRV SSDSmartPathCap- En- Exp=1
[   20.497690] hpsa 0000:0b:00.0: scsi 30:0:1:0: added Direct-Access     ATA      WDC WD30EFRX-68E PHYS DRV SSDSmartPathCap- En- Exp=1
[   20.500025] hpsa 0000:0b:00.0: scsi 30:0:2:0: added Direct-Access     ATA      WDC WD30EFRX-68E PHYS DRV SSDSmartPathCap- En- Exp=1
[   20.502359] hpsa 0000:0b:00.0: scsi 30:0:3:0: added Direct-Access     ATA      WDC WD30EFRX-68N PHYS DRV SSDSmartPathCap- En- Exp=1
[   20.504692] hpsa 0000:0b:00.0: scsi 30:0:4:0: masked Enclosure         PMCSIERA SRCv8x6G         enclosure SSDSmartPathCap- En- Exp=0
[   20.507063] hpsa 0000:0b:00.0: scsi 30:3:0:0: added RAID              HP       P222             controller SSDSmartPathCap- En- Exp=1

 

All disks seen...

 

SynologyNAS> fdisk -l
Disk /dev/synoboot: 1024 MB, 1073741824 bytes, 2097152 sectors
130 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device       Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/synoboot1 *  0,32,33     6,62,56           2048     100351      98304 48.0M 83 Linux
/dev/synoboot2    6,62,57     15,205,62       100352     253951     153600 75.0M 83 Linux
/dev/synoboot3    15,205,63   130,138,8       253952    2097151    1843200  900M 83 Linux
fdisk: device has more than 2^32 sectors, can't use all of them
Disk /dev/sdae: 2048 GB, 2199023255040 bytes, 4294967295 sectors
267349 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device   Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sdae1    0,0,1       1023,254,63          1 4294967295 4294967295 2047G ee EFI GPT
fdisk: device has more than 2^32 sectors, can't use all of them
Disk /dev/sdaf: 2048 GB, 2199023255040 bytes, 4294967295 sectors
267349 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device   Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sdaf1    0,0,1       1023,254,63          1 4294967295 4294967295 2047G ee EFI GPT
fdisk: device has more than 2^32 sectors, can't use all of them
Disk /dev/sdag: 2048 GB, 2199023255040 bytes, 4294967295 sectors
267349 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device   Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sdag1    0,0,1       1023,254,63          1 4294967295 4294967295 2047G ee EFI GPT
fdisk: device has more than 2^32 sectors, can't use all of them
Disk /dev/sdah: 2048 GB, 2199023255040 bytes, 4294967295 sectors
267349 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device   Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sdah1    0,0,1       1023,254,63          1 4294967295 4294967295 2047G ee EFI GPT
Disk /dev/md0: 2431 MB, 2549940224 bytes, 4980352 sectors
622544 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1: 2047 MB, 2147418112 bytes, 4194176 sectors
524272 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/md1 doesn't contain a valid partition table

But naming looks weird ¯\_(ツ)_/¯ 

 

Clicking "Recover" in the web UI reboots the VM and brings me back to the same page. It's still stuck in a recovery loop.

 

@WiteWulf as you probably know, VMware SATA controller has like 31 ports on each controller. If you dont limit that with SataPortMap, you are pushing the next ones after 31. You disks are starting at sdae which is 26+5 = 31 ? 

 

So i would start by limiting VMware controller (its the 1st, i guess) with SataPortMap="18" and DiskIdxMap="0A00" 

 

 

Edited by pocopico
  • Thanks 1
Link to comment
Share on other sites

  • 0

@Peter Suh

SynologyNAS> cat /var/log/*rc*
START /linuxrc.syno.impl
Insert Marvell 1475 SATA controller driver
Insert basic USB modules...
:: Loading module usb-common ... [  OK  ]
:: Loading module usbcore ... [  OK  ]
:: Loading module ehci-hcd ... [  OK  ]
:: Loading module ehci-pci ... [  OK  ]
:: Loading module xhci-hcd ... [  OK  ]
:: Loading module xhci-pci ... [  OK  ]
:: Loading module usb-storage ... [  OK  ]
:: Loading kernel modules from extensions ...
Loading kmod #0 "hpsa.ko" for pocopico.hpsa (args: )
Loading kmod #0 "vmxnet3.ko" for pocopico.vmxnet3 (args: )
:: Loading kernel modules from extensions ... [  OK  ]
:: Executing "on_boot" custom scripts ...
Running "check-hpsa.sh" for pocopico.hpsa->on_boot
Loading module hpsa -> Module hpsa loaded succesfully
Ran "check-hpsa.sh" for pocopico.hpsa->on_boot - exit=0
Running "check-vmxnet3.sh" for pocopico.vmxnet3->on_boot
Loading module vmxnet3 -> Module vmxnet3 loaded succesfully
Ran "check-vmxnet3.sh" for pocopico.vmxnet3->on_boot - exit=0
Running "boot-wait.sh" for redpill-boot-wait->on_boot
Confirmed a valid-looking /dev/synoboot device
Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=0
Running "install_rd.sh" for redpill-misc->on_boot
Starting ttyd, listening on port: 7681
Ran "install_rd.sh" for redpill-misc->on_boot - exit=0
:: Executing "on_boot" custom scripts ... [  OK  ]
Extensions processed
insmod: can't insert '/lib/modules/etxhci-hcd.ko': No such file or directory
Insert net driver(Mindspeed only)...
Starting /usr/syno/bin/synocfgen...
/usr/syno/bin/synocfgen returns 0
Insert synorbd kernel module
Insert synofsbd kernel module
Insert sha256 kernel module
All disk ready or timeout execeed
Assemble args: -u 724e4f33:087db4e2:3017a5a8:c86610be /dev/sdag1 /dev/sdah1
mdadm: /dev/md0 has been started with 2 drives (out of 12).
Partition Version=8
 /sbin/e2fsck exists, checking /dev/md0... 
e2fsck 1.44.1 (24-Mar-2018)
/sbin/e2fsck -yvf returns 0
Mounting /dev/md0 /tmpRoot
------------upgrade
Begin upgrade procedure
Failed to found any patch
No upgrade file found
============upgrade
------------bootup-smallupdate
Failed to AssertFileKeyValueEqual
  value1: /etc.defaults/VERSION:smallfixnumber -> 0
  value2: /tmpRoot/.syno/patch/VERSION:smallfixnumber => 3
Skip bootup smallupdate, because root is not matched to junior
============bootup-smallupdate
Failed to AssertFileKeyValueEqual
  value1: /etc.defaults/VERSION:smallfixnumber -> 0
  value2: /tmpRoot/.syno/patch/VERSION:smallfixnumber => 3
Exit on error [7] root not matched with junior...
Tue Sep 20 13:06:30 UTC 2022
/dev/md0 /tmpRoot ext4 rw,relatime,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0

 

@pocopicothanks for the tip re. ESXi sata devices. I'll rebuild the bootloader again with the suggested settings and try again. At least I understand what the parameters mean now, and how it's interacting with the hardware (virtual and physical).

Link to comment
Share on other sites

  • 0
35 minutes ago, WiteWulf said:

@Peter Suh

SynologyNAS> cat /var/log/*rc*
START /linuxrc.syno.impl
Insert Marvell 1475 SATA controller driver
Insert basic USB modules...
:: Loading module usb-common ... [  OK  ]
:: Loading module usbcore ... [  OK  ]
:: Loading module ehci-hcd ... [  OK  ]
:: Loading module ehci-pci ... [  OK  ]
:: Loading module xhci-hcd ... [  OK  ]
:: Loading module xhci-pci ... [  OK  ]
:: Loading module usb-storage ... [  OK  ]
:: Loading kernel modules from extensions ...
Loading kmod #0 "hpsa.ko" for pocopico.hpsa (args: )
Loading kmod #0 "vmxnet3.ko" for pocopico.vmxnet3 (args: )
:: Loading kernel modules from extensions ... [  OK  ]
:: Executing "on_boot" custom scripts ...
Running "check-hpsa.sh" for pocopico.hpsa->on_boot
Loading module hpsa -> Module hpsa loaded succesfully
Ran "check-hpsa.sh" for pocopico.hpsa->on_boot - exit=0
Running "check-vmxnet3.sh" for pocopico.vmxnet3->on_boot
Loading module vmxnet3 -> Module vmxnet3 loaded succesfully
Ran "check-vmxnet3.sh" for pocopico.vmxnet3->on_boot - exit=0
Running "boot-wait.sh" for redpill-boot-wait->on_boot
Confirmed a valid-looking /dev/synoboot device
Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=0
Running "install_rd.sh" for redpill-misc->on_boot
Starting ttyd, listening on port: 7681
Ran "install_rd.sh" for redpill-misc->on_boot - exit=0
:: Executing "on_boot" custom scripts ... [  OK  ]
Extensions processed
insmod: can't insert '/lib/modules/etxhci-hcd.ko': No such file or directory
Insert net driver(Mindspeed only)...
Starting /usr/syno/bin/synocfgen...
/usr/syno/bin/synocfgen returns 0
Insert synorbd kernel module
Insert synofsbd kernel module
Insert sha256 kernel module
All disk ready or timeout execeed
Assemble args: -u 724e4f33:087db4e2:3017a5a8:c86610be /dev/sdag1 /dev/sdah1
mdadm: /dev/md0 has been started with 2 drives (out of 12).
Partition Version=8
 /sbin/e2fsck exists, checking /dev/md0... 
e2fsck 1.44.1 (24-Mar-2018)
/sbin/e2fsck -yvf returns 0
Mounting /dev/md0 /tmpRoot
------------upgrade
Begin upgrade procedure
Failed to found any patch
No upgrade file found
============upgrade
------------bootup-smallupdate
Failed to AssertFileKeyValueEqual
  value1: /etc.defaults/VERSION:smallfixnumber -> 0
  value2: /tmpRoot/.syno/patch/VERSION:smallfixnumber => 3
Skip bootup smallupdate, because root is not matched to junior
============bootup-smallupdate
Failed to AssertFileKeyValueEqual
  value1: /etc.defaults/VERSION:smallfixnumber -> 0
  value2: /tmpRoot/.syno/patch/VERSION:smallfixnumber => 3
Exit on error [7] root not matched with junior...
Tue Sep 20 13:06:30 UTC 2022
/dev/md0 /tmpRoot ext4 rw,relatime,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0

 

@pocopicothanks for the tip re. ESXi sata devices. I'll rebuild the bootloader again with the suggested settings and try again. At least I understand what the parameters mean now, and how it's interacting with the hardware (virtual and physical).

 

smallfixnumber version of the loader and
The smallfixnumber version of DSM is mismatched.
Use the postupdate action in ./rploader.sh .

  • Thanks 1
Link to comment
Share on other sites

  • 0

Right, we're getting somewhere!

 

The VM is now booted up into DSM proper, no recover prompt, and I can see all four physical drives on the passthrough adapter :D

image.thumb.png.dd8d034b99ad6cd5f560bca892ee2c4d.png


 

 

However:

  • disks are numbered starting at 2 (as mentioned previously, DiskIdxMap seems to have not worked with it starting at sdb). This is, of course, cosmetic, and doesn't seem to affect the operation of the system
  • it's saying system partition failed for the first two disks

Also:
image.thumb.png.2ac297d09757238c169517cf573b9cfb.png

 

I let Storage Manager repair the system partitions and it was fine after 5 minutes syncing with the other disks.

 

I think this is all finally done, now. Thanks for everyone's help, I've learned a huge amount doing this.

Edited by WiteWulf
  • Like 1
Link to comment
Share on other sites

  • 0
19 minutes ago, WiteWulf said:

Right, we're getting somewhere!

 

The VM is now booted up into DSM proper, no recover prompt, and I can see all four physical drives on the passthrough adapter :D

image.thumb.png.dd8d034b99ad6cd5f560bca892ee2c4d.png


 

 

However:

  • disks are numbered starting at 2 (as mentioned previously, DiskIdxMap seems to have not worked with it starting at sdb). This is, of course, cosmetic, and doesn't seem to affect the operation of the system
  • it's saying system partition failed for the first two disks

Also:
image.thumb.png.2ac297d09757238c169517cf573b9cfb.png

 

Am I safe to let it repair those two disks?

 

Yes, please proceed with the repair.

  • Like 1
Link to comment
Share on other sites

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