spammy

I find that I only really use the SHR feature of synology - is is possible to extract this functionality to a generic Linux install? I believe it's mountable okay, but the main thing I'm looking for is the management of adding/expanding disks etc. If not, the alternative in mind is to virtualise a very basic Syno install just to manage SHR... but this seems overkill to me. Thoughts appreciated.

Apologies if these were inane questions - if anyone has a link to a source(s) that will help me out that'd be great?

I've acquired some more powerful hardware and wish to transfer my current bare metal N40L (with 4 drives) to a ESXi set up on Lenovo TS140. Some questions if I may? 1) The TS140 has 5 SATA ports. Am I right in understanding that I need one reserved for ESXi, even if I boot off of a USB (virtual host files and config and the like?), leaving a max of four for Syno? 2) I'm currently running nanoboot. Should I simultaneously update that to Xpenoboot? Should I update the Syno software too? 3) I'm using a SHR volume of four drives. Can I just transfer over the HDDs? Will/should these be directly reserved for the Syno VM? I'm sure there's more but I'd appreciate help with the above for now!

So should we be expecting a new XPEnoboot release with this fix?

How did you manage to solve this?

Inception Synology

CAD - you're right. In fact the redundancy part isn't primarily why I run SHR, I use it because for the flexibility it affords in abstracting away from the HW I'm using - I can easily grow volumes as the requirement arises in a way JBOD (puke) and other RAID options might not. That I also get some level of HDD redundancy is a bonus. And at that stage creating a new volume/new disk just for applications (say) seems like a bit of a ballache.

There's no reason why you wouldn't want to protect applications and data with RAID. >At the moment (in hindsight) I don't really see why you would run more than one volume... Flexibility. You may want to have a fast non RAID volume for a responsive use case, a SHR volume for redundant data, and a flash volume for something else.

https://www.synology.com/en-us/knowledgebase/faq/568 "Packages" section. Again, that's not to say that it's not possible.

Plex explicitly states that you will lose hibernation if you install the app, so your efforts may be futile. Perhaps you could disable the auto file watch library update stuff?

Thanks so much! With regards to Get nanoboot boot image, install/upgrade to dsm 4493 I'll be using: http://www.xpenology.nl/hardware-installatie/ and then http://www.xpenology.nl/standaard-installatie-dsm/ I'm assuming that nanoboot's "upgrade" option will keep my volumes?

Sorry for the bump but if I could at least get some tips on 0) and 1) I'd know where to focus my efforts. Thanks!

I'm currently running Gnoboot with a DSM pat directly from Synology. The version is DSM 5.0-4458 Update 2 which I gather is a bit old, but understand to be the latest Gnoboot can run. 0) Does the "volume unmount" issue still exist in Gnoboot? 1) Is Nanoboot the only way to use any version of DSM later than the one I'm using? 2) Does Nanoboot still use patching on the fly to get past the issue? Does it still use unmodified pat files to set up otherwise? 3) Is there a current tutorial or set of instructions to migrate from Gno to Nano in order for me to get these later updates? 4) Should I even bother? Apologies for what are obvious questions, but not only have I searched but I also generally check the forum every day and I'm still not sure what the answers are .

Do we still need nanoboot for this to avoid the "unmounted volumes" issue? I'm still on gnoboot.

Just to be clear - does this patch only work for nanoboot?

I'm running on an N40, but still reassuring to hear your experience with heavier videos. Thanks.

No, all volumes (actually, disks) are redundant and when you installed your second RAID volume DSM was installed to that too... and when you install your new disk DSM will be copied to that. Just follow XPEH's instructions and you'll be okay.

@avpap - I presume you have a Microserver? Which one? Good news if so.

Aha. Seems the misunderstanding was mine. Sorry!

I think there's still a gap in understanding here. The USB is NEVER written to, so the amount of free space you keep on it is irrelevant.

The NL40 (slower proc than N54) serves all my Plex transcoding needs, although the majority of my source files are 720p or less - it manages to transcode at 3-4x so I'm not too concerned. I've not seen any issues with the 1080p sources I have, but I might have been lucky - worst case I can manually transcode these if I really need them. Generally however, as many will tell you here, the solution might be to look at the client side and see if they even need transcoding. Ideally they should not. I have 8GB in both of my microservers which is probably overkill, but RAM was cheap when I filled them up.

And just to add - it will probably outlast the HDDs, which is kind of the point of this setup. More redundancy is good!

You would need to do something like: 1) remove one of the disks from the volume (resulting in a degraded RAID) 2) re add the disk as a NEW non RAID volume. 3) copy the contents of the degraded RAID to the new volume 4) re add the degraded RAID disk as a new disk 5) add it to the new non RAID volume. However to qualify this I don't think anyone here would a) condone using a non RAID set up and b) condone using contiguous unprotected space over two disks - your chance of data loss due to disc failure will increase if you do this. My advice is to keep your current set up, and buy another 4TB (now or at a later date) if you really need 8TB. Yes it's painful to have a whole disk given to redundancy, but you'll get over it.

VPN FTW. Yes it'll take a bit of effort to set up, but once you do all these issues go away.

You need to enter chroot. Unfortunately the docs have been lost from the web since synocom updated their website but it's still in the git repo: https://github.com/SynoCommunity/spksrc ... index.html It's a short yet clear doc so have a read. In particular, the command to enter chroot is: >/var/packages/debian-chroot/scripts/start-stop-status chroot Have fun.