Jump to content

Recommended Posts

Posted

In my experience, this is very common of leaf sprung trucks. I’ve owned many trucks from various brands, and I’ve had to either grease and/or replace those pads in most of them to stop the noises that develop. I consider it to be part of normal maintenance.

Posted

Thanks for the TSB and part #s. Mine started doing this about 4 months ago when COVID was just flaring up and I didnt want to deal with the dealership. I placed some 1/8” thick rubber between the leaf springs as a temporary solution and it got rid of the noise completely but looks terrible. I will order these pads if available and use those since they look much better.

Sent from my ONEPLUS A6013 using Tapatalk

Posted

I'm happy to report I had TSB 19-NA-129 performed today and the rear suspension is now quiet as a church mouse.  They put in the four new spring inserts/isolators and retorqued the U-bolts.  Everywhere I've driven today that would normally generate the clunking sound did not cause any at all.  So far, so good.  ??

  • Like 2
Posted
On 7/29/2020 at 6:31 PM, dmitrysgarage said:

Did it fix the issue?

Absolutely! No noise at all now. 

Posted
On 7/30/2020 at 10:03 PM, Chrisd534 said:

Absolutely! No noise at all now. 

 

On 7/30/2020 at 7:33 PM, lapoolboy said:

I'm happy to report I had TSB 19-NA-129 performed today and the rear suspension is now quiet as a church mouse.  They put in the four new spring inserts/isolators and retorqued the U-bolts.  Everywhere I've driven today that would normally generate the clunking sound did not cause any at all.  So far, so good.  ??

 

Nice thanks guys! So much for the "it's normal for it to sound like a medieval carriage" nonsense. Going in Tuesday as I'm now throwing a CEL related to the brake module too (P25A2-00 Brake System Control Module 1 Requested MIL Illumination).

Posted

Well, I went to the dealer this AM and they fixed it up right after lunch time.

  1. They did that TSB everyone else had (19-NA-129) which eliminated the sound. So no it's not "normal" for a solid axle to make that sound:
  2. They did a software flash to address the CEL I had. 
  3. They enabled afterblow for me to help reduce mildew smell. My garage is air conditioned and i think the evap coil was just sitting there wet and never baking off. 

 

  • 4 weeks later...
Posted (edited)

I had inserts put in about a month ago, noise went away initially but is back now.  What gives????  Question, how many new inserts should I have put in?  2 in front and 2 in rear?  Are they indeed gray vs black so I can easily tell if I look at the springs?  

Edited by nluchau
Posted
3 hours ago, nluchau said:

I had inserts put in about a month ago, noise went away initially but is back now.  What gives????  Question, how many new inserts should I have put in?  2 in front and 2 in rear?  Are they indeed gray vs black so I can easily tell if I look at the springs?  

The lubricant they squirted between the pads and the leaves has washed away.  The pads do nothing to solve the problem.

Posted
13 hours ago, lapoolboy said:

The lubricant they squirted between the pads and the leaves has washed away.  The pads do nothing to solve the problem.

Interesting!  Why would they replace the pads then if it doesn't remedy the issue?  Note: The pads were on a later revision of the Service Bulletin also.  

  • 5 weeks later...
Posted

I just hit 12,000 miles and the same noise started.  My truck sounds like an old squeaky truck coming down the road.  The squeak is coming from the driver's side rear.  At least when I take it in, I have the service bulletin so they can't give me any trouble.

Posted

My 03 2500HD Duramax has 278,000 miles on it and the springs don't make any noise. That's not normal. I hope they fixed it as mine was a very recent build.

Sent from my SM-A505U using Tapatalk

  • 2 weeks later...
Posted

Torqued mine, Bet they were less than 50flbs, I did it before it made any noise and had bout 500 miles on truck so maybe saved the factory inserts..

  • Like 1
  • 1 year later...
Posted
On 7/27/2020 at 8:19 PM, Dean Sterling said:

I replaced the pads last week that lapoolboy linked. So far so good, I had a bad squeak from any movement at all. Hopefully this fixes it for a while.


Sent from my iPhone using Tapatalk

Where did you buy the pads?

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   4 Members, 0 Anonymous, 2,136 Guests (See full list)


  • Latest Articles

  • Posts

    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...