Jump to content
XPEnology Community

Search the Community

Showing results for tags 'restart issue'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Information
    • Readers News & Rumours
    • Information and Feedback
    • The Noob Lounge
  • XPEnology Project
    • F.A.Q - START HERE
    • Loader Releases & Extras
    • DSM Updates Reporting
    • Developer Discussion Room
    • Tutorials and Guides
    • DSM Installation
    • DSM Post-Installation
    • Packages & DSM Features
    • General Questions
    • Hardware Modding
    • Software Modding
    • Miscellaneous
  • International
    • РУССКИЙ
    • FRANÇAIS
    • GERMAN
    • SPANISH
    • ITALIAN
    • KOREAN

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Found 2 results

  1. Hello All, Thought I would quickly post what I have been having trouble with here. I have been trying to get XPEnology to run DSM on VMware ESXi 6.x and 7 (I have also tried all of this on VMware Workstation Pro 15). Every time I get things configured inside DSM, I loose the entire configuration and my RAID Pool crashes upon restart (reboot, shutdown & start). I am presented with the Web Assistant / "Welcome to Synology" screen asking me to install DSM again. Each time this happens I am loosing my configurations. I will admit, I am trying to mod the limits of the system by making changes to the /etc.defaults/synoinfo.conf file. Specifically what I am changing is as follows: Increase of the total number of supported disks: Old Value: maxdisks="12" New Value: maxdisks="40" Telling DSM to treat every volume connected to it as an internal disk (so it can be used in pools): Old Values: internalportcft="0xfff" usbportcfg="0x300" esataportcft="0x3c00" New Values: internalportcft="0xffffffffff" usbportcfg="0" esataportcft="0" As I stated, I have tried this on ESXi 6.x, ESXi 7 and VMware Workstation Pro 15. I am experiencing this issue in each environment. This makes me thing that some process may be trying to check the integrity of the synoinfo.conf file... no sure of this at all however. Has anyone else experienced this issue? Any advice or guidance anyone may be able to provide would be greatly appreciated. Best,
  2. Hello, Did some of you found how to get the DSM (6.2.2+) restart and shutdown functions to work correctly? Is there something related to BIOS version(s) or settings? Or the issue is in the DSM software itself? I've updated successfully to 6.2.2-24922-3 on bare-metal systems (both with 1.03b bootloader & DS3615xs and additional HP NC365T Quad Gigabit Intel NIC): HP Microserver G8 with latest BIOS (04/2019). Tried No C-States setting at CPU power management, but behavior is the same HP Microserver G7 N54L with modded BIOS 041 (2013, Kamzata version). I've tried ACPI 1.0/2.0/3.0 with no success. C1E and PCI-E power management were already disabled (no worky without them disabled) I've seen many users with successful bare-metal updates and wanted to ask if anybody knows more about the shutdown/restart issue... Thanks, Chris
×
×
  • Create New...