Nathan Kennedy wrote: > is down as of tonight. I talked to Xiolink. Lilo fails to boot with a > CRC error. I think now is the time to have it taken offline and shipped > to Peer1. Recovery should be a matter of swapping a drive and > rebuilding like with fyodor, since it has RAID (right?). >
What a big old smelly coincidence that we have to deal with two of these failures so close together.... I agree that it doesn't make sense to attempt any repairs that end with Abulafia back at Xiolink. Abulafia is still fulfilling an important role: during the periods when fyodor was down, it was important to retain Abulafia's secondary DNS services. Thus, I think it would be best to get Abulafia up at Peer 1 with its exact current configuration and change the ns2.hcoop.net IP address at our registrar. I continue to recommend not thinking about re-configuring Abulafia for its intended role at Peer 1 until after we have deleuze and mire working properly with everyone migrated. ntk, are you volunteering to do all of the work of getting Abulafia running again once it reaches Peer 1? Any objections from anyone to this general course of action? _______________________________________________ HCoop-SysAdmin mailing list [email protected] http://hcoop.net/cgi-bin/mailman/listinfo/hcoop-sysadmin
