Oops! My bad - the title said it: UEFI boot, but somehow I missed it. Same things comments, but since this not a USB drive, check the output of smartclt -a and run a few tests too. On a spinning disk the faults could be related to hard drive failure, or the SATA cable coming loose. Reseat the cable to see if the errors go away.
On Saturday, 21 March 2020 15:28:44 GMT Michael wrote: > On Saturday, 21 March 2020 13:49:04 GMT Caveman Al Toraboran wrote: > > questions: > > * what's going on? > > It looks as if your USB stick connector or its microcontroller is faulty. > There is also a smaller probability the USB port on the PC is playing up. > > > * how to find out? > > Look at dmesg -w and syslog for I/O errors. > > > * how to fix? > > If this is a hardware fault, check for dirty/oxidized contacts on the USB > connector and clean these as appropriate. If they look OK, try a different > USB port on the PC. > > > symptoms: > > * can't write (gives read/write error). > > * but files can get created and deleted. > > * newly created files, which also have failed writes > > > > have 0 bytes in them. > > > > * mount /dev/sda1 /boot is slow. > > * umount /boot is slow. > > > > cave ~ # fsck.vfat -v -a -w /dev/sda1 > > fsck.fat 4.1 (2017-01-24) > > Checking we can access the last sector of the filesystem > > 0x41: Dirty bit is set. Fs was not properly unmounted and some data may be > > corrupt. Automatically removing dirty bit. > > Boot sector contents: > > System ID "mkfs.fat" > > Media byte 0xf8 (hard disk) > > > > 512 bytes per logical sector > > > > 4096 bytes per cluster > > > > 32 reserved sectors > > > > First FAT starts at byte 16384 (sector 32) > > > > 2 FATs, 32 bit entries > > > > 565248 bytes per FAT (= 1104 sectors) > > > > Root directory start at cluster 2 (arbitrary size) > > Data area starts at byte 1146880 (sector 2240) > > > > 140520 data clusters (575569920 bytes) > > > > 63 sectors/track, 255 heads > > > > 2048 hidden sectors > > > > 1126400 sectors total > > > > Got 4096 bytes instead of 562088 at 16384 > > > > > > > > > > thoughts? > > > > rgrds, > > cm. > > > > Sent with ProtonMail Secure Email. > > You could try formatting the USB drive with -v -t and then monitor the logs > to see if the errors persist. If the errors do not come back, then the > problem is unlikely to have been caused by hardware faults. If they do, > its time to destroy the USB drive (unless the data on it does not contain > private information) and throw it away.
signature.asc
Description: This is a digitally signed message part.
