Error /dev/sda1...

[simone]

Hi, I have a problem at start of the two PC with installed Salixos. It gives me this error:

FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

Code: Select all

simone[~]$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 465,8G  0 disk 
├─sda1   8:1    0   300M  0 part /boot/efi
├─sda2   8:2    0   512M  0 part [SWAP]
└─sda3   8:3    0   465G  0 part /
sr0     11:0    1  1024M  0 rom  

simone[~]$ sudo fdisk -l
Disk /dev/ram0: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram1: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram2: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram3: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram4: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram5: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram6: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram7: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram8: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram9: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram10: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram11: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram12: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram13: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram14: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram15: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sda: 465,8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: C0788C50-B0DE-4143-B40A-BB9B8A03818D

Dispositivo   Start      Fine   Settori  Size Tipo
/dev/sda1      2048    616447    614400  300M EFI System
/dev/sda2    616448   1665023   1048576  512M Linux swap
/dev/sda3   1665024 976773134 975108111  465G Linux filesystem


simone[~]$ sudo dmesg | grep corrupt
[   18.600591] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

simone[~]$ sudo fsck.vfat -v -a -w /dev/sda1
fsck.fat 3.0.28 (2015-05-16)
Checking we can access the last sector of the filesystem
Seek to 536870400:Argomento non valido

What may have happened?

Thanks

[mimosa]

I see this too, and without having got to the bottom of it, I suspect it is not a big deal. In my case, as in yours, that partition is /boot.

In order to check/repair the filesystem, it needs to be unmounted.

Again in my case, running it without the -a switch, the errors are trivial. I selected to take no action.

[simone]

Code: Select all

simone[~]$ sudo umount /dev/sda1

simone[~]$ sudo fsck.vfat /dev/sda1
fsck.fat 3.0.28 (2015-05-16)
Seek to 536870400:Invalid argument

you, the computers boot, it was only to understand ...

[mimosa]

A little searching suggests this "Invalid argument" message may be a bug with fsck for dos filesystems. However, it is possible something is up with your partitions - but if the only sign of it is that message about "not properly unmounted", I think there is probably nothing to worry about.

[laprjns]

Appears to be a nuisance message;

Code: Select all

rich[log]$ sudo grep "properly" syslog syslog.1 syslog.2 syslog.3 syslog.4
syslog.2:Feb  6 19:25:49 rich-laptop kernel: [   21.388795] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
syslog.2:Feb 12 08:50:52 rich-laptop kernel: [   20.576333] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
syslog.2:Feb 12 09:00:29 rich-laptop kernel: [   20.976619] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
syslog.2:Feb 12 09:20:39 rich-laptop kernel: [   21.076571] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
syslog.2:Feb 12 10:17:11 rich-laptop kernel: [   20.665720] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
syslog.4:Jan 22 13:08:39 rich-laptop kernel: [   20.798911] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
syslog.4:Jan 22 14:20:18 rich-laptop kernel: [   20.564937] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
syslog.4:Jan 22 17:57:27 rich-laptop kernel: [13050.790168] FAT-fs (sdb2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
syslog.4:Jan 22 18:18:10 rich-laptop kernel: [14294.132299] FAT-fs (sdc2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
syslog.4:Jan 23 05:48:08 rich-laptop kernel: [   20.753552] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
syslog.4:Jan 24 19:40:21 rich-laptop kernel: [   21.242383] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
syslog.4:Jan 29 16:51:06 rich-laptop kernel: [421852.705240] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.