From owner-freebsd-questions@FreeBSD.ORG Mon May 28 16:05:23 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A3FB816A46C for ; Mon, 28 May 2007 16:05:23 +0000 (UTC) (envelope-from warrenhead@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mx1.freebsd.org (Postfix) with ESMTP id 1A77D13C4B0 for ; Mon, 28 May 2007 16:05:22 +0000 (UTC) (envelope-from warrenhead@gmail.com) Received: by ug-out-1314.google.com with SMTP id u2so924421uge for ; Mon, 28 May 2007 09:05:21 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=PED1M4JxJlJS9cDH53l3/1ee2s7M4GGQfFCgZaJaPgPbMdA0BMjeLwOcfiwCd2KxJANG6gPr1Ck21qNAjXKh2ieIIdNB2EWk2aGPixBJjotzSS3lwig/gohCfT7pKdYZCUx0tzTiKLoMDUWwqbkISH4Fd6BaGGzkBZsnpYS2h0g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=CDmKyj5y4cjhuDKH1An9gK/8t6ae1bA0hBLtgypER/G9L2R2dZfudOyewhhQfX8vKAI4jsWSYFcgnSJfyWcuCGz7p3jV71o2n/4PtZ8sLbUUwABV1Gt/G1o9T7lR2kk9iv5DctfwBRt7pEBe76mixd6ZCRSSG4rpxuyNmEZ69CU= Received: by 10.67.25.9 with SMTP id c9mr5375552ugj.1180368321619; Mon, 28 May 2007 09:05:21 -0700 (PDT) Received: from ?192.168.179.16? ( [81.206.93.205]) by mx.google.com with ESMTP id w40sm4931057ugc.2007.05.28.09.05.20; Mon, 28 May 2007 09:05:20 -0700 (PDT) Message-ID: <465AFDBB.8050304@gmail.com> Date: Mon, 28 May 2007 18:05:15 +0200 From: WarrenHead User-Agent: Thunderbird 1.5.0.10 (X11/20070403) MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: machine will no longer boot 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: Mon, 28 May 2007 16:05:23 -0000 Hi list, Yesterday I installed a new sata disk into my server, which is connected to a highpoint rocket raid card. I plugged in only one disk, so no raid yet. I ran sysinstall and then fdisk and disklabel. All was fine and I placed files onto the disk. Then I realized I had made a mistake, I had made only one partition with fdisk, and two slices with disklabel. (Mountpoints pointing to /mnt/x and /mnt/y.) Somehow I got another mountpoint automatically which mounted the entire disk as one, to /media/z. Weird. So I ran sysinstall again and used fdisk to erase everything and create two partitions. I wrote these changes successfully to the disk. I then started disklabel (still from within sysinstall) and created the two mount points for the two partitions again. I tried to write these changes to the disk, but that failed. Mmm, weird. So, perhaps I needed to reboot first? Which I did, and now I cannot boot anymore. The error messages that show on screen are something like this: Can't stat /dev/ad4sd1 No such file or directory Can't stat /dev/ad4se1 No such file or directory After that I get a bogus shell which can do virtually nothing. I have no idea what it is. I can cat /etc/fstab though and noticed that the two lines with mountpoints for the new disk are indeed the new lines. I guess disklabel was partially succesfull? Perhaps I should simply remove these lines in /etc/fstab? Unfortunately, with this ridiculous shell, I don't know how to. So I tried a livecd (Knoppix 5.1). Since the system disk was formatted as ufstype=5xbsd, I have trouble writing to it. Bummer. But... should I remove these lines in /etc/fstab? Will this matter? Luckily I can read the disk, so if necessary I can start over, but I hope there is something I can do from within that odd shell. Please advise, this particular problem is not fun. Cheers, Warren