/dev/chat

« first day (1726 days earlier) ← previous day next day → last day (3230 days later) »

1:03 PM

Preconfiguring packages ...
dpkg: unrecoverable fatal error, aborting:
 reading files list for package 'adduser': Input/output error
E: Sub-process /usr/bin/dpkg returned an error code (2)

oh fun!

Faheem Mitha

Hey @derobert. Upgrading stuff?

derobert

@FaheemMitha security updates.

Apparently that SSD has developed a bad sector.

Faheem Mitha

@derobert Breaking things?

@derobert Oh. I'm relieved.

derobert

I wonder what else it's taken out, as presumably a corrupt flash block is bigger than 6k

Faheem Mitha

I thought for a minute Debian had gone insane. Though they did have a bad security update the other day, if I recall correctly.

derobert

1:10 PM

I remember the one a bit back that broke multiarch, which other bad one was there?

(copying that file from another wheezy box got it working again...)

Faheem Mitha

@derobert Hmm, I forget. It was relatively recently. And I think you announced it here. Before I had got to it. But it was fixed quickly. What package was that?

derobert

@FaheemMitha Forget which package, but that's the one.

Faheem Mitha

@derobert Wow, you figured that out from my vague description?

derobert

@FaheemMitha Mainly the part that I announced it here.

Faheem Mitha

@derobert Ah, Ok. What package was it, then?

derobert

1:21 PM

I forget...

Faheem Mitha

derobert

unix.stackexchange.com/questions/213309/… ... haven't gotten a Windows question for a bit!

Until now. At least that I've stumbled across.

terdon

@derobert poof, gone

derobert

@FaheemMitha Oh wait, there was another recent broken update. For squeeze only, though. And probably a few other distros.

A: Kernel panic? After ram increase

That's a kernel bug, Debian bug #789037 aka upstream bug #99161. It was introduced in a recent kernel update, and you probably saw it after the reboot (to install RAM) because you're now running that kernel. The fix is already available; you need to install it (and reboot).