*scottstuff*

I’ve finally had it with my downstairs TiVo. As I mentioned before, it’s been crashing with increasing regularity. I’ve been avoiding dealing with it for a few reasons; mostly, I’ve been too busy with other things, but I also hate debugging problems with black boxes, and my TiVo is definitely a black box, even if it does run Linux.

Unfortunately, my inaction hasn’t made the problem go away. If anything, it’s happening even more often now then it was a month or two ago. But, in the meantime, I’ve been able to watch a couple crashes and gleaned a bit of information:

1. It doesn’t just stop–when playing back recordings, it skips a couple times first, with long pauses, then a few frames, then another long pause. This repeats for a couple cycles, and then it finally crashes.
2. When it’s working right, the TiVo’s front-panel LEDs blink brightly when I press buttons on the remote. When it’s dead, the front panel LEDS still blink, but only slightly. It looks like there are two LEDs that blink, one driven by hardware and the other by software. When it’s dead, the software one doesn’t respond. But, when the box has just crashed, the software LED still works. It takes a while for it to die.

If I saw the same symptoms on a server, I’d be thinking “bad hard drive”–we’re seeing processes lock up in the ‘D’ state here, followed by a congestive collapse of the whole system, as every system process that touches the disk (or talks to a process that talks to the disk, like syslog) slowly crawls to a halt. Bad motherboards or power supplies don’t usually leave parts of the OS working right for a few minutes.

So, I pulled the drive out of the box and I’m currently cloning it onto a new, larger drive. There are decent tools and directions online for this, so it’s not a big pain rounding up all of the pieces. Plus, when it’s done, I should have twice as much disk space.

As a plus, the original drive started spitting out unrecoverable drive errors around 2% of the way into the copy. Hopefully that was in the data area of the drive, not in the middle of important program code. Hmm–I wonder if it’s in the swap area? That’d really kill the box, but it’d leave it working fine after a reboot, until it got busy enough to swap. Yeah, that’s probably what happened.

Update (Apr 20, 2004): It seems to have worked. The TiVo has made it two days without crashing; that hasn’t happened in weeks. It seems slightly faster, and it now holds 146 hours, up from 60 hours.

Around 6 months ago, I registered the ‘.ing.ly’ domain, largely for the possibilities it presents for entertaining subdomains: surpris.ing.ly, stunn.ing.ly, and so forth. Unfortunately, I never really got around to using any of them. I received this today:

Dear .ly domain user,

Re. CcTLD nic.ly

It is with regret that we have to inform you, that due to unilateral action by the Internet Assigned Numbers Authority (http://www.iana.org), the Domain Name Servers that host the zone files for the ccTLD .ly have been disabled.

The ccTLD .ly has made repeated official requests to the above authority to relocate the Name Servers to an independent environment, to ensure the continued operation of the .ly zone. Unfortunately, these requests, so far, have been declined by IANA.

Consequently, your .ly domain name(s), along with all other .ly domain names, will cease to function until corrective action is taken by IANA to rectify the matter.

IANA is the international authority responsible for the management of ccTLD functionality. Thereby, only IANA has the power and authority to rectify this problem and reactivate the .ly name zone, consequently, allowing your domain name(s) to function.

Despite our best efforts to maintain the continued operation of the .ly zone, its failure today is totally outside our control. The effect of this is explained in the disclaimer within our advertised Business Terms which each registrant has signed up to during the time of registering a .ly domain name. See our business terms at http://www.lydomains.com/businessTerms.htm.

To get more information or to make a comment, please write to IANA at root-mgmt@icann.org.

Meanwhile, please accept our apologies for any inconvenience that may be caused. We will endeavour to keep you informed of any future developments.

Yours

.ly administrator lydomains.com

Has anyone seen the real story? Now that Libya isn’t an international pariah anymore, are they trying to take their TLD back?

Update (Apr 19, 2004): Looks like it’s back. ICANN basically claims that they had nothing to do with it, and that the .ly people’s DNS servers had disappeared from the Internet. Reading between the lines, there’s still something going on, but it’s largely a case of incompetence. The weird thing is that UUNet was acting as one of the DNS providers for .ly, and I’m not really sure why they stopped providing services.