Jump to content

Recommended Posts

Posted

I took a short drive this evening to run errands. All smooth roads; didn't hit anything or go offroading or anything like that.

 

I was about 5 minutes from home and the truck starts making an audible chime sound and the DIC is flashing "low oil pressure turn engine off." I parked on a side street and turned it off. Oil was gushing out of the engine and running all over the air dam, down the knuckle to the front passenger tire and onto the street.  The whole load of oil drained out. 

 

GMC roadside assistance towed it to my dealer. My last oil change was a couple of months ago so I can't imagine it's something like an improperly installed filter. Could the main seal fail at just 5,500 miles?? It's the 6.2L engine. 

 

I was quick to park and shut it off, but I'm quite concerned the engine may have been harmed. 

20190421_194919.jpg

Posted

Won’t speculate or just guess but I’m sure it quite possibly a simple fix.


Sent from above

Posted

Oil cooler line it is. Had them collect an oil sample that I'm going to send away as a baseline. A few weeks after repair I'm going to change the oil again and collect another sample from the filter to send in for a comparison analysis to see if there are signs of damage. 

Posted
40 minutes ago, Shawn O'Leary said:

Oil cooler line it is. Had them collect an oil sample that I'm going to send away as a baseline. A few weeks after repair I'm going to change the oil again and collect another sample from the filter to send in for a comparison analysis to see if there are signs of damage. 

Filter is a bad choice for collecting an oil analysis sample.  Suck it out from the dipstick with a vac pump if you can.  

Posted

My Vac pump wouldn't go all the way down to the pan, tried and tried and no success. 

Posted
15 minutes ago, eppieguy said:

My Vac pump wouldn't go all the way down to the pan, tried and tried and no success. 

Need a longer suction tube.  I get the line from the hardware store and chuck it after each use.  Something like 19 cents a foot.  

Posted

Ugh.... they refilled it with oil and started it up to see how the engine was running and it seized about 3 seconds in. Looking like an engine replacement. 5,500 miles... unbelievable. 

  • Sad 2
Posted
23 minutes ago, Shawn O'Leary said:

Ugh.... they refilled it with oil and started it up to see how the engine was running and it seized about 3 seconds in. Looking like an engine replacement. 5,500 miles... unbelievable. 

Guess I should go give my cooler lines a tug.  

  • Confused 1
  • Sad 2
Posted
48 minutes ago, Shawn O'Leary said:

Ugh.... they refilled it with oil and started it up to see how the engine was running and it seized about 3 seconds in. Looking like an engine replacement. 5,500 miles... unbelievable. 

Don’t get me wrong, the whole situation is awful, but I’d almost say that’s a good thing. I feel like I’d never trust my engine again after running without oil. You never know how long it would take for problems to appear.

  • Like 1
Posted
14 minutes ago, OnTheReel said:

Don’t get me wrong, the whole situation is awful, but I’d almost say that’s a good thing. I feel like I’d never trust my engine again after running without oil. You never know how long it would take for problems to appear.

Yeah,  but to play Devil's Advocate here, they can't even fix leaking rear windows here as of late.  Engine replacement?  I would have to get out of it and get another one to ever be happy I think.  This just sucks.

  • Like 2
Posted
1 hour ago, Shawn O'Leary said:

Ugh.... they refilled it with oil and started it up to see how the engine was running and it seized about 3 seconds in. Looking like an engine replacement. 5,500 miles... unbelievable. 

It's good that it did in a way.  They probably would have tried to tell the engine is fine and sent you on your way other wise. It's annoying that they use these crimped external oil lines. Toyota and GM need to find an oil line supplier that doesn't suck at crimping hoses.

Posted

It is good, in a way, that the engine will be replaced. But, wow, is it disheartening. I contacted a friend who is a GM engineer; he took the VIN, dealer name, etc. He's going to call to have the faulty parts sent to his team (he works in the truck division). Hopefully they do something about this problem.

Posted
34 minutes ago, Limelight said:

Yeah,  but to play Devil's Advocate here, they can't even fix leaking rear windows here as of late.  Engine replacement?  I would have to get out of it and get another one to ever be happy I think.  This just sucks.

True. Hopefully they are just stabbing a new long block in it. I’m not the most mechanical person in the world and have done that successfully, so I would trust most GM techs to handle it. The window stuff is a lot about cosmetics in the end, and I don’t trust them to not make a mess of that. 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Latest Articles

  • Posts

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...