From owner-freebsd-questions@FreeBSD.ORG Sun Apr 18 05:10:28 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0BF8F16A4CE for ; Sun, 18 Apr 2004 05:10:28 -0700 (PDT) Received: from smtp.thilelli.net (jgabel.net1.nerim.net [80.65.226.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8AC0143D58 for ; Sun, 18 Apr 2004 05:10:27 -0700 (PDT) (envelope-from jpeg@thilelli.net) Received: from localhost (localhost.thilelli.net [127.0.0.1]) by bento.thilelli.net (Postfix) with ESMTP id 017B478C50; Sun, 18 Apr 2004 14:10:26 +0200 (CEST) Received: from bento.thilelli.net ([127.0.0.1]) by localhost (bento.thilelli.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 57127-02; Sun, 18 Apr 2004 14:10:25 +0200 (CEST) Received: from webmail.thilelli.net (localhost.thilelli.net [127.0.0.1]) by bento.thilelli.net (Postfix) with SMTP id 10A5F78C4B; Sun, 18 Apr 2004 14:10:25 +0200 (CEST) Received: from 192.168.0.105 (SquirrelMail authenticated user jgabel) by webmail.thilelli.net with HTTP; Sun, 18 Apr 2004 14:10:25 +0200 (CEST) Message-ID: <49988.192.168.0.105.1082290225.squirrel@webmail.thilelli.net> In-Reply-To: <49983.192.168.0.105.1082290113.squirrel@webmail.thilelli.net> References: <49983.192.168.0.105.1082290113.squirrel@webmail.thilelli.net> Date: Sun, 18 Apr 2004 14:10:25 +0200 (CEST) From: "Julien Gabel" To: chad@shire.net User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal X-Virus-Scanned: by amavisd-new at thilelli.net cc: freebsd-questions@freebsd.org Subject: Re: [SOLVED] Can't *write* to a hard disk, not even a slice using fdisk(8). X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Apr 2004 12:10:28 -0000 >>> do you have your securelevel set in rc.conf to YES and to a higher >>> level (like 3)? >> Yes, this machine had a securevel positionned: it set to '2'. But >> because I can't touch the disk even in Single User Mode, I don't >> think it is related, but... >> >> What is your idea? > Ok. I had missed the earlier parts. I had a problem recently where a > new disk was not "touchable" at all and it was related to the > securelevel being at 3... > > Was just a thought. I don't know if you follow the current@ list too, but I sovled my problem: http://lists.freebsd.org/mailman/htdig/freebsd-current/2004-April/\ 025943.html I can note that if I said that "I can't touch the disk even in Single User Mode"... that was right, but just because I went to single-user mode from multi-user mode, so the kern.securelevel was always to '2' (which is very different to boot directly to single-user mode)! Sorry for the mistake and thanks for your reply which appeared to be the right point here. -- -jpeg.