random problem with 8.3 from yesterday

[Erich Dollansky]

On Friday 24 February 2012 23:23:53 Ian Lepore wrote:
> On Fri, 2012-02-24 at 13:50 +0700, Erich Dollansky wrote:
> > Hi,
> > 
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.
> > > > 
> > > -- 
> > > Stefan Bethke <stb at lassitu.de>   Fon +49 151 14070811
> 
> I've been putting up with problems like this since first upgrading to
> 8.2.  I guess I haven't dug deeper into them because it's actually a
> huge improvement from what I was used to in 6.x and 7.x where complete
> system lockups were more common with removable usb drives.  Here's an
> example sequence that just happened to me with a compact flash card in a
> usb multi-card reader...
> 
I was lucky then. Since 8.0, these problems disappeared for me and came back only with 8.3.

>         revolution # mount /dev/da0s1a /mnt
>         mount: /dev/da0s1a : Invalid argument
>         revolution # fsck -y /dev/da0s1a
>         fsck: Could not determine filesystem type
>         revolution # fsck -t ufs -y /dev/da0s1a
>         ** /dev/da0s1a
>         Cannot find file system superblock
>         ioctl (GCINFO): Inappropriate ioctl for device
>         fsck_ufs: /dev/da0s1a: can't read disk label
> 
> At this point I unplug the multi-card reader and plug it back in.
> 
>         revolution # fsck -y /dev/da0s1a
>         fsck: Could not determine filesystem type

Yes, this are some of the messages. They changed randomly for me.

> 
> I'm not sure whether or not this is related to the problem Erich
> originally reported, but there are some similarities in symptoms such as
> the inability to recognize the filesystem type, so I thought I'd mention

It is the same what happened to me.

Erich