From owner-freebsd-questions@freebsd.org Tue Nov 21 09:27:06 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 1B46DDE8BF0 for ; Tue, 21 Nov 2017 09:27:06 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay13.qsc.de (mailrelay13.qsc.de [212.99.187.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 90A86665C2 for ; Tue, 21 Nov 2017 09:27:05 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay13.qsc.de; Tue, 21 Nov 2017 10:26:47 +0100 Received: from r56.edvax.de (port-92-195-48-11.dynamic.qsc.de [92.195.48.11]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 8EB783CC3F; Tue, 21 Nov 2017 10:26:46 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id vAL9QjCr001967; Tue, 21 Nov 2017 10:26:45 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Tue, 21 Nov 2017 10:26:45 +0100 From: Polytropon To: Konstantin Cc: freebsd-questions@freebsd.org Subject: Re: Boot problem Message-Id: <20171121102645.5a5d58fd.freebsd@edvax.de> In-Reply-To: References: Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay13.qsc.de with D7D9C68355F X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1583 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Nov 2017 09:27:06 -0000 On Mon, 20 Nov 2017 16:54:23 +0300, Konstantin wrote: > I have a problem booting freebsd-box. > It stop working about six months ago. Loading stops at the first stage, the > first 20 seconds I still can reboot the machine through ctrl-alt-del, after > that the keyboard does not work. What exactly is this "first stage"? The actual first stage of (classic BIOS) booting is the MBR / boot manager, second stage is the kernel loader, third stage is the kernel itself, fourth stage is init. :-) Also, please explain the system behaviour: Does it hang (i. e., become fully unresponsive both regarding keyboard input and network access, for example via SSH or telnet), does it crash (and if yes, with which message), or does it suddenly reboot? Does it do this every time or just occassionally? In case your keyboard is a USB keyboard which first runs in some legacy mode (via BIOS), and then using the kernel's ukbd driver: If the kernel didn't recognize your keyboard, its input won't reach anything. Can you check the boot messages for the "ukbd" entry? Six months ago, did you do something "unusual" to your system, like replacing a hardware component or changing the OS software? > I boot the system from the installation flash drive, from the bootloader > command line I do the following > unload > set currdev="disk1p2" > read-conf /boot/loader.conf > boot-conf Does the OS (on the disk) boot correctly, and will it stay responsive after booting this way? Have you tried booting from a 11.0 flash drive and using the kernel from that media (i. e., without the "unload" command)? This way you could rule out a kernel problem. Additionally, when booting from USB flash media, does booting the _whole OS_ from that media stay responsive after booting? Those are at least a few tests you can do. > How I can repair normal booting? This depends on what's actually wrong. The information you provided sadly doesn't help much... > FreeBSD 11.0-RELEASE-p12 That's a fairly current OS version. Is it running a custom kernel? On Mon, 20 Nov 2017 17:55:04 +0300, Konstantin wrote: > There are no UEFI on the PC - it`s a 8-years old socket 775 platform. And > no optical drive. This shouldn't be a problem, except of course you're experiencing some kind of hardware failure, which is at least possible at such an age, but the age alone doesn't imply it. (My home PC is 10 years old and still working.) > First I want to try repair without reinstall FreeBSD. That would probably be the best thing to do, but without further diagnostics, it's hard to tell what's wrong in your specific case. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...