| 1 |
On Saturday, 21 March 2020 13:49:04 GMT Caveman Al Toraboran wrote: |
| 2 |
> questions: |
| 3 |
> * what's going on? |
| 4 |
|
| 5 |
It looks as if your USB stick connector or its microcontroller is faulty. |
| 6 |
There is also a smaller probability the USB port on the PC is playing up. |
| 7 |
|
| 8 |
|
| 9 |
> * how to find out? |
| 10 |
|
| 11 |
Look at dmesg -w and syslog for I/O errors. |
| 12 |
|
| 13 |
|
| 14 |
> * how to fix? |
| 15 |
|
| 16 |
If this is a hardware fault, check for dirty/oxidized contacts on the USB |
| 17 |
connector and clean these as appropriate. If they look OK, try a different |
| 18 |
USB port on the PC. |
| 19 |
|
| 20 |
|
| 21 |
> symptoms: |
| 22 |
> * can't write (gives read/write error). |
| 23 |
> * but files can get created and deleted. |
| 24 |
> * newly created files, which also have failed writes |
| 25 |
> have 0 bytes in them. |
| 26 |
> * mount /dev/sda1 /boot is slow. |
| 27 |
> * umount /boot is slow. |
| 28 |
> |
| 29 |
> |
| 30 |
> cave ~ # fsck.vfat -v -a -w /dev/sda1 |
| 31 |
> fsck.fat 4.1 (2017-01-24) |
| 32 |
> Checking we can access the last sector of the filesystem |
| 33 |
> 0x41: Dirty bit is set. Fs was not properly unmounted and some data may be |
| 34 |
> corrupt. Automatically removing dirty bit. |
| 35 |
> Boot sector contents: |
| 36 |
> System ID "mkfs.fat" |
| 37 |
> Media byte 0xf8 (hard disk) |
| 38 |
> 512 bytes per logical sector |
| 39 |
> 4096 bytes per cluster |
| 40 |
> 32 reserved sectors |
| 41 |
> First FAT starts at byte 16384 (sector 32) |
| 42 |
> 2 FATs, 32 bit entries |
| 43 |
> 565248 bytes per FAT (= 1104 sectors) |
| 44 |
> Root directory start at cluster 2 (arbitrary size) |
| 45 |
> Data area starts at byte 1146880 (sector 2240) |
| 46 |
> 140520 data clusters (575569920 bytes) |
| 47 |
> 63 sectors/track, 255 heads |
| 48 |
> 2048 hidden sectors |
| 49 |
> 1126400 sectors total |
| 50 |
> Got 4096 bytes instead of 562088 at 16384 |
| 51 |
> |
| 52 |
> |
| 53 |
> |
| 54 |
> |
| 55 |
> thoughts? |
| 56 |
> |
| 57 |
> rgrds, |
| 58 |
> cm. |
| 59 |
> |
| 60 |
> Sent with ProtonMail Secure Email. |
| 61 |
|
| 62 |
You could try formatting the USB drive with -v -t and then monitor the logs to |
| 63 |
see if the errors persist. If the errors do not come back, then the problem |
| 64 |
is unlikely to have been caused by hardware faults. If they do, its time to |
| 65 |
destroy the USB drive (unless the data on it does not contain private |
| 66 |
information) and throw it away. |
Archives