Am Montag, 10. Dezember 2018 schrieb Baron:
> Hi Nik,
>
> On Monday 10 December 2018 19:33:50 Dr. Nikolaus Klepp wrote:
> > Am Montag, 10. Dezember 2018 schrieb Baron:
> > > Hi Dan, Guys,
> > >
> > > On Monday 10 December 2018 16:59:25 Dan Youngquist wrote:
> > > > On 12/08/2018 12:23 PM, Baron wrote:
> > > > > If I have a HDD connected via a USB adaptor, I've found that
> > > > > after an initial plugging and use, then safely removing it,
> > > > > going back to it, in the same session, it may or may not be
> > > > > recognised.
> > > >
> > > > I've always had a similar problem when using Safely Remove.
> > > > The solution is to use Unmount rather than Safely Remove; then
> > > > you can mount & unmount it as many times as you like with no
> > > > problems.
> > >
> > > I will try that option !
> > > However I think I've killed my USB - HDD adaptor ! Non of the
> > > machines that I have now even recognise that I've plugged the
> > > thing in. That's two desktops and my laptop. The ports are OK
> > > since they all recognise my USB sticks.
> > >
> > > I'll order a new one and try again.
> >
> > What does dmesg say when plugging in?
>
>
> Absolutely nothing, but if I plug in a USB stick I get this,
>
> [ 7258.600228] usb 1-1.1: new high-speed USB device number 3 using
> ehci-pci
> [ 7258.694671] usb 1-1.1: New USB device found, idVendor=1aa6,
> idProduct=0201
> [ 7258.694676] usb 1-1.1: New USB device strings: Mfr=1, Product=2,
> SerialNumber =3
> [ 7258.694680] usb 1-1.1: Product: USB 2.0 Flash
> [ 7258.694683] usb 1-1.1: Manufacturer: USB
> [ 7258.694685] usb 1-1.1: SerialNumber: 05100846020087
> [ 7258.745210] usb-storage 1-1.1:1.0: USB Mass Storage device detected
> [ 7258.745352] scsi6 : usb-storage 1-1.1:1.0
> [ 7258.745408] usbcore: registered new interface driver usb-storage
> [ 7259.745916] scsi 6:0:0:0: Direct-Access USB USB 2.0 Flash
> 1.00 PQ : 0 ANSI: 0
> [ 7259.746137] sd 6:0:0:0: Attached scsi generic sg2 type 0
> [ 7259.746987] sd 6:0:0:0: [sdb] 127104 512-byte logical blocks: (65.0
> MB/62.0 M iB)
> [ 7259.747756] sd 6:0:0:0: [sdb] Write Protect is off
> [ 7259.747759] sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00
> [ 7259.748356] sd 6:0:0:0: [sdb] No Caching mode page found
> [ 7259.748357] sd 6:0:0:0: [sdb] Assuming drive cache: write through
> [ 7259.754413] sdb: sdb1
> [ 7259.757635] sd 6:0:0:0: [sdb] Attached SCSI removable disk
> [ 7260.385411] FAT-fs (sdb1): utf8 is not a recommended IO charset for
> FAT files ystems, filesystem will be case
> sensitive!
>
> When I remove it this line gets added.
> [ 7902.788999] usb 1-1.1: USB disconnect, device number 3
>
> Does this help ?
OMG, I have a flashback! If you search the TDE archives you'll find earlier post from me with a simillar problem. TDE did nothing, when I plugged in my Casio camera (usb mass storage device). It turned out that a genius from freedesktop.org changed an entry in the hardware database so that my caera was not recognized as "disk" any more. I still have the udev-rule on my computer, 'cause freedesktop.org don't fix this feature:
#/etc/udev/rules.d/99-casio.rules
# UDEV erkennt CASIO Kamera als "generic", nicht als "disk" :-(
ENV{ID_SERIAL}=="CASIO_COMPUTER_CASIO_QV_DIGITAL", ENV{ID_TYPE}="disk", ENV{UDISKS_AUTO}="1", ENV{UDISKS_SYSTEM}="0", ENV{UDISKS_SYSTEM_INTERNAL}="0"
ENV{ID_SERIAL}=="TANDBERG_RDX_TANDBERGRD6520236564-0:0", ENV{ID_TYPE}="disk", ENV{UDISKS_AUTO}="1", ENV{UDISKS_SYSTEM}="0", ENV{UDISKS_SYSTEM_INTERNAL}="0"
... looks I had the same problem on my Tandberg, as well ...
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: trinity-users-help@xxxxxxxxxxxxxxxxxxxxxxxxxx
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
