Jump to content
XPEnology Community

Chrunchy

Banned (spammer)
  • Posts

    8
  • Joined

  • Last visited

Everything posted by Chrunchy

  1. Another update: The script has now been merged, so no manual changing needed anymore. Just run the patch as described in the first post.
  2. Update, it still works with DSM 6.2.3 25426-2 - just needs a little "fix" in the patch.sh file to include that version. I made a pull request and hope Jlzode accepts it https://github.com/Jlozde/Xpenology-6.2.3-EasyFix/pull/1/files
  3. Ive been using this with success, but at sometime it broke - i guess after some DSM update as i now have 1247 items waiting to "be discovered". Tried running the patch, but seems it's incompatible with 6.2.3 25426-2
  4. Hi, I have some minor issues i hope to get some help on being fixed. I'm running ESXI 6.7 with DSM 6.2.3-25426 U2 (bootloader 1.04b, DS918+), with a sata controller passed through to DSM to handle the disks. There are 5disks running in a SHR volume, and another disk for a second volume with no raid etc. 1. DSM always needs to be recovered, when being powered on. If it's rebooted, it boots into DSM directly as its supposed to. The recovery is always fine, but rather annoying it needs to be recovered if i powered off the VM host or did some minor changes. I noticed that when rebooting, the bootloader acknowledges my 10sec timeout during boot - but it's more like 1 second when being powered on from off state. 2. DSM Storage manager sees the synoboot.vmdk 5mb file as drive 1. One solution i read is to change the controller location, to lets say disk 20. But that results the DSM to go into recovery state upon boot, and keeps failing when trying to do so. Does anyone know a "fix" for these issues on this booatloader and setup? Thanks in advance.
  5. wdawd It is possible, however you need to re-enable it in a config through terminal (SSH/telnet). https://xpenology.club/enable-shr-in-dsm-6/
  6. Chrunchy

    DSM 6.2 Loader

    Thanks for that! it pointed me in the right direction atleast - i got around it by setting the vm disk as sata 0:20. Does DiskIdxMap also work with 1.04b? When reading the post it indicates that it's already written in the grub file as hex 0C. Mine however didn't contain anything related to DiskIdxMap. Atleast now works, and VMXNet3 flawlesssly too 🙂 (Reason i moved to DS918 loader from 3617) Thanks again
  7. Did you ever find a solution to this? I'm running a similar setup, but i really want to get rid of the bootloader disk inside DSM as its hogging /var/log/messages because it can't read it's data (temperatur etc).
  8. How are your guys network setup for your Xpenology to your other VM's or even your esxi host? I've been using esxi's E1000e since VMXNET 3 doesen't work on 6.2.2, but i sure miss faster filetransfers than 1gbit. In my search to be able to transfer files faster than 112MB/s to a windows VM i'm primarily using, i tried passing through a 10gbit NIC (Intel X550) and it was detected by xpenology just fine at first boot. I passed another 10gbit NIC to my Windows server VM and was able to transfer files with ~4gbit between the two VM's. This setup however requires me linking a networkcable from one NIC directly to the other since i don't have any 10g switch. Windows VM: 1x 1gbit Intel i350 NIC passed trough for internet/LAN network. 1x 10gbit NIC passed through - networkcable connected directly to Xpenology VM assigned 10gbit NIC. Xpenology VM: 1x esxi E1000e for general internet/LAN network. 1x 10gbit NIC passed trough connected directly to Windows VM's assigned 10gbit NIC. Are there any other solutions than the above (Besides buying a 10g switch) ?
×
×
  • Create New...