Skip to main content

Miata: Maintenance thoughts

It was a lot of fun, mixed with a lot of labour, and a little frustration (silly exhaust system).

Would I do it again?  Absolutely.  Would I do it again next week?  Ah, no.  Maybe next year.

I think the most fun was all the new things I got to do:

  • Using an engine hoist to remove a functional engine/trans from my daily driver
  • Changing a clutch/flywheel
  • Bleeding the clutch system (thank you, 949racing!)
  • Now knowing how to bleed the brake system
  • Putting a valve cover gasket on (we'll see how the sealant works out)
  • Removing suspension from a car I was promised required two people to do...by myself :) (yay leverage)
The planning/reading was enjoyable as well.

I think the worst part of the job was trying (and failing) to get the exhaust unbolted.  Pretty sure it'll need to be cut out whenever that job comes up - stripped one of the cat bolts using the impact gun (the other one came out fine :S ).  Wasn't even going to attempt the header->downpipe bolts...haha zero room.  

Also...the rearmost PPF bolt was NOT moving.  I had a 30" 1/2" breaker bar on it...pushing will all my strength just flexed the bar!!  With the little compressor I had...the impact gun made....no impact....  At any rate, that was not a deal ...breaker?

What surprised me most was how simple the process really was, once you knew what the components were and how they plugged in/attached to the block.  I won't detail it to save boredom, but it really was, unbolt the big stuff, unplug connectors, unbolt the small stuff, forcibly remove engine (it did require some encouragement).  Putting it back in went much faster even though I was on my own (had a helper during the removal).

The firing order in the Haynes manual was reversed...this was a big delay (~1-2 hours), also fiddling with the idle, and looking for what could be causing the weird noise (that disappeared after an hour of driving) - those also caused unnecessary delays.  However, the engine is now running MUCH better than it did before - idle droop is gone - albeit the exhaust smells of running very rich, how it has been since I got it.  I think that change will require perhaps a new O2 sensor?  Or a MSPNPv2 :)

Further revelation is that a V8 swap is off the radar - the car is lots of fun with stock power (new flywheel/clutch has a big part in that) - if anything I would do a 1.8 swap (~5% the cost of a V8 swap) for that additional 30hp, and then a low-PSI turbo kit.  With the gearing the way it is, car is not pleasant to drive above 100-120km/h, so big horsepower turbo just doesn't make any sense to me.  It's got probably 80-90whp as it is...I'd say 150-200 would be plenty - puts the power:weight ratio in Corvette territory.  Those numbers are also well within what a moderate turbo 1.8 could do on pump gas.

Enough rambling.  

I'm still not 100% convinced the suspension is correct, but so far only bad potholes are jarring.  I'm guessing this is normal due to the shocks/bumpstops/shockmounts actually being functional, rather than super spongy/loose.  If it's still really bad with the 14" wheels, I'll go back in to investigate.  Otherwise, car is running great (ok, 2nd gear is unhappy with the cold weather)...for a 20 year-old car!!!

Gonna stop worrying about it and just enjoy it.

Comments

  1. Nice work, Chris! Sounds like it was a fun project. :)

    ReplyDelete
  2. Yar, it was. I failed to mention how, in my rush to complete the suspension, I neglected to place the passenger-front sway bar inside its mount prior to bolting/torquing. Haha, glad my guess as to what that awful clunk was proved correct.

    All good now, tho!

    ReplyDelete

Post a Comment

Popular posts from this blog

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder:


You are trying to set up replication for a DFS folder (no existing replication)Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2)You have no issues getting replication configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally you get EventID 4312:
The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.  Additional Information:  Folder: F:\Users$\user.name\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D-5E67-4DA1-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):
MSSQLSVC/tor-sql-01.domain.local:1433

If you use a user object to auth (such as a service account, or admin account):
MSSQLSVC/username:1433

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/server1.company.local:1433 is registered on these accounts:
CN=SERVER1,OU=servers,OU=resources,DC=company,DC=local
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get going...so here's a config and brain dump...

Why?
You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

How?
ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
OMD
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…