From owner-freebsd-questions Thu Jun 6 18: 0:45 2002 Delivered-To: freebsd-questions@freebsd.org Received: from empty1.ekahuna.com (empty1.ekahuna.com [198.144.200.196]) by hub.freebsd.org (Postfix) with ESMTP id 5437637B408 for ; Thu, 6 Jun 2002 18:00:39 -0700 (PDT) Received: from pc-02 (pc02.ekahuna.com [198.144.200.197]) by empty1.ekahuna.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with ESMTP id com; Thu, 6 Jun 2002 18:00:39 -0700 From: "Philip J. Koenig" Organization: The Electric Kahuna Organization To: questions@FreeBSD.ORG Date: Thu, 6 Jun 2002 18:00:38 -0700 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: slice/partition/disklabel/disk copy question Reply-To: pjklist@ekahuna.com Cc: Axel Scheepers X-mailer: Pegasus Mail for Win32 (v3.12c) Message-ID: <20020607010039037.AAA494@empty1.ekahuna.com@pc02.ekahuna.com> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > OK, so I'm sitting here with the emergency shell booting from the > fixit CD. I decided to try editing the disklabel, which looked easier > than creating one from scratch. Something about the fixit environment > is unfriendly though - this is what I got: > > > Fixit# disklabel -er /dev/amrd1s2 > disklabel: /mnt2/stand/vi: No such file or directory OK, fixed this problem - for some reason when using the fixit CD from 4.5-RELEASE, it sets an invalid "EDITOR" variable. I reset that and disklabel -e now works. (maybe I should file a bug report?) I fixed the disklabel by manually adjusting the values so the system doesn't complain on boot, and I installed booteasy on the first (MSDOS) partition. But now the problem is that it thinks there's no slice 1 on disk2, only a slice 2, so it won't boot. (The freebsd boot manager shows 2 options: F1: MSDOS, and F2: disk 2) If I try to run fdisk from the fixit CD, I get: Fixit# fdisk -s fdisk: cannot open any disk: no such file or directory The disklabel actually was changed by the system when I edited it to reflect what should be the correct slice, but when the system boots it doesn't think slice 1 exists: Fixit# disklabel -r amrd1s2 (note the disk: line) # /dev/amrd1s2 type: SCSI disk: amrd1s1 [...] Fixit# disklabel -r amrd1s1 disklabel: /dev/amrd1s1: no such file or directory Any ideas how I can fix this? Thx, Phil -- Philip J. Koenig pjklist@ekahuna.com Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message