Logan

Today I wanted to write at length about our big old black lab mix Logan.

In September of 2013 we euthanized our longtime mixed herding dog Rocket after he had contracted bone cancer and undergone a hind-leg amputation. He had about a year after the amputation and continued in good spirits to the end. Putting him down was emotionally very difficult for me as he had been my primary social companion for about six years, and he was an extremely intelligent animal with a large and continually expanding vocabulary.

We put him down just before I met my birth mother in person for the first time when she came out to meet me and visit later that month.

Vivian and I began to discuss the possibility of another dog sometime the next spring, probably around my March birthday. Sometime in May or June 2014 we went to an animal adoption event on the Eastside, possibly in Bellevue. We had thought about looking for a German Shepherd or similar dog but the adoption expenses for the puppies available at the event were higher than we desired and so we kept looking. We did not really intend to pick a dog that day. Our thought was more that by attending we could familiarize ourselves with the way these events work.

We noticed an older dog, a large black dog that appeared to be a lab/shepherd mix. He was evidently depressed, non-interactive and lying flat in his cage showing little interest in the proceedings and attracting no notice. I was interested in his apparent calm and so we took him for a short walk, and he demonstrated good knowledge of basic commands.

Unexpectedly we decided to take him home that day. Later we found that black dogs, especially larger older black dogs, have very low rates of placement from shelters, apparently because of concern about shedding in indoor environments.

The shelter told us that he had been found feral in the woods in Snohomish County and that they estimated he had been in the woods for a couple of months. He had a chip when he was found but the number recorded in association with the chip did not produce any response when called. The shelter would not disclose the name of his former family to us.

The adoption fee was about $150 which was supposed to cover exams and meds needed when he came out of the woods. I am skeptical that he received this care because as soon as we got him home, we observed worms in his stool and took him in for treatment.

He did not seem to know what furniture was for when indoors and he had clearly been subject to hose discipline, leaving him fearful of running water and bathing for the rest of his life. Over time he came to understand that couches were softer than the floor and would climb up on them. He was always resistant to certain expressions of physical affection and reluctant to maintain physical contact with us. However as soon as he walked in the door, our tiny longhaired tortie cat Lark nose-touched him and then headbutted him, expressing immediate affection and acceptance. He reciprocated kindly and patiently, and I never saw him express a dominant motion toward her. He was always extremely phobic of loud noises such as thunderstorms, firecrackers, and gunfire.

He would alert on pickup trucks and especially on trucks driven by women. Taken all together, we suspect that in his former life he had been an outside dog and probably one in a rural environment.

Sometime before late June Vivian and I sat on the porch trying to come up with a name for him. I wanted to name him “Kuma”, “Bear” in Japanese and the nickname of then-rookie Japanese Mariners pitcher Hisashi Iwakuma. I suggested it for that reason and because the big black dog looked somewhat like a bear. Vivian then suggested “Wolverine”, thinking it was the same as a wolf and also due to the popularity of the Marvel comics superhero character Wolverine and portrayed by Hugh Jackman. I chuckled and pointed out that a wolverine really doesn’t look much like a dog. However, I noted, the character’s given name is “Logan”.

As soon as I said that word, the dog, who had been lying disinterestedly on the porch, thumped his tail and put his head up. He got up and came over to us and continued to respond very directly to the word “Logan”. He clearly understood it to be his name. We can’t ever know if that was the name he had previously, of course, or if it merely sounded similar enough to his original name, but in effect he named himself.

The first time we went through a thunderstorm with him he was completely inconsolable and it was a trying experience for all of us. Over time we learned to give him benadryl to settle him down during noise events and he did begin to ease up in his phobia about it after a few years.

He also had significant separation anxiety and would not accept caging, crating, or being consigned to a small room. He managed to claw his way out of both a portable cage kennel and an airline large-dog transport container, thankfully not while in cargo. Several doors in the house show significant clawing and chewing from early in his time with us.

The worst thunderstorm related event was on an afternoon when I had intended to go to an afternoon Mariners game that Kuma was starting. As I showered at about 11am during the storm, he whimpered and yipped and whined outside the closed bathroom door, eventually hurling himself against it and attacking the molding outside the door with such intensity that I had to refinish the molding to a height of about three feet. In the end with him experiencing such fear and anxiety I stayed home and watched the game from the couch with Logan by my side. That game, on August 12, 2015, would prove to be the best game that Hisashi Iwakuma ever threw, a no-hitter against Baltimore with no runs and three walks allowed, two in the fourth inning and one in the eighth.

