Re: [trinity-users] Re: Re: Unable to mount this device error when using usb stick but not always
Hi Guys,
On Wednesday 05 December 2018 23:35:57 deloptes wrote:
Kate Draven wrote:
I do have several computers in me wee lab. The sticks are all fine, mount and umount on all other computers, including another pclos 64 with the same kernels. At first I thought it was a kernel bug, wrong.
I can only guess I'm installing something that messes it up.
I reinstalled the OS into the test computer and incrementally installing packages until I find the culprit.
mounting was udev job - no ? or at least to notify the system that there is something attached to it and what exactly it is.
Probably nothing to do with this problem, but anyway:
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. Doing a hard reboot seems to clear what ever causes this. Simply logging out and logging back in doesn't seem to work.
On Sat, 8 Dec 2018 20:23:13 +0000 Baron baron@linuxmaniac.net wrote:
Hi Guys,
On Wednesday 05 December 2018 23:35:57 deloptes wrote:
Kate Draven wrote:
I do have several computers in me wee lab. The sticks are all fine, mount and umount on all other computers, including another pclos 64 with the same kernels. At first I thought it was a kernel bug, wrong.
I can only guess I'm installing something that messes it up.
I reinstalled the OS into the test computer and incrementally installing packages until I find the culprit.
mounting was udev job - no ? or at least to notify the system that there is something attached to it and what exactly it is.
Probably nothing to do with this problem, but anyway:
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. Doing a hard reboot seems to clear what ever causes this. Simply logging out and logging back in doesn't seem to work.
Stupid question: Are you plugging these into the same port every time, or ports connected to the same headers on the motherboard? Loose connectors / flaky hardware can cause all sorts of weird symptoms. I've never seen this one in particular, but my sample size is small.
E. Liddell
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.
said Dan Youngquist: | 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.
yup. i have no idea what "safely remove" is for.
dep wrote:
yup. i have no idea what "safely remove" is for.
It is for what it stays - remove. It does unmount and detach - you can remove the device safely after this operation. If you do not intend to unplug the device, then use unmount option.
regards
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.
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?
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 ?
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 ?
Well, that's interesting. Can you mount /dev/sdb1 manually?
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
Dr. Nikolaus Klepp wrote:
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
The world is getting crazy. Last time I checked something related I found out, there is now MTP and PTP - media and picture transfer protocols. Some newer cameras (see post from 2006 [1] do this as well and you have to tell it in which mode it should present itself when attached via usb.
On our new camera I configured few years ago mass storage and never bothered, but recently I had to learn that there is something I was not aware of for many years :) Modern mobile phones are even worse as they incorporate many devices and you have only 1 usb plug on it :)
Am Dienstag, 11. Dezember 2018 schrieb deloptes:
Dr. Nikolaus Klepp wrote:
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
The world is getting crazy. Last time I checked something related I found out, there is now MTP and PTP - media and picture transfer protocols. Some newer cameras (see post from 2006 [1] do this as well and you have to tell it in which mode it should present itself when attached via usb.
On our new camera I configured few years ago mass storage and never bothered, but recently I had to learn that there is something I was not aware of for many years :) Modern mobile phones are even worse as they incorporate many devices and you have only 1 usb plug on it :)
If you are a "luck" person and you run Windooz10, then you find that this multi gadget protocol is broken since ~ 1 year ... hail progress!
At least on *nix you can fix stuff like this, even when redhat tries hard to break it.
[1] https://bbs.archlinux.org/viewtopic.php?id=19825
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net 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
Dr. Nikolaus Klepp wrote:
If you are a "luck" person and you run Windooz10, then you find that this multi gadget protocol is broken since ~ 1 year ... hail progress!
don't know why corp is doing windows - I think it is pure burning of money ... I got one v10 few months ago and it is still laying on my desk unused. But I have no idea how this is working with cameras there. The corp is paying for it to stay there on the desk and do some work. It is doing it more or less good on its own. I alaways have to repeat myself what Linuz Torvald said about it - something like a very good company, but the problem is they make crappy software. So ... times go by and some things never change - amazing.
At least on *nix you can fix stuff like this, even when redhat tries hard to break it.
Well for the Windows, you have the windows admin - a person that should be admired for the skill to support "crappy software" :) and keep the universe in balance :) Honestly ... no idea how those guys have the patience. I had to factory restore one PC lately for a friend, because it got unusable after 6y of use ... I think it took 8h or more to install all the updates or at least to try to ... with numerous reboots in between. I have not done this for years and it was impressive experience. In the mean time I could do a lot of work on the linux PC that was installed 15y ago. Amazing!
regards
Am Dienstag, 11. Dezember 2018 schrieb deloptes:
Dr. Nikolaus Klepp wrote:
If you are a "luck" person and you run Windooz10, then you find that this multi gadget protocol is broken since ~ 1 year ... hail progress!
don't know why corp is doing windows - I think it is pure burning of money ... I got one v10 few months ago and it is still laying on my desk unused. But I have no idea how this is working with cameras there. The corp is paying for it to stay there on the desk and do some work. It is doing it more or less good on its own. I alaways have to repeat myself what Linuz Torvald said about it - something like a very good company, but the problem is they make crappy software. So ... times go by and some things never change - amazing.
"From history we learn that we learn nothing from history" ... was the favorit saying of my history teacher back at school.
On Wednesday 12 December 2018, Dr. Nikolaus Klepp wrote:
Am Dienstag, 11. Dezember 2018 schrieb deloptes:
Dr. Nikolaus Klepp wrote:
If you are a "luck" person and you run Windooz10, then you find that this multi gadget protocol is broken since ~ 1 year ... hail progress!
don't know why corp is doing windows - I think it is pure burning of money ... I got one v10 few months ago and it is still laying on my desk unused. But I have no idea how this is working with cameras there. The corp is paying for it to stay there on the desk and do some work. It is doing it more or less good on its own. I alaways have to repeat myself what Linuz Torvald said about it - something like a very good company, but the problem is they make crappy software. So ... times go by and some things never change - amazing.
"From history we learn that we learn nothing from history" ... was the favorit saying of my history teacher back at school.
And now one of my favs as well.
Cheers Doc,
Kate
Am Mittwoch, 12. Dezember 2018 schrieb Kate Draven:
On Wednesday 12 December 2018, Dr. Nikolaus Klepp wrote:
Am Dienstag, 11. Dezember 2018 schrieb deloptes:
Dr. Nikolaus Klepp wrote:
If you are a "luck" person and you run Windooz10, then you find that this multi gadget protocol is broken since ~ 1 year ... hail progress!
don't know why corp is doing windows - I think it is pure burning of money ... I got one v10 few months ago and it is still laying on my desk unused. But I have no idea how this is working with cameras there. The corp is paying for it to stay there on the desk and do some work. It is doing it more or less good on its own. I alaways have to repeat myself what Linuz Torvald said about it - something like a very good company, but the problem is they make crappy software. So ... times go by and some things never change - amazing.
"From history we learn that we learn nothing from history" ... was the favorit saying of my history teacher back at school.
And now one of my favs as well.
Cheers Doc,
Kate
Just to show what happens when somebody remembers history: Thutmose III took Megiddo at about 1479 BC by executing an "impossible" plan (3 ways lead to the city, 2 are suitable for an army, one is impossible for an army to take, but it leads just to the city gates. Sure as hell that's the way he went with his army). September 1918 General Edmund Allenby executed the very plan of Thutmose III and took the city again ... he found the tactics in a history book :-)
On Wednesday 12 December 2018 01:55:53 Dr. Nikolaus Klepp wrote:
Am Dienstag, 11. Dezember 2018 schrieb deloptes:
Dr. Nikolaus Klepp wrote:
If you are a "luck" person and you run Windooz10, then you find that this multi gadget protocol is broken since ~ 1 year ... hail progress!
don't know why corp is doing windows - I think it is pure burning of money ... I got one v10 few months ago and it is still laying on my desk unused.
Corporate has been to MDA school, and the first two things they teach is how to break the law w/o getting caught, and always have somebody to sue if things don't work. Never ever admit the failure was yours to own.
But I have no idea how this is working with cameras there. The corp is paying for it to stay there on the desk and do some work. It is doing it more or less good on its own. I alaways have to repeat myself what Linuz Torvald said about it - something like a very good company, but the problem is they make crappy software. So ... times go by and some things never change - amazing.
"From history we learn that we learn nothing from history" ... was the favorit saying of my history teacher back at school.
I'd observe that he was smarter by far than the average bear. Applying the cold light of day to both his own studies, and to his students. The best kind of teacher, and we need lots more like that teaching STEM!
Good Morning Nik,
On Monday 10 December 2018 21:23:02 Dr. Nikolaus Klepp wrote:
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
Somehow I don't think that this quite applies to my case, since the USB adaptor has been recognised by all my machines recently. This issue arose because I wanted to be selective in transferring data from my old AMD desktop machine to my new HP 8300 one.
Thanks for this anyway because it might help with another old problem in a similar vein.
-
Baron -
Dan Youngquist -
deloptes -
dep -
Dr. Nikolaus Klepp -
E. Liddell -
Gene Heskett -
Kate Draven