From owner-freebsd-questions@freebsd.org Mon Aug 20 17:58:32 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 29D6F107790E for ; Mon, 20 Aug 2018 17:58:32 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.75]) (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 8615079E0C for ; Mon, 20 Aug 2018 17:58:31 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.99.237]) by mrelayeu.kundenserver.de (mreue104 [212.227.15.183]) with ESMTPA (Nemesis) id 0Mdurl-1fUXMA02kn-00PeoA; Mon, 20 Aug 2018 19:58:23 +0200 Date: Mon, 20 Aug 2018 19:58:21 +0200 From: Polytropon To: Balaji Balaji Cc: freebsd-questions@freebsd.org Subject: Re: Fwd: $ true is not set properly error Message-Id: <20180820195821.da9e1d04.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-Provags-ID: V03:K1:s7vY4M2g5Sy/qGsqavRFMHGo/YRMdwhkcDaVxl8LDwsKDnIFQ/n vXVkQyeZ12jqLEDmtqYiRRCXSHDUywa6qgvv5yxhvm0FOm8pYe9AwoDjxIJ5qsu+afbM3Iw ZXaqXtUv064Rzc4/c3MPf3cswh5L6G/l1ZNtcY44MwLsqFaOM2FJCZQuyI1xiVeuoW8JVzH 0ih8MdG7cYNPOnxyFDaWg== X-UI-Out-Filterresults: notjunk:1;V01:K0:PHt5mZp+uzc=:uqtpkVklKOfBwforqAN8Y6 GyRWNwBPHjb6RZcSV0e4umzyOqPLwOjTlxefLZG/howH8GSq98FbkKcMfFPLmWLEc0aQUYk4t fSnkQaepdla2D9g32XssQh2mDKSQ9HsE9tIaFA5DNmgequ8Z0thDqeHlnVf/HYmHvdZvVAH9Q TSGs82/pYfMoWyXR+U762PKszDKeuwHiwjffdOYj73SRviTyxfhVB2lIzAbWg379DTWwrCUTi mTH6E61Met25JVSY94QeIBWYwIRNqd47QLMHN81bkj92gKQR8jdBZpTh1Qdg4SENtKsyCf+g8 hnsJZPBi3m5zmkd+pMXTGrnT1yENrNfhd7Hm1d0ALa3IY/ufo2yRV6QTQZEB12uy39nH9yOgu 0t2IFGKlnQKKQ8t3BUc8mEgYh8Ake1FFHNPqERzfRzdk0DRMfqP79aYNCqDLZcsbJ+72O5r3b WrAABrEAOAaoTo2V8YgNrQwSP9B7YaQI5oqDE4M9tqQPDGV9jAGNPj7o9meBbJilxo3IMz9Oj ndXShYnlI78VwY1l1mDB3Hgcpsx74Qao8RwFU9lXDfYIAqxfDHpMHyN9zi1mAqneNE258S07c 48oLMRqA1KBC3+5ptG9t0KImQUTvZPbmOnlYlsBXxS5+zEFSeIxeA5ONDyQgNWrnq1E19o5Xy sCltnT6Qo/xAgIjZXY9uV3PsZXy1PipTpceS1RnyR8U36HYOSJCk0dq4LiUc1aX20gZeJfddZ fQswJcHZS3TQnCB3 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: Mon, 20 Aug 2018 17:58:32 -0000 On Mon, 20 Aug 2018 13:41:44 +0530, Balaji Balaji wrote: > We have Server PC with FreeBSD 6.3 used in Toshiba MRI > for store rawdata. FreeBSD 6.3 is out of support for several years already. If you can, consider upgrading that system to a version that receives support. However, FreeBSD is known to run for decades (if maintained properly, or _not_ touched at all). :-) > Now we have following problem in server PC it is not booting fully showing > error > Mounting /etc/fstab filesystems failed, startup aborted > /etc/rc:Warning:$true is not set properly -see rc.conf(5) What does "now" mean in this context? Did it happen suddenly out of nowhere, or did you change something on the server? If yes, what did you change? The error seems to indicate some problem with /etc/rc.conf content. Maybe this older discussion is helpful: https://lists.freebsd.org/pipermail/freebsd-questions/2016-March/270788.html Check in /etc/rc.conf if you somewhere have a line like "true=" in it... But that is a warning. Probably there's an error with bigger impact related to mounting, maybe an error in /etc/fstab? You could try to boot the system into single user mode first ("boot -s" at loader prompt), then run "fsck", and finally "mount -a". This should give you a good indication of what could be the problem. > attached picture 1 with booting error This mailing list does not support non-text attachments. Please upload the picture somewhere - or even better, especially for future reference, type the error message (and all other important information that might appear on the server) directly into the message. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...