After a few of these extreme reactions we began to wonder why he was experiencing such strong fears and anxieties. We easily related his separation anxiety to the loss of his prior family, but did not have a clear hypothesis for his extreme reaction to storms in particular. After thinking about it for a while we formed an untestable hypothesis that fits the information we were given by the shelter, as sketchy and questionable as it may be. It may have taken us some time to come up with it – I note it in a blog post from the following April, in 2015.

We adopted him in May or June. We were told that he had been in the woods in Snohomish County for an unknown length of time, possibly two months. His chip appeared to be associated with an active number but that number never produced a response.

On March 22, 2014, an enormous landslide took out a suburban neighborhood in unincorporated Snohomish County as well as other buildings within the mile-long slide. If we adopted Logan within a month or so of May 22, which seems likely – our first vet bill associated with Logan appears to be for deworming meds in late June, 2014 – then the timeline for his ferality, the lack of phone response, and as well a possible explanation for both his phobic response to storms and his frantic separation anxiety seems within reach. We will never really know, of course. But it’s certainly a possible explanation.

After he bonded with us some of that anxiety diminished over time. He appeared to be affected by the lower-spine and rear-leg issues that can affect shepherds and one of the types of dog he was always eager to interact with were shepherds. I formed the hypothesis that his mother may have been a shepherd or that he was raised in a dog population that included shepherds.

He was only ever interested in playing with balls, stuffed animals, rope tugs, and chew toys were not of much interest to him. He was very strongly treat motivated and once he’d begun to interact with us on a basis of verbality he quickly acquired a limited functional vocabulary of his own. A tail thump or vigorous wag meant “yes”, an eye roll or redirected gaze away meant “no.” A single quick lip smack meant either “yes I am hungry,” or “I want a treat”. He would sit just outside the kitchen and gaze meaningfully at the treats stored on top of the refrigerator until asked “Do you want a treat?” The query would produce a lipsmack and a more pointed look at the treat container, followed by a look back to his interlocutor to observe if the intended effect had been accomplished.

As he aged and his rear legs developed issues we stopped bringing balls for him to chase. About three times he developed a rear leg injury that produced a yip and persistent limping. Twice these were diagnosed by two separate vets as canine cruciate ligament tears requiring surgery and we were advised that left untreated the other leg’s CCL would fail and this eighty to ninety-pound dog would be left unable to climb or descend stairs. By the third time it happened we did not even seek a diagnosis, we just let him heal on his own as he had the other two times.

He was unfailingly cheerful and kind and developed many human friendships in the area, especially with our neighbors David and Dot. Dot adopted an energetic pup named Scout and I would occasionally walk her together with Logan. She adored him and he found her a bit rambunctious for his elderly self. He would take the time to try to calm her down when she was smaller. By the time she was larger she did not try to wrestle with him anymore but always became nearly uncontrollable with excitement when she would see him.

He did have a tendency to bark when on leash and seeing another dog. Sometimes this would lead to escalations in behavior in both dogs and I took to walking him in a harness so that I could haul him up and away. The only times I ever saw him act in aggression were when he interpreted another dog’s behavior as an attack, and he was impressively frightening in these moments. I assume that this likely represented adaptive behavior from his time in the woods, but it may well have been encouraged in his time as a rural outdoors animal as well.

I wanted to take the time to write as much of this down as I could today because yesterday at about 2 pm we euthanized him. He weighed a bit less than 84 pounds at the end; his preferred healthy weight was about 89 pounds. He fell ill just about a month ago with what we took for a flu or something along those lines and had taken to not eating and drinking. Vivian and I had ourselves fallen ill in mid-January, the week of the 19th, with several successive illnesses (flu, possible food poisoning, another flu) which actually may have delayed us getting him to the vet by a few days. It was a little weird that all three of us were coughing and sleeping all day in discomfort.

We were finally able to get him in for treatment on the 24th of January and he was held overnight for rehydration and to give him antibiotics to bring his fever down. On the 27th we took him in again for swelling in his forelegs and for some different medications. At this point everyone involved still thought we were looking at a conventional transmissive illness although we were uncertain how he might have been exposed to it as he typically did not have any social time with other dogs.

