jensmander

Members
  • Content Count

    197
  • Joined

  • Last visited

  • Days Won

    9

jensmander last won the day on April 21

jensmander had the most liked content!

Community Reputation

60 Excellent

2 Followers

About jensmander

  • Rank
    Advanced Member

Recent Profile Visitors

1,734 profile views
  1. I doubt that the loader/DSM will recognize the controller. I would also stay with soft RAID whenever possible. The usual low-end controllers have no benefits. There are several drawbacks compared to soft RAID: - DSM will not be able to detect failing drives - if your controller dies you’ll have to find and buy a compatible spare part to regain access to the RAID - you’ll have no speed advantages A soft RAID can be mounted in any other Linux system in case of failure. Unless you‘re not playing around with large ssd arrays including an adequate controller (like Avago‘s 9361-8i for example) you‘re doing yourself not a favor. Just my 2 cents.
  2. You can use an external drive for HyperBackup but it must be large enough. Usually the individual user storage setups are much larger than the typical usb hdd. So that would lead to the solution @flyride mentioned above: an additional system for backups (either another Xpenology or an rsync compatible system like OpenMediaVault etc.). A backup or copy of your current usb boot stick (or the synoboot.img you modified) and regulary backups of the system configuration (can be done from Dsm‘s control panel) are an additional step. A simple approach for testing updates would be a separate hdd/ssd. Install the current stable and working version for your system on it and in case of an update thought just use only this drive and disconnect the current drives (as mentioned before in your other thread). So you could play around with the update and see if it works. Unfortunately there is no simple out of the box one-click solution for Xpenology.
  3. A new usb drive won‘t help because of DSM‘s system partitions on each hdd which contain the „new“ system. There are several methods to get back in business. 1st) Boot a live linux, mount the raid and try to modify the text file which contains the version info (you‘ll have to search the forum for the exact name and path). 2nd) Disconnect all hdds, connect a new one, install the older version of DSM on it, shut down the system, reconnect the old drives and start it again. DSM should recognize the old RAID. 3rd) Hardcore method: delete each system partition (first partition) and reinstall DSM after that. Normally DSM should recognize the RAID array after the initial setup but with no warranty. In case of 2 & 3 all your settings will be lost.
  4. Try to wipe the vdisks and start over. Error 35 usually occurs if there‘s a partition layout which can‘t be deleted.
  5. DSM‘s firewall is disabled by default. Did you define any custom HTTPS ports? Or just the standard setup? I‘m not familiar with EdgeRouters but several NAT errors consist of improper rules. Did you try to use <your-ddns-address>:9901 in DS Cam or just the ddns-address/external IP?
  6. With such equipment I would use a Hypervisor. Would make more sense. You‘ll have enough power to run Dsm along with other VMs. I have a similar system with Dsm, 4x Win10, 5x Debian and one W2019 nano.
  7. I don’t know if it works ootb with 1.02b but you won’t be able to use the 1.02b with DSM 6.2 (or I missed something). Usually Mellanox cards of this series are supported by Synology.
  8. Should work as any other network card but it depends on the model and if it’s supported by the built-in drivers.
  9. Afaik this card is supported without extra drivers with 1.03b and 1.04b.
  10. I had a similar setup in a bare-metal system. Before I could expand the storage pool the SSD cache had to be removed. Otherwise DSM threw up an error.
  11. Did you unmount the SSD Cache before you added the new hdd?
  12. Yes. With Xpenology you can even change other components like the board and RAM.
  13. jensmander

    DSM 6.2 Loader

    Did anybody encounter the phenomenon of a non-working Intel card (i340-T2, gets no IP) if C-states are disabled in the BIOS (Z97 chipset)? Even if "only" C1E is disabled? Loader: 1.04b
  14. Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.1-23824 Update 6 - Loader version and model: JUN'S LOADER v1.03b (DS3615XS ) & v1.04b (DS918+) - Using custom extra.lzma: NO - Installation type: BAREMETAL | DS3615XS: B150, Z77, Z87, Z97, Z170, C232, C236, HP Microserver | DS918+: B360, Z170 - Additional comments: If you modified your synoinfo.conf in /etc & /etc.default make a backup before you update! On my Z97 board (i7 4770k) the system reboots several times a day if the SSD cache (RAID1) is enabled with loader 1.04b.
  15. Mit Tools wie bspw. MiniTool Partition Wizard Free kann man der ersten Partition des Sticks unter Windows einen Laufwerksbuchstaben zuweisen. Dann kann darauf mit dem Explorer oder Notepad++ zugegriffen werden, um die grub.cfg zu ändern. Nach der Änderung Partitionsbuchstaben mit dem Tool wieder entfernen. MiniTool Partition Wizard ist u.a. auch im XPEnology Tool for Windows enthalten.