Huge Problems with USB Stick (aka flash drive)

All Gurus once were Newbies
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help
Dirkoir
Level 4
Level 4
Posts: 201
Joined: Wed Jul 30, 2014 12:43 pm

Huge Problems with USB Stick (aka flash drive)

Post by Dirkoir »

Hello, Gurus:

I never had problems with USB sticks before. Not on Windows, not on a Mac, and in the years that I am now using Linux Mint on my laptop so far neither. But when I recently bought a 32 GB Intenso USB stick onto which to move files from my Linux Mint machine, the hell broke loose.


Problems:

1. Frequent kernel panic crashes when with Nemo I copy large files (several hundred MB or sometimes even over 1GB per file) onto the USB stick forcing me to move them one by one but it would still sometimes crash.

2. Several times the sudden claim that the USB stick was read-only, a problem I could overcome with "sudo chmod 777 /media/USERNAME" (with the real username, of course, and (always?) requiring either a restart or unplug-replug of the USB stick)

3. When sticking the USB stick into my TV to run the copied video files (to test them), at least one wasn't recognized and had to be copied on the USB stick again (despite exact same size, I think).

4. Last night the TV no longer recognized the USB stick, and neither did my Linux Mint laptop (at least not mounting it, although Nemo did scroll its sidebar when I plugged the USB stick in (still not listing it there, though)). I can no longer use the USB stick. :-(



Investigation:

When I run the "Disk" utility (gnome-disk-utility 3.10.0), it mentions the USB stick not just once but twice, as if there were two of them:

Code: Select all

---
32 GB Drive

Model: Intenso Alu Line (8.07)
Size: 32 GB (32,023,511,040 bytes)
Serial Number: E3BBE0E7
Volumes: No Media
---

---
32 GB Drive
/dev/sdb
Model: Intenso Alu Line (8.07)
Size: 32 GB (32,023,511,040 bytes)
Serial Number: Intenso_Alu_Line-0:0
Volumes: 32 GB Unknown
Size: 32 GB (32,023,511,040 bytes)
Device: /dev/sdb
Contents: Unknown
---

In the terminal "~ lsusb" gives me info like this regarding the USB stick (with a sometimes changing Device number): Bus 003 Device 023: ID 058f:6387 Alcor Micro Corp. Flash Drive


Here are the detailed terminal feedbacks:

Code: Select all

FIRST TRY ("Alcor Micro Corp. Flash Drive" SEEMS TO REPRESENT THE USB STICK):
~ $ lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 015: ID 04f3:0122 Elan Microelectronics Corp. 
Bus 003 Device 003: ID 0bda:b728 Realtek Semiconductor Corp. 
Bus 003 Device 022: ID 058f:6387 Alcor Micro Corp. Flash Drive
Bus 003 Device 019: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
Bus 003 Device 006: ID 04f2:b398 Chicony Electronics Co., Ltd 
Bus 003 Device 005: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint Reader
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

AFTER USB REMOVAL THE LINE WAS GONE:
 ~ $ lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 015: ID 04f3:0122 Elan Microelectronics Corp. 
Bus 003 Device 003: ID 0bda:b728 Realtek Semiconductor Corp. 
Bus 003 Device 019: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
Bus 003 Device 006: ID 04f2:b398 Chicony Electronics Co., Ltd 
Bus 003 Device 005: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint Reader
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

AFTER NEW INSERTION (Device CHANGE 022 --> 023):
 ~ $ lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 015: ID 04f3:0122 Elan Microelectronics Corp. 
Bus 003 Device 003: ID 0bda:b728 Realtek Semiconductor Corp. 
Bus 003 Device 023: ID 058f:6387 Alcor Micro Corp. Flash Drive
Bus 003 Device 019: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
Bus 003 Device 006: ID 04f2:b398 Chicony Electronics Co., Ltd 
Bus 003 Device 005: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint Reader
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 ~ $ lsusb

THE NEXT MORNING BACK FROM SUSPENSION (Device CHANGE 023 --> 024):
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 015: ID 04f3:0122 Elan Microelectronics Corp. 
Bus 003 Device 003: ID 0bda:b728 Realtek Semiconductor Corp. 
Bus 003 Device 024: ID 058f:6387 Alcor Micro Corp. Flash Drive
Bus 003 Device 019: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
Bus 003 Device 006: ID 04f2:b398 Chicony Electronics Co., Ltd 
Bus 003 Device 005: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint Reader
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


REPEATED MENTIONINGS OF INTENSO Alu Line ALCOR FROM dmesg:
 ~ $ dmesg | grep -i USB
[111941.146764] usb 3-7: reset full-speed USB device number 3 using xhci_hcd
[111941.163265] usb 3-7: No LPM exit latency info found.  Power management will be impacted.
[111941.274994] usb 3-11: reset full-speed USB device number 5 using xhci_hcd
[111941.403047] usb 3-12: reset high-speed USB device number 6 using xhci_hcd
[111941.531149] usb 3-9: reset full-speed USB device number 15 using xhci_hcd
[111941.547587] usb 3-9: ep 0x2 - rounding interval to 64 microframes, ep desc says 80 microframes
[112459.099665] usb 3-6: new high-speed USB device number 20 using xhci_hcd
[112459.129057] usb 3-6: New USB device found, idVendor=058f, idProduct=6387
[112459.129060] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[112459.129061] usb 3-6: Product: Intenso Alu Line
[112459.129062] usb 3-6: Manufacturer: ALCOR
[112459.129063] usb 3-6: SerialNumber: E3BBE0E7
[112459.129619] usb-storage 3-6:1.0: USB Mass Storage device detected
[112459.129858] scsi8 : usb-storage 3-6:1.0
[112480.969433] usb 3-6: USB disconnect, device number 20
[112488.107498] usb 3-6: new high-speed USB device number 21 using xhci_hcd
[112488.131627] usb 3-6: New USB device found, idVendor=058f, idProduct=6387
[112488.131635] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[112488.131639] usb 3-6: Product: Intenso Alu Line
[112488.131643] usb 3-6: Manufacturer: ALCOR
[112488.131646] usb 3-6: SerialNumber: E3BBE0E7
[112488.132346] usb-storage 3-6:1.0: USB Mass Storage device detected
[112488.133336] scsi9 : usb-storage 3-6:1.0
[112615.350042] usb 3-6: USB disconnect, device number 21
[112628.013187] usb 3-6: new high-speed USB device number 22 using xhci_hcd
[112628.037521] usb 3-6: New USB device found, idVendor=058f, idProduct=6387
[112628.037528] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[112628.037532] usb 3-6: Product: Intenso Alu Line
[112628.037535] usb 3-6: Manufacturer: ALCOR
[112628.037538] usb 3-6: SerialNumber: E3BBE0E7
[112628.038112] usb-storage 3-6:1.0: USB Mass Storage device detected
[112628.038190] scsi10 : usb-storage 3-6:1.0
[113183.050109] usb 3-6: USB disconnect, device number 22
[113191.608254] usb 3-6: new high-speed USB device number 23 using xhci_hcd
[113191.632612] usb 3-6: New USB device found, idVendor=058f, idProduct=6387
[113191.632618] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[113191.632622] usb 3-6: Product: Intenso Alu Line
[113191.632625] usb 3-6: Manufacturer: ALCOR
[113191.632628] usb 3-6: SerialNumber: E3BBE0E7
[113191.633301] usb-storage 3-6:1.0: USB Mass Storage device detected
[113191.634266] scsi11 : usb-storage 3-6:1.0
[113417.686187] usb 3-12: reset high-speed USB device number 6 using xhci_hcd
[113417.814336] usb 3-9: reset full-speed USB device number 15 using xhci_hcd
[113417.830775] usb 3-9: ep 0x2 - rounding interval to 64 microframes, ep desc says 80 microframes
[113417.942398] usb 3-11: reset full-speed USB device number 5 using xhci_hcd
[113418.070533] usb 3-7: reset full-speed USB device number 3 using xhci_hcd
[113418.086613] usb 3-7: No LPM exit latency info found.  Power management will be impacted.
[113419.908644] usb 3-6: USB disconnect, device number 23
[113420.156704] usb 3-6: new high-speed USB device number 24 using xhci_hcd
[113420.177086] usb 3-6: string descriptor 0 read error: -71
[113420.177089] usb 3-6: New USB device found, idVendor=058f, idProduct=6387
[113420.177091] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[113420.177546] usb-storage 3-6:1.0: USB Mass Storage device detected
[113420.177590] scsi12 : usb-storage 3-6:1.0


ADDRESSED BY "Vendor=058f ProdID=6387 Rev=01.00" IN THE 9th BLOCK:
 ~ $ usb-devices

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 3
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev=03.13
S:  Manufacturer=Linux 3.13.0-24-generic ehci_hcd
S:  Product=EHCI Host Controller
S:  SerialNumber=0000:00:1a.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480 MxCh= 6
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=8087 ProdID=8008 Rev=00.04
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 3
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev=03.13
S:  Manufacturer=Linux 3.13.0-24-generic ehci_hcd
S:  Product=EHCI Host Controller
S:  SerialNumber=0000:00:1d.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480 MxCh= 8
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=8087 ProdID=8000 Rev=00.04
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh=14
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev=03.13
S:  Manufacturer=Linux 3.13.0-24-generic xhci_hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=0000:00:14.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=03 Lev=01 Prnt=01 Port=10 Cnt=01 Dev#=  5 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=ff(vend.) Sub=11 Prot=ff MxPS= 8 #Cfgs=  1
P:  Vendor=138a ProdID=0011 Rev=00.78
S:  SerialNumber=a98e2c788441
C:  #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 4 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)

T:  Bus=03 Lev=01 Prnt=01 Port=11 Cnt=02 Dev#=  6 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=04f2 ProdID=b398 Rev=39.89
S:  Manufacturer=Vimicro corp.
S:  Product=Integrated Camera
C:  #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=256mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=0e(video) Sub=01 Prot=00 Driver=uvcvideo
I:  If#= 1 Alt= 0 #EPs= 0 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo

T:  Bus=03 Lev=01 Prnt=01 Port=01 Cnt=03 Dev#= 19 Spd=1.5 MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=045e ProdID=00cb Rev=01.00
S:  Manufacturer=PixArt
S:  Product=Microsoft USB Optical Mouse
C:  #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid

T:  Bus=03 Lev=01 Prnt=01 Port=05 Cnt=04 Dev#= 24 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=058f ProdID=6387 Rev=01.00
C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=200mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage

T:  Bus=03 Lev=01 Prnt=01 Port=06 Cnt=05 Dev#=  3 Spd=12  MxCh= 0
D:  Ver= 2.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=0bda ProdID=b728 Rev=02.00
S:  Manufacturer=Realtek 
S:  Product=Bluetooth Radio 
S:  SerialNumber=00e04c000001
C:  #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

T:  Bus=03 Lev=01 Prnt=01 Port=08 Cnt=06 Dev#= 15 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=04f3 ProdID=0122 Rev=00.15
S:  Manufacturer=ELAN
S:  Product=Touchscreen
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid

T:  Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=5000 MxCh= 6
D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=1d6b ProdID=0003 Rev=03.13
S:  Manufacturer=Linux 3.13.0-24-generic xhci_hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=0000:00:14.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub



NOTHING (NEITHER WHEN TARGETING THE USB STICK NOR MY MOUSE):

 ~ $ lsusb -d -v 058f:6387
Usage: lsusb [options]...
List USB devices
  -v, --verbose
      Increase verbosity (show descriptors)
  -s [[bus]:][devnum]
      Show only devices with specified device and/or
      bus numbers (in decimal)
  -d vendor:[product]
      Show only devices with the specified vendor and
      product ID numbers (in hexadecimal)
  -D device
      Selects which device lsusb will examine
  -t, --tree
      Dump the physical USB device hierarchy as a tree
  -V, --version
      Show version of program
  -h, --help
      Show usage and help

 ~ $ lsusb -d -v 058f
Usage: lsusb [options]...
List USB devices
  -v, --verbose
      Increase verbosity (show descriptors)
  -s [[bus]:][devnum]
      Show only devices with specified device and/or
      bus numbers (in decimal)
  -d vendor:[product]
      Show only devices with the specified vendor and
      product ID numbers (in hexadecimal)
  -D device
      Selects which device lsusb will examine
  -t, --tree
      Dump the physical USB device hierarchy as a tree
  -V, --version
      Show version of program
  -h, --help
      Show usage and help

 ~ $ lsusb -D -v 045e:00cb
Usage: lsusb [options]...
List USB devices
  -v, --verbose
      Increase verbosity (show descriptors)
  -s [[bus]:][devnum]
      Show only devices with specified device and/or
      bus numbers (in decimal)
  -d vendor:[product]
      Show only devices with the specified vendor and
      product ID numbers (in hexadecimal)
  -D device
      Selects which device lsusb will examine
  -t, --tree
      Dump the physical USB device hierarchy as a tree
  -V, --version
      Show version of program
  -h, --help
      Show usage and help
In Nemo under [computer:///] were also 2 instances of it shown. After I just unplugged it, only one is shown, even after re-plugging, but with no properties and not mountable.

When I run gnome-disk-utility 3.10.0 again, now only one instance shows up (the more detailed second one).

More terminal stuff:

Code: Select all

 ~ lsblk
sda ... (cut out)
sdb      8:16   1  29.8G  0 disk

 ~ $ sudo mount /dev/sdb /media
Sorry, try again.
GParted also lists /edv/sdb and its partition and file system as unallocated (mentions its size, tho: 12.82 GiB).
  • Side note 1: I want to leave my USB sticks accessible by other devices and operating systems. Hence no Linux-specific reformatting. Also, the files I was copying onto the USB stick came from an NTFS partition (where the original Windows OS still resides).
    Side note 2: USB stick is a.k.a. a USB flash drive, thumb drive, pen drive, gig stick, flash stick, jump drive, disk key, disk on key, flash-drive, memory stick, USB key, or USB memory ... *sigh*


Can anyone help? The files copied to the USB stick are already deleted from the hard drive and will be gone if I can't get the stick to work again.
Last edited by Dirkoir on Sun Feb 16, 2020 6:48 am, edited 1 time in total.
______
Linux Mint 17 Qiana Cinnamon 64-bit

User avatar
trytip
Level 12
Level 12
Posts: 4425
Joined: Tue Jul 05, 2016 1:20 pm

Re: Huge Problems with USB Stick (aka flash drive)

Post by trytip »

i don't have a solution for you, but i do have a comment that relates to your situation. i never had issues with usb sticks until i used mint cinnamon and all hell broke loos when i tried installing mint 19.3 on my brand new lenovo ryzen5.
after getting what i think all the bios settings to boot and install linux, i wanted to transfer some files from my other computers and inserted a usb flash drive i have used for years. i believe it was fat32

so after i fill up my flashdrive with programs and wallpapers and whatnots, i plug it into my new lenovo and new mint 19.3 when at first things worked. after i unplugged it and put it back in all my files and folders became read-only :twisted: :twisted: :twisted:

seriously i have have seen posts about this but always thought the users might probably pulled it out as it was still copying and corrupted the file system. but no, i was amazed now that all my files were locked not only in my new mint 19.3 but in windows and other distros like live linux.

i did not want to pursue and waste my time with figuring out what caused the issue and formatted the flash drive which seemed to fix it's issue but what caused it in the first place?

Linux Mint has permission issues, and the mint team needs to look at this closer.
Image

CajunLanMan
Level 1
Level 1
Posts: 26
Joined: Tue Jan 28, 2014 12:01 pm

Re: Huge Problems with USB Stick (aka flash drive)

Post by CajunLanMan »

Just to add an interesting counter point, I've had the exact opposite experience with Mint and flash drives. As a guy who has a bit of an issue with hoarding flash drives, Mint is my goto when Windows and MacOS just don't want to deal with said flash drives. For me they are more likely to work in Mint than anything else I've used. Often if they are to a point where Windows nor MacOS can't even format them, Mint can always seem to sort them out.

I don't have any experience with the flash drive brand OP is using here, but based on the symptoms, it sounds an awful lot like a bad USB drive. I've seen flash drives fail in several different ways. I've actually got a 15 year old 128 MB Lexar flash drive that can't be written to, but the existing files are still accessible. I've got another old one where only some of the existing files on it are accessible, where the rest are corrupt when you try to copy them to a machine. I just think the symptoms are presenting as bad. (Hindsight, but never have important files in only one place)

As far as not using Linux specific formatting, since I frequently move between Windows, MacOS, and Mint, I always format my drives in exFAT. I've got a SanDisk 256 GB drive that I've had for over 2 years, formatted in exFAT, and I've never had an issue with it.

cliffcoggin
Level 5
Level 5
Posts: 783
Joined: Sat Sep 17, 2016 6:40 pm
Location: England

Re: Huge Problems with USB Stick (aka flash drive)

Post by cliffcoggin »

I've never heard of that brand. Are you sure they are reputable? There are many cheap USB sticks around that do not have the advertised capacity so I usually stick to Sandisk.
Cliff Coggin
Mint 19.2 Cinnamon

asinoro
Level 5
Level 5
Posts: 609
Joined: Mon Feb 12, 2018 11:43 am

Re: Huge Problems with USB Stick (aka flash drive)

Post by asinoro »

Can you post:

Code: Select all

 sudo parted -l ;  inxi -Fxxxz

Dirkoir
Level 4
Level 4
Posts: 201
Joined: Wed Jul 30, 2014 12:43 pm

Re: Huge Problems with USB Stick (aka flash drive)

Post by Dirkoir »

Thanks for all the replies so far. I am not familiar with brands. I bought this USB stick in the local branch of a major big-electronics-store-chain.

sudo parted -l
After the sda hard drive info this gives me only:

Code: Select all

Error: /dev/sdb: unrecognised disk label
inxi -Fxxxz
The part I guess to be relevant:

Code: Select all

Drives:    HDD Total Size: 532.1GB (80.2% used) 1: id: /dev/sda model: HGST_HTS725050A7 size: 500.1GB serial: TF655BWH2UZTTR temp: 45C 
           2: USB id: /dev/sdb model: Alu_Line size: 32.0GB serial: E3BBE0E7-0:0 temp: 0C
______
Linux Mint 17 Qiana Cinnamon 64-bit

oldbob
Level 1
Level 1
Posts: 45
Joined: Thu Jan 02, 2020 8:54 am

Re: Huge Problems with USB Stick (aka flash drive)

Post by oldbob »

Bit of a daft question this, so excuse me... but has the USB stick been formatted? Disks is saying 'Volumes: No Media', and 'Volumes: 32 GB Unknown'.

Dirkoir
Level 4
Level 4
Posts: 201
Joined: Wed Jul 30, 2014 12:43 pm

Re: Huge Problems with USB Stick (aka flash drive)

Post by Dirkoir »

oldbob wrote:
Fri Feb 14, 2020 1:18 pm
Bit of a daft question this, so excuse me... but has the USB stick been formatted? Disks is saying 'Volumes: No Media', and 'Volumes: 32 GB Unknown'.
Hm? Has any USB stick ever been sold unformatted? Well, this one clearly did come formatted like all others I ever got. I couldn't have copied files on it and then played video files from it on a TV if it had no formatting. As I mentioned before, I do not replace the default formatting with a Linux-only formatting, the reason being that I want it to remain sharable with as many other devices as possible.

The formatting, as expected, is FAT32 as shown when I stick its twin into another USB port (sdc instead of sdb where the broken one still sits), this twin not yet being harmed because I didn't use it yet:

The unbroken twin:

Code: Select all

32 GB Drive
/dev/sdc
Model: Intenso Alu Line (8.07)
Size: 32 GB (32,023,511,040 bytes)
Partitioning: Master Boot Record
Serial Number: E5B87873
Volumes: [no description in the graphic block]
Size: 32 GB — 32 GB free (0.1% full)
Device: /dev/sdc1
Partition Type: W95 FAT32
Contents: FAT (32-bit version) — Mounted at /media/USERNAME/INTENSO
So, the unbroken twin is shown to have a partition, and it gets mounted when plugged in like the broken USB stick used to get before it broke last night (not physically by the looks of it). Something seems to have gone wrong on the 'broken' one regarding a driver or the partition setup or such.
Last edited by Dirkoir on Sun Feb 16, 2020 6:47 am, edited 1 time in total.
______
Linux Mint 17 Qiana Cinnamon 64-bit

User avatar
pbear
Level 11
Level 11
Posts: 3889
Joined: Wed Jun 21, 2017 12:25 pm
Location: San Francisco

Re: Huge Problems with USB Stick (aka flash drive)

Post by pbear »

Dirkoir wrote:
Fri Feb 14, 2020 10:17 am
The files copied to the USB stick are already deleted from the hard drive and will be gone if I can't get the stick to work again.
Any chance of running data recovery on the hard drive? Cuz that's probably your most realistic option. Everything you've posted says the flash drive is toast. Possibly the data is still there and the controller is the problem, but you would need a professional to pursue that option (it's a bit like brain surgery), won't be cheap, and I suspect there's no way to know on the front end whether it will work.
Time flies like an arrow. Fruit flies like a banana.
If your problem has been solved, please edit the thread title.

Dirkoir
Level 4
Level 4
Posts: 201
Joined: Wed Jul 30, 2014 12:43 pm

Re: Huge Problems with USB Stick (aka flash drive)

Post by Dirkoir »

pbear wrote:
Sat Feb 15, 2020 3:49 am
Dirkoir wrote:
Fri Feb 14, 2020 10:17 am
The files copied to the USB stick are already deleted from the hard drive and will be gone if I can't get the stick to work again.
Any chance of running data recovery on the hard drive? Cuz that's probably your most realistic option. Everything you've posted says the flash drive is toast. Possibly the data is still there and the controller is the problem, but you would need a professional to pursue that option (it's a bit like brain surgery), won't be cheap, and I suspect there's no way to know on the front end whether it will work.
Thanks a lot for chiming in, pbear. :-)

File Recovery
I admit that I have been asking myself, too, if I could do data recovery on the hard drive to get those files back. But can I do this on a Windows8 NTFS partition (where they were stored) when booted on my Linux partition? From Linux or from Windows8?

(Explanation: The partition I have been using for extra storage is the original OS partition. Back when I bought this laptop, it had Windows 8 installed, which I couldn't stomach. So I shrunk its partition (rather than delete W8 completely in case I might ever need to run Windows again), created extra partitions, switched to the use of Linux Mint and never turned back. Since my hard drive is so darn small, I eventually began using free space on the Windows8 NTFS partition as a storage place for large files. I'd mount it from within Linux and store or retrieve with Nemo. I have been wondering if Nemo's recent kernel panic crashes didn't result only from copying onto a FAT32 flash drive but also from an NTFS partition.)


USB Stick (flash drive) Repair
Could a broken controller (or whatever is called what may sit on the flash drive) not perhaps be replaced by me with an unbroken one copied from its twin with some available tool? (of course, I now wonder if these Intenso USB sticks are always going to break on Linux, at least when not reformatted)


USB Stick (flash drive) Reformatting
If I can recover the lost files from elsewhere or give up on them, I'd still want to make the USB stick work again (but trustworthily), if necessary even with a Linux type formatting (like Ext4) if that is absolutely required, because I need file backup options smaller than (and of higher capacity than) DVDs as I may have to move to another continent again this year. And because I must make room on the hard drive to upgrade to the newest LM version. So, a tip along this potential side branch of this thread could help, too.


I'd love continued commentaries with helpful suggestions. :-)
______
Linux Mint 17 Qiana Cinnamon 64-bit

Dirkoir
Level 4
Level 4
Posts: 201
Joined: Wed Jul 30, 2014 12:43 pm

Re: Huge Problems with USB Stick (aka flash drive)

Post by Dirkoir »

Continued Study
I just had the idea to peek into an events log, both when unplugging the USB stick and when plugging it back in:

Command:

Code: Select all

~ sudo tail -f /var/log/syslog
unplugged:

Code: Select all

kernel: [168091.122244] usb 3-6: USB disconnect, device number 34
plugged back in:

Code: Select all

kernel: [168098.494893] usb 3-6: new high-speed USB device number 35 using xhci_hcd
kernel: [168098.519054] usb 3-6: New USB device found, idVendor=058f, idProduct=6387
kernel: [168098.519069] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: [168098.519078] usb 3-6: Product: Intenso Alu Line
kernel: [168098.519085] usb 3-6: Manufacturer: ALCOR
kernel: [168098.519092] usb 3-6: SerialNumber: E3BBE0E7
kernel: [168098.519996] usb-storage 3-6:1.0: USB Mass Storage device detected
kernel: [168098.522194] scsi23 : usb-storage 3-6:1.0
mtp-probe: checking bus 3, device 35: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-6"
mtp-probe: bus: 3, device: 35 was not an MTP device
kernel: [168099.521613] scsi 23:0:0:0: Direct-Access     Intenso  Alu Line         8.07 PQ: 0 ANSI: 4
kernel: [168099.522532] sd 23:0:0:0: [sdb] 62545920 512-byte logical blocks: (32.0 GB/29.8 GiB)
kernel: [168099.523203] sd 23:0:0:0: [sdb] Write Protect is off
kernel: [168099.523207] sd 23:0:0:0: [sdb] Mode Sense: 23 00 00 00
kernel: [168099.524685] sd 23:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
kernel: [168099.524935] sd 23:0:0:0: Attached scsi generic sg1 type 0
kernel: [168099.531843]  sdb: unknown partition table
kernel: [168099.534539] sd 23:0:0:0: [sdb] Attached SCSI removable disk
The device number keeps growing (now 35). That SCSI is mentioned surprises me. And "sdb: unknown partition table" maybe elaborates the earlier encountered "unknown" claims?
______
Linux Mint 17 Qiana Cinnamon 64-bit

carum carvi
Level 6
Level 6
Posts: 1053
Joined: Sun Apr 16, 2017 11:44 pm

Re: Huge Problems with USB Stick (aka flash drive)

Post by carum carvi »

Could very well be a faulty usb stick. Simply bad luck.

Fat32 does not support files larger than 4 GB. Could be a possible culprit. Just a thought, because you mentioned that you copied large files, but you also said the files werent much larger than 1GB, which would rule out the size as a possible cause.

Sorry I cant offer you a clear solution or explanation, but reformatting your usb stick rigorously perhaps could be worth a try?

ColdBootII
Level 5
Level 5
Posts: 691
Joined: Wed Aug 02, 2017 8:19 am

Re: Huge Problems with USB Stick (aka flash drive)

Post by ColdBootII »

Hi,

Maybe you have pulled out the stick prematurely at some prior session which corrupted the file system, ergo, the unknown partition table, shows up? Nemo's copy progress dialog is quite unreliable when it comes to determining when the copying has finished. Truth be said all Linux file managers suck at it. On the other hand, this can be an indication that the stick is failing.

Here's what I would try: reformat the stick and then try to copy all of the video files you intended, not one by one but all of them as you initially did. But this time around monitor the output of

Code: Select all

awk "{ print \$9 }" /sys/block/sdb/stat
command and don't attempt to eject it or pull it out until the command outputs a zero.

Cheers

Dirkoir
Level 4
Level 4
Posts: 201
Joined: Wed Jul 30, 2014 12:43 pm

Re: Huge Problems with USB Stick (aka flash drive)

Post by Dirkoir »

carum carvi wrote:
Sat Feb 15, 2020 6:56 am
Could very well be a faulty usb stick. ... Fat32 does not support files larger than 4 GB. ... reformatting your usb stick rigorously perhaps could be worth a try?
Thanks, carum carvi, for reminding me of the 4 GB limit on Fat32. Yes, luckily no file so far even got too close to 2 GB. A tip on how to reformat it when I no longer try to recover the files could be helpful. Are there certain formats our user community has the best experience with? And, then, use GParted?
______
Linux Mint 17 Qiana Cinnamon 64-bit

carum carvi
Level 6
Level 6
Posts: 1053
Joined: Sun Apr 16, 2017 11:44 pm

Re: Huge Problems with USB Stick (aka flash drive)

Post by carum carvi »

Good question. Gparted is known to be very reliable. But you could start with the simple format option in Linux which offers Exfat as well.

Dirkoir
Level 4
Level 4
Posts: 201
Joined: Wed Jul 30, 2014 12:43 pm

Re: Huge Problems with USB Stick (aka flash drive)

Post by Dirkoir »

carum carvi wrote:
Sat Feb 15, 2020 7:30 am
Good question. Gparted is known to be very reliable. But you could start with the simple format option in Linux which offers Exfat as well.
I am not familiar with that. Where is that?

But probably a more important question: which format can we best trust?
______
Linux Mint 17 Qiana Cinnamon 64-bit

Dirkoir
Level 4
Level 4
Posts: 201
Joined: Wed Jul 30, 2014 12:43 pm

Re: Huge Problems with USB Stick (aka flash drive)

Post by Dirkoir »

ColdBootII wrote:
Sat Feb 15, 2020 6:59 am
... Maybe you have pulled out the stick prematurely at some prior session which corrupted the file system... Nemo's copy progress dialog is quite unreliable when it comes to determining when the copying has finished. ... try: reformat the stick and then try to copy all of the video files ... not one by one but all of them... But this time around monitor the output of

Code: Select all

awk "{ print \$9 }" /sys/block/sdb/stat
command and don't attempt to eject it or pull it out until the command outputs a zero.

Thanks, ColdBootII, especially for that [awk "{ print \$9 }" /sys/block/sdb/stat] suggestion that's new to me. :-)


Questions:

1. So, file copies may not have been finished even though I always waited for Nemo's copy progress popup to disappear and then (usually or always? -- not sure anymore) checked the file size on the USB stick to be the same as the original on the hard drive?

2. Why would an interrupted file copy corrupt the whole file system rather than onlythe file?

3. As for copying a bunch of videos (even folders) in Nemo instead of one file at a time, this seemed to always result in a kernel panic crash. How to avoid that? Close many applications to free up a lot of RAM? Deal with different media formats? Any idea where those crashes come from?

4. How to recover the original files already deleted from the NTFS partition on my hard drive?


BTW, in my next reply I will expose an odd syslog report hinting at filesystem & mounting problems on the still mounting twin of the no longer mounting USB stick. (I bought a pack of 3, the one important one of which no longer mounts. The 'twin' I haven't copied anything onto, yet.)
______
Linux Mint 17 Qiana Cinnamon 64-bit

carum carvi
Level 6
Level 6
Posts: 1053
Joined: Sun Apr 16, 2017 11:44 pm

Re: Huge Problems with USB Stick (aka flash drive)

Post by carum carvi »

Dirkoir wrote:
Sat Feb 15, 2020 7:48 am
2. Why would an interrupted file copy corrupt the whole file system rather than onlythe file?
It simply can. LARGE files being copied can cripple Linux. It is an (unfortunate) well known flaw. I have experienced it many times.(unfortunately).
Dirkoir wrote:
Sat Feb 15, 2020 7:48 am
3. As for copying a bunch of videos (even folders) in Nemo instead of one file at a time, this seemed to always result in a kernel panic crash. How to avoid that? Close many applications to free up a lot of RAM? Deal with different media formats? Any idea where those crashes come from?
No Idea. Sorry. Genuingly sorry, because I would love to know it as well.
Dirkoir wrote:
Sat Feb 15, 2020 7:48 am
4. How to recover the original files already deleted from the NTFS partition on my hard drive?
There are recovery programs. Other members will chime in with their valuable advice.

Dirkoir
Level 4
Level 4
Posts: 201
Joined: Wed Jul 30, 2014 12:43 pm

Re: Huge Problems with USB Stick (aka flash drive)

Post by Dirkoir »

A few weeks ago I bought the now no longer mounting USB stick together with 2 more same ones in a pack. One of them I haven't copied anything onto yet. I have by now done a [sudo tail -f /var/log/syslog] check on it, as well, to compare it with the one done (and reported a few postings above) on the no longer mounting USB stick. Here are the results on this not yet utilized INTENSO flash drive that I call the failed one's "twin":

Code: Select all

THE YET 'UNBROKEN' (STILL MOUNTING) TWIN:

~ sudo tail -f /var/log/syslog


WHEN PLUGGING IT IN:
-------------------
kernel: [170760.108076] usb 3-1: new high-speed USB device number 40 using xhci_hcd
mtp-probe: checking bus 3, device 40: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1"
mtp-probe: bus: 3, device: 40 was not an MTP device
kernel: [170760.132331] usb 3-1: New USB device found, idVendor=058f, idProduct=6387
kernel: [170760.132334] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: [170760.132335] usb 3-1: Product: Intenso Alu Line
kernel: [170760.132337] usb 3-1: Manufacturer: ALCOR
kernel: [170760.132338] usb 3-1: SerialNumber: E5B87873
kernel: [170760.132924] usb-storage 3-1:1.0: USB Mass Storage device detected
kernel: [170760.133080] scsi28 : usb-storage 3-1:1.0
kernel: [170761.134855] scsi 28:0:0:0: Direct-Access     Intenso  Alu Line         8.07 PQ: 0 ANSI: 4
kernel: [170761.135174] sd 28:0:0:0: Attached scsi generic sg2 type 0
kernel: [170761.137334] sd 28:0:0:0: [sdc] 62545920 512-byte logical blocks: (32.0 GB/29.8 GiB)
kernel: [170761.138009] sd 28:0:0:0: [sdc] Write Protect is off
kernel: [170761.138013] sd 28:0:0:0: [sdc] Mode Sense: 23 00 00 00
kernel: [170761.138687] sd 28:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
kernel: [170761.144796]  sdc: sdc1
kernel: [170761.147069] sd 28:0:0:0: [sdc] Attached SCSI removable disk
kernel: [170761.370929] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
udisksd[2699]: Mounted /dev/sdc1 at /media/USERNAME/INTENSO on behalf of uid 1000


WHEN EJECTING IT IN NEMO:
------------------------
udisksd[2699]: Cleaning up mount point /media/USERNAME/INTENSO (device 8:33 is not mounted)
udisksd[2699]: Unmounted /dev/sdc1 on behalf of uid 1000
kernel: [170775.700122] sdc: detected capacity change from 32023511040 to 0


WHEN UNPLUGGING IT:
-------------------
kernel: [170781.806615] usb 3-1: USB disconnect, device number 40


The differences I notice here when plugging the not yet utilized twin in (my comments preceded by //):

Code: Select all

kernel: [170761.144796]  sdc: sdc1

 // the sdc1 port instead of "unknown partition table"


kernel: [170761.370929] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
udisksd[2699]: Mounted /dev/sdc1 at /media/USERNAME/INTENSO on behalf of uid 1000

 // The weird complaint about "not properly unmounted" despite always ejecting in Nemo before unplugging it...
 // ... followed by the recommendation to "run fsck".
 // The "mounted" claim after being unplugged.

So, even the not yet used for storage twin INTENSO USB stick that still mounts when plugged in gets some disapproving comments in the syslog. Odd that persistent "was not properly unmounted" comment after being "ejected" in Nemo before un- and re-plugging. And where might that "run fsck" recommendation lead?
______
Linux Mint 17 Qiana Cinnamon 64-bit

carum carvi
Level 6
Level 6
Posts: 1053
Joined: Sun Apr 16, 2017 11:44 pm

Re: Huge Problems with USB Stick (aka flash drive)

Post by carum carvi »

It still could well be a faulty CHEAP usb stick. They are being sold. I have bought and experienced it first hand as well. And they dont work from the get go. Intenso, never heard of it. Generally speaking, a good advice would be to AVOID cheap usb sticks, because they are cheap for a reason, they are less reliable...

Post Reply

Return to “Newbie Questions”