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