Jump to content
XPEnology Community

flyride

Moderator
  • Posts

    2,438
  • Joined

  • Last visited

  • Days Won

    127

Community Answers

  1. flyride's post in Disk Health Info: remove / reset disk reconnection count was marked as the answer   
    Edit /var/log/disk_overview.xml
  2. flyride's post in 6.2.x Loaders (DS918+ & DS3617xs) finding nothing [VMware] was marked as the answer   
    Which loader and DSM are you trying to use?  Recommended VM type is "Other 3.x Linux 64-bit" for ESXi, but I don't know if that translates to VMWare Workstation.
     
    EDIT: It would appear from topic that you have tried both 1.04b/DS918 and 1.03b/DS3617.
     
    I recommend 1.04b/DS918 and vmxnet3-equivalent NIC (not sure what VMW "host" type is), or 1.03b/DS3615 and e1000e NIC type
  3. flyride's post in System Partition Failed?? was marked as the answer   
    The "System Partition" is the DSM generic term for the reserved space for DSM itself and its swap area.
     
    This is actually manifested as an "n-disk RAID 1" across all disks in your system.  In other words, you have a mirrored array across all disks for the DSM partition and another one for the swap partition.
     
    Anytime something happens to break either array, DSM will report that the "System Partition" has failed, and will immediately remirror it.  As long as you have one array member that is intact, it will rebuild successfully.  And if you don't have at least one array member intact, DSM will already have irrevocably crashed.
     
    So it's a bit of a noise about nothing.  Just click the button to repair, or let it fix itself.  Your data is not at risk, but make sure the error is corrected prior to replacing another drive.
  4. flyride's post in Troubles to acces via ubuntu to my volumes was marked as the answer   
    A new DSM installation won't overwrite your data unless you explicitly authorize it to clear the disks.  Proceed carefully, however.
     
    DSM is not a backup, always have your data somewhere else in the future!
  5. flyride's post in Only 1.02b works, 1.03b and 1.04b don't. was marked as the answer   
    First, use the 3615 PAT file not the 3617, the latter has problems.
     
    Second, 1.03b/DS3615 and DSM 6.2.1 requires an Intel NIC recognized by the e1000e driverset and disable the onboard NIC.  I haven't heard of any other network card working with this combination thus far.
     
    Third, the DS918 PAT file (1.04b loader) requires a Haswell CPU or equivalent.  I'm not sure when the processor extensions added in Haswell were implemented on AMD but suspect your chip is not compatible.
     
    To your last question about whether 6.2 is a necessary upgrade, not really IMHO.
  6. flyride's post in Set static IP address on Bootloader was marked as the answer   
    You will initially need a DHCP server for installation.  Once installed you can change to static with no problem.
  7. flyride's post in How to Model Type Change? was marked as the answer   
    You can use 1.03b on DS3615 as long as you have an Intel NIC in your system and use BIOS mode for boot, not UEFI.
     
    This might help you.
  8. flyride's post in DSM running on ESXi shows loader HD in Disks was marked as the answer   
    Make sure you are selecting the ESXi boot option from the console.  Then make sure the boot image is drive 0:0
  9. flyride's post in how to reset without loosing data? was marked as the answer   
    What exactly are you trying to reset? You can reset to default settings from Control Panel within DSM, with no risk to data. [Edited by Polanskiman]
     
    Also this will work:
    sudo /usr/syno/sbin/synodsdefault --reset-config  
    Options:
    Synology DS Default Reset Util. Usage: synodsdefault   --reset-config      Reset DSM configs.   --reinstall         Reset to reinstall DSM.   --factory-default   Reset to brand new DSM. Include remove all data volumes.   --help              Show this help.  
×
×
  • Create New...