Date: Sat, 10 Nov 2012 00:26:05 -0800 (PST) From: Jack Mc Lauren <jack.mclauren@yahoo.com> To: Ian Lepore <freebsd@damnhippie.dyndns.org> Cc: "freebsd-embedded@freebsd.org" <freebsd-embedded@freebsd.org> Subject: Re: nanobsd image Message-ID: <1352535965.38849.YahooMailNeo@web126006.mail.ne1.yahoo.com> In-Reply-To: <1352388773.17290.66.camel@revolution.hippie.lan> References: <1352387998.10370.YahooMailNeo@web126003.mail.ne1.yahoo.com> <1352388773.17290.66.camel@revolution.hippie.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
>It's hard to guess what's going on with a description of "messages=0A=0A>l= ike..." rather than the actual messages verbatim.=C2=A0 But if I had to=0A>= guess at this point, I'd lean towards a difference between SATA devices=0A>= being "ad0" and "ada0" which might be different between target systems=0A>b= ased on the BIOS settings on each system for whether to present the=0A>driv= es as legacy/compatible IDE versus AHCI.=C2=A0 The options used to build=0A= >the kernel also have some effect on ad0 vs ada0, but I'll admit to being= =0A>in a complete state of confusion over that because of working on system= s=0A>using 8.x, 9.x and 10.0 every day, and I've completely lost track of= =0A>what behaviors are seen in which versions.=0A=0A>-- Ian=0A=0AThank you = Lan. this is the whole message, and what i do :=0A=0A######################= ############################=0AIf you have invalid mount options, reboot, a= nd first try the=0Afollowing from the loader prompt :=0A=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 se= t vfs.root.mountfrom.options=3Drw=0AAnd then remove the invalid mount optio= ns from /etc/fstab.=0A=C2=A0=0ALoader variables:=0Avfs.root.mountfrom=3Dufs= :/dev/da0s1a=0Avfs.root.mountfrom.options=3Dro=0A=C2=A0=0AManual root files= ystem specifications:=0Ada0 at umass-sim0 bus 0 scbus0 target 0 lun 0=0A=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0 <fstype>:<device>=0AMount <device> using filesystem <fstype>= =0Ada0 :=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 eg. Ufs:/dev/da0s1a=0A<UFD 2.0 Silic= on-Power8G PMAP> Removable Direct Access=0ASCSI-4 device=0A=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= Eg. Cd9660:/dev/acd0=0Ada0: 40.000MB/s transfers=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 This=0Ais equivalent to:=0Amount =E2= =80=93t cd9660 /dev/acd0/=0Ada0: 7388MB (15130624 512 byte sector: 255H 63S= /T 941C)=0A=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 ?=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 List valid disk boot devices=0A=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 <empty=0Aline>=C2=A0=C2=A0=C2=A0=C2=A0 Abort manual input=0Amountroo= t >=0Amountroot>?=0AList of GEOM managed disk devices:=0A=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 da= 10s1a=C2=A0=C2=A0 da0s4=C2=A0 =C2=A0da0s3=C2=A0 da0s1=C2=A0 =C2=A0da0=0A###= ################################################=0A=0AI have to set the mou= nt root manually :=0AMountroot>ufs:/dev/da0s1a=0AThe system does not do thi= s automatically. Fstab file is=0Acorrect as you can see the =E2=80=9Cloader= variables=E2=80=9D.=0AWhat=E2=80=99s the problem ? I am so confused !!!=0A= The point is that we don=E2=80=99t dace this problem on one our=0Asystem !!= !=0Aby the way, I have copied the image on a flash memory. From owner-freebsd-embedded@FreeBSD.ORG Sat Nov 10 16:40:45 2012 Return-Path: <owner-freebsd-embedded@FreeBSD.ORG> Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B4DD0152 for <freebsd-embedded@freebsd.org>; Sat, 10 Nov 2012 16:40:45 +0000 (UTC) (envelope-from bob@drinksbeer.org) Received: from mail.drinksbeer.org (107-0-69-251-ip-static.hfc.comcastbusiness.net [107.0.69.251]) by mx1.freebsd.org (Postfix) with ESMTP id 8C47F8FC0A for <freebsd-embedded@freebsd.org>; Sat, 10 Nov 2012 16:40:44 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.drinksbeer.org (Postfix) with ESMTP id 17B865D44EF; Sat, 10 Nov 2012 08:32:27 -0800 (PST) X-Virus-Scanned: amavisd-new at drinksbeer.org Received: from mail.drinksbeer.org ([127.0.0.1]) by localhost (mail.drinksbeer.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4BqIaL0YfXze; Sat, 10 Nov 2012 08:32:17 -0800 (PST) Received: from mail.drinksbeer.org (mail [107.0.69.251]) by mail.drinksbeer.org (Postfix) with ESMTP id 2367B5D44EE; Sat, 10 Nov 2012 08:32:17 -0800 (PST) Date: Sat, 10 Nov 2012 08:32:16 -0800 (PST) From: Bob Ryan <bob@drinksbeer.org> To: Jack Mc Lauren <jack.mclauren@yahoo.com> Message-ID: <3071705.80.1352565121545.JavaMail.Bob@Toad-PC> In-Reply-To: <1352535965.38849.YahooMailNeo@web126006.mail.ne1.yahoo.com> Subject: Re: nanobsd image MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Originating-IP: [71.197.83.152] X-Mailer: Zimbra 7.1.4_GA_2565 (Zimbra Desktop/7.2.1_11637_Windows) Cc: freebsd-embedded@freebsd.org X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Dedicated and Embedded Systems <freebsd-embedded.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-embedded>, <mailto:freebsd-embedded-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-embedded>; List-Post: <mailto:freebsd-embedded@freebsd.org> List-Help: <mailto:freebsd-embedded-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-embedded>, <mailto:freebsd-embedded-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 10 Nov 2012 16:40:45 -0000 I don't see da0s1a in this list- List of GEOM managed disk devices: da10s1a da0s4 da0s3 da0s1 da0 ################################################### ----- Original Message ----- From: "Jack Mc Lauren" <jack.mclauren@yahoo.com> To: "Ian Lepore" <freebsd@damnhippie.dyndns.org> Cc: freebsd-embedded@freebsd.org Sent: Saturday, November 10, 2012 12:26:05 AM Subject: Re: nanobsd image >It's hard to guess what's going on with a description of "messages >like..." rather than the actual messages verbatim.=C2=A0 But if I had to >guess at this point, I'd lean towards a difference between SATA devices >being "ad0" and "ada0" which might be different between target systems >based on the BIOS settings on each system for whether to present the >drives as legacy/compatible IDE versus AHCI.=C2=A0 The options used to bui= ld >the kernel also have some effect on ad0 vs ada0, but I'll admit to being >in a complete state of confusion over that because of working on systems >using 8.x, 9.x and 10.0 every day, and I've completely lost track of >what behaviors are seen in which versions. >-- Ian Thank you Lan. this is the whole message, and what i do : ################################################## If you have invalid mount options, reboot, and first try the following from the loader prompt : =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 set vfs.root.mountfrom.options=3Drw And then remove the invalid mount options from /etc/fstab. =C2=A0 Loader variables: vfs.root.mountfrom=3Dufs:/dev/da0s1a vfs.root.mountfrom.options=3Dro =C2=A0 Manual root filesystem specifications: da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 <fstype>:<device> Mount <device> using filesystem <fstype> da0 :=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 eg. Ufs:/dev/da0s1a <UFD 2.0 Silicon-Power8G PMAP> Removable Direct Access SCSI-4 device =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 Eg. Cd9660:/dev/acd0 da0: 40.000MB/s transfers=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0 This is equivalent to: mount =E2=80=93t cd9660 /dev/acd0/ da0: 7388MB (15130624 512 byte sector: 255H 63S/T 941C) =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 ?=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 List valid disk boot devices =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 <empty line>=C2=A0=C2=A0=C2=A0=C2=A0 Abort manual input mountroot > mountroot>? List of GEOM managed disk devices: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 da10s1a=C2=A0=C2=A0 da0s4=C2=A0 =C2=A0da0s3=C2=A0 da0s1=C2= =A0 =C2=A0da0 ################################################### I have to set the mount root manually : Mountroot>ufs:/dev/da0s1a The system does not do this automatically. Fstab file is correct as you can see the =E2=80=9Cloader variables=E2=80=9D. What=E2=80=99s the problem ? I am so confused !!! The point is that we don=E2=80=99t dace this problem on one our system !!! by the way, I have copied the image on a flash memory. _______________________________________________ freebsd-embedded@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-embedded To unsubscribe, send any mail to "freebsd-embedded-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1352535965.38849.YahooMailNeo>