Skip to main content

Miata: Order of operations

Just trying to sketch out ahead of time what order things should be done in so as not to waste fluids and/or time.  Haha, jeepers.  Better get a head start and clean the garage up tonight...

I spoke to Sylvie at Robert-Piece-Auto yesterday, she said the FM parts have been ordered!  So probably safe to say it'll be at least next weekend before everything arrives.  Waiting on the FM/Moss stuff, another Rosenthal order, 949racing parts, and I have to get some more tools/miscellany.

Preliminary prep work

  1. Clean floor around work area
  2. Lay out necessary tools
  3. Car onto jackstands - at least 18" clearance
  4. Disconnect battery
  5. Spray all bolts to remove with penetrating fluid & let sit overnight
    1. Transmission & diff fill ports
    2. Transmission bellhousing bolts
    3. Exhaust system bolts
    4. PPF bolts?

Phase1 - Fluid drain

  1. Remove undertray
  2. Remove intake ducts
  3. Drain coolant
  4. Drain transmission oil
  5. Drain diff oil
  6. Drain engine oil
  7. Close all drain valves/bolts
Phase2 - Cooling system and top of engine
  1. Remove radiator
  2. Remove all old coolant hoses
  3. Remove plugs & wires
    1. Check compression & note results
  4. Remove valve cover
  5. Mark & remove CAS sensor unit
Phase3 - Transmission removal & rear of engine
  1. Disconnect anything transmission-related for the clutch job
    1. Exhaust pieces
  2. Drop transmission
  3. Remove clutch/flywheel
  4. Remove slave cylinder & clutch hard line
  5. Clean transmission & rear of engine
  6. Remove & replace 'cursed' coolant plug
  7. Replace rear crank seal
  8. Replace front/rear transmission seals
  9. Replace trans gasket
  10. Replace fuel filter
  11. Shifter turret maintenance while outside of car?
Phase4 - Transmission install & clutch bleed
  1. Install new 949 clutch line & slave cylinder
  2. Install flywheel/clutch and parts
  3. Re-install transmission
  4. Re-attach all transmission-related stuff disconnected for clutch job
  5. Flush & bleed clutch/brake systems
Phase5 - Suspension
  1. Compress springs & remove shocks, bumpstops
  2. Clean suspension tower area
  3. Install new shocks & bumpstops to spec
Phase6 - Cooling system re-install & intake clean
  1. Install new cooling system components
    1. Thermostat & gasket
    2. Coolant hoses & clamps
    3. Radiator
  2. Replace CAS & o-ring
  3. Replace valve cover & gasket
  4. Replace filters
    1. Engine
    2. Air
  5. Clean throttle body
  6. Clean idle air valve
Phase7 - Fluid replacement
  1. Double-check all fill port bolts are torqued to spec
  2. Fill engine oil
  3. Fill diff oil
  4. Fill trans oil
  5. Fill coolant
  6. Verify reservoirs are appropriately full
Phase8 - Test and troubleshoot
  1. Reconnect battery
  2. Start engine until warm
  3. Check fluid levels
    1. Transmission
    2. Engine
    3. Coolant
    4. Brake/clutch
  4. Test drive slowly - issues?
  5. Troubleshoot if so


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$\\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):

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

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/ is registered on these accounts:
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 here's a config and brain dump...

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)

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
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…