wolfwood

Members
  • Content count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About wolfwood

  • Rank
    Newbie
  1. wolfwood

    DSM 6.2-23739 Update 1

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2-23739 - Loader version and model: JUN'S LOADER v1.03a2 (DS918p) - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.5.0 Update 1 (Build 5969303) - Additional comments: Updated my test build without problems to latest Update 1 build. Update was fairly quick, everything done within 5 minutes. All docker containers are up and running as well. Haven't used much other options, but that all works so far just fine.
  2. wolfwood

    DSM 6.1.3-15152 Update 7

    No Issues here with update 7. ESXi 6.5.1 2 LSI cards passthrough 13 disks Update from control panel en simpel reboot.
  3. wolfwood

    [SOLVED] 24Bay Supermicro XPEnology

    Works with me. Had 3 controllers with 8 disks each to test the max. Had to use this trick to have it working and it did. Atleast up until patch 8 of latest DSM. Patch 9 I still have avoided at the moment
  4. wolfwood

    ESXI 6.5 guide for xpenology?

    I know that 6.5 works just fine with the vm. I haven't had any issues since upgrading to 6.5 tbh, but I started out with 6.0 and haven't used 5.5 for my DSM VM. Upgrade was pretty easy and after reboot everything worked out of the box. Haven't had the need to tweak anything yet.
  5. wolfwood

    DSM 6 / Esxi 6.5

    For the vm tools, latest version I found is open vm tools is 6.0_10.0.7-1 Maybe a new version will help? I don't have the issue of a 'improper shutdown" with the above tools.
  6. wolfwood

    DSM 6.1.x Loader

    For easy reference, one of the sources I used was this youtube video: Parameters (example names): Datastore name = DSTORE Folder name = RDM Disk name = t10.ATA________WDC_WD20EARX2D00PASB0_________________________WD2DWMC4N2456242 Disk name on datastore = WD2000GB - Start with creating a folder to hold the 'direct' connections to your disk on one of the datastores: RDM - Log in on your ESXi with PuTTY - type: cd /dev/disks - type: ls -l - You'll find all drives connected listed as for example: t10.ATA________WDC_WD20EARX2D00PASB0_________________________WD2DWMC4N2456242 - Identify the drives you'll want to map as RAW LUN (note their names) - type: cd /vmfs/volumes/DSTORE/RDM (or the folder you created yourself) - type: vmkfstools -z /vmfs/devices/disks/t10.ATA________WDC_WD20EARX2D00PASB0_________________________WD2DWMC4N2456242 /vmfs/volumes/DSTORE/RDM/WD2000GB.vmdk Once all the drives are created you can go to your vSphere and you can add a disk - Add drive - Existing disk - Browse datastore to RDM folder and you'll see the created drives from above - Make sure you select Independent (enable) because of direct passthrough (and no need for snapshots etc.) and Persistant is choosen. - And repeat the steps to add drives that way. That's a quick type, but the video shows more information. Otherwise you can also check the following sites: https://www.tumfatig.net/20120226/raw-d ... s-on-esxi/ https://blog.0xbadc0de.be/archives/98
  7. wolfwood

    DSM 6.1.x Loader

    It actually does just fine. Just create a new VM with OS Microsoft (whatever version supports EUFI), add a USB controller and USB device, enable EUFI boot in the advanced settings en have the VM boot in UEFI directly. Then just choose the USB drive as boot disk and have fun. That's what I did. I use 2 USB sticks to run everything: Bootdevice USB1 = ESXi (boots the Baremetal) Bootdevice USB2 = Synology (boots through ESXi in VM)
  8. Just finished a "downgrade" re-installation of 6.0.2 which indeed activated my synology quickconnect (this was without patches yet). Rebooted, no issues at all. Then installed latest Synology patch 2 and rebooted. And still everything works. I'll have to reconfigure it completely (but that's what I wanted to do anyway at some point So all is good now, even after a third reboot.
  9. I know it doesn't work without a proper match as much as I know I can use a custom DDNS This is just a thing I noticed after migrating from 5.2 (with a working setup for synology.me DDNS) to 6.0 with the same SN/MAC no longer working and would rather post it in here so ppl have an idea as if to why something isn't working. Also doing a clean test with 2 disk laying around to test it. See if it works out of the box and after some restarts etc.
  10. After all the updates it worked for me during the day (yesterday). But I had to restart my server last night and after reboot I noticed 2 items no longer working: 1) I changed user setting in "/etc/passwd" and noticed this gets reset after reboot (even though it's changed with "root" user) 2) The above quoted part by bignjato I have as well. I noticed my dsm no longer was connected after reboot and looking further into this that this has to do with getting an api reply to either log in or register the serial number. So if you manually try running "/usr/syno/sbin/synocloudserviceauth -a get -f" I get a message "failed to get a api key". I removed my serial number from the synology website as registered and that didn't do the trick. I then registered the serial number again on the site and still nothing. It should return with an api/ID The serial + mac address I use are the same as the one I used on 5.2 loader. I also tried a new MAC and new Serial, but nothing. Maybe they are inherently different processes on DSM 6.0 then on DSM 5.2. Anyone a clue? I'm thinking of completely resetting my DSM (with some spare disks) to test this out so I'll probably come back with some more results.
  11. I followed the exact steps as described and worked flawlessly on my Asrock MoBo, i7 4770, 32Gb Ram, 2 SSD and 6 HDD's Very much appreciated. Sofar it looks to be working asap! Keep up the good work!