On the 2nd of February we started a second round of 10-day antibiotics as his cough had not lessened over the prior treatment, and again on the 12th. On that day I specifically asked for an x-ray and the x-ray clearly showed a large mass in Logan’s right lung which seemed likely to be a cancerous tumor. We waited two more days, until Friday the 15th and brought him in again to attempt to get the mass lab analyzed for cancer and to get non-x-ray imaging (ultrasound). We ten took him home to observe his resting over the next couple days to see if his breathing worsened or not. That afternoon I had a conversation with the primary vet on Logan’s case and he advised me that while they would not have the labs back until after the weekend he strongly suspected the growth as cancer and that it would rapidly worsen and that it was time for us to begin considering euthanasia.

This aligned well with what my own non-professional research seemed to indicate, and I let Viv know about it as soon as she returned from an errand.

By this time Logan was refusing medication and nearly all food and had noticeably lost weight. He was disoriented and anxious when medicated and as we were expecting that the medication would not relieve his symptoms in any case we stopped trying to give them to him.

His frequency of coughing was a fit every hour to forty-five minutes, usually a set of three or four coughs. This appeared to produce fluid or phlegm that he would then swallow.

The next day, Saturday the 16th, Viv offered him cool boiled and shredded chicken in a light chicken broth and he greedily ate a few bites and lapped at the broth. A moment later he began to vomit, producing a mix of blood, broth and phlegm. We brought him in again and were advised that the blood might not be from his lung or his stomach but to watch for more blood.

That afternoon he began producing more bloody vomit as well as significant amounts of just blood when he coughed. I advised the vet via phone and he seemed to think that was effectively definitive. I wanted to wait until the lab results returned to be certain. The doctor advised me that even if the tumor was not cancerous the recovery process would be challenging for the dog and we should still consider euthanasia as the best option.

Logan’s breathing and coughing continued to worsen Saturday night the 16th and through Sunday the 17th into Sunday night. I called Monday the 18th seeking the lab results but they would not be available until Tuesday the 19th. Overnight Monday into Tuesday was difficult for all three of us and at around midnight Vivian shifted to the floor to sleep next to the dog. His coughing and breathing had continued to worsen, and he was coughing for about five minutes every half-hour and often producing blood.

Monday afternoon we took him for his last, very short walk, to our neighbor David’s place. David and Logan were good friends and Logan would often pull to visit David on our walks. Logan’s other neighbor friend was Dot and she was able to come by and visit him at our home on Monday evening at about 6.

Early Tuesday morning we were advised that the lab results were positive for cancer and so we made arrangements with the vet to have an in-home euthanasia, which we did. They came at about 2pm and we put him to sleep on the floor of our media room. I helped them put his body into a heavy plastic bag and together with them we put him into their vehicle.

We opted for the private cremation and a container return and hope to have him back home with us shortly.

Solar wear

in 2013 I bought this 60-LED solar-recharge security light on Amazon. This winter it failed and I took it down to see if it was the battery or not. It did appear to be the battery but I was unable to locate the exact replacement, a welded pack of five 1.5 volt AAs with an aggregate output listed at 6v on the battery wrap itself.

I thought I had found the correct replacement at Home Depot for about $15, a special-order item, but the unit that arrived appeared to be wired backward, either a manufacturing flaw or simply a battery with reversed polarity. I was kinda grumpy about a $15 battery anyway and just returned it.

Once I had determined that the battery was dead I pulled the wiring harness off and experimentally attached it to a 9v battery, and the light illuminated very brightly. What I don’t know is how many illumination cycles the battery might support, and of course finding a rechargeable battery would be even more preferable – the solar array is still producing juice without difficulty.

UPDATE: Sunforceproducts.com sells the part for $10, fee shipping. Ordered.

New Boots and Contracts

This past week or so of torrential rain preceded by snow let me to discover what I had already known, namely that my ten-year-old Docs are about as useful as a pair of sandals in keeping water away from my feet. It’s my own fault, I did not know where our show care kit was here in the house after we moved here for many years and by the time I got around to finding and restocking it the leather was thoroughly cracked and useless.

