jensmander

Members
  • Content Count

    364
  • Joined

  • Last visited

  • Days Won

    18

jensmander last won the day on October 11

jensmander had the most liked content!

Community Reputation

91 Excellent

3 Followers

About jensmander

  • Rank
    Super Member

Recent Profile Visitors

2,472 profile views
  1. Does your NIC indicate any activity when the system boots? If not then it’s not recognized by the drivers.
  2. Schau mal in die Update Report Threads. Darin finden sich Angaben zu Board/Cpu/Nic usw. Die meisten Boards neuerer Bauart funktionieren, meist hapert es nur an den onboard Nics.
  3. Bei solch einem alten Chipsatz offenbar nicht. Wahrscheinlich sitzt ein Intel P4x auf dem Board, dessen Southbridge schlichtweg nicht voll kompatibel ist, da bereits über 10 Jahre alt. Mit anderen Distros wie OpenMediaVault könnte es vielleicht besser klappen, da Debian eine umfassendere Treiberunterstützung mit sich bringt.
  4. Yes, always advisable. You can choose your current setup/hardware with a simple procedure: - shut down Xpenology - unplug all HDDs/SSDs - insert a (small) unused HDD/SSD and plug in the cables - start your system with your current boot stick and install DSM on the test drive - reboot, set up the necessary features (user, password) and install (if an older pat file has been used) the newest update - if everything is still working after the reboot (especially the network) you‘re almost safe to update your production system - shut down the system, unplug the test drive, reconnect your HDDs/SSDs and proceed
  5. The TS mentioned that his bootloader is bricked. This means that the NAS can not boot the normal way. @perroloko: afaik you‘ll have to do some „engineering“ on the flash module. The image is in the PAT file which can be extracted (PAT files are similar to TAR). Take a closer look on this thread: https://community.synology.com/enu/forum/17/post/69287
  6. To be sure I would change the serial in the grub.cfg too. In my test the original Synology 918+ never had any issues after this.
  7. You can assign a drive letter to the first partition of your boot stick with freeware tools. One of it is the MiniTool Partition Wizard (look at the thread Xpenology Tool for Windows...). Start the tool, right click on the first partition of your stick and choose „assign drive letter“. After that click on „apply“ on the upper left menu. Now you can browse into the grub folder, open, edit and save your grub.cfg. Once you‘re done go back to the Partition Wizard, right click the first partition, „assign drive letter“ -> none and apply. No rocket science 🙂
  8. I made a test with a real 918+ I bought and a Xpenology (flashed the MACs to an Intel dual port NIC, serial and same MACs in grub.cfg). Only one system was online, never both of them. At first I could login to my Synology account within DSM on the Xpenology, but didn’t activate QC. Shut down the system and started the real 918+ for the first time. After a few hours I shut it down, powered on the Xpenology box and after that I couldn’t login to my Synology account within DSM anymore (login window displays a spinning circle forever). The same happened with a DS3615. So I think there are many ways for Synology to keep an eye on „fake“ boxes beside serial numbers and MACs.
  9. Afaik the Z400 series supports UEFI even on older models. And most of them have the Intel AMT onboard (useful for remote power cycling/reset, etc.).
  10. If you‘ve disabled the built-in admin account then it’s obvious why the SynoAssistant can’t connect/login. What do you mean by „new base IP“? Is it only a different IP or a different subnet? Subnet means the typical 192.168.xxx.yyy for private networks. If you’re on the same subnet as before then you should be able to login into DSM by entering the IP address of your Xpenology box in the browser‘s address bar. Afaik the SynoAssistant scans only the subnet you’re in and doesn’t hop or search other networks. However - if you’re on a different subnet now you should assign a static IP of your old subnet to your PC, login to DSM and change the IP according to the new subnet. For example: Old subnet: 192.168.0.0/24 New subnet: 192.168.10.0/24 If your Xpenology had 192.168.0.123 as the old address then you can change it to 192.168.10.123. This is only an example. Check on which subnet you are and which IP (last three digits) can be used/is free.
  11. Yep. For apps like Video Station/Moments/Photostation a valid combo is required for video conversions and thumbnail creation.
  12. I doubt that you can use a Rackstation as an expansion device. The expansion units have different boards inside the case which have nothing to do with the normal mainboards. You can think about iSCSI/LUNs in combination of Xpenology <> RS812.
  13. Bei echten Servern solltest Du schauen, dass ein „it mode“-kompatibler Controller verbaut ist. Zwar werden einige RAID Controller erkannt, es empfiehlt sich jedoch der Einsatz von HDDs im AHCI Modus bzw. 1:1 Passthrough durch Host Bus Adapter. Einige RAID Controller mit LSI Chipsatz lassen sich in den besagten IT Mode flashen und agieren dann als HBA. Die NICs sollten neben der CPU (je nach gewünschtem Loader) natürlich auch passen, dann sollte alles klappen.
  14. Hm and why not the Synology chat? It has some useful features and (together with emotions and hashtags, screenshots, etc.) some kind of „social media“ touch. It can be backed up with HyperBackup regular and is relatively good maintained.
  15. 1st) It‘s not necessary to double post the same question in different sections. You already asked this question here: Once you opened a thread you should wait until someone can give you an answer. Please read the forum rules and FAQ @Polanskiman set up. 2nd) There are some XMPP packages available in the synocommunity. But most of them are relatively old or do not provide click and run functionality. I doubt that you can achieve something simple in comparison to widely spread messengers like the one from FB. Another problem: a simple and available client for desktops and smartphones. And the willingness of your contacts to install and use it. In the end you have to rely on a web based solution which is usually not widely accepted by users. You could search the Docker repos for an appropriate solution, like prosody.