okay sir
I wonder if the replacement drive has any impact on moving the data. Let me check if this is something weâve looked at.
I guess you couldnât rule it out, but the surgery was done by doing a 1:1 âcloneâ of the original SSHD to the new SSD. In fact if you DON"T do it that way there is no chance the Shield will boot off the ânewâ SSD as the partition structure is quite complex.
If it IS baulking at something, it would have to be a a very low level, such as disk serials or the like.
Thanks again for pursuing this, it really is a bit of a mystery to me.
I hope not⊠cause I have the same thing as well. I am going to be in the process of moving over my database/metadata to the internal but user accessible location probably today after do a bit of testing on my 16GB test machine I have set up. Clearly the first test will not be exactly the same, but I am making sure I can copy out the data and then reset Plex and copy it back into that same location and work.
I think I can see an issue already. Even tho I will be using the same name for my new server from the backed up version, it still shows up as a new server. I am pretty sure this is going to mess up all of my Syncâed music on my Iphone. However, this is a small price to pay after weeks and weeks for setting up everything correctly.
I donât think itâs the drive itself, but something with the cloning that changes something. Did you use the original sector size or change to use 4K?
The server is not identified based on the name. There is a setting file that does it. You wonât see the server as being the old one until after you restore the appdata.
Correct, itâs not until I put in the backup data did it show up as I new server⊠because I basically did create a new server at that point.
So, I was able to move my 55GB database/metadata out to Internal (UAS) in about 30 min. One thing to note is that I am using a samsung 500G drive. This was the first drive that people were able to clone the original drive with that was the exact size. Now I know that later you were able to put in smaller or bigger drives so that could be something to look at. As for me, in the latest public version of plex (1.18.1.1973) I was able to move my storage location out the UAS just fine.
I used the HDD Guru âHDD Raw Copyâ program to do the Cloning, it has no options for doing any any sector realignment for 4K from memory so no, I didnât do any :-).
Link to program page:-
I used a 500 GB Samsung EVO 840 SSD I had lying around, as this had been proven to work as it had the same sector count as the original 500 GB Seagate SSHD.
As @ASiDiE says, there are various other more complex methods for âcloningâ to larger SSDs, but I did not do that, stuck to the 500 GB.
The mystery as to why my migration fails gets deeper I guess?
@MovieFan.Plex, any update on your investigation into this?
I have just re-attempted the move since updating to latest PMS beta 1.18.2.2031 and the problem still exists for me.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