So I needed a new pair of boots! I had the idea of an appropriate price point for the boots, DM’s classic 1460, at $60-70 or so and was shocked and frustrated to find that the average best price for a standard-edition black version of this boot is about $120 and that the boots themselves appear to be in relatively short supply from independent sellers online, usually the best place to look for a MAP-controlled item such as these appear to have become in the last decade.

Even eBay has only a few merchants selling the boots new, although there are many individual and pro sellers offering a range of Doc Martens footwear both on eBay and Amazon. Buying direct, we see that the boots are offered at $135 + tax and shipping (with frequent free shipping offers).
eBay’s results are a mishmash of used and new goods. It was difficult to determine the correct pricing for new 1460s that met my specs. This is in part because DM has dramatically expanded the range of models of this boot. They range from high-end guaranteed for life and/or Made in England throwbacks to inexpensive non-leather canvas models made in China and Thailand. In the end, there are only a few new-in-box listings, with an offer point of about $115.

Amazon’s offerings are even more confusing. I think this is due to the platform’s stated policy of combining seller’s offers for a given SKU into one detail page. Sadly, they are not actually able to enforce the policy effectively. It’s nearly impossible to determine a set of prices for goods such as this, in which individually distinct products differentiated by style, model, materials, appearance, and size are randomly grouped together in detail pages aggregating seller’s offers both active and inactive.

It’s the functional equivalent of matrix pricing, which is the underlying economic mechanism driving spiraling healthcare costs and software licensing cost uncertainty. It unquestionably increases profitability on a unit-sales level for Amazon. Creating conditions of obfuscated pricing reduces consumer willingness to research and evaluate for cost, due to time constraints. The long-term effect is to increase the average price paid. However, in a consumer-goods environment, this may also cause lower overall volume as price-constrained consumers decline purchases, an option not available in medicine.

I was somewhat amazed to see this occurring because it inverted my consumer expectations for a shopping experience between eBay and Amazon. Amazon was once the most efficient place to locate a good, determine a fair price for it, and to purchase that good with a high degree of consumer confidence. Instead, although eBay has a smaller set of pro merchants selling the goods, I was able to find and compare those seller’s prices with DM’s full-retail price immediately. On Amazon, detail page selections changed apparently at random as individual seller’s stock levels fluctuated. Instead of a single price per detail page, each variation of an item was priced distinctly. It was the opposite of a smooth online shopping experience.

In the end, I made the inefficiencies of Amazon’s shopping model work for me by literally going through each 1460 listing’s detail page and selecting each instance of sizing that fit me and was in stock. I did not find any NIB black 1460 that fit me and met or were even close to my pricing expectations. I did, however, find two pairs in brown, one a new-fangled variation, each for about $75, each in low stock quantities and discounted by the merchants due to low demand.

Another possibility I did not pursue was locating and purchasing two pairs at a second-half-off price with the intent of selling the second pair NIB on eBay just under the $120 price point. I may actually experiment with that, as arbitrage is a pretty good online merchandising model.

UPDATE:

To my bemusement (and living up to my site slogan, “holy cow, did I write that?“) I appear to have predicted this exact outcome specifically for Amazon and in part due to attempting to shop for boots online:

I strongly suspect that the partial progress in place in Amazon and eBay to increase transparency to the purchaser will be eroded over time as these organizations seek in turn to emulate Google in its’ disheartening turn toward user captivity. …The end result of this will be to diminish, to some extent, the long-term shift toward online shopping, while at the same time increasing margins only for the largest merchants. And it will keep the process of shopping for women’s boots online a fruitless nightmare.

I was actually referring to Google and Apple (and eventually therefore Amazon and eBay) seeking to emulate Facebook’s walled-garden approach as a means to diminish price transparency. As it happens, that is not the mechanism by which Amazon has achieved diminished price transparency. but hey, whatever works. Or makes life harder for the consumer, at any rate.

 

noted for future reference

I installed a 200-lumen battery-powered dark-and-motion sensor spotlight with a 20 second cycle under the carport on Viv’s driver side. It’s all plastic, so we’ll see how it fare amidst the elements. I note the install date here via this post so that I will have a sense of how long both it and the 3 D-cells it uses last.

A deep draught

John Seabrook, Behind the Cellar Door, The New Yorker, January 23, 2017

I enjoyed this very much, as it refracted some aspects of my father’s relationship with wine, and my own, back to me.

