From owner-freebsd-questions@FreeBSD.ORG Sun Aug 14 23:20:44 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 9374816A41F for ; Sun, 14 Aug 2005 23:20:44 +0000 (GMT) (envelope-from chad@shire.net) Received: from hobbiton.shire.net (hobbiton.shire.net [166.70.252.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 408A943D48 for ; Sun, 14 Aug 2005 23:20:44 +0000 (GMT) (envelope-from chad@shire.net) Received: from [67.161.222.227] (helo=[192.168.99.68]) by hobbiton.shire.net with esmtpa (Exim 4.51) id 1E4RmL-000Ppu-Lt; Sun, 14 Aug 2005 17:20:34 -0600 In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v733) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <950333AF-D55D-4FF8-BA5B-3E242661557D@shire.net> Content-Transfer-Encoding: 7bit From: "Chad Leigh -- Shire.Net LLC" Date: Sun, 14 Aug 2005 17:20:33 -0600 To: Bo Xiao X-Mailer: Apple Mail (2.733) X-SA-Exim-Connect-IP: 67.161.222.227 X-SA-Exim-Mail-From: chad@shire.net X-SA-Exim-Scanned: No (on hobbiton.shire.net); SAEximRunCond expanded to false Cc: freeBSD Questions Subject: Re: Can FreeBSD handle 300G SATA disk? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Aug 2005 23:20:44 -0000 On Aug 14, 2005, at 4:30 PM, Bo Xiao wrote: > > Installation on another box, also with 5.4R, went well. So it > must be > this particular Dell PowerEdge 750. After moving the disk back, > > % sudo newfs /dev/ad3s1d > newfs: /dev/ad3s1d: failed to open disk for writing > % sudo mount /dev/ad3s1d /mnt/a > mount: /dev/ad3s1d: Operation not permitted > % Does the box you are trying this on have a SECURELEVEL set? kern_securelevel_enable="YES" kern_securelevel="3" (or 2 or other number) After one of the secure levels, you cannot open disks for writing. You will have to reset it to NO and reboot and do what you need. Read in the handbook for exact details, which I cannot remember now (like at which secure level this takes effect) Chad --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider chad@shire.net