top of page
Writer's pictureLeilani H

update happy, upgrade happy, update crashed & cpu pinning


 
 

previous setup:

unraid os + hp omen + i5-12th gen + 64GB

8 bay enclosure + 4 bay enclosure


moved to:

hp proliant + intel xeon silver 4208 + 32GB


something i've been meaning to do for months, but lagged on because migrating is never easy or straightforward; that is, until unraid is in the picture. so i finally said f-- it because it should* be easy and moved the bootsb and the drives to the proliant.


once booted, the drives were assigned where they needed to be. i set new cache drives (more storage), and brought everything online. it took a minute, but everything appeared as it was on the previous hardware, then i made some network changes and we were up... kind of... my bookmarks were loading my apps, but they weren't launching from the unraid. they were trying to open with an old ip address - so i went into each container, re-applied the current settings and then we were good.


then i moved on to cpu pinning, which was another reason i moved back to the proliant. running a media server and photo gallery on the omen was too much for an i5 so i split them up and put the media server onto the xeon. used chatgpt to learn more about cpu pinning (what it does is in the name, but for clarity and suggestions why not ai [google, you are really fucking my search game up with whatever you're doing]). anyway, i think i gave the most resource hungry apps 3 cores each, and everything else 1 or 2 cores depending on need. then i text the homie about the updates to the media server and he noticed the difference compared to two days ago, and then i text the other homie all of this im writing but in less words to tell him i was going to put this into more words.


i started updating all of my apps, it's been a while since i'd done anything and for fear of breaking something when i just fixed everything - i told myself not to do it. this lasted all of a few hours and i began little by little. i was just about to catch up on a show, said fuck it, update the last app - plex. i updated, it completed successfully, i went to test it, and it wouldn't load. why? a sqlite3 database error throwing up bloods in my logs (the header photo of this post).

i did about 5 minutes of research and said fuck it and went to bed.


i debated even dealing with this today, but i text the homie again and let him know what happened. he'd just had this issue and what he said and linked matched up with what i'd read before i went to bed.


once i did this plex finally loaded, with a few annoyances of needing to re-add my library to then reshare. besides that, it was the easiest migration i've ever done


commands used:

navigate to the following:

cd /mnt/user/appdata/plex/Library/Application\ Support/Plex\ Media\ Server/

make a backup:

cp -r "Plug-in Support" "Plug-in Support_backup"

move the corrupted database out of the way:

mv com.plexapp.plugins.library.db com.plexapp.plugins.library.db.bak

copy the latest backup to the main database file:

cp com.plexapp.plugins.library.db-<timestamp>-<number> com.plexapp.plugins.library.db

restart the plex container



7 views

Recent Posts

See All

5/5/24

Comments


bottom of page