In particular, parts of this passage:

The heavy door swung open, drawing the cool air of the cellar behind it. The viny scent of wine, cut with the stringent reek of strong alcohol, enveloped us. It was pitch black within, and, in the moment it took my father to find the light switch, I imagined a demon rat rushing past us and disappearing into some other part of the house.

Then the lights blazed up on a square room, about fifteen feet per side, filled from floor to ceiling with wine and liquor, resting in sturdy wooden bins stacked four high, stained dark brown and built around three sides of the room, along with a two-sided row of bins in the middle, forming two bays. It was like stepping into King Tut’s tomb.

My father began making wine before I was born and, I presume, collecting it as well. Seabrook’s family experiences with his father’s cellar are on a grander scale than that I share with my father, but that line about the scent chimes with early childhood for me, and by the time I was 16 or so my father built a special room in our basement dedcated to his wine collection, walls lined with bins, a table and notebooks there for recordkeeping, smells and all.

New friends

A few months ago I met our backside neighbors, the tenants of our other backside neighbor. He’s from Paris via Beijing, and she’s from Russia and the Ukraine via Moldova, Romania and Beijing. We like them very much and first fed them here in early autumn, spontaneously one Sunday evening when he’d dropped by to introduce himself.

They had us over last weekend for dinner and it was loads of fun, staying up talking and drinking wine until 2 am, getting to know each other better. He’s an aerospace guy at Boeing, ex-Airbus,  but frustrated by the salaryman aspect of the work. She won a scholarship to a university of Chinese traditional medicine in Beijing at 19 and spent 12 years there, completing her studies.

Our buddy Joe, who spent 8 years in Taiwan and China and married a Taiwanese lady there, invited us over for dinner on Saturday night. Joe and Lilian have a large extended social circle of Chinese and Taiwanese people that live in Seattle, many of whom are in international marriages, and it seemed obvious to me I should try to get our neighbors included in the invitation. In the end, he went, she didn’t, and a good time was had by all. Joe and Jason and I played some music together for the first time in more than a year and it wasn’t terrible and it was fun. Our neighbor kept shooting video with his phone, probably gawking at the Americanness of it all, in the midst of all the baiju and Chinese food.

So far so good

After some instensive digging around various Subaru fora and borrowing an OBDC II code reader from a friend, I still don’t have a good read on the car. The code reader did not show any codes recorded, which seems odd, but whatever.

Fora posts describe my car’s symptoms in similar cars but not the ’99 Forester. The consensus appears to be that transient loss of power accompanied by a front end shimmy is a cylinder misfire, likely due to a bad plug, a bad wire to the plug, or imminent failure of other associated parts. Which, great. Except I have actually experienced this and had all that both replaced and serviced within the last 3k. Furthermore, the shimmy I was experiencing was much less intense than that I had when the cap was failing. 

So possibly that indicates incomplete chamber combustion rather than total non-combustion?

Another possibility, which seems somewhat more likely as it has a possible causal tie to the recent oil change, is that Carter overfilled the oil reservoir. A few posts here and there (interestingly, the most informative one was from a Seattle-area owner who had taken his Outback to “the dealer,” presumably Carter, for an oil change) indicated that oil overflow into parts of the engine that did not need it could lead to power loss, and that this overflow could occur if the oil reservoir was overfilled. The dip stick is said to have fill marks for hot and for cold weather, the cold weather mark indicating a greater acceptable quantity of oil. 

Persons discussing this issue and possibility indicated that burning oil, blue smoke, would be expected to accompany the issue. No smoke has been noted. However, when I checked the oil level this morning it clearly exceeded the highest fill dot level. So presumably they did overfill the car. However others also note that moderate overfills are used in some situations to provide a safety buffer for a car in extreme situations, and this past three weeks might kinda qualify from a temperature perspective, so who knows.

The car had two runs today, each about three miles, and no shimmy or loss of power was resultant.

UPDATE: After subsequent power loss and a diagnostic visit to Scanwest on Greenwood, it was suggested that the ignition coil might be failing. The replacement was within warranty horizon, so I toot it to the initial shop that replaced it, Maddy’s on Aurora, and they verified the issue and replaced the coil without incident.

Alerts

