Leaderboard

I had couple of troubles with my installition with a good google search, I have found out couple of fixes. I have combined them into one script. This will be easier for many beginners. I am not really good Bash script writer but this is just fine. I have tried couple of times. Tried on DSM 6.2.3 with Juns 1.04 Loader on a Vm. Use it with caution. https://github.com/Jlozde/Xpenology-6.2.3-EasyFix Usage: wget https://raw.githubusercontent.com/Jlozde/xpenology-6.2.3-easyfix/master/patch.sh chmod +x patch.sh ./patch.sh reboot & reindex Thanks to;

SHR is for Synology Hybrid Raid, so yes it's only for Synology (and Xpenology of course). I don't know anything about QNAP - my suggestion is to google it. SHR is nothing about stability or self healing. SHR lets to use full disks capacity for different size disks. If you have all disks of the same capacity SHR is pointless. Synology or QNAP? Qnap has it's features as well - for sure you can install additional software as well (Entware?). Biggest benefit of DSM (Synology/Xpenology) is number of android/ios apps to access data remotely. Everything else can be achieved on any PC setup with Open Media Vault. And one more word about Xpenology - studying forum is needed only to find hardware that you could use + information how to prepare USB stick with bootloader.

yes and NO its a combination a two standard tools in linux, mdadm and lvm2 (and the file systems ability to "grow") any linux should be able to read a SHR volume, the special of synology is automatically creating and extending things without the user having any trouble or even seeing how its working (but it needs some basic understanding of the matter - your example with 3 x 8TB and adding a fourth disk in a 4 disk units will not work as the added bigger disk part over 8TB will not have redundancy and would not be used in a SHR, only if one the three 8TB disks is also replaced with a bigger disk you would be able to user the additional space because there would be space of two disks above 8TB and that would be a raid1 - i'd suggest reading synology's article about SHR as intro) it would be possible to do all this (creation and extending of SHR volumes) manually, but it would need some knowledge about the tools used the clever scripting and using the ability's of linux is what makes it SHR if something goes wrong such volumes more difficult to recover, nothing serious for professionals but can be a challenge for 1st timer's but in a well organized nas world there is also a backup, resulting in no or very little need for recovery of broken volumes especially when usig old and unreliable hardware there is a higher chance of things going south, there is a reason why server hardware is of higher quality (and the nas is a server), using desktop hardware can be a risk, if its worth the money is on the user to decide (some go with ecc ram, some use more proven controller, ...) no, seems no other nas company is pursuing this also synology disabled this feature in the business hardware running dsm look for docker support, that way the "extension" in question depends not on the brand as it's seen with synology or qnap specific packats maybe look into open media vault as alternative, way more open and might be easier to handle dsm is a closed source appliance and has some problems because of this (and its hacked so from time to time synology "act's", usually with new major versions)

@Steveyg777: if you're update freak then you should go with Synology and actually you always may consider some older models . As from observations, Synology supports their devices with DSM updates for 6-7 years, so even with models from 2017-2018 you would have better guarantee of future updates then with Xpenology. With Synology you also have easy access to your NAS with Quick Connect which is not supported on Xpenology and on Xpenology you have to use DDNS or Virtual LAN (like ZerotierOne). Sometimes also you may experience hardware compatibility issues, installation issues etc. To avoid that you have to spend time studying forum, tutorials, installation reports etc. When you decide what hardware to use, only easy part left - prepare loader (which takes maybe 15-30minutes) and set up your Xpenology NAS the same way as you would do with Synology. Xpenology also has it's benefits - you can use better hardware then any genuine Synology device, you can use very cheap old PCs (I spent 50 quid for my HP Gen7 Microserver) and install pretty new DSM. So it's not so pointless to use Xpenology, but building it isn't for everyone. You must want to learn some knowledge, and decide to live with some weaknesses of it. In terms of usage and maintenance and rescuing data there is no real difference. Just to remember to not update DSM without checking if it's save and how to do it. So actually Xpenology if installed by someone who know the rules can be administrated by anyone with just that simple rule - to not do firmware update. Everything else is normal - packages updates, management etc. Maybe I'm writing a bit chaotic way - sorry I'm getting old.

thats a big fat NO, updates usually is a "it depends" and for now dsm 6.2.3 update3 is the last version you can install (6.2.4 and 7.0 beta do not work with the current loader and there is no sign for a new loader), accidental update can be a lot more trouble then you can handle (or might willing to handle) if some command line for linux and bios settings are "geeky" then i'd suggest a original unit from synology or qnap, in most cases a 4 drive unit with 2-3 big enough disks should do it (there are 16TB disks available) i'd also suggest just reading the synology faq/knowledge base, they have good information and schematics about things like SHR or raid in general not sure if it has to be synology - qnap has also reliable hardware and nice looking easy to handle gui with plugins/packages if you just want to USE a nas and don't want to learn about linux, hardware and the inner workings of a nas then imho you are batter off using a original unit

@asdvsss Nein, sorry. Ich weiß auch gar nicht mehr genau wie ich das hinbekommen habe Habe mich grob an eine Anleitung aus dem Unraid Forum gehalten. - Linux VM - I assigned 1 core (2 threads) to the VM - Q35-2.11 (Q35-2.9 works too) - OVMF - put the synoboot.img to you primary vdisk location, USB Bus - another disk (either vdisk or actual disk) in 2nd vdisk location, SATA Bus - go to XML view and edit the network line <interface type='bridge'> <mac address='XX:XX:XX:XX:XX:XX'/> <source bridge='br0'/> <model type='e1000e'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface> Damit hat es dann bei mir funktioniert. Wichtig ist, dass man nach jeder Änderung an der VM per XML wieder den Model Type auf e1000e ändert.

Да завсегда на здоровье ....)))

Добавил в комплект 8.2.7 https://mega.nz/folder/q80zQATS#1VAWvg4Dr0rfSnRjM5X9pQ Vir-US спасибо тебе огромное за труды!

Fixed with this

For those Linux newbs who need exact instructions on installing the script, follow this here. Please be VERY careful with syntax especially when working as root. If you have not turned on ssh in Control Panel remote access, do it Download putty or other ssh terminal emulator for ssh access Connect to your nas with putty and use your admin credentials. It will give you a command line "$" which means non-privileged In File Station, upload FixSynoboot.sh to a shared folder. If the folder name is "folder" and it's on Volume 1, the path in command line is /volume1/folder From command line, enter "ls /volume1/folder/FixSynoboot.sh" and the filename will be returned if uploaded correctly. Case always matters in Linux. $ ls /volume1/folder/FixSynoboot.sh FixSynoboot.sh Enter "sudo -i" which will elevate your admin to root. Use the admin password again. Now everything you do is destructive, so be careful. The prompt will change to "#" to tell you that you have done this. $ sudo -i Password: # Copy the file from your upload location to the target location. # cp /volume1/folder/FixSynoboot.sh /usr/local/etc/rc.d Make the script executable. # chmod 0755 /usr/local/etc/rc.d/FixSynoboot.sh Now verify the install. The important part is the first -rwx which indicates FixSynoboot.sh can be executed. # ls -la /usr/local/etc/rc.d/FixSynoboot.sh -rwxr-xr-x 1 root root 2184 May 18 17:54 FixSynoboot.sh Ensure the file configuration is correct, reboot the nas and FixSynoboot will be enabled.