From owner-freebsd-questions@FreeBSD.ORG Thu Apr 17 09:11:19 2003 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 8327F37B401 for ; Thu, 17 Apr 2003 09:11:19 -0700 (PDT) Received: from mail.uhs.utexas.edu (exchange.uhs.utexas.edu [146.6.22.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id C763243F85 for ; Thu, 17 Apr 2003 09:11:18 -0700 (PDT) (envelope-from N.Hinson@mail.uhs.utexas.edu) Received: from mail.uhs.utexas.edu ([146.6.22.202] RDNS failed) by mail.uhs.utexas.edu with Microsoft SMTPSVC(5.0.2195.5329); Thu, 17 Apr 2003 11:11:18 -0500 Date: Thu, 17 Apr 2003 11:11:18 -0500 Mime-Version: 1.0 (Apple Message framework v551) Content-Type: text/plain; charset=US-ASCII; format=flowed From: Nathen Hinson To: freebsd-questions@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: <38FCFC1E-70EF-11D7-9A2A-003065C47B66@mail.uhs.utexas.edu> X-Mailer: Apple Mail (2.551) X-OriginalArrivalTime: 17 Apr 2003 16:11:18.0320 (UTC) FILETIME=[FA8AAB00:01C304FB] Subject: Sysinstall and others do not detect disks 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: Thu, 17 Apr 2003 16:11:19 -0000 To Whomever may know the answer I have run into an issue which I am at a loss as how to resolve. I am attempting to add a disk to a running FreeBSD system, however no application seems to be able to detect this new disk. This is a FreeBSD 4.4-RELEASE(GENERIC) system. The system boots off the primary disk (ad0) without issue and was installed on this disk without issue. However this disk is too small to be useful by itself and so I wanted to add a disk. I read the appropriate sections of the FreeBSD manual regarding adding disks however I have tried all the options presented there ( i.e. sysinstall, manually compatibility mode, and manually dedicated mode ), and none of these options want to detect the disk. Sysinstall finds no disks whatsoever, including the boot disk. fdisk give operation not permitted errors when trying to use it on the disk device (i.e. ad1 ). I have used DOS fdisk to create a single DOS partition. Even after this sysinstall, fdisk, disklabel and even dd would give errors trying to read this disk.Sysinstall states that no disks are present in the system, and fdisk, disklabel and dd all give operation not permitted errors. I then formatted this disk with FAT32 and even mounted it with mount -t msdos /dev/ad1s1 /mnt/. Because of this I do not believe that the disk is bad. I can't perform an fsck on it because it has no filesystem. If anyone has any suggestions as to where I can look for more information or any advice whatsoever I would really appreciate it. Thank-you very much for your time and attention Sincerely Nathen Hinson Systems Analyst On - Site Support User Services Information Technology Services University of Texas at Austin