Viv asked me to look into the Diabetes Sentry, a $500 FDA-approved non-invasive perspiration-based wristband glucometer intended for night wear by diabetics and oriented to catching nighttime lows and highs, so I am gathering links in this post. This technology has been in development for years and has always proven challenging to implement, the ideal end-deployment scenario being that diabetics could wear a non-invasive continuous-monitoring glucometer and that device would then feed adjustment data to an automated invasive (or implanted, eventually) insulin pump, establishing what would effectively be a replacement for the diabetic’s damaged organs.

Links:

University of Florida Clinical Trial, 2014. Clinical Evaluation of a Non-Invasive Hypoglycemia Detector in a Glycogen Storage Disease Population “The device often failed to detect hypoglycemic episodes in glycogen storage disease patients and the rate of false positive alarms was high.” 

Bummer.

Journal of Diabetes Science and Technology, September 2015. Hypo- and Hyperglycemic Alarms – Devices and Algorithms. Daniel Howsmon, BS and B. Wayne Bequette, PhD. 

Article includes noninvasive and invasive monitoring devices and concentrates on invasive continuous glucose monitoring technology as demonstrably most effective, noting an approximate 1-in-3 false positive rate over several noninvasive devices. I did not note if the article cites the UofF study linked above, whose results are in line with the studies of other, older noninvasive monitors cited. The article does note that trial users of earlier systems did not want to stop using them despite the rate of false positives and cites “quality of life,” presumably deriving from the better-safe-than-sorry thesis combined with the diabetic user’s response to the alarm, which would require awakening and testing prior to adjusting insulin dosages.

This is interesting from another perspective in that it is well established that a key to long term healthy adjustment to living with diabetes is frequency of testing. Presumably the false overnight alarms drive up frequency of testing and therefore increase the diabetic’s data set, resulting in better glucose control. This is a powerful argument in favor of the device.

Health Central, Will the Diabetes Sentry Prevent Hypos?, David Mendosa, November 2013. 

A consumer-oriented review in which the writer obtains an early review unit and enlists the help of an insulin-dependent diabetic friend to assess the device’s performance. Interestingly, the writer notes that the Diabetes Sentry does not use the infrared perspiration analysis that other similar devices such as the GlucoWatch did in the past, but rather uses changes in skin temperature and skin humidity to invoke its alert. Mendosa’s user reported both false positives and failed detection, in one case citing a low that reached 40 without triggering an alarm. The user also appeared to be primarily testing the device in daytime and active conditions, which is not necessarily our visualized use case. The article also notes that the Diabetes Sentry is the second to-market iteration of the device, the prior incarnation having been marketed as the Sleep Sentry apparently under the mistaken impression by the manufacturer that the device had recieved FDA approval, which it had not.

All together, I would say that while $500 seems expensive for a device whose primary benefit appears to be increasing randomized overnight blood-sugar testing and insulin dosage adjustment – a result which could be obtained by setting randomized alarms on one’s cell phone or digital information device such as an Apple Watch or other fitness band – if Viv remains inclined to this purchase after understanding the projected limitations of the device, I am in favor of the pirchase simply because it has the potential to increase overnight testing frequency.

Tone

For many years I have run an antiquated virtual answering machine on one of my Macs using the long-unsupported and discontinued Parliant PhoneValet software and dongle combo. Sometime about midyear I noticed that the software was no longer picking up and doing the various things it was supposed to, such as presenting a phone tree to callers and forwarding messages via email and calling our cell phones and so forth.

After some troubleshooting I concluded that my housewide move to OS X 10.x Yosemite around June had finally done in the software. I have a very elderly pre-Intel Mini that I keep around as a print server for some older printers and figured at some point I would move the dongle and software to that machine, still a possibility.

However, at some point well after that, date uncertain, I noticed that there had been no messages left on the traditional handset-base answering machine either, which seemed strange, especially in an election year. Sometime around then, my parents mentioned in a conversation that they had tried to call our land line but been unable to leave a message.

I thought that was strange, so I called the number from my cell. It rang in the handset but not in the hardware attached to the line, even though our DSL was working fine. When I picked up the landline handset, there was no dial tone.

After looking into it, I concluded that the likely course of events was that our cat had knocked a handset off a cradle at some point and we had not noticed it until after the emergency tone had been cut off and the POTS voice line disabled, probably in telco software, and would likely need to be reinitialized. I did not expect that there was a hardware or wiring issue because our DSL service remained fine.

