Jun 16 23:32:15 linux-lz34 kernel: usb 1-4.2: new high speed USB device using ehci_hcd and address 6
Jun 16 23:32:15 linux-lz34 kernel: usb 1-4.2: configuration #1 chosen from 1 choice
Jun 16 23:32:15 linux-lz34 kernel: usb 1-4.2: New USB device found, idVendor=152d, idProduct=2329
Jun 16 23:32:15 linux-lz34 kernel: usb 1-4.2: New USB device strings: Mfr=10, Product=11, SerialNumber=3
Jun 16 23:32:15 linux-lz34 kernel: usb 1-4.2: Product: DataStation maxi n.u
Jun 16 23:32:15 linux-lz34 kernel: usb 1-4.2: Manufacturer: TrekStor GmbH & Co. KG
Jun 16 23:32:15 linux-lz34 kernel: usb 1-4.2: SerialNumber: 0F0000000003937
I need to mount this drive, but don’t know what I should put where I would normally put “/dev/sdb” for example, in the command
The device name can not be /dev/sdb
It is the drive name and the mount should really refer to a particular partition in that.
In openSUSE 11.1, you don’t need to execute a mount command or need to put any entry in fstab. Within a couple of seconds after inserting the USB drive, it will get auto-mounted thru the plug-in/HAL architecture.
In openSUSE 11.1, you don’t need to execute a mount command or need to put any entry in fstab. Within a couple of seconds after inserting the USB drive, it will get auto-mounted thru the plug-in/HAL architecture.
Further to that, after plugging the device in, navigate to /media with file manager. See what is mounted there. (You can see what partitions are mounted with ‘mount’ command).
There may well have been a kernel upgrade going on - the system spends a lot of time up and doesn’t often reboot. I’m by no means familiar with the internal workings of a kernel upgrade - can anyone explain to me in a few words how doing so renders the vfat an unknown file system? What would have happened if a file system actually in use at the time had become unknown, or is that impossible?
> There may well have been a kernel upgrade going on - the system spends
> a lot of time up and doesn’t often reboot. I’m by no means familiar with
> the internal workings of a kernel upgrade
there has been a kernel upgrade in the last (say) week…
depending on how your system is setup it may have done an automatic
kernel update, but that is NOT complete until the system has been
rebooted…
you need to talk to your system administrator to pay attention, and
reboot…
then maybe the USB will automatically mount and make itself
available, as it should…
if not…i don’t know what to do…
> can anyone explain to me in
> a few words how doing so renders the vfat an unknown file system? What
> would have happened if a file system actually in use at the time had
> become unknown, or is that impossible?
in an earlier post in this thread you said “playing with the mount
command on a drive . . . returned the error 'Unknown file system type
‘vfat’ … why might vfat have suddenly stopped being a recognised
file system type?” and i can say with some authority that in my
experience most of of the things that happen suddenly while playing on the command are usually unexplainable other than to say:
user induced error.
> There may well have been a kernel upgrade going on - the system spends
> a lot of time up and doesn’t often reboot. I’m by no means familiar with
> the internal workings of a kernel upgrade - can anyone explain to me in
> a few words how doing so renders the vfat an unknown file system? What
> would have happened if a file system actually in use at the time had
> become unknown, or is that impossible?
Well, I think vfat module is “linked” to the old kernel, so when
calling “mount -t vfat” it tries to load from a place that currently does
not exist.
I think I can understand that, although I had the idea that when kernels were rebuilt, the new kernel was built and was placed somewhere safe and at reboot the old kernel replaced with the new. If my picture was wrong, that all makes sense.
