DSfuchs
-
Posts
259 -
Joined
-
Last visited
-
Days Won
4
Posts posted by DSfuchs
-
-
2 hours ago, bearcat said:
That might be some of the reasons why he wants to build a Xpenology box
@SrBas97
Your DSM will automaticly be installed on your "data disks", as a Raid1 mirrored across "all" of them.
The drives will get 3 separate partitions during install: 1=System (for DSM), 2=Swap, 3=Data storage, and you do not need to think about it.
If you have a singe SSD, you *can* use it for cache, but just as "read-cache", and depending of usage pattern, it might be un-useful.Regardless of the reading pattern, reading under RAID1 has twice the performance anyway, since two hard drives offer the same content and the second read head is already delivering data even though the other one is still busy. Therefore, a read cache is quite unnecessary under RAID1/RAID10.
-
1
-
-
1. Upload the "vender" file to the DiskStation's general purpose share.
2. Installation of the synocli-file package from here:
https://packages.synocommunity.com/synocli-file/19/synocli-file.v19.f15047[apollolake-avoton-braswell-broadwell-broadwellnk-broadwellntbap-bromolow-cedarview-denverton-dockerx64-geminilake-grantley-purley- kvmx64-v1000-x86-x86_64%5D.spk
3. Now log into the SSH terminal and switch to root:
sudo -i
4. Then mount the internal flash to /mnt:
cd /dev
mount synoboot2 /mnt
cd /mnt
6. The newly installed package includes the Midnight commander.
Call this with mc on the command line.
7. Switch right and get to the new vender file in its directory like /volume1/...
Copy the vender file there to the flash module (/mnt) with F5.
8. Leave mc with F10.
9. back to /root:
cd /root
10. Remove the integration from the flash module:
umount synoboot2
11. Done and reboot with:
reboot -
Yes, the one-time license file specific to the device is corrupt. We have to recreate these.
-
Hello, you've come to the right place, but not at Synology
Can you provide me with the backup of the DOM for review? If it is uploaded, send me a PM please.
-
52 minutes ago, SrBas97 said:
I still don't know where to install the OS, whether on the data disks or on a separate disk
You can't control this, it is written mirrored to at least the first two hard drives.
-
There is not enough RAM in your DS220j. In addition, the CPU is too slow. The right device is the DS223j, where 2.5GbE also works via the USB port.
If the processor should be an Intel one, the DS224+ is the device of choice.
-
2 SSDs are required for a cache, as they must be mirrored. This only makes sense if they are enterprise SSDs with SLC memory that does not wear out.
The "DSM" operating system is installed on both drives for data. You set up a RAID1 as normal, just not SHR! -
SSD cache doesn't work, it's also unnecessary because of mirroring. I use a 3rd drive as parity of a mega-fast RAID4 stripe.
-
32 minutes ago, reiou said:
Thank you for your replies.
I'm sure I can get around the lack of QC via actually setting up my environment/network to properly support external access. And regarding updating DSM to a higher version, I will try to update to the latest supported with the single free hard drive method you suggest.
Out of curiousity, what are our device options for modding? Modding DS412+ to DS713+ and RS814+ both worked successfully. What other devices are we able to use? I'm wondering if we can go up to DSM 7.2 (or higher in future...?) on the DS412+ by using other devices.
But we can take advantage of the lack of quality control ;-). A little play on words here with QuickConnect and Quality Control, hope you know what I mean.
The device options for the Intel Cedarview CPU are already at the end, because there is no newer model that supports DSM >=7.2.
-
Since the update problem has nothing to do with modding, the manufacturer is responsible. I would only try with a single otherwise free hard drive. When the level is reached, I would then plug in the correct hard drives.
-
7 hours ago, reiou said:
One other question: Does this method to move the 412+ to DSM 7 prevent the use of QuickConnect? I was using it for DS Audio but can use an alternative method if QuickConnect can't be used and there is no workaround to use it.
QC only works with a valid combination of model/serial number/MACs. The model has been changed so it no longer fits. Interestingly, there are no problems if the same real device is listed twice in different Synology accounts. The manufacturer doesn't check it.
-
10 hours ago, reiou said:
Update that as I didn't have any essential files remaining before I tried this process, I just rebuilt the storage pool. Issue 1 is resolved, so just issue 2 now.
Cannot update to latest DSM Version: 7.1.1-42962 Update 6 -- would like to fix and upgrade it instead of rolling back to DS713+ if that is possible.
If you mess up your hard drives, only the "cat /proc/mdstat" command will be able to help you, but not the GUI.
-
@StandBugz Did you expand the original DOM and read it externally as an image?
Was the image successfully written to the modified USB stick. If yes, can you provide a file list of both partitions?
Otherwise, the first thing to do is to renew the 4 files on partition 2, analogous to the screenshot of the RS814+, with the source:
https://global.synologydownload.com/download/DSM/release/6.2.4/25556/DSM_DS1813%2B_25556.pat
-
21 minutes ago, StandBugz said:
Nice!
yesterday I tried to change VID & PID with an old 1GB Mem-UP stick with success, F400 wrotten. But the DS1813+ won't start...
so I am still looking for solution...
Do you have answers to #6 for me?
-
@StandBugz I checked myself. I have a DOM of my DS1815+, from which we can also create a ...13+ or 17+ on a USB replacement.
-
On 4/26/2024 at 5:50 PM, DSfuchs said:
I would like to once again urgently point out the need to back up every DOM of Synology + models. It's done in a few seconds.
Simply run via SSH with root:
dd if=/dev/synoboot of=/volume1/myShare/DS412+synoboot-6.2.4u5.img
where "myShare" is your share for general purpose. Of course, it only makes sense if the file is then downloaded from the Synology to another location.
@StandBugz do you have such a backup of your DOM?
How urgent is it, and in which country/time zone are you based?
-
Hello, I have summarized the many requests/problems here, with accompanying model upgrade, in a new topic, you are welcome:
-
Has anyone had the DS224+ run as a DS720+ without any problems?
This will be the last Synology hardware that supports DSM6.
-
Has anyone had the DS224+ run as a DS720+ without any problems?
This will be the last Synology model that supports DSM6.
-
In order for DSM 7.2 to be available to you, you need model modding on one of the following models:
DS1517+
DS1817+
RS818(RP)+
RS1219+
RS2416(RP)+Take a look at this in the related topic:
https://xpenology.com/forum/topic/70401-synology-plus-series-internal-flashdom-repair-and-model-modding -
Ja, das geht. Auch kannst Du direkt ein modding auf ein 18/19er-Modell mit machen.
Dafür habe ich dieses Thema hier aufgemacht:
-
Ist das Problem behoben?
Wenn nein, dann schreibe mal bitte welche CPU verbaut ist, und welcher Lader genutzt wird.
-
Hallo,
eine CPU mit einer TDP von 65w ist als NAS wegen des Stromverbrauchs und der Abwärme ungeeignet. Außerdem gibt es mit INTEL CPUs keine Probleme, um ein neueres DSM zu nutzen.
Alles mit TDP <10w ist sinnvoll. Das geht z.B. los ab
Bei neueren CPU-Familien sollte man nur die "Apollo Lake" wegen der begrenzten Lebensdauer außen vor lassen.
-
I would like to once again urgently point out the need to back up every DOM of Synology + models. It's done in a few seconds.
Simply run via SSH with root:
dd if=/dev/synoboot of=/volume1/myShare/DS412+synoboot-6.2.4u5.img
where "myShare" is your share for general purpose. Of course, it only makes sense if the file is then downloaded from the Synology to another location.
On which disk should I install the operating system?
in General Installation Questions/Discussions (non-hardware specific)
Posted
Now there are trophies if only different words are written for the given answers.