## My Pixel C Tablet Ran Out Of Power Last Night.

I own a Google Pixel C tablet, that runs Android 8.1.0 . As is customary for me, I leave it In Standby each night, which means that it’s still drawing some small amount of current from its battery.

Usually, I’d inspect the tablet before going to bed each night, to verify that it will still have enough juice in its battery, to sleep through the night. But somehow, last night, I just failed to verify this, and assumed that the tablet was okay to sleep through the night.

Also, I slept-in this morning. Well as I was sleeping in, the tablet made a few notification sounds which I’d never heard from it before, and the fact that it was doing so did not alarm me in my sleep.

So this morning, when I tried to reboot the tablet, it would proceed partially into the boot process, and then just play its notification sound, and shut off again. So what I needed to do was leave it plugged in for two hours, and then try rebooting it again. Which worked!

But there was just a possible scenario in my mind, of what could have gone wrong last night, and what could potentially have bricked the tablet.

## System Update Today, Downtime

I take the unusual measure, of hosting my Web-site, and therefore also this blog, on a PC running at home. The PC I use is the Debian / Jessie (Linux) computer I name ‘Phoenix’.

This morning, I installed a major set of updates on this computer, which included 137 packages, and doing so, brought it from Debian version 8.9 to version 8.10 .

But, because this PC is also my Web-server, the required reboot also meant, that the site was offline from about 10h20 until about 10h30.

I apologize for any inconvenience.

BTW, ‘Phoenix’ had been Up, for 62 straight days.

It’s too early really to tell, whether this large an update has affected reliability adversely, but they usually do not. So for now, I’m counting this as a successful update.

Dirk

## System Maintenance Today

As a follow-up to this test yesterday, I just performed a reboot of the home-computer that acts as my Web-server, and that I name ‘Phoenix’ on my LAN. Unlike how it was yesterday, the reboot took place effortlessly tonight, requiring less than 5 minutes to complete, and undertaken around 21h20.

Again, my purpose was just to determine, whether a reboot would work, and again, there was a plausible reason why it might not have. Luckily, this one worked on the first try.

## System Maintenance Today, Downtime

I take the somewhat unusual approach, Of hosting this Web-site, and therefore also my blog, on my personal computer at home. Therefore, any downtime of my home computer, also affects the visibility of the blog. And, as long as the actual Web-server is not online, I also cannot make it display a maintenance-mode page.

Just in recent days, I took the more-unusual step, of running the command:


root@Phoenix:/home/dirk# update-initramfs -u -k 3.18.0-14-generic




root@Phoenix:/home/dirk# update-initramfs -u -k 3.16.0-4-amd64



While it seemed nice for some time, to be running a kernel-version named ‘3.18.0-14-generic’, the mainstream version which a Debian / Jessie system is supposed to be running, is ‘3.16.0-4-amd64′. So, while the mainstream kernel had been receiving regular updates, I was running a kernel, which had not been receiving any updates, for years now. This helped reduce the number of reboots which I needed to carry out, due to frequent updates on the ‘3.16.0’ kernel.

But just because this was the first time in ages, that I had run the ‘update-initramfs’ command on the running kernel, I next needed to attempt a reboot, just to see whether the computer could still boot.

Therefore, readers would have experienced problems accessing my blog or site, from about 16h40 until about 17h10 today.

And No, My system Failed to Reboot.