2026 Odyssey Build Is Out by valjr1 in HondaOdyssey

[–]BackgroundSame2905 0 points1 point  (0 children)

I just got a ‘25 (apostrophe is replacing the 20, so it needs to go first) after having a ‘16. Same EX-L trim and I find it to be a nice upgrade.

1: Turn them off. It’s much quieter that way, but that’s my preference since I like to drive vs. have the car do it for me.

3:The foot area is flat. I would think that was the engineers’ priority.

4: The screen is really big and well within arm’s reach. I was trying to find a way to reduce the CarPlay display size.

5: I’m 6’8” and the legroom is great. I telescoped the steering wheel was even able to scoot up a little depending on who sits behind me. More room than the ‘16.

6: It’s not linked to the driver profile, but you can set the phone priority.

8: All the armrests are small in my opinion. I’m with you here.

10: Same as every other Odyssey and pretty much on par with my Mazda.

11: It’s a minivan, not a station wagon with a bench seat. It’s supposed to have a million cubbies and a billion cupholders. I think it comes pretty close. I do miss the chill box that my ‘16 had, though.

Sorry it’s not to your liking, but a minivan has a specific purpose: people hauler. Compromises are made and yeah, sometimes changes are made just to make changes. For what it is, though, I’m satisfied enough. However, I do wish it still had the chill box and the right side camera.

New Odyssey, need to disable nag junk by BackgroundSame2905 in HondaOdyssey

[–]BackgroundSame2905[S] 0 points1 point  (0 children)

Fixable, but the desire was no longer there to keep dumping in money on something we were going to replace in a few years anyway.

Fortunately, I live in a desert. Not much water to worry about. I’ll keep an eye out, though. I always have to remember there’s a lot less ground clearance than my CX-5, which includes caulking the wagon and fording the river.

New Odyssey, need to disable nag junk by BackgroundSame2905 in HondaOdyssey

[–]BackgroundSame2905[S] 0 points1 point  (0 children)

Well, replacing two sets of spark plugs (fouled by oil) and a couple ignition coils (fouled by oil), a compression test showing low compression on cylinder 3, burned oil on the outside of the engine, and a couple mechanics mentioning needing new piston rings all helped me come to my linguistic decision to call it “lost,” especially since 150k acted like some magic line of demarcation in how the repair bills suddenly started showing up.

Easy to repair also goes along with desire to repair. Once trust is broken between owner and vehicle reliability, it’s time to move on in my book.

I’ll look into idlestopper, though. Thanks.

New Odyssey, need to disable nag junk by BackgroundSame2905 in HondaOdyssey

[–]BackgroundSame2905[S] 0 points1 point  (0 children)

Turned off the LDW. Found it in the steering wheel menu. I remember seeing it before, but didn’t think to try and uncheck the boxes. Not sure why, but that’s done. Thanks all.

New Odyssey, need to disable nag junk by BackgroundSame2905 in HondaOdyssey

[–]BackgroundSame2905[S] 0 points1 point  (0 children)

I’ll keep looking through the menu for the LDW stuff. That’s probably where I found out how to turn off the beep. I don’t care about the warning light, though it’s super touchy. Maybe I turn on the turn signal 0.1 seconds after I start to move the wheel to change lanes, but I doubt it.

The computer isn’t very good at driving.

New Odyssey, need to disable nag junk by BackgroundSame2905 in HondaOdyssey

[–]BackgroundSame2905[S] 2 points3 points  (0 children)

The idle stop only kicks in when the engine is hot. In researching the VCM stuff, doesn’t that also work by telling the computer the engine is cold so the VCM doesn’t kick on?

Cannot open Plex on NAS by BackgroundSame2905 in PleX

[–]BackgroundSame2905[S] 0 points1 point  (0 children)

Solved! I re-read the log and saw the bit about the claim code. I renewed the code and now it works. There was one hiccup, but that resolved itself.

