Jump to content
XPEnology Community

Polanskiman

Administrators
  • Posts

    2,598
  • Joined

  • Last visited

  • Days Won

    108

Community Answers

  1. Polanskiman's post in update question was marked as the answer   
    Not sure what hack you did since you do not detail it but if I am not wrong you simply modified the synoinfo.conf file. That means that after (usually) a major update the file will be overwritten with the one contained in the update thus crushing any edits you did to it. Here is a way to overcome this:
     
     
  2. Polanskiman's post in N54L 5.2 5967 Update 9 upgrade... was marked as the answer   
    Well I believe that tutorial I made is rather explicit on the matter and if you read you will see many people have updated their N54L. After the upgrade don't forget to delete the .xpenoboot directory that will be located in the root of your machine. Simply SSH in and delete it. That is a reminiscence of the old xpenoboot loader and will create problems if left there.
     
    Since you are running an AMD based machine make sure you have the C1E disabled in the bios if you upgrade else it wont work.
     
    If you decide to upgrade beyond DSM 6.2 (DSM 6.2.1) then your will also need an Intel NIC. People use the HP NC360T and works fine. Install it before the update.
     
    I suggest reading the threads in here: https://xpenology.com/forum/forum/78-dsm-updates-reporting/
     
     
    As for the above comment, all versions will have bugs and patches following discovery of the bug. This brings me again to the link posted earlier. Read this sub forum: https://xpenology.com/forum/forum/78-dsm-updates-reporting/
  3. Polanskiman's post in Registering my Xpenology Serial number on Synology was marked as the answer   
    The question(s) in this topic have been answered and/or the topic author has resolved their issue. This topic is now closed. If you have other questions, please open a new topic.
  4. Polanskiman's post in DSM web-ui stopped working was marked as the answer   
    Ok you need to download the 3617xs DSM6.1.7-15284 PAT file (version you are currently using) and extract the libsynopkg.so.1 and the libsynoshare.so.6 files and remplace those in your box with these ones.
    Once you have replaced them run this:
    chmod u-w /lib/libsynopkg.so.1 /lib/libsynoshare.so.6 Then run synoscgi It should now work. Reboot your machine for good measures and for all services to start normally. To reboot run this: reboot now You can use 7-Zip to unpack the PAT file and the hda1.tgz archive under it. You can use scp or wget or curl to copy the 2 files to your box or anyway you see fit.
     
    I highly recommend you migrate to 3615xs unless you have specific needs for 3617xs.
  5. Polanskiman's post in Can hard disk with bad sectors still be used? was marked as the answer   
    If the HDD has bad sectors it will only get worse. That HDD should not be part of your raid or you might regret it sooner rather than later.


    Sent from my iPhone using Tapatalk
  6. Polanskiman's post in Bootloader 1.02b to 1.03b Tutorial? was marked as the answer   
    No such tutorial, but as you said it's the same process than with v1.02b. I suggest you read the new loader thread just to make sure you are not missing anything.
  7. Polanskiman's post in SSH to 1.02b loader not DSM? was marked as the answer   
    No you can’t SSH to the loader. Have you tried login in with your admin credentials through SSH? I suspect the ssh deamon is still running. Try a reboot.


    Sent from my iPhone using Tapatalk
  8. Polanskiman's post in DS916 vs DS3615 vs DS3617 was marked as the answer   
    You might not have searched much because the answer is in the FAQs of the forum:
     
  9. Polanskiman's post in Lien vers DSM_DS916+_15284.pat (6.1.7) was marked as the answer   
    https://archive.synology.com/download/DSM/release/6.1.7/15284/
  10. Polanskiman's post in Jun loader 1.03a2 was marked as the answer   
    In principal your data should be safe. A migration WILL be required though since the model he postes is DS918+ and that is a new model that was never released before on XPEnology. Most settings will most certainly be reset and DSM will be installed from scratch.
     
    Note that the loader is still in alpha stage and Jun hasn't made any announcement about it so I advise caution. 
  11. Polanskiman's post in DSM_DS3617xs_15284.pat was marked as the answer   
    You are advised to provide transparent links. No redirects even pointing to official sources.
     
    @cyberdott Those are not official download links, at least not the way they have been provided. See my comment above.
    Some basic search on the forum would have yielded the info you were looking for. If Synology has not yet made the PAT file available then it is clear you should not be downloading it. Patience is a vertue.
     
  12. Polanskiman's post in How to get correct system Info in DSM (CPU, RAM, Serial) was marked as the answer   
    Answered countless times. There is no need to change the serial number and the CPU information is hardcoded so you wont be able to change it. It's simply a cosmetic issue. Your CPU's actual specs are actually being used by DSM.
  13. Polanskiman's post in update 6.1.4 to 6.1.6 dsm xpenology with latest JunLoader v1.02b was marked as the answer   
    Keep an eye in the section linked below and you shall get your answer soon enough:
    https://xpenology.com/forum/forum/78-critical-updates/
  14. Polanskiman's post in Emplacement Disque was marked as the answer   
    Non ça ne vient pas du fichier synoinfo. La raison vient du fait que le contrôleur de disque déclare les 2 premiers ports comme étant autre que les 4 ports SATA visible sur la carte. J'ai déjà vue cela dans d'autres installations et parfois changer AHCI à IDE permet de solutionner la chose. Essayez de désactiver d'autres options dans BIOS et vous verrez si cela fini par s'arranger.
    Quoi qu'il en soit cela ne pose aucun problem de fonctionnement.
  15. Polanskiman's post in quel version de loader prendre pour vm workstation? was marked as the answer   
    @matou83 Ca sera du pareil au même. Utilisez DS3615xs car plus répandu dans le communauté.
  16. Polanskiman's post in How can I change xpenology model to RS18016xs+? was marked as the answer   
    I believe you wont be able to because if I'm not mistaken it is hardcoded same as the CPU specs/speed. The only way would be for you to modify the source code and then recompile the kernel. This would only be a temporary fix as you would need to do this at every major upgrade of DSM.
  17. Polanskiman's post in My Nas not appear in network location was marked as the answer   
    @Water The Media Server package needs to be installed and running for that icon to come up. If it's not the case then install it in the Package Center first. Then on your computer go to the Computer tab in Windows Explorer >Access Media > Connect to a media server. Let it install. When finished refresh the window and voila.
     
    Google could have help: https://forum.synology.com/enu/viewtopic.php?t=109576
  18. Polanskiman's post in Apollo Lake J3455 need 918+ image was marked as the answer   
    I do not think that jun will release a 918+ loader. It's not just about creating an .iso. The loader would need to be customised with its own patch for the corresponding kernel of that model.
×
×
  • Create New...