[Rack] [Noisebridge-discuss] Access

Jonathan Lassoff jof at thejof.com
Thu Jul 4 23:26:27 UTC 2013


On Thu, Jul 4, 2013 at 3:30 PM, Jake <jake at spaz.org> wrote:
> On Thu, 4 Jul 2013, Jonathan Lassoff wrote:
>
>> I'm not suggesting that this *needs* to come off of minotaur now, I'm
>> just hypothesizing how we could make it even more awesome and
>> reliable.
>
>
> i think it has been pretty reliable for the past two years.  this is the
> only time it has fucked up and it seems clear to me that it's a hardware
> problem, which surely can be solved.  perhaps the hard drive is failing?
>
>
>> That's exactly my point: we've added a lot of moving parts to
>> minotaur, when really all we're doing with the keypads is super
>> simple. Looking for certain combinations of keypresses and sending
>> several bits of state back to the keypad.
>> Running this on something more solid state and less-consumptive should
>> make it easier to add battery backups, and isolate the few components
>> that are needed to make the door work.
>
>
> my view is that since minotaur is already running, it's no big deal to have
> it do this stuff too.. as opposed to adding a new piece of gear. Also, do
> you think the raspberry pi is reliable?  hint:  sudoroom has been using one
> for their door, using baron.py and some other stuff, and they have been
> having like 50% downtime.
>
>
>> Probably a good idea. It's still just attached to the Parallel port,
>> right? Something is latching down those pins, or the UART goes offline,
>> uncontrolled or something.
>
>
> it has only happened once, ever, that i know of, and i wasn't even there.
> minotaur doesn't have a parallel port, it has a USB to parallel adaptor (for
> using old printers) and that peripheral is how it opens the gate.
>
>
>> I still have no idea what's causing the lockups. We'd need to see what's
>> getting logged on the kernel's console. Any idea what's wrong with it?
>
>
> i was too busy to look in the logs but i can tell you it was tuesday
> afternoon and evening when it locked up.  look for the reboots.

I see a reboot in the log, along with some ATA/disk errors:

Jul  2 08:00:54 minotaur kernel: [3596812.797389] ata3.00: exception
Emask 0x50 SAct 0x0 SErr 0x480900 action 0x6
Jul  2 08:00:54 minotaur kernel: [3596812.797535] ata3.00: BMDMA stat 0x26
Jul  2 08:00:54 minotaur kernel: [3596812.797606] ata3.00: SError: {
UnrecovData HostInt 10B8B Handshk }
Jul  2 08:00:54 minotaur kernel: [3596812.797717] ata3.00: failed
command: WRITE DMA
Jul  2 08:00:54 minotaur kernel: [3596812.797806] ata3.00: cmd
ca/00:10:c0:d6:5d/00:00:00:00:00/e0 tag 0 dma 8192 out
Jul  2 08:00:54 minotaur kernel: [3596812.797809]          res
51/84:01:cf:d6:5d/00:00:00:00:00/e0 Emask 0x70 (host bus error)
Jul  2 08:00:54 minotaur kernel: [3596812.798067] ata3.00: status: { DRDY ERR }
Jul  2 08:00:54 minotaur kernel: [3596812.798140] ata3.00: error: { ICRC ABRT }
Jul  2 08:00:54 minotaur kernel: [3596812.798223] ata3.00: hard resetting link
Jul  2 08:00:54 minotaur kernel: [3596813.116084] ata3.01: hard resetting link
Jul  2 08:00:55 minotaur kernel: [3596813.592183] ata3.00: SATA link
up 1.5 Gbps (SStatus 113 SControl 300)
Jul  2 08:00:55 minotaur kernel: [3596813.592203] ata3.01: SATA link
down (SStatus 0 SControl 300)
Jul  2 08:00:55 minotaur kernel: [3596813.610894] ata3.00: failed to
IDENTIFY (I/O error, err_mask=0x2)
Jul  2 08:00:55 minotaur kernel: [3596813.610911] ata3.00:
revalidation failed (errno=-5)
Jul  2 08:01:00 minotaur kernel: [3596818.592094] ata3.00: hard resetting link
Jul  2 08:01:00 minotaur kernel: [3596818.912133] ata3.01: hard resetting link
Jul  2 08:01:00 minotaur kernel: [3596819.388172] ata3.00: SATA link
up 1.5 Gbps (SStatus 113 SControl 300)
Jul  2 08:01:00 minotaur kernel: [3596819.388190] ata3.01: SATA link
down (SStatus 0 SControl 300)
Jul  2 08:01:00 minotaur kernel: [3596819.404475] ata3.00: configured
for UDMA/133
Jul  Jul  2 17:50:52 minotaur kernel: imklog 5.8.6, log source =
/proc/kmsg started.

Then, no disk errors and another reboot around Jul  2 23:16:05


Originally, this box didn't have a SATA drive, it was just a solid
state 2GB CF card with noatime and a mostly read-only FS.
I'd love to get this back into a state like that, where there are no
moving parts.

For now, we ought to suck down the important parts of the disk, and
swap out a new disk in there. :(

I think it's just a laptop-sized SATA drive in a little enclosure,
that goes to a SATA cord to the motherboard.
Anyone have an SSD to spare?

--j


More information about the Rack mailing list