Qnap to Qnap Move

Hi all,

I’m having issues with my QNAP TS-453B which keeps crashing and restarted, supposedly something due to Plex transcoding, according to QNAP help desk.

I am planning to upgrade to the TS-453D in hope to make this issue go away.

I will literally be transferring my four HDDs (RAID 10) straight over to the new NAS (server and library are on the NAS).

Will it simply be a case of claiming the server on the new NAS, as file paths etc. should be the same? (although I doubt it will be this straight forward).

I want to ensure I retain metadata, settings, artwork, play history etc.

I’m got pretty much zero experience with command line…

Thanks in advance.

Are you sure this is true? I have had no such problems on my TS-453Bmini (which is essentially the same device but with a smaller footprint).

1 Like

Well, I said supposedly, as that’s what QNAP have advised…

I made a post about this on here about 2 months back and other people did report the same issue.

Have also seen the same complaint on some Plex Facebook groups, so I guess there is something to it.

agh, OK then - bummer.

@ChuckPa can probably answer this.

1 Like

Do not believe QNAP. I have worked with them several times and they are not real good at resolving random crash issues.

I would check your RAM and HDDs, consider changing the firmware and look into reseating components.

I have had QNAP blame Plex only to see my TS-453Be crash and Plex was not even running. For me RAM was the issue, well a combination of a firmware upgrade QNAP pushed out that changed how the QNAP used RAM and my RAM then not being compatible…

1 Like

I originally had aftermarket RAM when the crashes started happening, and I saw other people say this could be the issue. I then switched back to 4GB of original QNAP RAM, however the crashes haven’t stopped, although seem to be less frequent. Have run checks on HDDs and they’re fine too, so I’m stumped.

You might consider a firmware downgrade. Though bad boxes do happen

Is there a specific firmware version that is more stable as such?

QTS 4.3.6.1070 build 20190919 was the version everyone used when they could not resolve the random reboots but that is a bit old and will have security vulnerabilities.

I believe ChuckPa currently uses QTS 4.5.1.1495 build 20201123 as he now considers that a stable build.

I just went to QTS 4.5.2.1594 Build 20210302 and it seems ok but is only a day old, 1566 was not stable.

Oh, I can add one more comment, at the QNAP forums it is suggested to do a completely clean upgrade if nothing else works, that means basically a hard reset / wipe then upgrade your firmware to a known stable version and rebuild your database. Might be worth considering if you have already come to terms with just buying a whole new box, kind of a last ditch effort to save some money, just will cost you time.

1 Like

Morning,

  1. Yes, 4.5.1.1495 is stable for this TVS-1282-i7. I would recommend starting with this version.

  2. QNAP → QNAP migration

  1. If done using direct migration then no reclaiming needed. The migration simply installs new firmware appropriate for that CPU & chassis.

  2. Which memory is in the NAS and how is it configured ?

PS: Not related, HGST drives are junk. One month after warranty expires so does the drive.

Many thanks @ChuckPa, direct migration is supported so hopefully it’s as easy as just swapping the drives over!

In terms of the memory, it’s literally just the original RAM that came with the NAS from QNAP (2x2GB).

The J3455 CPU supports 32 bit physical memory addressing == 4 GB/DIMM. It supports two banks which gives us the 8GB (2x 4GB)

Folks who’ve had random crashes due to memory often have 8GB DIMMs installed (which requires that 33rd , and not existent, bit to address it)

Just to check / verify the RAM. Are you certain both sides click/locked when they were pushed into position? I’ve seen strange behavior if only one of the two latches locks down (incomplete contact by all pins)

I swear you are a certified genius, my TS-453Be is very hard to get both ram sticks locked and this has indeed been an issue!

My issue started when I had two 8GB sticks installed (16GB in total), that’s why I switched back to the 2x2GB original QNAP RAM. I have also taken the RAM out and installed again, to ensure this was done properly, but still get the crashes, albeit less often than when I have the 8GB sticks…

Something isn’t right.

at this point, I’d make a bootable Memtest86+ USB, plug in the HDMI and keyboard, then run the full extended battery of tests.

1 Like

Hi @ChuckPa, I found a good deal on the TS-453D so I gave up on the 453B and switched today.

I recall there being a driver issue with the J4125 CPU when it comes to transcoding, is there anything I need to do to sort this?

Thanks

Hi @ChuckPa, I’ve got myself into a right pickle…

I was trying to play H265 files on a H264 device and it buffered every few seconds. So I shut Plex and edited the Preferences.xml to add the VaapiDriver line.

When I booted Plex back up, it asked me to sign in, and then create a server. The server was the same name as I had before, so I thought it was referring to the previous server. I pressed okay, and realised it had created a new server with the same name. When signed in, all my libraries where should as inaccessible.

I then went to delete the duplicate, but accidentally deleted my previous server, now I don’t know how to get it back!

The easiest way / safest way is going to be through use of the Plex Claim Token method.

On QNAP, it does require you to do a little work.

  1. Stop the server

  2. Settings - Authorized Devices - Server tab

  3. Make certain to delete anything with the server name or the real host name.

  4. Given you likely have a completely new Preferences.xml file due to a typo when you were in it, let’s start over.

  5. Delete Preferences.xml

  6. Start PMS

  7. ssh into the QNAP

  8. Open a new browser tab to https://plex.tv/claim

  9. Copy the claim token to the clipboard

  10. At the command line in SSH, type the following but do not type the ENTER key

curl -X POST 'http://127.0.0.1:32400/myplex/claim?token=

  1. Right-click to paste the claim-xxxxxxx value
  2. Type the closing apostrophe (single quote)

will look like: curl -X POST ‘http://127.0.0.1:32400/myplex/claim?token=claim-xxx

  1. Hit ENTER
  • It will pause for a moment while PMS and Plex.tv communicate.
  • When done, it will print out a whole bunch of “feature flags”

When this happens, the server is yours again.

LOL whatever you are paid it is not enough :wink: