USB stick isn't recognized correctly by Linux Mint

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
4
down vote

favorite
1












I've got a usb stick which isn't recognized correctly by my system (Linux Mint 18, kernel version 4.4.0-34-generic). With lsusb the device is shown (it's the Kingston Technology DataTraveler G4):



Bus 002 Device 003: ID 062a:4102 Creative Labs 
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 04f2:b217 Chicony Electronics Co., Ltd Lenovo Integrated Camera (0.3MP)
Bus 001 Device 035: ID 0951:1666 Kingston Technology DataTraveler G4
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


But sudo fdisk -l doesn't show my device. This is why I can't get a UUID or something like /dev/sdb1, so I can't mount or format my thumb drive. Now I'm searching for ideas to make the thumb drive working properly again.



I plugged the thumb drive into a USB 2 port as I haven't got a USB 3 port. The thumb drive is connected directly with my laptop and it's the only device which is connected. I often tried disconnecting and reconnecting the thumb drive, but nothing happened.



Gparted doesn't recognize the usb stick. There is no driver related to "Kingston" in the driver manager.



This is the output of dmesg: http://pastebin.com/NR21FEWC



fdisk /dev/sg2 gives me this output:



Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

fdisk: cannot open /dev/sg2: No such file or directory


ls /dev/sd* gives me this output:



/dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4


lsblk shows:



NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465,8G 0 disk
├─sda1 8:1 0 1G 0 part /boot
├─sda2 8:2 0 20G 0 part
│ └─root 252:0 0 20G 0 crypt /
├─sda3 8:3 0 10G 0 part
│ └─swap 252:1 0 10G 0 crypt [SWAP]
└─sda4 8:4 0 434,8G 0 part
└─home 252:2 0 434,8G 0 crypt /home
sr0 11:0 1 1024M 0 rom


/sbin/blkid shows:



/dev/mapper/root: UUID="007efd79-966b-43bd-a5c5-d67f5d987624" TYPE="ext4"
/dev/mapper/swap: UUID="b4960aab-6cbb-4c46-b74d-ee4fa56d01fd" TYPE="swap"
/dev/sda1: LABEL="BOOT" UUID="128f7dc5-1961-457b-90ca-421fc7eb481f" TYPE="ext2" PARTUUID="1138e37e-01"
/dev/sda2: UUID="d68911dd-172a-4608-86d4-084eb72f409c" TYPE="crypto_LUKS" PARTUUID="1138e37e-02"
/dev/sda3: UUID="4800307a-714c-4aca-b5d1-6b9ccf8b467c" TYPE="crypto_LUKS" PARTUUID="1138e37e-03"
/dev/sda4: UUID="db432f20-3889-44c2-8e67-7271634788be" TYPE="crypto_LUKS" PARTUUID="1138e37e-04"


tree /sys/bus/hid shows:



/sys/bus/hid
├── devices
│   └── 0003:062A:4102.0001 -> ../../../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/0003:062A:4102.0001
├── drivers
│   └── hid-generic
│   ├── 0003:062A:4102.0001 -> ../../../../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/0003:062A:4102.0001
│   ├── bind
│   ├── module -> ../../../../module/hid_generic
│   ├── new_id
│   ├── uevent
│   └── unbind
├── drivers_autoprobe
├── drivers_probe
└── uevent

6 directories, 7 files


This is the output of /sbin/udevadm monitor --property > thumbdrive.txt: http://pastebin.com/4SpYin45
or
http://paste.debian.net/790206/










share|improve this question



















  • 1




    Looks like a common problem with this device; eg ubuntuforums.org/showthread.php?t=2262490 or github.com/genodelabs/genode/issues/1664 - if you google for 0951:1666 then you'll see lots of commentary.
    – Stephen Harris
    Aug 13 '16 at 17:26










  • But in contrast to that case (https://ubuntuforums.org/showthread.php?t=2262490), my thumb drive isn't recognized in windows as well.
    – Earl Nick
    Aug 13 '16 at 17:53















up vote
4
down vote

favorite
1












I've got a usb stick which isn't recognized correctly by my system (Linux Mint 18, kernel version 4.4.0-34-generic). With lsusb the device is shown (it's the Kingston Technology DataTraveler G4):



Bus 002 Device 003: ID 062a:4102 Creative Labs 
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 04f2:b217 Chicony Electronics Co., Ltd Lenovo Integrated Camera (0.3MP)
Bus 001 Device 035: ID 0951:1666 Kingston Technology DataTraveler G4
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


But sudo fdisk -l doesn't show my device. This is why I can't get a UUID or something like /dev/sdb1, so I can't mount or format my thumb drive. Now I'm searching for ideas to make the thumb drive working properly again.



I plugged the thumb drive into a USB 2 port as I haven't got a USB 3 port. The thumb drive is connected directly with my laptop and it's the only device which is connected. I often tried disconnecting and reconnecting the thumb drive, but nothing happened.



Gparted doesn't recognize the usb stick. There is no driver related to "Kingston" in the driver manager.



This is the output of dmesg: http://pastebin.com/NR21FEWC



fdisk /dev/sg2 gives me this output:



Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

fdisk: cannot open /dev/sg2: No such file or directory


ls /dev/sd* gives me this output:



/dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4


lsblk shows:



NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465,8G 0 disk
├─sda1 8:1 0 1G 0 part /boot
├─sda2 8:2 0 20G 0 part
│ └─root 252:0 0 20G 0 crypt /
├─sda3 8:3 0 10G 0 part
│ └─swap 252:1 0 10G 0 crypt [SWAP]
└─sda4 8:4 0 434,8G 0 part
└─home 252:2 0 434,8G 0 crypt /home
sr0 11:0 1 1024M 0 rom


/sbin/blkid shows:



/dev/mapper/root: UUID="007efd79-966b-43bd-a5c5-d67f5d987624" TYPE="ext4"
/dev/mapper/swap: UUID="b4960aab-6cbb-4c46-b74d-ee4fa56d01fd" TYPE="swap"
/dev/sda1: LABEL="BOOT" UUID="128f7dc5-1961-457b-90ca-421fc7eb481f" TYPE="ext2" PARTUUID="1138e37e-01"
/dev/sda2: UUID="d68911dd-172a-4608-86d4-084eb72f409c" TYPE="crypto_LUKS" PARTUUID="1138e37e-02"
/dev/sda3: UUID="4800307a-714c-4aca-b5d1-6b9ccf8b467c" TYPE="crypto_LUKS" PARTUUID="1138e37e-03"
/dev/sda4: UUID="db432f20-3889-44c2-8e67-7271634788be" TYPE="crypto_LUKS" PARTUUID="1138e37e-04"


tree /sys/bus/hid shows:



/sys/bus/hid
├── devices
│   └── 0003:062A:4102.0001 -> ../../../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/0003:062A:4102.0001
├── drivers
│   └── hid-generic
│   ├── 0003:062A:4102.0001 -> ../../../../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/0003:062A:4102.0001
│   ├── bind
│   ├── module -> ../../../../module/hid_generic
│   ├── new_id
│   ├── uevent
│   └── unbind
├── drivers_autoprobe
├── drivers_probe
└── uevent

6 directories, 7 files


This is the output of /sbin/udevadm monitor --property > thumbdrive.txt: http://pastebin.com/4SpYin45
or
http://paste.debian.net/790206/










share|improve this question



















  • 1




    Looks like a common problem with this device; eg ubuntuforums.org/showthread.php?t=2262490 or github.com/genodelabs/genode/issues/1664 - if you google for 0951:1666 then you'll see lots of commentary.
    – Stephen Harris
    Aug 13 '16 at 17:26










  • But in contrast to that case (https://ubuntuforums.org/showthread.php?t=2262490), my thumb drive isn't recognized in windows as well.
    – Earl Nick
    Aug 13 '16 at 17:53













up vote
4
down vote

favorite
1









up vote
4
down vote

favorite
1






1





I've got a usb stick which isn't recognized correctly by my system (Linux Mint 18, kernel version 4.4.0-34-generic). With lsusb the device is shown (it's the Kingston Technology DataTraveler G4):



Bus 002 Device 003: ID 062a:4102 Creative Labs 
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 04f2:b217 Chicony Electronics Co., Ltd Lenovo Integrated Camera (0.3MP)
Bus 001 Device 035: ID 0951:1666 Kingston Technology DataTraveler G4
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


But sudo fdisk -l doesn't show my device. This is why I can't get a UUID or something like /dev/sdb1, so I can't mount or format my thumb drive. Now I'm searching for ideas to make the thumb drive working properly again.



I plugged the thumb drive into a USB 2 port as I haven't got a USB 3 port. The thumb drive is connected directly with my laptop and it's the only device which is connected. I often tried disconnecting and reconnecting the thumb drive, but nothing happened.



Gparted doesn't recognize the usb stick. There is no driver related to "Kingston" in the driver manager.



This is the output of dmesg: http://pastebin.com/NR21FEWC



fdisk /dev/sg2 gives me this output:



Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

fdisk: cannot open /dev/sg2: No such file or directory


ls /dev/sd* gives me this output:



/dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4


lsblk shows:



NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465,8G 0 disk
├─sda1 8:1 0 1G 0 part /boot
├─sda2 8:2 0 20G 0 part
│ └─root 252:0 0 20G 0 crypt /
├─sda3 8:3 0 10G 0 part
│ └─swap 252:1 0 10G 0 crypt [SWAP]
└─sda4 8:4 0 434,8G 0 part
└─home 252:2 0 434,8G 0 crypt /home
sr0 11:0 1 1024M 0 rom


/sbin/blkid shows:



/dev/mapper/root: UUID="007efd79-966b-43bd-a5c5-d67f5d987624" TYPE="ext4"
/dev/mapper/swap: UUID="b4960aab-6cbb-4c46-b74d-ee4fa56d01fd" TYPE="swap"
/dev/sda1: LABEL="BOOT" UUID="128f7dc5-1961-457b-90ca-421fc7eb481f" TYPE="ext2" PARTUUID="1138e37e-01"
/dev/sda2: UUID="d68911dd-172a-4608-86d4-084eb72f409c" TYPE="crypto_LUKS" PARTUUID="1138e37e-02"
/dev/sda3: UUID="4800307a-714c-4aca-b5d1-6b9ccf8b467c" TYPE="crypto_LUKS" PARTUUID="1138e37e-03"
/dev/sda4: UUID="db432f20-3889-44c2-8e67-7271634788be" TYPE="crypto_LUKS" PARTUUID="1138e37e-04"


tree /sys/bus/hid shows:



/sys/bus/hid
├── devices
│   └── 0003:062A:4102.0001 -> ../../../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/0003:062A:4102.0001
├── drivers
│   └── hid-generic
│   ├── 0003:062A:4102.0001 -> ../../../../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/0003:062A:4102.0001
│   ├── bind
│   ├── module -> ../../../../module/hid_generic
│   ├── new_id
│   ├── uevent
│   └── unbind
├── drivers_autoprobe
├── drivers_probe
└── uevent

6 directories, 7 files


This is the output of /sbin/udevadm monitor --property > thumbdrive.txt: http://pastebin.com/4SpYin45
or
http://paste.debian.net/790206/










share|improve this question















I've got a usb stick which isn't recognized correctly by my system (Linux Mint 18, kernel version 4.4.0-34-generic). With lsusb the device is shown (it's the Kingston Technology DataTraveler G4):



Bus 002 Device 003: ID 062a:4102 Creative Labs 
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 04f2:b217 Chicony Electronics Co., Ltd Lenovo Integrated Camera (0.3MP)
Bus 001 Device 035: ID 0951:1666 Kingston Technology DataTraveler G4
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


But sudo fdisk -l doesn't show my device. This is why I can't get a UUID or something like /dev/sdb1, so I can't mount or format my thumb drive. Now I'm searching for ideas to make the thumb drive working properly again.



I plugged the thumb drive into a USB 2 port as I haven't got a USB 3 port. The thumb drive is connected directly with my laptop and it's the only device which is connected. I often tried disconnecting and reconnecting the thumb drive, but nothing happened.



Gparted doesn't recognize the usb stick. There is no driver related to "Kingston" in the driver manager.



This is the output of dmesg: http://pastebin.com/NR21FEWC



fdisk /dev/sg2 gives me this output:



Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

fdisk: cannot open /dev/sg2: No such file or directory


ls /dev/sd* gives me this output:



/dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4


lsblk shows:



NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465,8G 0 disk
├─sda1 8:1 0 1G 0 part /boot
├─sda2 8:2 0 20G 0 part
│ └─root 252:0 0 20G 0 crypt /
├─sda3 8:3 0 10G 0 part
│ └─swap 252:1 0 10G 0 crypt [SWAP]
└─sda4 8:4 0 434,8G 0 part
└─home 252:2 0 434,8G 0 crypt /home
sr0 11:0 1 1024M 0 rom


/sbin/blkid shows:



/dev/mapper/root: UUID="007efd79-966b-43bd-a5c5-d67f5d987624" TYPE="ext4"
/dev/mapper/swap: UUID="b4960aab-6cbb-4c46-b74d-ee4fa56d01fd" TYPE="swap"
/dev/sda1: LABEL="BOOT" UUID="128f7dc5-1961-457b-90ca-421fc7eb481f" TYPE="ext2" PARTUUID="1138e37e-01"
/dev/sda2: UUID="d68911dd-172a-4608-86d4-084eb72f409c" TYPE="crypto_LUKS" PARTUUID="1138e37e-02"
/dev/sda3: UUID="4800307a-714c-4aca-b5d1-6b9ccf8b467c" TYPE="crypto_LUKS" PARTUUID="1138e37e-03"
/dev/sda4: UUID="db432f20-3889-44c2-8e67-7271634788be" TYPE="crypto_LUKS" PARTUUID="1138e37e-04"


tree /sys/bus/hid shows:



/sys/bus/hid
├── devices
│   └── 0003:062A:4102.0001 -> ../../../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/0003:062A:4102.0001
├── drivers
│   └── hid-generic
│   ├── 0003:062A:4102.0001 -> ../../../../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/0003:062A:4102.0001
│   ├── bind
│   ├── module -> ../../../../module/hid_generic
│   ├── new_id
│   ├── uevent
│   └── unbind
├── drivers_autoprobe
├── drivers_probe
└── uevent

6 directories, 7 files


This is the output of /sbin/udevadm monitor --property > thumbdrive.txt: http://pastebin.com/4SpYin45
or
http://paste.debian.net/790206/







usb-drive fdisk lsusb






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 18 '16 at 8:44

























asked Aug 13 '16 at 15:24









Earl Nick

2114




2114







  • 1




    Looks like a common problem with this device; eg ubuntuforums.org/showthread.php?t=2262490 or github.com/genodelabs/genode/issues/1664 - if you google for 0951:1666 then you'll see lots of commentary.
    – Stephen Harris
    Aug 13 '16 at 17:26










  • But in contrast to that case (https://ubuntuforums.org/showthread.php?t=2262490), my thumb drive isn't recognized in windows as well.
    – Earl Nick
    Aug 13 '16 at 17:53













  • 1




    Looks like a common problem with this device; eg ubuntuforums.org/showthread.php?t=2262490 or github.com/genodelabs/genode/issues/1664 - if you google for 0951:1666 then you'll see lots of commentary.
    – Stephen Harris
    Aug 13 '16 at 17:26










  • But in contrast to that case (https://ubuntuforums.org/showthread.php?t=2262490), my thumb drive isn't recognized in windows as well.
    – Earl Nick
    Aug 13 '16 at 17:53








1




1




Looks like a common problem with this device; eg ubuntuforums.org/showthread.php?t=2262490 or github.com/genodelabs/genode/issues/1664 - if you google for 0951:1666 then you'll see lots of commentary.
– Stephen Harris
Aug 13 '16 at 17:26




Looks like a common problem with this device; eg ubuntuforums.org/showthread.php?t=2262490 or github.com/genodelabs/genode/issues/1664 - if you google for 0951:1666 then you'll see lots of commentary.
– Stephen Harris
Aug 13 '16 at 17:26












But in contrast to that case (https://ubuntuforums.org/showthread.php?t=2262490), my thumb drive isn't recognized in windows as well.
– Earl Nick
Aug 13 '16 at 17:53





But in contrast to that case (https://ubuntuforums.org/showthread.php?t=2262490), my thumb drive isn't recognized in windows as well.
– Earl Nick
Aug 13 '16 at 17:53











2 Answers
2






active

oldest

votes

















up vote
1
down vote













Try creating a UDEV rule under /etc/udev/rules.d/



So create a rules file /etc/udev/rules.d/test.rules then add this in there:



ACTION=="add", ATTRSidVendor=="0951", ATTRSidProduct=="1666", SYMLINK+="Earls-Kingston-Thumbdrive"


Restart UDEV by running sudo /etc/init.d/udev restart



Remove and plug in the thumb drive and now you should have UDEV detect and create a symlink under /dev/Earls-Kingston-Thumbdrive






share|improve this answer




















  • I tried this now. After plugging in the thumb drive, there is a symlink, but it's pointing only to an empty file named something like /dev/bsg/12:0:0:0 or /dev/bsg/15:0:0:0. This filename is changing every time I remove and reinsert the usb stick.
    – Earl Nick
    Aug 13 '16 at 19:27










  • Earl, please run lsmod | grep -i usb_storage in a terminal. if you see the usb_storage module is not loaded unplug the thumb drive then run sudo /sbin/modprobe usb_storage plug back the thumbdrive then re-check using fidsk -l
    – Aruna Hewapathirane
    Aug 14 '16 at 2:02











  • running lsmod | grep -i usb_storage gives me usb_storage 69632 1 uas. Does this mean that it's loaded or not? Btw: sometimes the symlink /dev/Earls-Kingston-Thumbdrive is also pointing to /dev/sg2
    – Earl Nick
    Aug 14 '16 at 7:59










  • It means the usb_storage module IS loaded but no harm in running modprobe usb_storage to make sure any dependencies are loaded. Your dmesg last line [ 4961.591664] sd 9:0:0:0: Attached scsi generic sg2 type 0 tells us the thumb drive was attached as sg2 so /dev/sg2 is good. Does fdisk -l detect sg2 when this happens ? Since dmesg identifies the drive we can rule out any hardware defects but the firmware may be defective ? Plug your drive into a friends PC or laptop to see if the problem persists ? The MBR may also be damaged and can be replaced with dd but that is very last option.
    – Aruna Hewapathirane
    Aug 14 '16 at 13:50










  • No, fdisk -l does not detect sg2. I already plugged the drive into two different Windows 10 machines and into a Raspberry Pi running Raspbian, but none of the systems recognized the usb stick.
    – Earl Nick
    Aug 15 '16 at 7:52

















up vote
0
down vote













i had an exact problem with my Garmin Nuvi 1100 Gps. The computer used to reconice the device. But i made a big mistake i formatted because i was distracted in a conversation (dam !). What can i do in my linux mint 18.2 to reconize the device again ? please help.






share|improve this answer








New contributor




user319500 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

















    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f303206%2fusb-stick-isnt-recognized-correctly-by-linux-mint%23new-answer', 'question_page');

    );

    Post as a guest






























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    1
    down vote













    Try creating a UDEV rule under /etc/udev/rules.d/



    So create a rules file /etc/udev/rules.d/test.rules then add this in there:



    ACTION=="add", ATTRSidVendor=="0951", ATTRSidProduct=="1666", SYMLINK+="Earls-Kingston-Thumbdrive"


    Restart UDEV by running sudo /etc/init.d/udev restart



    Remove and plug in the thumb drive and now you should have UDEV detect and create a symlink under /dev/Earls-Kingston-Thumbdrive






    share|improve this answer




















    • I tried this now. After plugging in the thumb drive, there is a symlink, but it's pointing only to an empty file named something like /dev/bsg/12:0:0:0 or /dev/bsg/15:0:0:0. This filename is changing every time I remove and reinsert the usb stick.
      – Earl Nick
      Aug 13 '16 at 19:27










    • Earl, please run lsmod | grep -i usb_storage in a terminal. if you see the usb_storage module is not loaded unplug the thumb drive then run sudo /sbin/modprobe usb_storage plug back the thumbdrive then re-check using fidsk -l
      – Aruna Hewapathirane
      Aug 14 '16 at 2:02











    • running lsmod | grep -i usb_storage gives me usb_storage 69632 1 uas. Does this mean that it's loaded or not? Btw: sometimes the symlink /dev/Earls-Kingston-Thumbdrive is also pointing to /dev/sg2
      – Earl Nick
      Aug 14 '16 at 7:59










    • It means the usb_storage module IS loaded but no harm in running modprobe usb_storage to make sure any dependencies are loaded. Your dmesg last line [ 4961.591664] sd 9:0:0:0: Attached scsi generic sg2 type 0 tells us the thumb drive was attached as sg2 so /dev/sg2 is good. Does fdisk -l detect sg2 when this happens ? Since dmesg identifies the drive we can rule out any hardware defects but the firmware may be defective ? Plug your drive into a friends PC or laptop to see if the problem persists ? The MBR may also be damaged and can be replaced with dd but that is very last option.
      – Aruna Hewapathirane
      Aug 14 '16 at 13:50










    • No, fdisk -l does not detect sg2. I already plugged the drive into two different Windows 10 machines and into a Raspberry Pi running Raspbian, but none of the systems recognized the usb stick.
      – Earl Nick
      Aug 15 '16 at 7:52














    up vote
    1
    down vote













    Try creating a UDEV rule under /etc/udev/rules.d/



    So create a rules file /etc/udev/rules.d/test.rules then add this in there:



    ACTION=="add", ATTRSidVendor=="0951", ATTRSidProduct=="1666", SYMLINK+="Earls-Kingston-Thumbdrive"


    Restart UDEV by running sudo /etc/init.d/udev restart



    Remove and plug in the thumb drive and now you should have UDEV detect and create a symlink under /dev/Earls-Kingston-Thumbdrive






    share|improve this answer




















    • I tried this now. After plugging in the thumb drive, there is a symlink, but it's pointing only to an empty file named something like /dev/bsg/12:0:0:0 or /dev/bsg/15:0:0:0. This filename is changing every time I remove and reinsert the usb stick.
      – Earl Nick
      Aug 13 '16 at 19:27










    • Earl, please run lsmod | grep -i usb_storage in a terminal. if you see the usb_storage module is not loaded unplug the thumb drive then run sudo /sbin/modprobe usb_storage plug back the thumbdrive then re-check using fidsk -l
      – Aruna Hewapathirane
      Aug 14 '16 at 2:02











    • running lsmod | grep -i usb_storage gives me usb_storage 69632 1 uas. Does this mean that it's loaded or not? Btw: sometimes the symlink /dev/Earls-Kingston-Thumbdrive is also pointing to /dev/sg2
      – Earl Nick
      Aug 14 '16 at 7:59










    • It means the usb_storage module IS loaded but no harm in running modprobe usb_storage to make sure any dependencies are loaded. Your dmesg last line [ 4961.591664] sd 9:0:0:0: Attached scsi generic sg2 type 0 tells us the thumb drive was attached as sg2 so /dev/sg2 is good. Does fdisk -l detect sg2 when this happens ? Since dmesg identifies the drive we can rule out any hardware defects but the firmware may be defective ? Plug your drive into a friends PC or laptop to see if the problem persists ? The MBR may also be damaged and can be replaced with dd but that is very last option.
      – Aruna Hewapathirane
      Aug 14 '16 at 13:50










    • No, fdisk -l does not detect sg2. I already plugged the drive into two different Windows 10 machines and into a Raspberry Pi running Raspbian, but none of the systems recognized the usb stick.
      – Earl Nick
      Aug 15 '16 at 7:52












    up vote
    1
    down vote










    up vote
    1
    down vote









    Try creating a UDEV rule under /etc/udev/rules.d/



    So create a rules file /etc/udev/rules.d/test.rules then add this in there:



    ACTION=="add", ATTRSidVendor=="0951", ATTRSidProduct=="1666", SYMLINK+="Earls-Kingston-Thumbdrive"


    Restart UDEV by running sudo /etc/init.d/udev restart



    Remove and plug in the thumb drive and now you should have UDEV detect and create a symlink under /dev/Earls-Kingston-Thumbdrive






    share|improve this answer












    Try creating a UDEV rule under /etc/udev/rules.d/



    So create a rules file /etc/udev/rules.d/test.rules then add this in there:



    ACTION=="add", ATTRSidVendor=="0951", ATTRSidProduct=="1666", SYMLINK+="Earls-Kingston-Thumbdrive"


    Restart UDEV by running sudo /etc/init.d/udev restart



    Remove and plug in the thumb drive and now you should have UDEV detect and create a symlink under /dev/Earls-Kingston-Thumbdrive







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Aug 13 '16 at 18:28









    Aruna Hewapathirane

    46128




    46128











    • I tried this now. After plugging in the thumb drive, there is a symlink, but it's pointing only to an empty file named something like /dev/bsg/12:0:0:0 or /dev/bsg/15:0:0:0. This filename is changing every time I remove and reinsert the usb stick.
      – Earl Nick
      Aug 13 '16 at 19:27










    • Earl, please run lsmod | grep -i usb_storage in a terminal. if you see the usb_storage module is not loaded unplug the thumb drive then run sudo /sbin/modprobe usb_storage plug back the thumbdrive then re-check using fidsk -l
      – Aruna Hewapathirane
      Aug 14 '16 at 2:02











    • running lsmod | grep -i usb_storage gives me usb_storage 69632 1 uas. Does this mean that it's loaded or not? Btw: sometimes the symlink /dev/Earls-Kingston-Thumbdrive is also pointing to /dev/sg2
      – Earl Nick
      Aug 14 '16 at 7:59










    • It means the usb_storage module IS loaded but no harm in running modprobe usb_storage to make sure any dependencies are loaded. Your dmesg last line [ 4961.591664] sd 9:0:0:0: Attached scsi generic sg2 type 0 tells us the thumb drive was attached as sg2 so /dev/sg2 is good. Does fdisk -l detect sg2 when this happens ? Since dmesg identifies the drive we can rule out any hardware defects but the firmware may be defective ? Plug your drive into a friends PC or laptop to see if the problem persists ? The MBR may also be damaged and can be replaced with dd but that is very last option.
      – Aruna Hewapathirane
      Aug 14 '16 at 13:50










    • No, fdisk -l does not detect sg2. I already plugged the drive into two different Windows 10 machines and into a Raspberry Pi running Raspbian, but none of the systems recognized the usb stick.
      – Earl Nick
      Aug 15 '16 at 7:52
















    • I tried this now. After plugging in the thumb drive, there is a symlink, but it's pointing only to an empty file named something like /dev/bsg/12:0:0:0 or /dev/bsg/15:0:0:0. This filename is changing every time I remove and reinsert the usb stick.
      – Earl Nick
      Aug 13 '16 at 19:27










    • Earl, please run lsmod | grep -i usb_storage in a terminal. if you see the usb_storage module is not loaded unplug the thumb drive then run sudo /sbin/modprobe usb_storage plug back the thumbdrive then re-check using fidsk -l
      – Aruna Hewapathirane
      Aug 14 '16 at 2:02











    • running lsmod | grep -i usb_storage gives me usb_storage 69632 1 uas. Does this mean that it's loaded or not? Btw: sometimes the symlink /dev/Earls-Kingston-Thumbdrive is also pointing to /dev/sg2
      – Earl Nick
      Aug 14 '16 at 7:59










    • It means the usb_storage module IS loaded but no harm in running modprobe usb_storage to make sure any dependencies are loaded. Your dmesg last line [ 4961.591664] sd 9:0:0:0: Attached scsi generic sg2 type 0 tells us the thumb drive was attached as sg2 so /dev/sg2 is good. Does fdisk -l detect sg2 when this happens ? Since dmesg identifies the drive we can rule out any hardware defects but the firmware may be defective ? Plug your drive into a friends PC or laptop to see if the problem persists ? The MBR may also be damaged and can be replaced with dd but that is very last option.
      – Aruna Hewapathirane
      Aug 14 '16 at 13:50










    • No, fdisk -l does not detect sg2. I already plugged the drive into two different Windows 10 machines and into a Raspberry Pi running Raspbian, but none of the systems recognized the usb stick.
      – Earl Nick
      Aug 15 '16 at 7:52















    I tried this now. After plugging in the thumb drive, there is a symlink, but it's pointing only to an empty file named something like /dev/bsg/12:0:0:0 or /dev/bsg/15:0:0:0. This filename is changing every time I remove and reinsert the usb stick.
    – Earl Nick
    Aug 13 '16 at 19:27




    I tried this now. After plugging in the thumb drive, there is a symlink, but it's pointing only to an empty file named something like /dev/bsg/12:0:0:0 or /dev/bsg/15:0:0:0. This filename is changing every time I remove and reinsert the usb stick.
    – Earl Nick
    Aug 13 '16 at 19:27












    Earl, please run lsmod | grep -i usb_storage in a terminal. if you see the usb_storage module is not loaded unplug the thumb drive then run sudo /sbin/modprobe usb_storage plug back the thumbdrive then re-check using fidsk -l
    – Aruna Hewapathirane
    Aug 14 '16 at 2:02





    Earl, please run lsmod | grep -i usb_storage in a terminal. if you see the usb_storage module is not loaded unplug the thumb drive then run sudo /sbin/modprobe usb_storage plug back the thumbdrive then re-check using fidsk -l
    – Aruna Hewapathirane
    Aug 14 '16 at 2:02













    running lsmod | grep -i usb_storage gives me usb_storage 69632 1 uas. Does this mean that it's loaded or not? Btw: sometimes the symlink /dev/Earls-Kingston-Thumbdrive is also pointing to /dev/sg2
    – Earl Nick
    Aug 14 '16 at 7:59




    running lsmod | grep -i usb_storage gives me usb_storage 69632 1 uas. Does this mean that it's loaded or not? Btw: sometimes the symlink /dev/Earls-Kingston-Thumbdrive is also pointing to /dev/sg2
    – Earl Nick
    Aug 14 '16 at 7:59












    It means the usb_storage module IS loaded but no harm in running modprobe usb_storage to make sure any dependencies are loaded. Your dmesg last line [ 4961.591664] sd 9:0:0:0: Attached scsi generic sg2 type 0 tells us the thumb drive was attached as sg2 so /dev/sg2 is good. Does fdisk -l detect sg2 when this happens ? Since dmesg identifies the drive we can rule out any hardware defects but the firmware may be defective ? Plug your drive into a friends PC or laptop to see if the problem persists ? The MBR may also be damaged and can be replaced with dd but that is very last option.
    – Aruna Hewapathirane
    Aug 14 '16 at 13:50




    It means the usb_storage module IS loaded but no harm in running modprobe usb_storage to make sure any dependencies are loaded. Your dmesg last line [ 4961.591664] sd 9:0:0:0: Attached scsi generic sg2 type 0 tells us the thumb drive was attached as sg2 so /dev/sg2 is good. Does fdisk -l detect sg2 when this happens ? Since dmesg identifies the drive we can rule out any hardware defects but the firmware may be defective ? Plug your drive into a friends PC or laptop to see if the problem persists ? The MBR may also be damaged and can be replaced with dd but that is very last option.
    – Aruna Hewapathirane
    Aug 14 '16 at 13:50












    No, fdisk -l does not detect sg2. I already plugged the drive into two different Windows 10 machines and into a Raspberry Pi running Raspbian, but none of the systems recognized the usb stick.
    – Earl Nick
    Aug 15 '16 at 7:52




    No, fdisk -l does not detect sg2. I already plugged the drive into two different Windows 10 machines and into a Raspberry Pi running Raspbian, but none of the systems recognized the usb stick.
    – Earl Nick
    Aug 15 '16 at 7:52












    up vote
    0
    down vote













    i had an exact problem with my Garmin Nuvi 1100 Gps. The computer used to reconice the device. But i made a big mistake i formatted because i was distracted in a conversation (dam !). What can i do in my linux mint 18.2 to reconize the device again ? please help.






    share|improve this answer








    New contributor




    user319500 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.





















      up vote
      0
      down vote













      i had an exact problem with my Garmin Nuvi 1100 Gps. The computer used to reconice the device. But i made a big mistake i formatted because i was distracted in a conversation (dam !). What can i do in my linux mint 18.2 to reconize the device again ? please help.






      share|improve this answer








      New contributor




      user319500 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.



















        up vote
        0
        down vote










        up vote
        0
        down vote









        i had an exact problem with my Garmin Nuvi 1100 Gps. The computer used to reconice the device. But i made a big mistake i formatted because i was distracted in a conversation (dam !). What can i do in my linux mint 18.2 to reconize the device again ? please help.






        share|improve this answer








        New contributor




        user319500 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        i had an exact problem with my Garmin Nuvi 1100 Gps. The computer used to reconice the device. But i made a big mistake i formatted because i was distracted in a conversation (dam !). What can i do in my linux mint 18.2 to reconize the device again ? please help.







        share|improve this answer








        New contributor




        user319500 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        share|improve this answer



        share|improve this answer






        New contributor




        user319500 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        answered 19 mins ago









        user319500

        11




        11




        New contributor




        user319500 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.





        New contributor





        user319500 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






        user319500 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.



























             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f303206%2fusb-stick-isnt-recognized-correctly-by-linux-mint%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Bahrain

            Postfix configuration issue with fips on centos 7; mailgun relay