From owner-freebsd-questions@freebsd.org Sat Dec 31 01:14:05 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6925FC97346 for ; Sat, 31 Dec 2016 01:14:05 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay11.qsc.de (mailrelay11.qsc.de [212.99.187.252]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CB8511365 for ; Sat, 31 Dec 2016 01:14:04 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay11.qsc.de; Sat, 31 Dec 2016 02:16:33 +0100 Received: from r56.edvax.de (port-92-195-83-137.dynamic.qsc.de [92.195.83.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 6CE743CC3F; Sat, 31 Dec 2016 02:13:55 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id uBV1DsHm002402; Sat, 31 Dec 2016 02:13:54 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Sat, 31 Dec 2016 02:13:54 +0100 From: Polytropon To: swjatoslaw gerus Cc: freebsd-questions@freebsd.org Subject: Re: can not read with ls -lsar but loader work Re: performed- Fwd: 2-Fwd: You have made error ...#### dd if=FreeBSD-11-RELEASE-amd64-memstick.img of=/dev/sdb1 bs=1M conv=sync Message-Id: <20161231021354.c30c04fa.freebsd@edvax.de> In-Reply-To: <1483145413.806714.833416057.0403136E@webmail.messagingengine.com> References: <1483143086.798193.833401249.611AE9E5@webmail.messagingengine.com> <1483145413.806714.833416057.0403136E@webmail.messagingengine.com> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay11.qsc.de with 9C9E56A355F X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.2302 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2016 01:14:05 -0000 On Sat, 31 Dec 2016 01:50:13 +0100, swjatoslaw gerus wrote: > can not read with ls -lsar but loader work Of course not. As I did already explain, the target USB stick now contains 4 GPT partitions, one of them is UFS, and it needs to be mounted properly (not as "msdos", not as "pcfs") and with the precaution of the -o ro option (read-only) if you wanted to look at it. However, this is not _needed_ to make the system boot with it. > in 1 attempt some 2 days before in version > 11.0 bs=1m sdb1 -invalid argument Wrong target device, wrong unit suffix. > 2 attempt 11.0 bs=1048576 sdb1 dd succes but can not start Wrong target device. > 3 attempt( 11 as in your suggest from multiple author) -file not exist Which file did not exist? Please be more specific. > 4 attempt 11.0 bs=1048576 sdb1 dd succes can not see with ls -lsar > after > mount in /mnt ... can see with more Of course you cannot, as explained. YOu did write the image's content (which is designed to cover a whole device, not a partition) into a partition that still had the FAT32 type attribute, and it was therefore empty because the image is not in FAT32 format. I'd even go so far to say that it probably isn't even possible to mount a partition that fdisk says is of _type_ FAT32 but doesn't have the corresponding _content_ FAT32. Again, the mount + ls step is _not needed_ at all. It's just a _possible_ check to verify that the image has been written correctly, but it doesn't enable (or affect) the USB stick's ability to boot. Also, the use of fdisk is not needed because the image already contains boot code and partitioning data for the FreeBSD installer. > poweroff > plug in > poweron > loader started asked about auto/manual partion Excellent - _this_ is what the installer is supposed to do! Now you can start the installation into a free partition of the hard disk. As I mentioned earlier, there is no need to assign or format the space where FreeBSD should be installed into. Just leave it unassigned, empty - the installer will take care of all steps needed. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...