Can you please update the qpkg to support volume selection / migration?

I did it big.

  1. Dual Samsung 860 EVO 1TB in RAID 1 (Mirror). 480 MB/s write, 960 MB/s read
  2. Install QTS with the main array pulled. This creates CACHEDEV1 on the M.2 (desired effect)
  3. power back off
  4. Brought in the main array (this became CACHEDEV2)
  5. Adjusted ALL my share paths to reflect new new real path on CACHEDEV2_DATA (painful) haha
  6. Installed PMS to CACHEDEV1 (since QTS didn’t know about it yet)
  7. Stop PMS
  8. Deleted the Library from within the fresh installed PMS (it’s empty anyway)
  9. 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)

Screenshot%20from%202018-07-17%2001-55-27

Cheers mate, thanks

Sorry, just wanted to ask another question. Did you already have data on your main array when you popped it to install QTS on the M2 Drives??

Yes All 29 TB is on my main array.

I must confess. It’s been several months since I did that and today is one of those “one-legged man at a butt kicking contest” days. :smiley:

A quick reaching out by you to QNAP and they will gladly verify what needs to be done. IIRC, they have a procedure for it too.

Thanks mate, I’ve done a search and so far no info, but I will keep trying. Or just wait for the migration stuff

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?! :smiley:

Plex never ever shows the road map, nor gives an ETA

All I can say is, that this is work in progress, but since it has to be coordinated with other work, we are back to the golden rule of No ETA :wink:

But it will happen!

@Sebastian87

I think you partially misunderstood me.

  1. QTS is indeed always installed on the internal flash which only QNAP can access.
  2. 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.
  3. After installing QTS, inserting the main array instantiates CACHEDEV2 (the main array)
  4. 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:

  1. Default location for apps: CACHEDEV1 - M.2 SSD mirror (M.2 EVO 860 mirror RAID)
  2. Main data storage array: CACHEDEV2 - 8x 8TB WD Red Pro
  3. Plex development: CACHEDEV3 - 2.5" 850 EVO
  4. SSD Cache - 2.5" 850 EVO
  5. Temporary scrap /workspace / chroot env: CACHEDEV4 - 2.5" 1TB WD Black

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

Screenshot%20from%202018-08-08%2017-29-51

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.

2 Likes

Sounds good. Keep up the good work!! :slight_smile:

Any news on this? I sound like a broken record, but my plex library is growing and growing and the speed on the SSD would be so much better.

Please recheck? I released it a while ago

EDIT: I’ll go find it. It was in production.

With the current Plex server for Qnap version there is no option to migrate it.

I’m looking. I see where it was released. I’m tracking down where/why the updated package configuration file isn’t being included.

It is done. The same SDK & config file is used on the ARMv8 Alpha

Which version does support it? I am using 1.13.7.5369

The ARMv8 alpha test is specific to those NAS boxes.

I figured out what’s happening. I’m working on it now.
Give me a few hours please to get this finished? (let the automation turn the crank)

Sure, was just curious what was going on. I have waited for so long that a few hours or a day won’t make a difference. Thanks for your work again!

Were you able to hunt the issue down and fix it - will there be a new qpkg that includes the migrating options today/soon?

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. :slight_smile: 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 :slight_smile:

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.)

I’ll do my best to notify all who’ve asked. There will be big forum announcement for all because it impacts everyone :smiling_imp: