Jump to content

Front Wheel/Axle Noise?

Coop8202
 Share

Recommended Posts

Coop8202 Enthusiast

Coop8202

Posted
Posted

Have a 2020 Silverado 1500 making an awful grind/whine noise while driving. Starts after warmed up. Had same issue at 28,000 miles now at 56,000 miles. 4wd does not affect noise. I believe dealer replaced front cv axle first time around but cannot find paperwork to verify. See links below (sorry for the wind noise):

 

https://youtube.com/shorts/IseghbusjB8?si=n7IulrwaaYsnpfb3

 

https://youtube.com/shorts/-KWPtfh_geU?si=JsYIV-gvJHnNIAsj

 

https://youtube.com/shorts/1xdrKx8x2KY?si=UkJG28_7yNizv73R

Coop8202 Enthusiast

Coop8202

Posted
  • Author
Posted
16 hours ago, Mario C said:

Thanks for this. Wondering was this covered under warranty. 

Should be, taking it in Thursday

Coop8202 Enthusiast

Coop8202

Posted
  • Author
Posted
2 hours ago, silveradosid said:

one video sounds like the dust shield is rubbing the rotor, does the noise get louder when you turn either way

I thought the same thing, took it all apart and turned out to be the brake wear sensor loose and rubbing/grinding. Video 1 is a different issue being addressed at the dealer Thursday. Sensor is $13 at Autozone.

Mario C Enthusiast

Mario C

Posted
Posted

That’s the same noise I hear. Problem is when I drop off at dealer they will say they can’t hear it because it hasn’t warmed up. Hopefully they can tell. 

Coop8202 Enthusiast

Coop8202

Posted
  • Author
Posted
15 hours ago, Mario C said:

That’s the same noise I hear. Problem is when I drop off at dealer they will say they can’t hear it because it hasn’t warmed up. Hopefully they can tell. 

Which video?  1 or 2, 3

Mario C Enthusiast

Mario C

Posted
Posted

Hey guys. So my front end noise. Had the mechanic at my Gmail dealership come for a ride. He thought it was brakes until I put in 4x4 and noise stopped. Brought the truck in today and they still say it’s my front brakes need replacing even though the computer says there at 65 percent. Didn’t know why noise stops in 4x4. Very frustrating. Especially when charged 200 dollars. 

Coop8202 Enthusiast

Coop8202

Posted
  • Author
Posted
4 minutes ago, Mario C said:

Hey guys. So my front end noise. Had the mechanic at my Gmail dealership come for a ride. He thought it was brakes until I put in 4x4 and noise stopped. Brought the truck in today and they still say it’s my front brakes need replacing even though the computer says there at 65 percent. Didn’t know why noise stops in 4x4. Very frustrating. Especially when charged 200 dollars. 

Sorry to hear that, Mario. Just got off the phone with dealer, they are trying to say its the brake pad wear sensor. I told them I didn't agree, to unplug it and reassess. Picking it up later. Will update 

Coop8202 Enthusiast

Coop8202

Posted
  • Author
Posted
On 9/20/2024 at 9:54 AM, Mario C said:

Ok thanks. Let me know how you make out. 

Mario, ended up being the brake wear sensor that caused both noises from the videos. I took it out from behind the pad and zip-tied it. No more noise, at least that I can tell, thank God. $13 part at AutoZone. The dealer quoted me $150 to replace it...

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
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      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...