We traveled a great deal in the second half of the year, on the road an average of a week a month through November, and that, plus the definite bonus of not even receiving any of the electioneering robo calls that plague election years, meant that I was in no hurry to get the line back up at all. 

Yesterday I finally filed a ticket and CenturyLink sent a truck. The technician was friendly and informative and although surprised to hear that the DSL remained functional and concurring that the infrastructure was likely fine, determined that his best reccomendation was to replace the line-drop to the node. 

So now we have landline POTS again for the first time in at least six months. Minutes after the hookup, we received our first call, from a scammy travel-offer telemarketer! We had qualified for a week of free travel, food, and lodging in Florida!

Hunh.

We really did not miss the line at all. I suppose I should look into seeing if we can keep just the DSL portion of the service and cut our rates by about $25. I’d like to keep the number, though. I wonder, can I port it to a virtual service or VOIP that would enable screening and phone tree forwarding for, oh, $5 or so? I sure wouldn’t be interested in paying any more than half the current cost and honestly any more than five bucks doesn’t generate enough savings annually to motivate me at all.

The Hard Drive Shuffle

On December 23, the boot drive in my MBP failed and I had to interweave backups and recovery and troubleshooting through the additional activities of the holidays. As I usually do when experiencing hardware issues, I journaled it. However, for reasons unknown even to me, I kept the journal on Facebook rather than here. 

Today, with the removal of the failing drive and its’ replacement with a 1TB SSD, I am done with the portion of tasks associated with resolving this issue that have to do with physically troubleshooting and replacing hard drives. There is a longer-term set of tasks upcoming involving the machine-by-machine deployment of outboard backup volumes, signaling the definitive end of my five years of desultory seeking to create a LAN-based backup system, but that’s a series of blog posts for another day.

Here’s all the stuff I posted on Facebook regarding this issue from December 23, 2016 until today, January 3, 2017. I have removed posts that were from friends and observers here; they can still be seen on the original FB thread.

 


 

December 23, 2016 at 12:38am ·

Arrgh, the boot volume on my MPB failed! The data I need, all my working files, are safely mirrored and I can just go work on one of my other machines, but geez, I won’t have time to fix the damn thing until next week!
December 23, 2016 at 9:17am
I was awakened this morning by my parents urgently calling to ask if I could locate some financial information, one of their HDs having failed, I think, although it was somewhat hard to follow their explanation of the issue.

December 23, 2016 at 12:00pm
I was able to mount the MPB as an external drive and am now ‘imaging’* the data over to another outboard. Roughly 600gb to sling, running at 16gb/hr give or take. The process ought to complete in 37 hours or so. Aargh.I cloned a 1TB SSD to a 2TB last night, coincidentally. A mere 12 hour process with today’s blazing transfer speeds. At least we don’t have to sit with the damn machine rotating floppies or swapping DVDs out any more.Oh, wait, hold on: SuperDuper just choked! Damn data integrity shinola!

*not actual, you know, bitwise imaging

December 23, 2016 at 12:57pm

hm, might be well fucked. I’ll look at CCC after I run an errand or two. I moved to SD! after CCC for some reason I now forget.

After SD! choked I went back to recovery mode and told DU to image the bad volume to the external and that failed too with an i/o error. SD! gave me a diagnostic on an individual file and halted instead of skipping and moving forward with a log, which would have been my preferred option.

I think my next best options here are directory-tree restricted copies and after that manual copies. I don’t actually think there’s anything unique or mission critical on the machine that’s not already mirrored, I just didn’t want to have to do a hand rummage and compare if I didn’t have to.

I set up the drive after the last machine failed this summer days before a revenue gig and I had to source this axe right quicklike. That machine was still on Mavericks and I migrated everything to Yosemite after I wrapped that gig. The old Mavericks boot drive is still viable and in the old machine, and I know it can reboot this machine, so I do have a known-good outboard boot solution.

All this fucking travel this year has prevented me committing the week or so of sustained effort to get that last-mile stuff set up. Bummer. At least the local mirroring stuff seems bulletproof, it’s twice this year that’s saved my bacon.

December 23, 2016 at 4:01pm
Well, disconcertingly, the Pro just self-booted in the middle of various tasks including running a CCC copy. CCC was able to pick up and move forward, though. CCC also reports physical read errors and, thankfully, does NOT abort the copy.

