From owner-freebsd-questions@freebsd.org Thu Mar 30 08:29:51 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B23F5D23286 for ; Thu, 30 Mar 2017 08:29:51 +0000 (UTC) (envelope-from bc979@lafn.org) Received: from zoom.lafn.org (71-83-145-83.static.rvsd.ca.charter.com [71.83.145.83]) by mx1.freebsd.org (Postfix) with ESMTP id 98522179 for ; Thu, 30 Mar 2017 08:29:51 +0000 (UTC) (envelope-from bc979@lafn.org) Received: from [10.0.1.251] (sermon-archive.info [71.177.216.148]) by zoom.lafn.org (Postfix) with ESMTPSA id B7B5234AA1A for ; Thu, 30 Mar 2017 01:08:32 -0700 (PDT) From: Doug Hardie Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Weird boot problem Message-Id: Date: Thu, 30 Mar 2017 01:08:32 -0700 To: "freebsd-questions@freebsd.org Questions" X-Mailer: Apple Mail (2.3273) X-Virus-Scanned: clamav-milter 0.98 at zoom.lafn.org X-Virus-Status: Clean X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Mar 2017 08:29:51 -0000 I had to move a bunch of servers to a new location yesterday. That was = an interesting exercise. However, two of the systems exhibited the same = behavior when first booted at the new facility. The message gptboot: = could not find on 0(ad2). I believe I recall this correctly. A search = on that message indicated that there should be another word between find = and on like kernel or loader. There was nothing there on either system. = The system appeared to reboot after that message as there were a couple = other messages and then that message reappeared. I believe all of the = systems are MBR formatted. I don't believe any are new enough to = support GPT. Given that there were other systems coming up at that time, I left them = till the end. Nothing seemed to change anything. In desperation we = power cycled one of them and it booted properly with no error messages. = Not being on site, I didn't see what was done to the other, but I = suspect it was a power cycle and then it came up. There was no = identifiable corruption on either system. I am a bit fearful of = rebooting them again. Any ideas what might have caused this and is it something telling me go = get new systems =E2=80=94 Doug