From owner-freebsd-questions@freebsd.org Tue Aug 21 19:59:10 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3CC5A107DCC4 for ; Tue, 21 Aug 2018 19:59:10 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A896194289 for ; Tue, 21 Aug 2018 19:57:57 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.99.237]) by mrelayeu.kundenserver.de (mreue004 [212.227.15.167]) with ESMTPA (Nemesis) id 0MSFaB-1fQJrL3Yvj-00TTix; Tue, 21 Aug 2018 21:57:49 +0200 Date: Tue, 21 Aug 2018 21:57:48 +0200 From: Polytropon To: Balaji Balaji Cc: freebsd-questions@freebsd.org Subject: Re: Fwd: $ true is not set properly error Message-Id: <20180821215748.151f4341.freebsd@edvax.de> In-Reply-To: References: <20180820195821.da9e1d04.freebsd@edvax.de> 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-Provags-ID: V03:K1:SzEkhDvkyIfV2TW2SF1PvAryyhx0PMZFXMVNbQoe3XVUnkpcykp TElH2OhfrDgU3LP/kZmBddcjgzWoIK6Tv+yT+ezfga0XPBuqP/Klv9zGOOsuRXzzdMKu3bF ieKDiqxUL9vTHT0uHtCQyPQCC1jlQ0REg24pPFy05E0tXdBdLDwSsXJG+fPJTLbkuToTu/y FaQPqmuSvF/t0AriSQF3w== X-UI-Out-Filterresults: notjunk:1;V01:K0:ZHbA2AbvHUU=:7GlAuZ5Z8kx30Fo2dO0otW I4wc3BSzrOZyIBlpH9hqgfmGz3JZjcFNWdT62O8KqG3zqokO4rIQ8L2GaD2HHabMNSc8Rm5d9 rZbm8KY0kFOzXt0vOcyZsKdn7gT1HyrxExGrIOMLfOrlYfA1pWGvh2+TyOqy6ZX5OKt87fTox Wj3RWJhsLsYQ+G7SdWjMTg+a6AfYB2XuItcsJ4p3qwV1913rF7rM/8ZLW5oscMFm+GjtgLHR+ pflytmRTPqO99btEn1Mmx+wJTo+yj98SRgj9o6lcOyiyvDFN6VIjZuQxJMnWMYdY3qAGg8CzP Yt/oZo9FRqSpAHYhi7iWZ3Zpm4B58+m/+QJWgcNCogkjFLl45IWAefi+xsCP7ufXfWWhiqW3b 9NCGZx94eCX+fgm+8+gTSxpzi3s3brNFKaLtmUdqSjF5H63178xEz2mDQKyD/QS/iCoCvmah3 MPp0sulK4U7G5Dn1eAn+CsxI0snZS+6Yf4ZarQLiN6Pf5PqPYVmazMxUDZ21z75dV+vHKJQGA LyI23IlMwHMEuIJ5fDsnb8jtchvnfdIIKo/bFWjn+4cIhum7jgKHPq6YTCZMbBGmDVYJhXsb8 jcrLSZe0kZEuEQM/f9LdamXyTSK7Y3Bx3PKb5vT18DnuE6D18BNVxVUg9olCb1tMswp0ZnS2V lem8C/+yBDLMIQ7ozOVvnOFgl7HXzPV5VJ8HhEguPrr3cpZmgZQJnJ5vE1uTsslnTiF9ZH4Pk q0nngbdvyeEM4ecF X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2018 19:59:10 -0000 On Tue, 21 Aug 2018 11:20:41 +0530, Balaji Balaji wrote: > This Server PC is comes in Toshiba MRI excelart Vantage model and > boot from Host PC I'm sorry, I don't understand what "the server PC boots from host PC". Is this some network booting? Or from local storage? > There was problem in server PC hard disk degraded so we rebuild > after rebuild Server PC boot without error Very good. So there is a hard disk with a fresh installation (or from backup)? > we connected the Server PC in MRI System and from Host PC we tried > to connect but failed > > and found that Server PC is not booting Okay, now it becomes more clear: You're using a "host PC" to connect to the "server PC", and you're using SSH / telnet for this purpose? Or some kind of serial console? When you try to do boot the server PC, do you have any direct control over booting (i. e., console)? Is it possible that you post the exact relevant error messages to this list? > > We tried as per your instruction by entering single user mode we > tried to boot -s in loader prompt it didnot work This strange statement raises two questions: 1. How did you try to boot into single-user mpde? 2. When you tried it, what exactly did happen? For reference purposes: https://www.freebsd.org/doc/handbook/boot-introduction.html https://lists.freebsd.org/pipermail/freebsd-questions/2004-February/037206.html For single-user mode, you need to interrupt automatic booting, and at the loader prompt, "boot -s" is the command that will bring up the system in single-user mode, and finally stop at the shell selection prompt. Press ENTER at the /bin/sh prompt, "fsck" to make sure your filesystems are okay, then "mount -a" to mount them, and finally "mount -o rw /" to make / accessible for possible writes - which you need when you edit /etc/rc.conf (with "ee /etc/rc.conf"), checking for errors in that file. > we did fsck it works all files seems ok This makes sure the filesystems are consistent - good! However, my suspicion still is that there is a problem in /etc/rc.conf. Can you mount the partition where /etc is located on (usually /, the boot partition) on a different system and check the content of /etc/rc.conf? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...