From owner-freebsd-questions@freebsd.org Fri Dec 30 23:33:09 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 2C483C98F23 for ; Fri, 30 Dec 2016 23:33:09 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay12.qsc.de (mailrelay12.qsc.de [212.99.163.153]) (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 A62E717B3 for ; Fri, 30 Dec 2016 23:33:08 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay12.qsc.de; Sat, 31 Dec 2016 00:35:44 +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 BC9DB3CC3F; Sat, 31 Dec 2016 00:33:04 +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 uBUNX46W003067; Sat, 31 Dec 2016 00:33:04 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Sat, 31 Dec 2016 00:33:04 +0100 From: Polytropon To: swjatoslaw gerus Cc: freebsd-questions@freebsd.org Subject: Re: fdisk -l .../dev/sdb1 system -invalid argument 1m #### dd if=FreeBSD-11-RELEASE-amd64-memstick.img of=/dev/sdb1 bs=1M conv=sync Message-Id: <20161231003304.01c07f1f.freebsd@edvax.de> In-Reply-To: <1483139624.784286.833372873.30E54F7C@webmail.messagingengine.com> References: <1483132051.752644.833300521.4E2EBB2A@webmail.messagingengine.com> <20161230231909.652499f9.freebsd@edvax.de> <1483139624.784286.833372873.30E54F7C@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 mailrelay12.qsc.de with DEBA56A35E5 X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.2107 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: Fri, 30 Dec 2016 23:33:09 -0000 On Sat, 31 Dec 2016 00:13:44 +0100, swjatoslaw gerus wrote: > fdisk -l > > /dev/sda1 > ... > /dev/sda6 > > /dev/sdb1 w95 FAT32 That is wrong. > Author performed that what freebsd stated .in email to author.. 1048576 This is equivalent to bs=1M or bs=1m, depending on what dd accepts for the size parameter. But that parameter isn't the problem - it's the _incorrect_ naming of the target device. The commend should be: # dd if=FreeBSD-11-RELEASE-amd64-memstick.img of=/dev/sdb bs=1048576 conv=sync Pay attention that it is "sdb", not "sdb1", which will write the image to the 1st partition and therefore the medium will _not_ boot - simply because no boot code is being written (to the _correct_ location). Again, check that you're not being blocked by a simple "fat fingers" mistake. :-) > possibly new sandisk must formated for ubuntu, No, it doesn't need to be formatted. The image itself already contains the formatted file system. Understand the image as a "ready-made" file system, or to be more precise, as a "medium image with boot code and file system". That image actually can contain several partitions (read: file systems) - and of course you cannot "put 4 partitions into a partition", you need to put them _directly_ on the USB stick). That's why it is so important that you specify the correct target device name. > than possibly can see > file after mounting with ls -lsar,to date can see with more No. You cannot mount the installation image (or the result on the USB stick) that way. It will have a UFS partition ("mount -t ufs" is required). You should then see the FreeBSD-typical files. This is what you can expect to see: # ls /mnt .cshrc HARDWARE.TXT boot/ media/ sys@ .profile README.HTM dev/ mnt/ tmp/ COPYRIGHT README.TXT docbook.css proc/ usr/ ERRATA.HTM RELNOTES.HTM etc/ rescue/ var/ ERRATA.TXT RELNOTES.TXT lib/ root/ HARDWARE.HTM bin/ libexec/ sbin/ If you have done everything as needed, you can see such kinds of entries, and the USB stick will boot as you expect it. The example above has been obtained like this: # mdconfig -a -t vnode -f FreeBSD-11.0-RELEASE-amd64-mini-memstick.img md0 # mount -t ufs -o ro /dev/md0p3 /mnt # ls /mnt ... see above ... # umount /mnt # mdconfig -d -u 0 It will work similarly with the real USB stick instead of a file-backed memory disk virtual device. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...