December 24, 2016 at 1:03am · Edited
Well, good news, and although I can’t match CCC’s bad file report with the size of the uncopied data, there’s nothing here that should prevent the cloned drive from booting. Trying tomorrow. Still probably best to wipe and bump to Sierra and then migrate. Man, I HATE running the current version of an OS release, it just offends my sensibilities. Maybe I can rig a work around to run that Yosemite clean install again. There’s nothing that makes me happier than defeating installer restrictions.


December 24, 2016 at 11:19am
Cloned drive boots. Now to ponder whether ’tis nobler in the eyes of man to clone and clone again, to a drive week-wiped free of foul corruptions’ stink, or to take up arms, and by opposing the screwdriver’s lance to the helices of steel that bind the shield, expose the innermost parts of that foe and servant, thereby to effect a transplant?

December 24, 2016 at 11:27am · Edited
I had actually planned on a drive swap to an SSD on this machine after Xmas. I still need the machine to work on a couple things before then. Opening and swapping drives two times in rapid succession increases the chances of zapping the mobo. Recloning it it is, because what s a day between friends?

December 24, 2016 at 11:55am
hm, I just had a thought – I think my old-style cloning of bootable volumes as a backup and migration strategy is probably not viable longterm any more because it won’t migrate the recovery partition. so even when I get this back in working shape I will need to do an install/migrate route for the SSD later on.

December 24, 2016 at 3:58pm
CCC has a Recovery HD creation function, cool. But it requires an extant recovery volume, and I have just noticed that my current primary boot vols were all stood up as clones, and thus lack the partition.
I will direct a squinty-eyed gaze at the one volume that did have said partition, the MPB drive that failed, kicking off this tech struggle journal.
Normally I keep a technical journal of these incidents on ye olde blogge, and these will migrate there in time.
I think the thesis is that I may record my mistakes, and learn from them.

December 28, 2016 at 12:42pm
Status update: internal drive reformatted and restored from successful CCC backup clone. No recovery partition in place yet. That requires a clean install of Yosemite to some machine or other, something that will require another hour or so of supervision and drive swapping, then CCC can clone those volumes as needed.Next steps: transfer this set of tech logs to the blog, finish deferred production tasks on the MPB, begin the SSD migration on the Pro, finalize SSD install to this machine. I’ll give myself a calendar week for each of these.

December 30, 2016 at 12:34pm
In working toward getting a clean install of Yosemite on an outboard drive so that CCC can harvest and distribute the recovery partition I ran afoul of a driver conflict on the Mac Pro – that machine has had an NVIDIA GTX 970 as its primary video card for a couple of years now, and running late-model NVIDIA cards in post OS X 10.7 systems requires custom drivers, without which the machine goes into a boot-looped kernel panic. Naturally, the temporary installer volumes created when you run an OS X installer lack this driver, and boom, a day of wondering where the heck the right web forum was again.Anyway, clean volume created. Next challenge is migrating the 1TB SSD to the 2TB SSD and re-merging the 2TB vol with the old Mavericks 2TB vol document directory that went from primary to offline when I moved to the SSD.

I guess I could hand merge, since the local Yosemite docs dir is intentionally thin and all the applications and licenses are on the SSD. What really want is a tiered local torrent cloud sync, where the current solution I use mixes with a longer-term storage solution for older files and docs. just figuring out the ruleset is time consuming enough that I doubt I’d ever try to set something like that up though.

December 30, 2016 at 4:21pm
Alrighty, both SSDs boot and have recovery partitions on ’em. Now to research folder-based one-off sync tools. Seems like CCC or Super Duper should just have that as a core feetch.

January 3, 2017 at 4pm
Closing in on winding this up. The initial drive failure appears to have recurred on the same drive, so it’s likely an unrecoverable hardware fault, although I haven’t traced that down to the bare iron yet. I was anticipating this as a possibility and had prepped to swap in the 1TB SSD in that event, which has now been done.

The last little cleanup bits are re-merging the various disaporan Documents folders, something that, as hoped, CCC can handle, but which will require a written plan and a couple of afternoons. Once that’s been done, I need to distribute local backup drives to all the machines and get that set up and I should be hard-drive circus complete for another year or more. I fucking hope.