Dual Samsung 860 EVO 1TB in RAID 1 (Mirror). 480 MB/s write, 960 MB/s read
Install QTS with the main array pulled. This creates CACHEDEV1 on the M.2 (desired effect)
power back off
Brought in the main array (this became CACHEDEV2)
Adjusted ALL my share paths to reflect new new real path on CACHEDEV2_DATA (painful) haha
Installed PMS to CACHEDEV1 (since QTS didn’t know about it yet)
Stop PMS
Deleted the Library from within the fresh installed PMS (it’s empty anyway)
Tarball from CACHEDEV2 of PlexMediaServer -> CACHEDEV1 (where QTS had placed it) Emphasis here is that /share/CACHEDEV1_DATA/.qpkg/PlexMediaServer/Library is perfectly in position.
What saved me, and what you may want to do upfront: Do not point PMS at /share/VOLUMENAME/sharename
rather, point it at /share/sharename (which is location independent)
Rather than doing all the above pain (which is what really prompted me to push to get this done), once the new packaging is out, it will look like this (just as you’d expect)
I contacted Qnap regarding the reinstallation of the whole system on the SSD volume without loosing data on the main volume. They answered me and told me that there really is no easy way to do this and also that there are no real benefits. I should just install the App on the SSD volume though the app center.
Literal answer:
"The QTS operating system is actually installed in the unit DOM, and operates from there. Its not possible to install it on the SSD.
If you are considering using the SSD volume as the system volume mainly for application performance, when you first install an application, most applications would ask you to select a destination. All you have to do is select the install destination on one of the shares mapping to the SSD volume.
Other than the default shares, and a few third party applications, there’s no real benefit with assigning the SSD volume as the system volume. The steps to assign it as the system volume is not easy either.
"
So how soon can we expect to be able to migrate Plex?!
QTS is indeed always installed on the internal flash which only QNAP can access.
With the motherboard M.2 SSDs installed and the main HD array pulled, the M.2 SSDs can become CACHEDEV1 on a fresh / reinstall of QTS. This is what I did.
After installing QTS, inserting the main array instantiates CACHEDEV2 (the main array)
a little shell script / command line work and all the shares were re-instantiated at the new CACHEDEV2 location.
It’s pretty easy if you think your way through it.
My system as it now stands:
Default location for apps: CACHEDEV1 - M.2 SSD mirror (M.2 EVO 860 mirror RAID)
Main data storage array: CACHEDEV2 - 8x 8TB WD Red Pro
I can migrate the entire PMS installation from 2.5" <-> HDDs in about 2 minutes
Regarding when you’ll will be able to migrate PMS. none of us can give you the “NSD” date.
The whole system (from building to deployment) has been rebuilt from scratch.
In order for migration to happen the existing, antiquated, QDK had to be replaced.
I’m running that new QDK here.
If you were running the ARMv8 Alpha test systems with multiple volumes, you would see it now. They are running from the new build system because it is in Alpha test.
I can at least show you it is alive
Please do just hang in a little bit longer. This is closer than you might think but I can’t spill any of the juicy details I know everyone wants to know.
Yes, I was able to track it down. I thought the change was also released to existing production. It was released to the new repository/build system only.
I’ve hinted about all the repository work over the summer.
It, plus a major back-end change, is where I’ve been working most of the time.
The ARMv8 was the pilot effort to verify the basics worked.
The rest is about to be available for everyone to beta before we kick it over to full production.
We’re at that frustrating part (candidly said) where fixing one minor thing breaks two others. you fix them and then the original issue is back. Yes, plenty of bloody foreheads here and colorful metaphors are flying. Long story short, we are down to the final days. We thought it would launch last night but I caught one show-stopper.
You’ll have full migration and volume selection on all QNAPs
Sounds good, can you post here once it is released, so that I get automatically notified? I am really excited about this! It is the only reason I added an SSD card and two NVMe SSDs to my Qnap. (I have a TVS-871 with 8x8TB and an Extension unit with another 8x8TB so a pretty large library. The library is over 100GB.)