ltoolio

Just tried, and no-go. No change in the amount of movement.

Didn't have a chance to buckle everything back together last night, so still haven't been able to test the clutch possibility. Will be taking the wheel off a bit later today just to remove the brakes as a possibility.

dr bob

Please take the steps I recommended in post 7 and report back with results. The pads rock ever so slightly in the caliper. Even when clamped on the rotor. The parking brake shoes move a little on their springs. Even when expanded in the drum.


Lots of things on the cars "worked fine when I parked it" but still have the potential to stop working.

If I depended on "worked fine when I parked it", the only things that would ever need attention would be things that failed while I was driving. For me anyway, more things "fail" as a result of something I did while the car is being worked on or parked than give up while I'm actually driving it. That's either my stellar rusty-wrenches PM program, or I don't drive the car enough. Or a blend of the two. I know I need to drive it more to even up the odds a bit. It's end of summer and I just put my second tank of gas in it this year.

Back to your car: The brakes are holding the wheel from turning.

ltoolio

This is what I deserve to do to myself:



Maybe a little dramatic, but this is why I'm still a n00b and what you guys have multiple thousands of posts and helpful, thorough responses.

Yes. Pads were frozen to the rotor. Compressed a bit and wheel rotates now. Crisis averted and lesson learned - what could be the cause, what was the cause and that I can't jump to what my still-in-many-ways-ignorant mind thinks it knows.

Thanks to all for the input, and especially to the dr for the guidance and the kick in the ***.

Randy V

That's gonna leave a mark.

Wisconsin Joe

Meh. Don't beat yourself up too hard.

Use it as a "Learning Opportunity."

Learn that:

It's often not as bad as we think it's going to be.

Methodical troubleshooting, following a good, thoughtful process is always the best route.

The advice given by the "smart ones" here is always worth following. It may not be correct, but it will eliminate possible causes, rather than send you on 'wild goose chases.'

Ignoring the suggestions from the "smart ones" on here will often leave you in the position in the above pic.

dr bob

Troubleshooting, at least the way I taught it for a couple decades, is really nothing more than identifying and listing possible causes, then eliminating them in some logical sequence. One person's definition of "logical sequence" may be way different from another's, so I seed the sorting with last thing I worked on, ease of testing, cost of testing (in both time and $$). How you sort things can alse benefit from gathered knowledge, hopefully based on the mistakes others have made rather than ones you have made. Education being cheaper than experience in most potentially-negative cases.