LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 07-16-2017, 07:27 AM   #1
cmk77
Member
 
Registered: May 2006
Location: netherlands
Distribution: slackware, centos, scientificlinux
Posts: 122

Rep: Reputation: 24
efi boot partition not properly unmounted


Recently, I've upgraded to slackware64-14.2 and decided to try efi booting for educational purposes, even though this box runs no other os. And it's working fine.

However, during shutdown, a message passes by saying something like "/dev/sda1 is succesfully unmounted", although I can't find this message in any of the /var/logs. Yet after (re)booting:
Code:
bash-4.3# dmesg | grep sda1
[    3.441534]  sda: sda1 sda2 sda3
[    8.592349] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Any idea what's wrong here? So far I seem to be getting away ignoring this, but it doesn't feel good.
 
Old 07-16-2017, 07:57 AM   #2
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2 on Lenovo Thinkpad W520
Posts: 7,621

Rep: Reputation: 2558Reputation: 2558Reputation: 2558Reputation: 2558Reputation: 2558Reputation: 2558Reputation: 2558Reputation: 2558Reputation: 2558Reputation: 2558Reputation: 2558
To check for a possible corruption, umount /dev/sda1 and run as root:
Code:
fsck.vfat -nvV /dev/sda1
 
Old 07-16-2017, 08:44 AM   #3
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 15,799

Rep: Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158
I see issues like this on my ARM (pi3) systems - not x86_64 tho'.
My attitude is "who cares" as it's such an old,flaky filesystem. How often does it get updated ?. Why would I care ?.
Let the boot fsck deal with it. Get on with life.
 
Old 07-16-2017, 12:39 PM   #4
cmk77
Member
 
Registered: May 2006
Location: netherlands
Distribution: slackware, centos, scientificlinux
Posts: 122

Original Poster
Rep: Reputation: 24
Here's what fsck says:
Code:
bash-4.3# fsck.vfat -nvV /dev/sda1
fsck.fat 3.0.28 (2015-05-16)
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
      1024 bytes per cluster
        32 reserved sectors
First FAT starts at byte 16384 (sector 32)
         2 FATs, 32 bit entries
    406528 bytes per FAT (= 794 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 829440 (sector 1620)
    101590 data clusters (104028160 bytes)
63 sectors/track, 255 heads
      2048 hidden sectors
    204800 sectors total
Starting check/repair pass.
Checking for unused clusters.
Checking free cluster summary.
Starting verification pass.
Checking for unused clusters.
Leaving filesystem unchanged.
/dev/sda1: 7 files, 10548/101590 clusters
 
Old 07-16-2017, 12:51 PM   #5
laprjns
Member
 
Registered: Oct 2005
Location: Connecticut USA
Distribution: SalixOS
Posts: 99

Rep: Reputation: 51
I believe you can safely ignore it. I get the same message on my system:
Code:
rich[log]$ sudo dmesg | grep sda1
[    3.575398]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda8 sda9 sda10
[   24.719752] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
here what fsck says:
Code:
rich[log]$ sudo fsck.vfat -nvV /dev/sda1
fsck.fat 3.0.28 (2015-05-16)
Checking we can access the last sector of the filesystem
0x25: 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
      8192 bytes per cluster
         1 reserved sector
First FAT starts at byte 512 (sector 1)
         2 FATs, 16 bit entries
     81920 bytes per FAT (= 160 sectors)
Root directory starts at byte 164352 (sector 321)
       512 root directory entries
Data area starts at byte 180736 (sector 353)
     38377 data clusters (314384384 bytes)
63 sectors/track, 255 heads
      2048 hidden sectors
    614400 sectors total
Starting check/repair pass.
Checking for unused clusters.
Starting verification pass.
Checking for unused clusters.
Leaving filesystem unchanged.
/dev/sda1: 338 files, 25705/38377 clusters
 
Old 07-16-2017, 01:03 PM   #6
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2 on Lenovo Thinkpad W520
Posts: 7,621

Rep: Reputation: 2558Reputation: 2558Reputation: 2558Reputation: 2558Reputation: 2558Reputation: 2558Reputation: 2558Reputation: 2558Reputation: 2558Reputation: 2558Reputation: 2558
Well, files in the ESP are only written by eliloconfig or by the user to edit elilo.conf or copy kernels or initrd, so I think that the risks of corruption are slim.

It wouldn't hurt to include in the mount command the flush option though, and possibly discard in case the device is a SSD.
 
Old 07-16-2017, 01:19 PM   #7
cmk77
Member
 
Registered: May 2006
Location: netherlands
Distribution: slackware, centos, scientificlinux
Posts: 122

Original Poster
Rep: Reputation: 24
What puzzles me is that the shutdown message says "successfully unmounted". Yes, the device is an SSD, I'll look into those options.
 
Old 07-16-2017, 01:39 PM   #8
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2 on Lenovo Thinkpad W520
Posts: 7,621

Rep: Reputation: 2558Reputation: 2558Reputation: 2558Reputation: 2558Reputation: 2558Reputation: 2558Reputation: 2558Reputation: 2558Reputation: 2558Reputation: 2558Reputation: 2558
Even simpler, comment out the line in /etc/fstab that mounts the ESP or add the noauto option then mount/umount it manually only when necessary, i.e. to run eliloconfig or modify files in it. And you don't need to mount if to run manually efibootmgr, but maybe to check your command's arguments (this is an assumption, I didn't try).

PS and OT:
Code:
63 sectors/track, 255 heads
I always find funny this legacy addressing for USB sticks and SSD

Last edited by Didier Spaier; 07-16-2017 at 02:54 PM.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Resizing the ESP /boot/efi partition RoqueOne Linux - Newbie 19 07-03-2017 09:55 PM
resize efi question [/boot/efi] with boot flag gparted mtdew3q Fedora 4 03-19-2017 10:02 PM
Is it good idea to have EFI partition mounted as /boot ? froff Linux - General 3 05-08-2015 07:20 PM
[SOLVED] How to recreate EFI boot partition? smokn Linux - Software 10 07-21-2013 02:21 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 01:12 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration