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

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

Post by Dirkoir »

Peter Linu wrote:
Sun Feb 16, 2020 8:28 am
Here's my 2 cents worth.
I have encountered the same issues as everyone here. I don't EVER rely on the factory formatting of a new USB. They must use software that does it very quickly and subsequently have unreliable outcomes. When I do it myself it always OK. If you have formatted in the wrong system, it doesn't take much effort to reformat.
Thanks for this insight, Peter Linu. :-)

Is self-formatted FAT32 perfectly fine? (ideal for sharing with all other devices, including a TV, I suspect)
______
Linux Mint 17 Qiana Cinnamon 64-bit

User avatar
Peter Linu
Level 5
Level 5
Posts: 567
Joined: Sun Nov 11, 2018 8:24 pm
Location: Sydney, Australia

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

Post by Peter Linu »

Again, experience tells me that FAT32 is the safest option for sharing.
Rules to understand;
1. if USB is 16Gb don't fill it to 15.99Gb
2. If FAT32 has a 4Gb file size limit, don't try to make 3.99Gb files.
I never fill any hard drive, fixed or portable to more than 80% capacity.
EVERYDAY Dual-boot Win7+Cinnamon 19.3 Thinkpad T440p#2: dual core i5-4300, 64-bit, 8Gb RAM, 500Gb SSD, 1Tb HDD +7 other laptops in various states of use and modification.

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 »

So... now... the recovery of the deleted files... (from the hard drive)... How I just did it:

Since I came across no simple traditional undelete possibility (reversing the delete flag in the table of contents of the file system), I bit the bullet and went for a low-level recovery that makes copies from the officially deleted (but still there) files.

Since the NTFS partition has hundreds or thousands of deleted files I didn't want to dig through, I chose to use the pattern matchings of ntfsundelete, with success (Yeah!):

Instructional sources:

https://www.howtogeek.com/howto/13706/r ... u-live-cd/
https://linux.die.net/man/8/ntfsundelete



Procedure:

Syntax note:
- Anybody using these command lines must replace USERNAME with their own user name of choice.
- /dev/sda4 happens to be the path to my NTFS partition. You'd need to find yours.
- PP-Parking/vidrecovs is the destination directory I created.


I. Find a test file (list all mp4 files that are 100% recoverable):
sudo ntfsundelete /dev/sda4 -s -m *.mp4 -p 100

Code: Select all

~ $ sudo ntfsundelete /dev/sda4 -s -m *.mp4 -p 100
Volume is scheduled for check.
Please boot into Windows TWICE, or use the 'force' option.
NOTE: If you had not scheduled check and last time accessed this volume
using ntfsmount and shutdown system properly, then init scripts in your
distribution are broken. Please report to your distribution developers
(NOT to us!) that init scripts kill ntfsmount or mount.ntfs-fuse during
shutdown instead of proper umount.
Ugh (more modern weirdness)!



II. Fine... Force skipping over that weirdness:

Code: Select all

~ $ sudo ntfsundelete /dev/sda4 -s -m *.mp4 -p 100 -f
...
Files with potentially recoverable content: 31


III. Now a single file recovery test (92955 being the Inode number of one file I picked for a test run):
sudo ntfsundelete /dev/sda4 -u -i 92955 -o test.mp4 -d /media/USERNAME/PP-Parking/vidrecovs

Hmpf. That weirdness again:

Code: Select all

Volume is scheduled for check.
Please boot into Windows TWICE, or use the 'force' option.
NOTE: If you had not scheduled check and last time accessed this volume
using ntfsmount and shutdown system properly, then init scripts in your
distribution are broken. Please report to your distribution developers
(NOT to us!) that init scripts kill ntfsmount or mount.ntfs-fuse during
shutdown instead of proper umount.


IV. So, apparently I now always had to include the force parameter and then did so. Grumble, grumble:

Code: Select all

~ $ sudo ntfsundelete /dev/sda4 -f -u -i 92955 -o test.mp4 -d /media/USERNAME/PP-Parking/vidrecovs
Phew! This worked. (it was a small file I had no desire to actually recover, but good for a test run)



V. So, then delete it again and try to recover ALL deleted *mp4 files:
sudo ntfsundelete /dev/sda4 -f -u -m *.mp4 -d /media/USERNAME/PP-Parking/vidrecovs

Since it also recovered a broken video file, it prolly would have been smarter to add -p 100:

Code: Select all

sudo ntfsundelete /dev/sda4 -f -u -m *.mp4 -p 100 -d /media/USERNAME/PP-Parking/vidrecovs



VI. Then, of course, all recovered files were owned by the root. *sigh* The permissions fix:

Code: Select all

sudo chown -R USERNAME:USERNAME /media/USERNAME/PP-Parking/vidrecovs/


Phew! Yippe! I got the lost files back. :-) (almost certainly all of them)


Now back to the USB stick (flash drive) issues. The consensus seems to be that the messed up stick can't be repaired, only reformatted and have files and folders copied and made all over again.
______
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 »

Peter Linu wrote:
Sun Feb 16, 2020 9:08 am
Again, experience tells me that FAT32 is the safest option for sharing.
Rules to understand;
1. if USB is 16Gb don't fill it to 15.99Gb
2. If FAT32 has a 4Gb file size limit, don't try to make 3.99Gb files.
I never fill any hard drive, fixed or portable to more than 80% capacity.

OK, I'll summarize the USB stick thoughts shared in this thread:
  • My massive problems of frequent kernel panic crashes, the flash drive (USB stick) switching regularly to read-only status (fixable in the terminal with: sudo chmod 777 /media/USERNAME), and it ultimately becoming unmountable may possibly be avoided by reformatting it after its purchase before beginning to use it.
  • If large files are fully transferred when Nemo suggests that they are is still a little unsure (possibly hurting the file system if the stick is pulled out too early). The transfer completion may be tested ("0" says yes) in the terminal with: awk "{ print \$9 }" /sys/block/sdb/stat
  • Avoid filling the stick completely up.
  • The FAT32 format is the most sharable with a wide range of other devices, but it has a 4GB file size limit.
Question: Have other file formats been found to be sharable with a TV?
______
Linux Mint 17 Qiana Cinnamon 64-bit

User avatar
pbear
Level 11
Level 11
Posts: 3883
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:
Sun Feb 16, 2020 9:11 am
I chose to use the pattern matchings of ntfsundelete, with success (Yeah!):

Instructional sources:

https://www.howtogeek.com/howto/13706/r ... u-live-cd/
https://linux.die.net/man/8/ntfsundelete
Excellent sleuthing and congratulations. I'm adding your walk-through and the links to my toolbox.

Sorry, no idea about format for sharing with a TV.
Time flies like an arrow. Fruit flies like a banana.
If your problem has been solved, please edit the thread title.

User avatar
ricardogroetaers
Level 4
Level 4
Posts: 286
Joined: Sat Oct 27, 2018 3:06 am
Location: Rio de Janeiro, Brasil

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

Post by ricardogroetaers »

Dirkoir wrote:
Sun Feb 16, 2020 6:53 am

Code: Select all

32 GB Drive
/dev/sdb
Model: Intenso Alu Line (8.07)
Size: 32 GB (32,023,511,040 bytes)
Serial Number: E3BBE0E7
Volumes: 32 GB Unknown
Size: 32 GB (32,023,511,040 bytes)
Device: /dev/sdb
Contents: Unknown
One storage partition would be enough. Which format would be best to pick is still an open question.
I didn't quite understand the text before the "code window" but it doesn't matter.
The "code window" appears to show 32 GB media with no content, empty. I don't know which command or program was used to show this. But it doesn't matter either.

Usually flash media (flash drives, memory cards) comes standard with loop partitioning and a fat or fat32 file system.
In this condition they are not bootable.

You can create an mbr partitioning and a single win95C partition, also called Win95lba ​​which must be formatted in fat32lba.
This fat32C or fat32lba provides support for large capacity units.
Sometimes the Linux Mint system gets in the way when a removable flash media has more than one partition.
Recommended when creating the partition:
- align it by the cylinder not by MB (MegaBytes)
- leave a free space at the end of about 2 MB (MegaBytes).
Some operating systems get in the way of counting space when the partition extends to the end of the media.

Older operating systems prior to Windows 95OSR2.5 (also called Windows 95C) may not recognize a fat32lba.
If a television can recognize it, it can vary.
I have no problems with my television for more than 10 years or with the automotive multimedia center.

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 »

Quick replies:
pbear wrote:
Sun Feb 16, 2020 12:22 pm
Dirkoir wrote:
Sun Feb 16, 2020 9:11 am
I chose to use the pattern matchings of ntfsundelete, with success (Yeah!):

Instructional sources:

https://www.howtogeek.com/howto/13706/r ... u-live-cd/
https://linux.die.net/man/8/ntfsundelete
Excellent sleuthing and congratulations. I'm adding your walk-through and the links to my toolbox.
Cool! I'm happy when I can contribute to others. :-)

ricardogroetaers wrote:
Sun Feb 16, 2020 5:33 pm
I didn't quite understand the text before the "code window"... I don't know which command or program was used to show this.
The info is taken from the Disks application.
ricardogroetaers wrote:
Sun Feb 16, 2020 5:33 pm
I have no problems with my television for more than 10 years or with the automotive multimedia center.
With which format, and how to do the formatting? (I briefly tried to reformat the twin today with the Disks application, but it failed)
______
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 »

I tried to format the 'twin' (the NOT messed up, not yet utilized 32 GB Intenso USB stick) with the Disks application, but it failed:

Settings:
* Don't overwrite existing data (Quick)
* Compatible with all systems and devices (MBR / DOS)

Result within 10 or 20 seconds:
Error formatting disk
Error synchronizing after initial wipe: Timed out waiting for object (udisks-error-quark, 0)


Did I pick the wrong settings and/or should I better use another application?
______
Linux Mint 17 Qiana Cinnamon 64-bit

User avatar
ricardogroetaers
Level 4
Level 4
Posts: 286
Joined: Sat Oct 27, 2018 3:06 am
Location: Rio de Janeiro, Brasil

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

Post by ricardogroetaers »

Dirkoir wrote:
Sun Feb 16, 2020 6:10 pm
Did I pick the wrong settings and/or should I better use another application?
1-Restart the computer to clear the information about the flash drive.
2-Insert the pendrive.
3-Open the Disks program.
4-Unmount any existing file system on the USB stick, if applicable.
5-Go to the top right corner of the Discos program, click on the hamburger icon (3 horizontal lines).
Format disk.
Options:
-Overwrite existing data with zeros (slow)
-No partitioning (empty)
6-Wait for the processing to finish.
7-Eject the media through the Discos program.
8-Physically remove the device.

Steps 7 and 8 are important for the partitioning programs and the operating system to understand the change in the device.

If you wish, repeat everything from 2.
The flash drive will be completely erased.

Create new partitioning as suggested in a previous post using Gparted or optionally the Disks program.

Observe suggestions:
-mbr partitioning
-partition:
-align by cylinder
-unpartitioned space of about 2 MB at the end
-partition and file system format: Win95lba

If you want a pendrive as it comes from the factory, choose the loop partitioning system in Gparted instead of choosing the mbr partitioning system.

Good luck.
Last edited by ricardogroetaers on Tue Feb 18, 2020 6:26 am, edited 1 time in total.

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

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

Post by pbear »

Try Ricardo's suggestion first. Disks is considered reliable, by the way. If that doesn't work, I'd be inclined to say you have another bum flash drive. If you want to try another test, open Terminal and run this command:

Code: Select all

sudo shred -s $((2048*512)) -vzn0 /dev/sdx # replace x with the correct device designation
This clears the head of the drive, including the MBR and partition table. Then try formatting with GParted. If that fails also, time to give up, IMHO.
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 »

Interim Report
  • Deleted data from NTFS partition recovered using ntfsundelete (see above).
  • The 'twin' of the no longer mounting USB stick reformatted and looking more reliable now (but not yet fully tested). How I overcame the formatting hurdle reported above comes in the next comment post below.
  • Other (luckily few) deleted data from my Ext4 data partition not recoverable with ntfsundelete, and all research for this is still bewildering.
  • A greatly desirable achievement would be a full repair or data extraction from the messed up USB stick, but all my research in this direction has not been very promising. Most finds on the Internet only aim at making it usable again, not recovering lost data from it, and TestDisk -- even if I should get past its current hurdles -- has a big problem by insisting to place recovered files in my home partition which is way too small.
______
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 »

How the reformatting worked. (of a still working flash drive to hopefully prevent future problems)

The flash drive: the still mounting 'twin' of the other one from the same packet that after several uses no longer mounts.

The procedure: The one described by ricardogroetaers above:
ricardogroetaers wrote:
Sun Feb 16, 2020 6:44 pm
1-Restart the computer to clear the information about the flash drive.
2-Insert the pendrive.
3-Open the Disks program.
4-Unmount any existing file system on the USB stick, if applicable.
5-Go to the top right corner of the Discos program, click on the hamburger icon (3 horizontal lines).
Format disk.
Options:
-Overwrite existing data with zeros (slow)
-No partitioning (empty)
6-Wait for the processing to finish.
7-Eject the media through the Discos program.
8-Physically remove the device.
(I didn't perfectly understand the unmount demand in this, nor the options that followed below the above quote (namely: "If you wish, repeat everything from 2." Q: Why? | New partitioning option. Q: Why and exactly how?)


I didn't unmount on the first try. (one reason being that I saw no such command option)

==> Again: "Error synchronizing after initial wipe: Timed out waiting for object (udisks-error-quark, 0)"

Tried to unmount by 'Eject' button in the sidebar of Nemo.

==> Formatting was no longer an option in Disks application's upper right ("hamburger") menu (actual icon: a cogwheel )

Replugged it. BTW, "Contents" at bottom in Disks application window told me: "FAT (32-bit version) — Mounted at /media/dirkoir/INTENSO"

Tried formatting it again:

==> Again: "Error synchronizing after initial wipe: Timed out waiting for object (udisks-error-quark, 0)"

So, I tried the other #2 options, as well. Here are all three:
* Compatible with all systems and devices (MBR / DOS)
* Compatible with modern systems and hard disks > 2TB (GPT)
* No partitioning (empty)

... and also with the other 1st option: "Don't overwrite existing data (Quick)"

Always the same error response as before ("Error synchronizing after initial wipe: Timed out waiting for object (udisks-error-quark, 0)")


This discussion page gave me a hint: https://elementaryos.stackexchange.com/ ... -usb-drive
It suggested another way of use of the Disks application, one that got around this error.
Quote:
You can work around this bug in gnome-disk-utility using these steps:
After selecting the SD card, instead of clicking the gear icon to format, click the partition in the "Volumes" section.
Delete the partition ("minus" icon)
Create a new partition


Rather than delete and recreate the one-and-only partition as suggested on this page, I chose to first try to achieve formatting again, but calling for this through the other interface mentioned, namely the icons at the bottom of the Volumes box in the middle of the window. The box displays partitions. The control icons below it are: black filled square = unmount the filesystem, - = Delete partition, 2 cogwheels = More options.


The last one (the two cogwheels icon) opens a menu similar to the one in the upper right corner.

The DIFFERENCE (I suspect), is that the upper right menu targets the whole device (/dev/sdb in my case), while the one below the volumes box targets the selected partition (which in this case can't be picked because there is only one, and that's picked by default already), in my case: dev/sdb1


The "Format..." option in that partition-menu didn't give me that "No partitioning (empty)" second option. So I went with these options:
-Overwrite existing data with zeros (slow)
-Compatible with all systems and devices (FAT)

(this second option choice to make it most likely to work on my TV, as well)

There is also a "Name" field to fill in. Being unsure if it's necessary, I entered a name (USB-V).


The formatting process claimed to take ~45 minutes but I think it took two or more hours. :-(

(I wonder if "Overwrite existing data with zeros (slow)" is really necessary.)

Anyway, I ended up with a renamed partition (USB-V).

The full display in Disks application:

32 GB Drive
/dev/sdb
Model: Intenso Alu Line (8.07)
Size: 32 GB (32,023,511,040 bytes
Partitioning: Master Boot Record
Serial Number: E5B87873
Volumes: USB-V
Partition 1
32 GB FAT
Size: 32 GB — 32 GB free (0.0% full)
Device: /dev/sdc1
Partition Type: W95 FAT32 (LBA)
Contents: FAT (32-bit version) — Mounted at /media/USERNAME/USB-V

So... changes:
* Volumes has three lines of info instead of no description
* The Size now claims to be 0.0% full instead 0.1% full
* "(LBA)" is appended to "W95 FAT32" in the Partition Type
* And unsurprisingly the partition has the new name I entered (USB-V)

Impression: Disks application (gnome-disk-utility 3.10.0) is more familiar with it now.



So, to see if the kernal would scream about errors again when plugging in, I did this again:

sudo tail -f /var/log/syslog

Code: Select all

EJECTED IN NEMO (THE UNMOUNT VERSION FOR DEVICES SELF-IDENTIFIED AS REMOVABLE):
------------------------------------------------------------------------------
udisksd[2753]: Cleaning up mount point /media/USERNAME/USB-V (device 8:17 is not mounted)
udisksd[2753]: Unmounted /dev/sdb1 on behalf of uid 1000
kernel: [13401.873299] sdb: detected capacity change from 32023511040 to 0


UNPLUGGED:
------------------------------------------------------------------------------
kernel: [13461.061643] usb 3-6: USB disconnect, device number 19


PLUGGED IN AGAIN:
------------------------------------------------------------------------------
kernel: [13469.662726] usb 3-6: new high-speed USB device number 20 using xhci_hcd
kernel: [13469.687500] usb 3-6: New USB device found, idVendor=058f, idProduct=6387
kernel: [13469.687511] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: [13469.687516] usb 3-6: Product: Intenso Alu Line
kernel: [13469.687520] usb 3-6: Manufacturer: ALCOR
kernel: [13469.687524] usb 3-6: SerialNumber: E5B87873
kernel: [13469.688457] usb-storage 3-6:1.0: USB Mass Storage device detected
kernel: [13469.688716] scsi10 : usb-storage 3-6:1.0
mtp-probe: checking bus 3, device 20: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-6"
mtp-probe: bus: 3, device: 20 was not an MTP device
kernel: [13470.689741] scsi 10:0:0:0: Direct-Access     Intenso  Alu Line         8.07 PQ: 0 ANSI: 4
kernel: [13470.690619] sd 10:0:0:0: Attached scsi generic sg1 type 0
kernel: [13470.691273] sd 10:0:0:0: [sdb] 62545920 512-byte logical blocks: (32.0 GB/29.8 GiB)
kernel: [13470.692140] sd 10:0:0:0: [sdb] Write Protect is off
kernel: [13470.692145] sd 10:0:0:0: [sdb] Mode Sense: 23 00 00 00
kernel: [13470.693011] sd 10:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
kernel: [13470.700434]  sdb: sdb1
kernel: [13470.702803] sd 10:0:0:0: [sdb] Attached SCSI removable disk
udisksd[2753]: Mounted /dev/sdb1 at /media/USERNAME/USB-V on behalf of uid 1000


EJECTED IN NEMO (THE UNMOUNT VERSION FOR DEVICES SELF-IDENTIFIED AS REMOVABLE):
------------------------------------------------------------------------------
udisksd[2753]: Cleaning up mount point /media/USERNAME/USB-V (device 8:17 is not mounted)
udisksd[2753]: Unmounted /dev/sdb1 on behalf of uid 1000
kernel: [13522.932336] sdb: detected capacity change from 32023511040 to 0


UNPLUGGED:
------------------------------------------------------------------------------
kernel: [13529.761645] usb 3-6: USB disconnect, device number 20




PLUGGED IN AGAIN:
------------------------------------------------------------------------------
kernel: [13813.580516] usb 3-6: new high-speed USB device number 21 using xhci_hcd
kernel: [13813.604778] usb 3-6: New USB device found, idVendor=058f, idProduct=6387
kernel: [13813.604788] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: [13813.604794] usb 3-6: Product: Intenso Alu Line
kernel: [13813.604798] usb 3-6: Manufacturer: ALCOR
kernel: [13813.604802] usb 3-6: SerialNumber: E5B87873
kernel: [13813.605700] usb-storage 3-6:1.0: USB Mass Storage device detected
kernel: [13813.605930] scsi11 : usb-storage 3-6:1.0
mtp-probe: checking bus 3, device 21: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-6"
mtp-probe: bus: 3, device: 21 was not an MTP device
kernel: [13814.607552] scsi 11:0:0:0: Direct-Access     Intenso  Alu Line         8.07 PQ: 0 ANSI: 4
kernel: [13814.608423] sd 11:0:0:0: Attached scsi generic sg1 type 0
kernel: [13814.609111] sd 11:0:0:0: [sdb] 62545920 512-byte logical blocks: (32.0 GB/29.8 GiB)
kernel: [13814.609845] sd 11:0:0:0: [sdb] Write Protect is off
kernel: [13814.609858] sd 11:0:0:0: [sdb] Mode Sense: 23 00 00 00
kernel: [13814.610587] sd 11:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
kernel: [13814.617553]  sdb: sdb1
kernel: [13814.619649] sd 11:0:0:0: [sdb] Attached SCSI removable disk
udisksd[2753]: Mounted /dev/sdb1 at /media/USERNAME/USB-V on behalf of uid 1000

UNMOUNTED THE PARTITION RATHER THAN WHOLE DEVICE IN THE DISKS APPLICATION:
------------------------------------------------------------------------------
udisksd[2753]: Cleaning up mount point /media/USERNAME/USB-V (device 8:17 is not mounted)
udisksd[2753]: Unmounted /dev/sdb1 on behalf of uid 1000

UNPLUGGED:
------------------------------------------------------------------------------
kernel: [13880.651165] usb 3-6: USB disconnect, device number 21



PLUGGED IN AGAIN:
------------------------------------------------------------------------------
kernel: [14059.690855] usb 3-6: new high-speed USB device number 22 using xhci_hcd
kernel: [14059.715144] usb 3-6: New USB device found, idVendor=058f, idProduct=6387
kernel: [14059.715154] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: [14059.715160] usb 3-6: Product: Intenso Alu Line
kernel: [14059.715164] usb 3-6: Manufacturer: ALCOR
kernel: [14059.715168] usb 3-6: SerialNumber: E5B87873
kernel: [14059.716020] usb-storage 3-6:1.0: USB Mass Storage device detected
kernel: [14059.716241] scsi12 : usb-storage 3-6:1.0
mtp-probe: checking bus 3, device 22: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-6"
mtp-probe: bus: 3, device: 22 was not an MTP device
kernel: [14060.717801] scsi 12:0:0:0: Direct-Access     Intenso  Alu Line         8.07 PQ: 0 ANSI: 4
kernel: [14060.718614] sd 12:0:0:0: Attached scsi generic sg1 type 0
kernel: [14060.720595] sd 12:0:0:0: [sdb] 62545920 512-byte logical blocks: (32.0 GB/29.8 GiB)
kernel: [14060.721474] sd 12:0:0:0: [sdb] Write Protect is off
kernel: [14060.721483] sd 12:0:0:0: [sdb] Mode Sense: 23 00 00 00
kernel: [14060.724551] sd 12:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
kernel: [14060.730266]  sdb: sdb1
kernel: [14060.732527] sd 12:0:0:0: [sdb] Attached SCSI removable disk
udisksd[2753]: Mounted /dev/sdb1 at /media/USERNAME/USB-V on behalf of uid 1000


UNMOUNTED THE DEVICE RATHER THAN PARTITION IN THE DISKS APPLICATION:
------------------------------------------------------------------------------
udisksd[2753]: Cleaning up mount point /media/USERNAME/USB-V (device 8:17 is not mounted)
udisksd[2753]: Unmounted /dev/sdb1 on behalf of uid 1000
kernel: [14130.413152] sdb: detected capacity change from 32023511040 to 0

UNPLUGGED:
------------------------------------------------------------------------------
kernel: [14142.165164] usb 3-6: USB disconnect, device number 22


Difference between before and after the formatting:

Code: Select all

THE LAST 3 LINES WHEN PLUGGING THE ORIGINAL-STATE-FROM-THE-MANUFACTURER 'TWIN' USB STICK IN:
-------------------------------------------------------------------------------------------
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


THE LAST 2 LINES WHEN PLUGGING THE SAME 'TWIN' USB STICK IN AFTER THE REFORMATTING:
-------------------------------------------------------------------------------------------
kernel: [14060.732527] sd 12:0:0:0: [sdb] Attached SCSI removable disk
udisksd[2753]: Mounted /dev/sdb1 at /media/USERNAME/USB-V on behalf of uid 1000

So, the scary complaint "Volume was not properly unmounted. Some data may be corrupt. Please run fsck." is now gone.



I am pondering whether to try a test with something like F3 (https://www.linuxbabe.com/command-line/ ... test-linux) or attempt a one-step copying of all desired files onto it with Nemo and hope their won't be a kernel panic crash nor read-only setup this time and hope it will continue to work well for (*chuckle*) eternity... and check whether the TV still accepts it, too...
______
Linux Mint 17 Qiana Cinnamon 64-bit

User avatar
ricardogroetaers
Level 4
Level 4
Posts: 286
Joined: Sat Oct 27, 2018 3:06 am
Location: Rio de Janeiro, Brasil

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

Post by ricardogroetaers »

Dirkoir,
You are making a salad of procedures obtained from various sources. It is not good practice.

I will not quote texts posted by you, I will comment directly.

-In the disks program, the gears below the partition graph act on the selected partition.
The hamburger acts on the entire media of the device.
To format a partition, it must be unmounted (black square).
To format the entire media on the device, all partitions on it must be unmounted.

-Filling data with zeros (slow) means overwriting data.
It doesn't matter if you are going to format, create, delete, with defined partitioning or without partitioning.

-Don't overwrite data (fast) means, roughly speaking, just changing addresses or descriptors, the previous data stays there and can be recovered and in some cases read or even confused.
Repeated use of this mode can cause multiple partition tables to fail.

For your post above I believe that everything is fine with your USB stick.
You put a "label" (optional) on the file system, called "USB-V".
So the mount point is:
/media/USERNAME/USB-V

I just didn't understand the paradox:
32 GB Drive
/dev/sdb
---------------------------------------
Partition 1
32 GB FAT
Size: 32 GB - 32 GB free (0.0% full)
Device: /dev/sdc1

It must be a typo.

JasonStonier
Level 2
Level 2
Posts: 67
Joined: Sun Oct 02, 2016 10:51 am

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

Post by JasonStonier »

I've had <exactly> the same thing - it was a crappy memory stick that had early life failure. Same symptoms that you have seen, including the kernel panic.

At one time I was doing a lot of support for people with Windows laptops that literally all had thousands of viruses, so I had a suite of tools on a memory stick with a physical write protect switch. I bought a couple of those sticks, and both failed in the same way you have described.

A format would bring them back for a few days, but ultimately they were junk.

Throw yours away and move on :)

User avatar
pbear
Level 11
Level 11
Posts: 3883
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:
Tue Feb 18, 2020 6:23 am
The DIFFERENCE (I suspect), is that the upper right menu targets the whole device (/dev/sdb in my case), while the one below the volumes box targets the selected partition (which in this case can't be picked because there is only one, and that's picked by default already), in my case: dev/sdb1
Two out of three ain't bad, but the point you misunderstand is important. So, yes, the upper-right ("hamburger") menu targets the device. And, yes, the tools below the graphic representation of the device are for partitions. What's wrong is: Can't select a partition "because there is only one, and that's picked by default already." Of course you can select a single partition. (What you can't do is select a different partition on that device, unless and until you create one.) More importantly, the partition commands work with a single partition, which indeed you did.

FWIW, I generally prefer GParted to Disks, as I like the tools and process better. On the other hand, Disks handles permissions more easily (it runs as mere user, where GParted runs as root). As my mother likes to say, there's a reason Baskin-Robbins makes more than one flavor of ice cream.
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 »

Update (on the reformatted not previously used USB stick):

I just finished the new compilation of video files destined to be packed onto the reformatted 'twin' USB stick.

And Nemo copied all 129 files (in 11 folders plus some sub-folders and amounting to almost 32 GB) to the USB stick in one single swoop without crashing this time. :-)

It seems as if the reformatted USB stick is indeed (at least on the first day of use) more cooperative with my Linux Mint 17 Cinnamon than its identical fellow was with its manufacturer's formatting.

Preliminary play tests on my TV have worked so far. (let's hope it doesn't break down within a few weeks as its not reformatted fellow did)
______
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 »

Weird event:

A video I had recently started to watch before but then shut down the TV (possibly before EXITing out of the media mode which I usually do as a precaution) could no longer be played the next day (some error message of being unusable or some such).

When some days later I unplugged the USB stick (flash drive) from the TV and plugged it into my laptop, [sudo tail -f /var/log/syslog] showed no complaint and I could play this video on the laptop. When I plugged the USB stick back into the TV and turned it on again and went into the media mode, this video did play again.

So, I thought it had become corrupted again, by itself or the TV (not having been plugged into anything but the TV since the reformatting-followed-installation of all the videos), but now it seems OK. I think that I had tried a restart of the TV before after which the video was still unplayable. If the laptop fixed any problem, it certainly didn't tell me.

All very weird.
______
Linux Mint 17 Qiana Cinnamon 64-bit

Post Reply

Return to “Newbie Questions”