Chronicles of MOBY - ACT 3

wayoflife

Administrator
Staff member
As some of you may know, MOBY is almost 20 years old and the last couple has seen him out of action more than in. Back in September of 2025, we were finally able to get his rear end fixed and you can learn what that was all about here:

And, while we were able to get him back and out on the trails again or at least once anyway, we soon found ourselves confronted with a new and bigger problem. Needless to say, I decided to move the posts below and start this thread to chronicle what's been going on and what we'll be doing to address his issues.

HOW IT STARTED
As some of you may have noticed, WAYALIFE was down yesterday and apparently, it was because there was some kind of data center outage in Chicago. Needless to say, we were just one of many website affected by it but of course, at the time we didn't know it. And, to make matters worse, we had literally just started our long drive down to Boulder City in both Moby (going down to Motech for some updates) and our 392.
20251023140108-132c77bb.jpg


To add insult to injury, about 3 hours into our drive, Moby got a check engine light soon after we did a big pass around 4 semi trucks. Being that I just installed a clean K&N filter, I figured it was just oil getting into the MAF sensor as this is something we've seen before. So, I pulled over, checked things out, cleared codes and hopped back on the highway.
20251023140110-20de2bc4.jpg


Unfortunately, as soon as we got going, I realized that I was still in a transmission limp mode and couldn't get past 3rd and so, I pulled over again. This is a known issue that happens every now and then can can be cleared simply by disconnecting the battery for a few minutes. I should note, this is actually why we were taking Moby down to Motech as they now have a fix for it.
20251023140109-519e2fb6.jpg

20251023140111-077f558c.jpg


After reconnecting the battery and clearing any codes that might be in the system, I fired up the engine, all was good and we were off again. But, after we were on the highway for about 5 minutes, Moby went back into limp mode and so I quickly pulled over again and shut off the engine especially being that this time, the oil pressure idiot light was on. After giving things a closer look, checked for any signs of trouble and verified there was oil in the engine, I went through the same things I did the first time to get us running again and then tried firing up the engine again.

Well, the good news is that there were no new codes and the oil pressure light was off but engine didn't sound good at all - kind of like a pully went bad but not exactly. Needless to say, I immediately cut the engine and started to plan what we were going to do next and just as rain started to fall 🤪

Fortunately, we were traveling with 2 Jeeps and so, we decided to have Cindy tow me in the 392, on a pole line paralleling the highway, to the nearest town (if you can call it that) and with Moby's engine off. As in, he had no power steering and no power boosted brakes.
20251023140111-533adeab.jpg


Once we got to a place were we felt that we could somewhat safely leave Moby, we unloaded him, hopped in the 392 and headed back to Carson City. 3 hours later, around 11 pm, we transferred all our stuff into our new RAM, drove down to Pizen, hooked up our trailer and then went back to rescue Moby.

At 1 am, we finally got back to Moby, loaded him up, hopped back on the highway and continued our drive down to Vegas.
20251023140104-c757a59b.jpg
20251023140105-bb33d556.jpg


Around 4am, I needed to sleep a bit and so we pulled over and took a couple hour nap before continuing our drive south.
20251023140107-403bbab8.jpg
20251023140107-f9c04e5b.jpg


At around 8:30 am, we finally made it to Motech.
i.php

i.php


With all that said, I just heard from Kalan and apparently, he found that the noise appeared to be coming from the flywheel. After pulling the inspection cover off, he noticed there were a few bolts that were missing on it but the real questions is, where did they go? Needless to say, Moby may be spending a bit more time down here than we had planned but really, I feel lucky that things worked out the way they did and this as opposed to being out in the middle of nowhere and solo - something we would never do 🤪

Anyway, I think I'll take a nap now but I'll keep you posted once we find out anything new.
 
Last edited:
As some of you may have noticed, WAYALIFE was down yesterday and apparently, it was because there was some kind of data center outage in Chicago. Needless to say, we were just one of many website affected by it but of course, at the time we didn't know it. And, to make matters worse, we had literally just started our long drive down to Boulder City in both Moby (going down to Motech for some updates) and our 392.
20251023140108-132c77bb.jpg


To add insult to injury, about 3 hours into our drive, Moby got a check engine light soon after we did a big pass around 4 semi trucks. Being that I just installed a clean K&N filter, I figured it was just oil getting into the MAF sensor as this is something we've seen before. So, I pulled over, checked things out, cleared codes and hopped back on the highway.
20251023140110-20de2bc4.jpg


Unfortunately, as soon as we got going, I realized that I was still in a transmission limp mode and couldn't get past 3rd and so, I pulled over again. This is a known issue that happens every now and then can can be cleared simply by disconnecting the battery for a few minutes. I should note, this is actually why we were taking Moby down to Motech as they now have a fix for it.
20251023140109-519e2fb6.jpg

20251023140111-077f558c.jpg


After reconnecting the battery and clearing any codes that might be in the system, I fired up the engine, all was good and we were off again. But, after we were on the highway for about 5 minutes, Moby went back into limp mode and so I quickly pulled over again and shut off the engine especially being that this time, the oil pressure idiot light was on. After giving things a closer look, checked for any signs of trouble and verified there was oil in the engine, I went through the same things I did the first time to get us running again and then tried firing up the engine again.

Well, the good news is that there were no new codes and the oil pressure light was off but engine didn't sound good at all - kind of like a pully went bad but not exactly. Needless to say, I immediately cut the engine and started to plan what we were going to do next and just as rain started to fall 🤪

Fortunately, we were traveling with 2 Jeeps and so, we decided to have Cindy tow me in the 392, on a pole line paralleling the highway, to the nearest town (if you can call it that) and with Moby's engine off. As in, he had no power steering and no power boosted brakes.
20251023140111-533adeab.jpg


Once we got to a place were we felt that we could somewhat safely leave Moby, we unloaded him, hopped in the 392 and headed back to Carson City. 3 hours later, around 11 pm, we transferred all our stuff into our new RAM, drove down to Pizen, hooked up our trailer and then went back to rescue Moby.

At 1 am, we finally got back to Moby, loaded him up, hopped back on the highway and continued our drive down to Vegas.
20251023140104-c757a59b.jpg
20251023140105-bb33d556.jpg


Around 4am, I needed to sleep a bit and so we pulled over and took a couple hour nap before continuing our drive south.
20251023140107-403bbab8.jpg
20251023140107-f9c04e5b.jpg


At around 8:30 am, we finally made it to Motech.
i.php

i.php


With all that said, I just heard from Kalan and apparently, he found that the noise appeared to be coming from the flywheel. After pulling the inspection cover off, he noticed there were a few bolts that were missing on it but the real questions is, where did they go? Needless to say, Moby may be spending a bit more time down here than we had planned but really, I feel lucky that things worked out the way they did and this as opposed to being out in the middle of nowhere and solo - something we would never do 🤪

Anyway, I think I'll take a nap now but I'll keep you posted once we find out anything new.
Holy hell now that's an ordeal! Glad you guys made it there in the end and that you had 2 Jeeps to drive down there, one Jeep to pull the other Jeep, a Jeep to drive back to get a truck and a trailer, and were able to drive that truck and trailer back down to the other Jeep... Lol

Bummer about Moby but he's in good hands and I know we'll see him again soon.
 
Last edited:
As some of you may have noticed, WAYALIFE was down yesterday and apparently, it was because there was some kind of data center outage in Chicago. Needless to say, we were just one of many website affected by it but of course, at the time we didn't know it. And, to make matters worse, we had literally just started our long drive down to Boulder City in both Moby (going down to Motech for some updates) and our 392.
20251023140108-132c77bb.jpg


To add insult to injury, about 3 hours into our drive, Moby got a check engine light soon after we did a big pass around 4 semi trucks. Being that I just installed a clean K&N filter, I figured it was just oil getting into the MAF sensor as this is something we've seen before. So, I pulled over, checked things out, cleared codes and hopped back on the highway.
20251023140110-20de2bc4.jpg


Unfortunately, as soon as we got going, I realized that I was still in a transmission limp mode and couldn't get past 3rd and so, I pulled over again. This is a known issue that happens every now and then can can be cleared simply by disconnecting the battery for a few minutes. I should note, this is actually why we were taking Moby down to Motech as they now have a fix for it.
20251023140109-519e2fb6.jpg

20251023140111-077f558c.jpg


After reconnecting the battery and clearing any codes that might be in the system, I fired up the engine, all was good and we were off again. But, after we were on the highway for about 5 minutes, Moby went back into limp mode and so I quickly pulled over again and shut off the engine especially being that this time, the oil pressure idiot light was on. After giving things a closer look, checked for any signs of trouble and verified there was oil in the engine, I went through the same things I did the first time to get us running again and then tried firing up the engine again.

Well, the good news is that there were no new codes and the oil pressure light was off but engine didn't sound good at all - kind of like a pully went bad but not exactly. Needless to say, I immediately cut the engine and started to plan what we were going to do next and just as rain started to fall 🤪

Fortunately, we were traveling with 2 Jeeps and so, we decided to have Cindy tow me in the 392, on a pole line paralleling the highway, to the nearest town (if you can call it that) and with Moby's engine off. As in, he had no power steering and no power boosted brakes.
20251023140111-533adeab.jpg


Once we got to a place were we felt that we could somewhat safely leave Moby, we unloaded him, hopped in the 392 and headed back to Carson City. 3 hours later, around 11 pm, we transferred all our stuff into our new RAM, drove down to Pizen, hooked up our trailer and then went back to rescue Moby.

At 1 am, we finally got back to Moby, loaded him up, hopped back on the highway and continued our drive down to Vegas.
20251023140104-c757a59b.jpg
20251023140105-bb33d556.jpg


Around 4am, I needed to sleep a bit and so we pulled over and took a couple hour nap before continuing our drive south.
20251023140107-403bbab8.jpg
20251023140107-f9c04e5b.jpg


At around 8:30 am, we finally made it to Motech.
i.php

i.php


With all that said, I just heard from Kalan and apparently, he found that the noise appeared to be coming from the flywheel. After pulling the inspection cover off, he noticed there were a few bolts that were missing on it but the real questions is, where did they go? Needless to say, Moby may be spending a bit more time down here than we had planned but really, I feel lucky that things worked out the way they did and this as opposed to being out in the middle of nowhere and solo - something we would never do 🤪

Anyway, I think I'll take a nap now but I'll keep you posted once we find out anything new.
That sucks, but it came out pretty good, all things considered. Glad you had 2 jeeps, to make it work. The weekend can only get better.
 
As some of you may have noticed, WAYALIFE was down yesterday and apparently, it was because there was some kind of data center outage in Chicago. Needless to say, we were just one of many website affected by it but of course, at the time we didn't know it. And, to make matters worse, we had literally just started our long drive down to Boulder City in both Moby (going down to Motech for some updates) and our 392.
20251023140108-132c77bb.jpg


To add insult to injury, about 3 hours into our drive, Moby got a check engine light soon after we did a big pass around 4 semi trucks. Being that I just installed a clean K&N filter, I figured it was just oil getting into the MAF sensor as this is something we've seen before. So, I pulled over, checked things out, cleared codes and hopped back on the highway.
20251023140110-20de2bc4.jpg


Unfortunately, as soon as we got going, I realized that I was still in a transmission limp mode and couldn't get past 3rd and so, I pulled over again. This is a known issue that happens every now and then can can be cleared simply by disconnecting the battery for a few minutes. I should note, this is actually why we were taking Moby down to Motech as they now have a fix for it.
20251023140109-519e2fb6.jpg

20251023140111-077f558c.jpg


After reconnecting the battery and clearing any codes that might be in the system, I fired up the engine, all was good and we were off again. But, after we were on the highway for about 5 minutes, Moby went back into limp mode and so I quickly pulled over again and shut off the engine especially being that this time, the oil pressure idiot light was on. After giving things a closer look, checked for any signs of trouble and verified there was oil in the engine, I went through the same things I did the first time to get us running again and then tried firing up the engine again.

Well, the good news is that there were no new codes and the oil pressure light was off but engine didn't sound good at all - kind of like a pully went bad but not exactly. Needless to say, I immediately cut the engine and started to plan what we were going to do next and just as rain started to fall 🤪

Fortunately, we were traveling with 2 Jeeps and so, we decided to have Cindy tow me in the 392, on a pole line paralleling the highway, to the nearest town (if you can call it that) and with Moby's engine off. As in, he had no power steering and no power boosted brakes.
20251023140111-533adeab.jpg


Once we got to a place were we felt that we could somewhat safely leave Moby, we unloaded him, hopped in the 392 and headed back to Carson City. 3 hours later, around 11 pm, we transferred all our stuff into our new RAM, drove down to Pizen, hooked up our trailer and then went back to rescue Moby.

At 1 am, we finally got back to Moby, loaded him up, hopped back on the highway and continued our drive down to Vegas.
20251023140104-c757a59b.jpg
20251023140105-bb33d556.jpg


Around 4am, I needed to sleep a bit and so we pulled over and took a couple hour nap before continuing our drive south.
20251023140107-403bbab8.jpg
20251023140107-f9c04e5b.jpg


At around 8:30 am, we finally made it to Motech.
i.php

i.php


With all that said, I just heard from Kalan and apparently, he found that the noise appeared to be coming from the flywheel. After pulling the inspection cover off, he noticed there were a few bolts that were missing on it but the real questions is, where did they go? Needless to say, Moby may be spending a bit more time down here than we had planned but really, I feel lucky that things worked out the way they did and this as opposed to being out in the middle of nowhere and solo - something we would never do 🤪

Anyway, I think I'll take a nap now but I'll keep you posted once we find out anything new.
Wow guys, sorry that happened, but happy it worked out. Hope they can get him fixed up quickly.
 
As some of you may have noticed, WAYALIFE was down yesterday and apparently, it was because there was some kind of data center outage in Chicago. Needless to say, we were just one of many website affected by it but of course, at the time we didn't know it. And, to make matters worse, we had literally just started our long drive down to Boulder City in both Moby (going down to Motech for some updates) and our 392.
20251023140108-132c77bb.jpg


To add insult to injury, about 3 hours into our drive, Moby got a check engine light soon after we did a big pass around 4 semi trucks. Being that I just installed a clean K&N filter, I figured it was just oil getting into the MAF sensor as this is something we've seen before. So, I pulled over, checked things out, cleared codes and hopped back on the highway.
20251023140110-20de2bc4.jpg


Unfortunately, as soon as we got going, I realized that I was still in a transmission limp mode and couldn't get past 3rd and so, I pulled over again. This is a known issue that happens every now and then can can be cleared simply by disconnecting the battery for a few minutes. I should note, this is actually why we were taking Moby down to Motech as they now have a fix for it.
20251023140109-519e2fb6.jpg

20251023140111-077f558c.jpg


After reconnecting the battery and clearing any codes that might be in the system, I fired up the engine, all was good and we were off again. But, after we were on the highway for about 5 minutes, Moby went back into limp mode and so I quickly pulled over again and shut off the engine especially being that this time, the oil pressure idiot light was on. After giving things a closer look, checked for any signs of trouble and verified there was oil in the engine, I went through the same things I did the first time to get us running again and then tried firing up the engine again.

Well, the good news is that there were no new codes and the oil pressure light was off but engine didn't sound good at all - kind of like a pully went bad but not exactly. Needless to say, I immediately cut the engine and started to plan what we were going to do next and just as rain started to fall 🤪

Fortunately, we were traveling with 2 Jeeps and so, we decided to have Cindy tow me in the 392, on a pole line paralleling the highway, to the nearest town (if you can call it that) and with Moby's engine off. As in, he had no power steering and no power boosted brakes.
20251023140111-533adeab.jpg


Once we got to a place were we felt that we could somewhat safely leave Moby, we unloaded him, hopped in the 392 and headed back to Carson City. 3 hours later, around 11 pm, we transferred all our stuff into our new RAM, drove down to Pizen, hooked up our trailer and then went back to rescue Moby.

At 1 am, we finally got back to Moby, loaded him up, hopped back on the highway and continued our drive down to Vegas.
20251023140104-c757a59b.jpg
20251023140105-bb33d556.jpg


Around 4am, I needed to sleep a bit and so we pulled over and took a couple hour nap before continuing our drive south.
20251023140107-403bbab8.jpg
20251023140107-f9c04e5b.jpg


At around 8:30 am, we finally made it to Motech.
i.php

i.php


With all that said, I just heard from Kalan and apparently, he found that the noise appeared to be coming from the flywheel. After pulling the inspection cover off, he noticed there were a few bolts that were missing on it but the real questions is, where did they go? Needless to say, Moby may be spending a bit more time down here than we had planned but really, I feel lucky that things worked out the way they did and this as opposed to being out in the middle of nowhere and solo - something we would never do 🤪

Anyway, I think I'll take a nap now but I'll keep you posted once we find out anything new.
Damn! What a story. Get some rest. Oh and how wide is your trailer?
 
Oh bummer! It’s funny how things work out sometimes but glad your have your Ram back to be able to haul it yourself!

Edit: how many miles do you have on that LT/10 speed now? I know it’s been down more than not lately (for other reasons)
 
Oh bummer! It’s funny how things work out sometimes but glad your have your Ram back to be able to haul it yourself!

Edit: how many miles do you have on that LT/10 speed now? I know it’s been down more than not lately (for other reasons)
Honestly, I'm not 100% sure. Maybe 30k miles.
 
UPDATED : WHAT MOTECH FOUND
10/30/25

Soon after dropping Moby off at Motech, I got a message from Kalan letting me know they pulled the transmission inspection cover and right off the bat, found that he had the wrong flywheel. Apparently, the flywheel he had was for a 3-bolt style converter and the 10 speed uses a 6-bolt. They weren't even sure how someone was able to bolt it on and apologized for not seeing it before. After installing a correct fly wheel, they did find that the loud chirp was gone for the most part but that there was a knock and it seems to be coming from the bottom - BOO :(

11/07/25
Just as we were wrapping up SEMA, I got a message from Kalan and he told me that they pulled Moby's pan and found... he spun a bearing :( While I was able to turn his engine it off in time and prevent it from seizing up, you can see that the crank is clearly scored.
JKRA4045.JPEGPLOO1129.JPEGEYFA8414.JPEGPPNU1139.JPEGUGSM6721.JPEGHCTC4623.JPEG

Being that the oil light came on when everything happened, that should indicate the oil pressure went low. However, the light was out when I tried restarting the engine and even when we dropped Moby off at Motech, it was still off. Because of this, Kalan thought that maybe their single module was freaking out and turned the light on but of course, that clearly wasn't the case.

After they replaced the flywheel and heard the knocking, Kalan set the AF gauge to read oil press and it was read 60 PSI! This was very much a surprise to see.

In any case, it appears that the flywheel issue and spun bearing happening at about the same time was unrelated. And, now the questions is, what to do next.
 
Top Bottom