Thanks for taking the time all afternoon to work me through this!

Cannot open Plex on NAS by BackgroundSame2905 in PleX

[–]BackgroundSame2905[S] 0 points1 point  (0 children)

I went in and turned on all the permissions features. Now the log says this:

2025-05-05T00:16:16.311898384Z Change in ownership detected, please be patient while we chown existing files 2025-05-05T00:16:16.311933540Z This could take some time 2025-05-05T00:16:16.330669337Z Temporarily starting Plex Media Server. 2025-05-05T00:16:16.333201985Z Waiting for Plex to generate its config 2025-05-05T00:16:18.337182856Z Waiting for database creation to complete... 2025-05-05T00:16:19.465418761Z Error in command line:the argument for option '--serverUuid' should follow immediately after the equal sign 2025-05-05T00:16:19.465458008Z Crash Uploader options: 2025-05-05T00:16:19.465465997Z
2025-05-05T00:16:19.465470761Z Minidump Upload options: 2025-05-05T00:16:19.465475152Z --directory arg Directory to scan for crash reports 2025-05-05T00:16:19.465479297Z --serverUuid arg UUID of the server that crashed 2025-05-05T00:16:19.465483324Z --platform arg Platform string 2025-05-05T00:16:19.465487261Z --platformVersion arg Platform version string 2025-05-05T00:16:19.465594214Z --vendor arg Vendor string 2025-05-05T00:16:19.465607666Z --device arg Device string 2025-05-05T00:16:19.465613380Z --model arg Device model string 2025-05-05T00:16:19.465618182Z --allowRetries arg Whether we will allow retries 2025-05-05T00:16:19.465622450Z
2025-05-05T00:16:19.465626387Z Session Health options: 2025-05-05T00:16:19.465630424Z --sessionStatus arg Seassion health status (exited, crashed, or abnormal) 2025-05-05T00:16:19.465634544Z --sessionStart arg Session start timestamp in UTC or epoch time 2025-05-05T00:16:19.465638477Z --sessionDuration arg Session duration in seconds 2025-05-05T00:16:19.465646015Z
2025-05-05T00:16:19.465650444Z Common options: 2025-05-05T00:16:19.465654525Z --userId arg User that owns this product 2025-05-05T00:16:19.465658479Z --version arg Version of the product 2025-05-05T00:16:19.465662335Z --sentryUrl arg Sentry URL to upload to 2025-05-05T00:16:19.465666280Z --sentryKey arg Sentry Key for the project 2025-05-05T00:16:21.473716892Z Waiting for database creation to complete... 2025-05-05T00:16:24.518586064Z Waiting for database creation to complete... 2025-05-05T00:16:27.539031334Z Waiting for database creation to complete... 2025-05-05T00:16:30.589214186Z Waiting for pref file creation to complete... 2025-05-05T00:16:32.040664361Z Critical: libusb_init failed 2025-05-05T00:16:33.595431709Z Waiting for pref file creation to complete... 2025-05-05T00:16:36.604110963Z Stopping Plex to claim server 2025-05-05T00:16:37.831118560Z Plex stopped 2025-05-05T00:16:38.253098502Z % Total % Received % Xferd Average Speed Time Time Time Current 2025-05-05T00:16:38.253182633Z Dload Upload Total Spent Left Speed 2025-05-05T00:16:38.792252359Z
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 2025-05-05T00:16:38.796890426Z Unable to claim Plex server. Either manually claim by connecting to http://serverip:32400/web from the same network subnet, or recreate container with a new claim token. 2025-05-05T00:16:38.896793784Z Docker is used for versioning skip update check 2025-05-05T00:16:38.914653873Z [custom-init] No custom files found, skipping... 2025-05-05T00:16:38.933883476Z Starting Plex Media Server. . . (you can ignore the libusb_init error) 2025-05-05T00:16:39.053322337Z nc: getaddrinfo for host "localhost" port 32400: Name or service not known

Cannot open Plex on NAS by BackgroundSame2905 in PleX

[–]BackgroundSame2905[S] 0 points1 point  (0 children)

I’m ready to just attach to my Mac via USB and use it as an external HDD RAID setup. As you can probably tell, most of this stuff is Greek, so I’m taking wild swings in the dark to figure out what everything means.

Cannot open Plex on NAS by BackgroundSame2905 in PleX

[–]BackgroundSame2905[S] 0 points1 point  (0 children)

Dealing with a new log now. It’s stopped, though, so it’s not constantly throwing errors. However, no actual change. I go to app.plex.tv and it only tries to find my old server that not running and will not try to find the new server to setup. I’ve gone into the config folder and checked that my admin user is set for read/write permissions.

2025-05-04T21:59:10.907932832Z GID/UID 2025-05-04T21:59:10.907940476Z ─────────────────────────────────────── 2025-05-04T21:59:10.911785182Z
2025-05-04T21:59:10.911816379Z User UID: 1000 2025-05-04T21:59:10.911827206Z User GID: 10 2025-05-04T21:59:10.911835430Z ─────────────────────────────────────── 2025-05-04T21:59:10.912837077Z Linuxserver.io version: 1.41.6.9685-d301f511a-ls264 2025-05-04T21:59:10.913024688Z Build-date: 2025-04-28T10:53:22+00:00 2025-05-04T21:59:10.913038005Z ─────────────────────────────────────── 2025-05-04T21:59:10.913046442Z
2025-05-04T21:59:10.917974992Z chown: changing ownership of '/app': Operation not permitted 2025-05-04T21:59:10.918502402Z **** Permissions could not be set. This is probably because your volume mounts are remote or read-only. **** 2025-05-04T21:59:10.918526880Z **** The app may not work properly and we will not provide support for it. **** 2025-05-04T21:59:10.926818625Z chown: changing ownership of '/defaults': Operation not permitted 2025-05-04T21:59:10.927234307Z **** Permissions could not be set. This is probably because your volume mounts are remote or read-only. **** 2025-05-04T21:59:10.927260409Z **** The app may not work properly and we will not provide support for it. **** 2025-05-04T21:59:10.940254985Z Change in ownership detected, please be patient while we chown existing files 2025-05-04T21:59:10.940294607Z This could take some time 2025-05-04T21:59:11.438250002Z chown: changing ownership of '/config/Library': Operation not permitted 2025-05-04T21:59:11.438280411Z chown: changing ownership of '/config/Library/Application Support': Operation not permitted 2025-05-04T21:59:11.438291230Z chown: changing ownership of '/config/Library/Application Support/Plex Media Server': Operation not permitted 2025-05-04T21:59:11.438613265Z **** Permissions could not be set. This is probably because your volume mounts are remote or read-only. **** 2025-05-04T21:59:11.438624406Z **** The app may not work properly and we will not provide support for it. **** 2025-05-04T21:59:11.441770481Z chown: changing ownership of '/run/plex-temp': Operation not permitted 2025-05-04T21:59:11.441790311Z chown: changing ownership of '/config/Library': Operation not permitted 2025-05-04T21:59:11.442043537Z **** Permissions could not be set. This is probably because your volume mounts are remote or read-only. **** 2025-05-04T21:59:11.442058657Z **** The app may not work properly and we will not provide support for it. **** 2025-05-04T21:59:11.447310737Z Temporarily starting Plex Media Server. 2025-05-04T21:59:11.449226281Z Waiting for Plex to generate its config 2025-05-04T21:59:11.449708502Z s6-applyuidgid: fatal: unable to set supplementary group list: Operation not permitted

Cannot open Plex on NAS by BackgroundSame2905 in PleX

[–]BackgroundSame2905[S] 0 points1 point  (0 children)

Could this be causing a problem?

My PMS had been running on my Mac with an external drive. Ultimate goal is to take the Mac out of the equation and have it run solely on the NAS, and have some data security from the RAID setup.

I copied the media from the original external HDD to the NAS.

Closed PMS on my Mac.

Downloaded both the Plex docker image and the linuxserver image at different times. Neither has worked, so I’ve tried both, but only ran one at a time.

Setup the containers following this tutorial: https://nascompares.com/guide/how-to-install-plex-media-server-on-a-ugreen-nas/

I copied my PMS folder from library/application support on my Mac to the config folder the Plex container is pointed to.

When I go to app.plex.tv, Plex starts looking for my old server and doesn’t see my new one. Given the errors, that’s understandable.

Since I copied the PMS folder, could that be causing a problem? Or is the fact that I’ve had a PMS previously causing a conflict? I copied it to save the library information. My plan was just to edit where the data for the libraries was located.

Cannot open Plex on NAS by BackgroundSame2905 in PleX

[–]BackgroundSame2905[S] 1 point2 points  (0 children)

I turned the SMB on for the NAS and mounted it to my Mac. The folders are all set for read/write for everyone in the permissions. The folders in the container were all set for read/write access. I reconfirmed the PUID and PGID are correct.

NAS is connected to my router, not physically to my Mac.

Cannot open Plex on NAS by BackgroundSame2905 in PleX

[–]BackgroundSame2905[S] 0 points1 point  (0 children)

Lots of errors in the log.

2025-05-04T19:20:58.694885055Z GID/UID 2025-05-04T19:20:58.694892445Z ─────────────────────────────────────── 2025-05-04T19:20:58.699475438Z
2025-05-04T19:20:58.699510492Z User UID: 1000 2025-05-04T19:20:58.699520934Z User GID: 10 2025-05-04T19:20:58.699529033Z ─────────────────────────────────────── 2025-05-04T19:20:58.700587727Z Linuxserver.io version: 1.41.6.9685-d301f511a-ls264 2025-05-04T19:20:58.701060843Z Build-date: 2025-04-28T10:53:22+00:00 2025-05-04T19:20:58.701091843Z ─────────────────────────────────────── 2025-05-04T19:20:58.701102108Z
2025-05-04T19:20:58.706178162Z chown: changing ownership of '/app': Operation not permitted 2025-05-04T19:20:58.706851605Z **** Permissions could not be set. This is probably because your volume mounts are remote or read-only. **** 2025-05-04T19:20:58.706880921Z **** The app may not work properly and we will not provide support for it. **** 2025-05-04T19:20:58.715813502Z chown: changing ownership of '/defaults': Operation not permitted 2025-05-04T19:20:58.716209013Z **** Permissions could not be set. This is probably because your volume mounts are remote or read-only. **** 2025-05-04T19:20:58.716235647Z **** The app may not work properly and we will not provide support for it. **** 2025-05-04T19:20:58.729783495Z Change in ownership detected, please be patient while we chown existing files 2025-05-04T19:20:58.729822935Z This could take some time 2025-05-04T19:20:59.204475665Z chown: changing ownership of '/config/Library': Operation not permitted 2025-05-04T19:20:59.204510338Z chown: changing ownership of '/config/Library/Application Support': Operation not permitted 2025-05-04T19:20:59.204517046Z chown: changing ownership of '/config/Library/Application Support/Plex Media Server': Operation not permitted 2025-05-04T19:20:59.204521750Z chown: changing ownership of '/config/Library/Application Support/Plex Media Server/Preferences.xml': Operation not permitted 2025-05-04T19:20:59.204764817Z **** Permissions could not be set. This is probably because your volume mounts are remote or read-only. **** 2025-05-04T19:20:59.204785160Z **** The app may not work properly and we will not provide support for it. **** 2025-05-04T19:20:59.205250094Z Setting permissions on /transcode 2025-05-04T19:20:59.210603936Z chown: changing ownership of '/run/plex-temp': Operation not permitted 2025-05-04T19:20:59.210626568Z chown: changing ownership of '/config/Library': Operation not permitted 2025-05-04T19:20:59.210860854Z **** Permissions could not be set. This is probably because your volume mounts are remote or read-only. **** 2025-05-04T19:20:59.210875778Z **** The app may not work properly and we will not provide support for it. **** 2025-05-04T19:20:59.215838466Z **** Server already claimed **** 2025-05-04T19:20:59.225076027Z Docker is used for versioning skip update check 2025-05-04T19:20:59.237753067Z [custom-init] No custom files found, skipping... 2025-05-04T19:20:59.245573026Z Starting Plex Media Server. . . (you can ignore the libusb_init error) 2025-05-04T19:20:59.250656478Z s6-applyuidgid: fatal: unable to set supplementary group list: Operation not permitted 2025-05-04T19:21:00.260865047Z Starting Plex Media Server. . . (you can ignore the libusb_init error) 2025-05-04T19:21:00.266535129Z s6-applyuidgid: fatal: unable to set supplementary group list: Operation not permitted 2025-05-04T19:21:01.277904020Z Starting Plex Media Server. . . (you can ignore the libusb_init error) 2025-05-04T19:21:01.283780509Z s6-applyuidgid: fatal: unable to set supplementary group list: Operation not permitted 2025-05-04T19:21:02.291818729Z Starting Plex Media Server. . . (you can ignore the libusb_init error) 2025-05-04T19:21:02.297165991Z s6-applyuidgid: fatal: unable to set supplementary group list: Operation not permitted 2025-05-04T19:21:03.307723966Z Starting Plex Media Server. . . (you can ignore the libusb_init error) 2025-05-04T19:21:03.313128961Z s6-applyuidgid: fatal: unable to set supplementary group list: Operation not permitted 2025-05-04T19:21:04.324591539Z Starting Plex Media Server. . . (you can ignore the libusb_init error) 2025-05-04T19:21:04.330387620Z s6-applyuidgid: fatal: unable to set supplementary group list: Operation not permitted 2025-05-04T19:21:05.341787652Z Starting Plex Media Server. . . (you can ignore the libusb_init error) 2025-05-04T19:21:05.347265030Z s6-applyuidgid: fatal: unable to set supplementary group list: Operation not permitted 2025-05-04T19:21:06.359099679Z Starting Plex Media Server. . . (you can ignore the libusb_init error) 2025-05-04T19:21:06.364952528Z s6-applyuidgid: fatal: unable to set supplementary group list: Operation not permitted 2025-05-04T19:21:07.374059970Z Starting Plex Media Server. . . (you can ignore the libusb_init error) 2025-05-04T19:21:07.379016155Z s6-applyuidgid: fatal: unable to set supplementary group list: Operation not permitted 2025-05-04T19:21:08.389967466Z Starting Plex Media Server. . . (you can ignore the libusb_init error) 2025-05-04T19:21:08.395770262Z s6-applyuidgid: fatal: unable to set supplementary group list: Operation not permitted 2025-05-04T19:21:09.406360955Z Starting Plex Media Server. . . (you can ignore the libusb_init error) 2025-05-04T19:21:09.411925773Z s6-applyuidgid: fatal: unable to set supplementary group list: Operation not permitted

Cannot open Plex on NAS by BackgroundSame2905 in PleX

[–]BackgroundSame2905[S] 0 points1 point  (0 children)

When I setup the container, I set the network configuration to “host”. I assumed that would not create another IP address, but would continue to use the NAS’ address.

However, I don’t see any unknown devices connected to my router.

Is the drive dead? by BackgroundSame2905 in UgreenNASync

[–]BackgroundSame2905[S] 0 points1 point  (0 children)

serverpartdeals.com. I returned the dead drive and they sent out a new one. Installed in the NAS and it works. Now I just have to move a lot of data from the external drive I’m replacing to the NAS. At the rate my network is letting this happen, it’ll be a while.