bateau

Members
  • Content Count

    48
  • Joined

  • Last visited

Community Reputation

5 Neutral

About bateau

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @Polanskiman, when using downgrade method described by @sbv3000 I end up with dowgraded DSM, but the configuration is all gone. Presumably since spare drive is a clean install, then it's used to replace system partition of the other drives. Am I missing something about how to retain DSM configuration prior to botched upgrade?
  2. +1 to I wish I had seen this thread. 6.2.3-Update 3 fails to connect to network on ESXi with LSI controller in pass-through. Rolling back to Update 2.
  3. I was a dummy and managed to kill my XPE install on ESXi with 6.2.3 Update 3. Could anyone educate me how to roll it back or update bootloader image to bring the machine back? - DSM version prior update: DSM 6.2.3 25426 Update 2 - Loader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.7 Serial log below: Hunk #1 succeeded at 184 (offset 13 lines). patching file etc/synoinfo.conf Hunk #1 FAILED at 261. 1 out of 1 hunk FAILED -- saving rejects to file etc/synoinfo.conf.re
  4. I was a dummy and managed to kill my XPE install on ESXi with 6.2.3 Update 3. Could anyone educate me how to roll it back or update bootloader image to bring the machine back? - DSM version prior update: DSM 6.2.3 25426 Update 2 - Loader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.7 Serial log below: Hunk #1 succeeded at 184 (offset 13 lines). patching file etc/synoinfo.conf Hunk #1 FAILED at 261. 1 out of 1 hunk FAILED -- saving rejects to file etc/synoinfo.conf.re
  5. I was a dummy and managed to kill my XPE install on ESXi with 6.2.3 Update 3. Could anyone educate me how to roll it back or update bootloader image to bring the machine back? Serial log below:
  6. - Outcome of the installation/update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.3 25426 Update 2 - Loader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.7 - Additional comments: Doesn't show up on the network. ESXi doesn't show IP address requested. @flyride, may I trouble you for some assistance? As far as I recall FixSinoboot.sh was applied before.
  7. I don't think I did anything special with my ESXi host. Passed the LSI controller to XPenology and it "just works"
  8. Not a reassuring sign when https://prerelease.synology.com/ blows up with a PHP error.
  9. Hello folks. I'm setting up a new XPenology instance in ESXi using SuperMicro X10SL7-F motherboard with an 8-channel LSI 2308 SAS adapter. Which of the existing loaders/DS models is best suited for this purpose? Just as an experiment I used 1.04b/918+, which appears to have installed without a hitch. However, SAS drives don't report serial/firmware/temp in Storage Manager. From cmdline I can find their basic stats with smartctl -all. EDIT: After poking around the forum it seems that 3617XS might have better support for SAS. Trying that out and so far seems good - n
  10. - Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.7 - Additional comments: Reboot required
  11. - Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Z230 (Xeon E3-1245 v3 - 8GB) - Additional comments: Reboot required
  12. Thank you. That settles it, I’ll boot from USB and dedicate SSD to scratch.
  13. Right now I have ESXi installed on the SSD connected to C224 controller. Should I bother using USB drive to boot from (motherboard has USB-A connector on the board, for conveniently hiding pen drives)?
  14. Would you mind educating me on the concept of scratch disks for ESXi? I have a ton of reading to do on ESXi, but as I understand things so far, I would use a SSD attached to C224 SATA for VM storage (my Linux VMs, synoboot, etc). I would pass through LSI to Xpenology and let DSM own the 8 drives attached to it. The chassis has room for 1 2.5" drive, which ought to be plenty for VM partitions.