From owner-freebsd-arm@freebsd.org Sat Mar 3 00:57:03 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E6891F32EE4 for ; Sat, 3 Mar 2018 00:57:02 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 47ACD839DB for ; Sat, 3 Mar 2018 00:57:02 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w230v1Qd037417 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 2 Mar 2018 16:57:02 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w230v03o037416; Fri, 2 Mar 2018 16:57:01 -0800 (PST) (envelope-from fbsd) Date: Fri, 2 Mar 2018 16:57:00 -0800 From: bob prohaska To: tech-lists Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: Can two USB flash drives conflict with each other? Message-ID: <20180303005700.GC37148@www.zefox.net> References: <20180302231317.GA37148@www.zefox.net> <0fd4b991-a7d8-0e04-7d73-26d351873390@zyxst.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0fd4b991-a7d8-0e04-7d73-26d351873390@zyxst.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2018 00:57:03 -0000 On Sat, Mar 03, 2018 at 12:32:27AM +0000, tech-lists wrote: > On 02/03/2018 23:13, bob prohaska wrote: > > The obvious solution is "don't do that!", but if somebody can offer > > a more insightful explanation I'd be grateful. Using two USB flash > > drives simultaneously would be very useful. > > I've found [this was a year ago, maybe two] that if I had two usb sticks > plugged in that sometimes they'd be detected in reverse order to what I > expected. > > What I mean is that sometimes the device called /dev/da0 and the one > called /dev/da1 would swap on reboot. I suppose it would depend on which > one woke up first. So if I had made /dev/da0p1, allocated it as swap, > /dev/da0p1 as data, perhaps put the ports tree there, /dev/da1p1 as > data, perhaps used the entire device for data, sometimes it'd boot, look > at /dev/da0 which was /dev/da1 previously, not seen swap, and complained > loudly. > > I think there is a way to wire device identities to names but it might > need GPT rather than MBR as a partitioning scheme. I worked around it by > labelling one of the usb sticks with sticky tape and ensuring it wasn't > plugged in before the other one when rebooting. > On the first try I plugged the second USB drive into a running machine, producing the errors reported. It's not obvious how a _second_ device can "unseat" one that is already represented in /dev/.... On a later try I plugged the second USB flash device in and powered the Pi3 up, whence the kernel got confused over which was which. That makes slightly more sense. I think that might be fixable with labels in /etc/fstab. In my case the second drive was labeled much like the first, so it couldn't help. Somewhere I got the idea USB flash devices had a unique serial number, or equivalent, so that more than one could co-exist on a host. Is this notion mistaken? Thanks for reading, bob prohaska