Jump to content

Is my fuel pump a whiner?

06pirate

Recommended Posts

06pirate Enthusiast

06pirate

Posted
Posted

This morning driving to work, after being on the road for about 5 minutes, I heard a whining sound from the rear of the truck, sure sounded like near the fuel tank area. This happened again two more times about five minutes apart (my total commute is 40 minutes). Each time it lasted only about five seconds. It happened again as I was leaving work, about two minutes after I started the truck. Note that in the morning the temperature outside was 19 degrees, and after work it was 26 degrees. No performance issues at all, engine still ran smooth and strong.

 

It isn't rear-end howl, nor wheel bearing chatter. I can't think of anything else that would produce this noise back there. I'm looking for ideas.

 

The truck is a 2006 GMC Sierra K1500, 5.3, 4x4, X-cab, short bed, SLT, trailer package, Z71, etc., with 140,000 miles on it.

 

I don't think I have any water in the tank, although that is certainly possible.

 

My main concern is if this is a precursor to the fuel pump giving up, then I'll get it changed quick before it leaves me stranded on some logging road somewhere.

 

In the experience of this group, is this whining noise something that predicts imminent failure of the pump? Just cold weather? Contaminated filter making it cavitate?

06pirate Enthusiast

06pirate

Posted
  • Author
Posted

The times it happened the truck was moving, but at various speeds, (35 to 70), but it was a very fast, high-pitched whine, sounded the same, not seemingly related to vehicle speed.

 

I'll be checking the pressure this weekend if I can, (can't do it before that) but I'm concerned if failure is likely the next day or so.

intheburbs Enthusiast

intheburbs

Posted
Posted

Turn the ignition on, but don't start the engine. Do you hear it?

 

It will also tend to be louder when the tank is closer to empty.

 

Mine whined for about a year before it died. It tended to whine the loudest on long road trips.

06pirate Enthusiast

06pirate

Posted
  • Author
Posted

Guys, I am really sorry to have wasted your time with this thread.

 

Number one, I should have "searched" before posting, I would have seen the other threads on this subject.

 

And "B", It wasn't anything to do with the fuel pump. It was the rear end. And the Grenade 80 lived up to its name, it blew up today.

 

I left for work and it started whining about three miles down the road and I hit the brakes to see if the sound changed with vehicle speed, and sure enough, as I slowed, the sound lost pitch and volume and stopped when the truck stopped. I made it to work, and then the same thing happened on the way home, again after about two miles. When I stopped at the local post office, as I pulled out of the parking lot, there was a loud crunch sound and for about three seconds or so, I had no drive, it was like everything was slipping. Then it grabbed again, and I limped it the last 1.5 miles home making weird noises.

 

Thinking back, about a month ago I was on some slick dirt and I remember the locker taking a couple of quick hits in a row, and I'm sure now that precipitated this. Oh, well, I half expected it given the number of failures I've seen here and on other parts of the interweb.

 

I'll have it towed to the dealer tomorrow and see what's up.

00Silverado4x4 Senior Enthusiast

00Silverado4x4

Posted
Posted

Well at least the truck still got you home. Once you get a chance to get it looked at, let us know how it goes. I'd be interested to see what may have happened in there.

KMGZ400 Senior Enthusiast

KMGZ400

Posted
Posted

If you plan on keeping the truck for a while Id look into getting an aftermarket locker like a Detroit or if you don't care just put and open diff in there.. One of my old gmt800's didn't have a locker and it was nice to not worry about it

02suburbanZ71 Senior Enthusiast

02suburbanZ71

Posted
Posted

Sorry about your gov-bomb. All 3 times i've heard that noise i've lost drive. Its like putting nails in a blender. Then you stop, foot off the gas and the speedo reads 25 mph and you aint movin

  • 2 weeks later...
06pirate Enthusiast

06pirate

Posted
  • Author
Posted

Well, I was wrong on both counts. Not the fuel pump, and not the G80.

 

After having it flat-bedded to the dealer, they got looking into things and the rear end was fine. Turns out the transfer case was the culprit. The technician showed me the oil they drained out of it, it was so full of metal it clanked when poured. Not just little sparklies, but pieces of steel and aluminum. A bearing and other things had gone bad. I didn't waste money and time having them tear it apart, it's not something I wanted repaired or rebuilt. I needed the truck ASAP and had a new unit put it. Not only did it fix that recurring "SERVICE 4WD" light I had been getting for some time (gee, ya think?) but also cured that annoying drive-line clunk that has always been there. The old transfer also made a LOT of noise when shifting, a kind of grind and clunk and groan. New one is slick and smooth, just goes "whiirr, click".

 

On another note, while it was in the shop (two days), I rented a 2014 Silverado Crew Cab LT. NIIICE! I really hated to turn it back in. I liked it a lot but not enough to spend the money to get one.

SouthernSilveradoGuy85 Senior Enthusiast

SouthernSilveradoGuy85

Posted
Posted

Well, I was wrong on both counts. Not the fuel pump, and not the G80.

 

After having it flat-bedded to the dealer, they got looking into things and the rear end was fine. Turns out the transfer case was the culprit. The technician showed me the oil they drained out of it, it was so full of metal it clanked when poured. Not just little sparklies, but pieces of steel and aluminum. A bearing and other things had gone bad. I didn't waste money and time having them tear it apart, it's not something I wanted repaired or rebuilt. I needed the truck ASAP and had a new unit put it. Not only did it fix that recurring "SERVICE 4WD" light I had been getting for some time (gee, ya think?) but also cured that annoying drive-line clunk that has always been there. The old transfer also made a LOT of noise when shifting, a kind of grind and clunk and groan. New one is slick and smooth, just goes "whiirr, click".

 

On another note, while it was in the shop (two days), I rented a 2014 Silverado Crew Cab LT. NIIICE! I really hated to turn it back in. I liked it a lot but not enough to spend the money to get one.

 

I had always wanted a a new '14 ever since seeing it unveiled. When I went to the dealer looking for a new truck I was actually looking for a used Silverado, but they can't keep used trucks and the only full size they had was an F150 so that wasn't an option lol. So I started looking at the '14s and of course he had me test drive the one that met what I was looking for and fell in love with it within 1 mile of driving it. I couldn't say no after that and worked out a pretty good deal. I'm really glad I got it. It's exactly how I'd want a truck other than I wish it had Bose (the non-Bose system is still really good) and that it has 3.08 gears which I plan on changing.

Archived

This topic is now archived and is closed to further replies.

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