From owner-freebsd-mobile Sat Aug 31 14: 1:49 2002 Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 923B737B400 for ; Sat, 31 Aug 2002 14:01:42 -0700 (PDT) Received: from medg.lcs.mit.edu (medg.lcs.mit.edu [18.30.0.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE5BB43E72 for ; Sat, 31 Aug 2002 14:01:41 -0700 (PDT) (envelope-from jg@medg.lcs.mit.edu) Received: from medg.lcs.mit.edu (pool-141-154-15-8.bos.east.verizon.net [141.154.15.8]) by medg.lcs.mit.edu (8.9.3/8.9.3) with ESMTP id RAA03070 for ; Sat, 31 Aug 2002 17:01:40 -0400 (EDT) Message-ID: <3D713B0E.70400@medg.lcs.mit.edu> Date: Sat, 31 Aug 2002 17:54:22 -0400 From: Jules Gilbert Reply-To: jg@medg.lcs.mit.edu Organization: compression and prediction and stuff like that... User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3 X-Accept-Language: en-us MIME-Version: 1.0 To: freebsd-mobile@freebsd.org Subject: failed disk dup?? Content-Type: multipart/alternative; boundary="------------050706090502020800010902" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --------------050706090502020800010902 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Please copy pg@eth1.com -- as he is the person having the problem any advice on the following just duped a laptop disk with dump|restore put it into new notebook i get invalid partition i get the 1st stage boot prompt with boot failure message and the expected default that failed 0:ad(0,a)/boot/loader the duped drive has the FBSD slice as ad0s1e if i say at this point 0:ad(0,e)/boot/loader OR if i say; 0:ad(0,e)/kernel i can boot to my custom compiled kernel sometimes BUT NOT always i can boot with just saying; 0:ad(0,e) i have tried making a boot.config, then a boot.conf file with 0:ad(0,e)/boot/loader in there doesn't work, i still have to boot it manually by saying the exact same thing as above i've tried putting a reference in loader.conf to try to get the loader to reckognize boot.config by just specifying the file name /boot/config in loader.conf but maybe i don't have the right syntax even tried doing a disklabel -B /dev/ad0s1, i thought maybe there weren't any boot blocks, tried disklabel -w -B also tried editing the disklabel disklabel -e ad0 and tried changing the partition label from e to a but even as root the system wouldn't lemme write to the disk when editing i finished fresh out of ideas, anyone know how to do this so it boots by itself again? HOW/where DO I SPECIFY THAT ad0 s1e, is the right place to boot from with out doing this manually each and every time? i haven't tried doing anything w/ boot0cfg but i figure i'm past that point anyways if i get to where i'm now getting to.. --------------050706090502020800010902 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit 
Please copy pg@eth1.com -- as he is the person having the problem




any advice on the following

just duped a laptop disk with dump|restore

put it into new notebook

i get invalid partition
i get the 1st stage boot prompt with boot failure
message and the expected default that failed 
0:ad(0,a)/boot/loader

the duped drive has the FBSD slice as ad0s1e

if i say at this point

0:ad(0,e)/boot/loader  OR if i say;
0:ad(0,e)/kernel

i can boot to my custom compiled kernel
sometimes BUT NOT always i can boot with just saying;

0:ad(0,e)

i have tried making a boot.config, then a boot.conf
file with 0:ad(0,e)/boot/loader in there

doesn't work, i still have to boot it manually by
saying the exact same thing as above

i've tried putting a reference in loader.conf to try
to get the loader to reckognize boot.config by just
specifying the file name /boot/config in loader.conf
but maybe i don't have the right syntax

even tried doing a disklabel -B /dev/ad0s1, i thought
maybe there weren't any boot blocks, 
tried disklabel -w -B also

tried editing the disklabel disklabel -e ad0
and tried changing the partition label from e to a but
even as root the system wouldn't lemme write to the
disk when editing i finished

fresh out of ideas, anyone know how to do this so it
boots by itself again? HOW/where DO I SPECIFY THAT ad0
s1e, is the right place to boot from with out doing
this manually each and every time?

i haven't tried doing anything w/ boot0cfg but i
figure i'm past that point anyways if i get to where
i'm now getting to.. 
 
--------------050706090502020800010902-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message