Differences between revisions 1 and 2
Revision 1 as of 2021-06-16 12:56:06
Size: 1153
Comment: added a node page for NodeC3PO
Revision 2 as of 2021-07-01 15:52:55
Size: 1943
Comment: added repair notes from today
Deletions are marked like this. Additions are marked like this.
Line 26: Line 26:
 * 2021-07-01: Outage intensified as the heatwave came on and it was not functioning over the weekend. Got down there the evening of 6/30, but missed Andrew, so came back today (he has the key to the enclosure), found the ER-X not working correctly, took it home, discovered a bad-block error in the NAND flash in the /rom section, rendering part of the squashfs unreadable, explaining the failure to connect its network despite powering the NanoBeam, recovered by TFTP booting a initramfs image, then reflashing (this seems to map out the bad block via the ubi block layer), and it seemed to function properly after that. I cleaned up the case, relabelled the ports for more clarity and also printed labels for the ethernet cables to ensure they are plugged in correctly. --RussellSenior

Node name: NodeC3PO
Live Date: May 3, 2020
Sponsor: PersonalTelco and a friendly neighboring business
Contact:

SE Water Avenue
Portland, OR

Configuration

  • Host: jet

    • Hardware: Ubiquiti ER-X and two Meraki MR24s
    • Software: OpenWRT

    • Internet IPv4: DHCP
    • PTPnet IPv4: 10.11.70.1/23

Installers / Organizers

Maintenance and System Log

  • 2020-05-03: Gear installed
  • 2021-02-20: Maintenance involving replacement of power supplies (due to sabotage) and provision of an enclosure to enhance security of the devices
  • 2021-06-12: Reports of problems with ethernet run across the street (possible damage) and possible water intrusion into AP2 (at the south village), requesting more information.
  • 2021-07-01: Outage intensified as the heatwave came on and it was not functioning over the weekend. Got down there the evening of 6/30, but missed Andrew, so came back today (he has the key to the enclosure), found the ER-X not working correctly, took it home, discovered a bad-block error in the NAND flash in the /rom section, rendering part of the squashfs unreadable, explaining the failure to connect its network despite powering the NanoBeam, recovered by TFTP booting a initramfs image, then reflashing (this seems to map out the bad block via the ubi block layer), and it seemed to function properly after that. I cleaned up the case, relabelled the ports for more clarity and also printed labels for the ethernet cables to ensure they are plugged in correctly. --RussellSenior

Notes


[CategoryNode][CategoryPersonalTelco]

NodeC3PO (last edited 2021-07-29 11:15:13 by RussellSenior)