Hi,
I got a new thumb drive which was FAT formatted. I use this script to change
this:
!/bin/tcsh
#
# This script format a thumb drive connected to USB as da0.
#
printf "You have to run this script as 'root' to succeed.\n"
printf "Warning this script will delete all your data from /dev/da0.
Continue? > "
set Eingabe = $<
if ("$Eingabe" == "y") then
printf "\nDeleting the device "
dd if=/dev/zero of=/dev/da0 bs=1k count=1
printf "\nWriting the BSD label "
bsdlabel -Bw da0 auto
printf "\nEditing the BSD label "
bsdlabel -e da0
newfs /dev/da0a
printf "\nThe device /dev/da0 was formated to be used with
FreeBSD.\n"
else
printf "\nScript aborted!\n"
endif
I then call manually
tunefs -L NewDeviceName /dev/da0a
Either this call or the mount command does not work randomly.
When I then try to mount the device on /dev/da0a it does not work always.
I do not know what this causes, I am only randomly able to reproduce it.
It might be affected by removing the device or keeping it plugged in.
uname says:
FreeBSD AMD620.ovitrap.com 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #28: Tue Feb 21
17:15:07 WIT 2012 erich@AMD620.ovitrap.com:/usr/obj/usr/src/sys/AsusAMD620
amd64
dmesg says:
ugen1.2: <vendor 0x1005> at usbus1
umass0: <vendor 0x1005 USB FLASH DRIVE, class 0/0, rev 2.00/1.00, addr 2>
on usbus1
umass0: SCSI over Bulk-Only; quirks = 0x4001
umass0:2:0:-1: Attached to scbus2
da0 at umass-sim0 bus 0 scbus2 target 0 lun 0
da0: < USB FLASH DRIVE PMAP> Removable Direct Access SCSI-0 device
da0: 40.000MB/s transfers
da0: 15272MB (31277056 512 byte sectors: 255H 63S/T 1946C)
It is not an urgent problem.
Erich
Am 22.02.2012 um 07:34 schrieb Erich Dollansky:> > tunefs -L NewDeviceName /dev/da0a > > Either this call or the mount command does not work randomly. > > When I then try to mount the device on /dev/da0a it does not work always. > > I do not know what this causes, I am only randomly able to reproduce it. > > It might be affected by removing the device or keeping it plugged in.You need to be more specific: what "does not work" mean? Output, results? Stefan -- Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
Hi, On Thursday 23 February 2012 20:22:57 Stefan Bethke wrote:> Am 22.02.2012 um 07:34 schrieb Erich Dollansky: > > > > > tunefs -L NewDeviceName /dev/da0a > > > > Either this call or the mount command does not work randomly. > > > > When I then try to mount the device on /dev/da0a it does not work always. > > > > I do not know what this causes, I am only randomly able to reproduce it. > > > > It might be affected by removing the device or keeping it plugged in. > > You need to be more specific: what "does not work" mean? Output, results? >it seems that I forgot to copy the console output for this. Ok, as far as I remember, tunefs said something like it does not recognise the slice. Mount has had two different messages. One also said that it could not find/recognise the slice. The other one said that the file system was unknown despite just running a newfs on it. I am very much aware that this kind of errors are very hard to find especially if they are not reproduceable. Erich> > Stefan > > -- > Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811 > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > >
On Wed, 22 Feb 2012 13:34:36 +0700 Erich Dollansky <erich@alogreentechnologies.com> wrote:>I got a new thumb drive which was FAT formatted. I use this script to change this: > >!/bin/tcsh ># ># This script format a thumb drive connected to USB as da0. ># >printf "You have to run this script as 'root' to succeed.\n" >printf "Warning this script will delete all your data from /dev/da0. Continue? > " >set Eingabe = $< >if ("$Eingabe" == "y") then > printf "\nDeleting the device " > dd if=/dev/zero of=/dev/da0 bs=1k count=1 > printf "\nWriting the BSD label " > bsdlabel -Bw da0 autoHmmm...so no MBR and no GPT either? Just the bare device? I guess I haven't tried that, so I don't know what that would do.> printf "\nEditing the BSD label " > bsdlabel -e da0 > newfs /dev/da0a > printf "\nThe device /dev/da0 was formated to be used with FreeBSD.\n" >else > printf "\nScript aborted!\n" >endif > >I then call manually > >tunefs -L NewDeviceName /dev/da0aJust out of curiosity, I'd like to know why you run tunefs manually, rather than using "-L NewDeviceName" on the newfs command, given that your script is clearing the physical device and then creating an empty file system.> >Either this call or the mount command does not work randomly. > >When I then try to mount the device on /dev/da0a it does not work always.What do you mean when you write "mount the device on /dev/da0a"? Normally one mounts a filesystem onto a "device", e.g., mount /dev/ad0s1d /var or some similar thing. Also, why do you refer to /dev/da0a at all if you labeled the file system? The whole point of labeling the file system is supposed to be so that you can mount it independently of the physical device name, e.g., mount /dev/ufs/NewDeviceName /thumbfs which allows you to have an entry in /etc/fstab for mounting the file system that doesn't need to be edited every time you reboot the system or move devices around.> >I do not know what this causes, I am only randomly able to reproduce it. > >It might be affected by removing the device or keeping it plugged in.Well, yes, that's what you label partitions/devices to avoid having to deal with manually, right?> >uname says: > >FreeBSD AMD620.ovitrap.com 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #28: Tue Feb 21 17:15:07 WIT 2012 erich@AMD620.ovitrap.com:/usr/obj/usr/src/sys/AsusAMD620 amd64 > >dmesg says: > >ugen1.2: <vendor 0x1005> at usbus1 >umass0: <vendor 0x1005 USB FLASH DRIVE, class 0/0, rev 2.00/1.00, addr 2> on usbus1 >umass0: SCSI over Bulk-Only; quirks = 0x4001 >umass0:2:0:-1: Attached to scbus2 >da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 >da0: < USB FLASH DRIVE PMAP> Removable Direct Access SCSI-0 device >da0: 40.000MB/s transfers >da0: 15272MB (31277056 512 byte sectors: 255H 63S/T 1946C) > >It is not an urgent problem. >It most likely is not a problem at all. See http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom-glabel.html#AEN27470 With best regards, Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at cs.niu.edu * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * **********************************************************************
On Sat, 25 Feb 2012 08:56:24 -0800 Kevin Oberman <kob6558@gmail.com> wrote:>On Sat, Feb 25, 2012 at 2:27 AM, Scott Bennett <bennett@cs.niu.edu> wrote: >> =A0 =A0 On Wed, 22 Feb 2012 13:34:36 +0700 Erich Dollansky >> <erich@alogreentechnologies.com> wrote: >> >>>I got a new thumb drive which was FAT formatted. I use this script to cha>nge this: >>> >>>!/bin/tcsh >>># >>># This script format a thumb drive connected to USB as da0. >>># >>>printf "You have to run this script as 'root' to succeed.\n" >>>printf "Warning this script will delete all your data from /dev/da0. Cont>inue? > " >>>set Eingabe =3D $< >>>if ("$Eingabe" =3D=3D "y") then >>> =A0 printf "\nDeleting the device " >>> =A0 dd if=3D/dev/zero of=3D/dev/da0 bs=3D1k count=3D1 >>> =A0 printf "\nWriting the BSD label " >>> =A0 bsdlabel -Bw da0 auto >> >> =A0 =A0 Hmmm...so no MBR and no GPT either? =A0Just the bare device? =A0I> guess >> I haven't tried that, so I don't know what that would do. > >Call me a bit confused, but I thought -B did write an MBR. It always >has seemed to do so for me, at any rate. From man bsdlabel: >"Installing Bootstraps > If the -B option is specified, bootstrap code will be read from the fi>le > /boot/boot and written to the disk." >Or am I not understanding something?I guess I understand the part that you quoted above as meaning that the bootstrap code would be copied to the bootstrap sectors. However, as I interpret it, the bsdlabel command does not write a MBR, which would include the slice map for the device. Further, Erich's later commands did not specify a slice number. In short, it looks to me as though he may have ended up with the initial boot code where it belonged at the start of the device, but the boot code looks for the slice map, which isn't there, so it should not be possible to boot a kernel because the bootstrap code would not be able to find it. But as far as simply mounting a file system, I really don't know whether it should work to have a BSD label written to a bare device with neither a MBR nor a GPT to find that label. IOW, would the device node to be used in the mount operation have been created? Note to Erich: did you look in /dev and /dev/ufs to see whether all of the device files that you expected to be there were, in fact, present before you attempted the mount? Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at cs.niu.edu * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * **********************************************************************