• ant: clean on boot up


    Hi, during the boot sequence, after grub but before logging in, my machine (thinkpad x240) briefly shows the message

    ant: clean. 217782/2260992 files, 241337
    

    googling just leads to java compilation, obviously nothing to do with boot-up!

    is this ‘ant’ an antergos thing?

    what does it mean?
    can i fix it?

    everything seems to work okay, it just seems to slow my boot by a few milliseconds.

    thanks in advance

  • @mickey-megabyte said in ant: clean on boot up:

    java compilation

    do you have such installed? any java stuff games… tools e.t.c.

    [updates once a week] = [90% less problems]
    antergos:_rescue
    how to add system logs:
    wget http://bit.ly/2GCG9k2 && sh 2GCG9k2
    :handshake: donate antergos

  • @joekamprad no, i’ve never had any java packages at all on this machine, not even a jdk

    i’m pretty sure it’s nothing to do with java - it wouldn’t be giving me messages before i log-in…

    i’ve also got an ubuntu partition, and i don’t see this ‘ant’ message when i boot into that.

    i simply jumped to the conclusion that ‘ant’ is an antergos thing, but maybe not?

  • Ha Ha you are forcing me to see an issue here …

    This is the strandard filesystem check at boot… and “ant” is the name of your disk
    It will look like this if filesystem is unclean:
    0_1529249798537_unclean.png

    [updates once a week] = [90% less problems]
    antergos:_rescue
    how to add system logs:
    wget http://bit.ly/2GCG9k2 && sh 2GCG9k2
    :handshake: donate antergos

  • @joekamprad great - i appreciate your help

    ** goes off to google about cleaning filesystems… **

    ☺

    i’ll mark it solved once i’ve fixed it

    thanks!

  • @mickey-megabyte
    Yes, you can see the disk label “ant” e.g. with gparted under Label.
    True, name “ant” it was a bit misleading… 🙂

    Please report issues including all details! ;-)
    Show files here: cat "file" | curl -F [email protected] https://ptpb.pw/?u=1
    and show the URL here.

  • @mickey-megabyte fix is to rename disk with something like:

    “filesystemcheck”

    👉

    [updates once a week] = [90% less problems]
    antergos:_rescue
    how to add system logs:
    wget http://bit.ly/2GCG9k2 && sh 2GCG9k2
    :handshake: donate antergos

  • @joekamprad
    But preferably not to: FatalError 👻
    Might be even more misleading.
    But off-topic aside, great that the reason was found. 🙂

    Please report issues including all details! ;-)
    Show files here: cat "file" | curl -F [email protected] https://ptpb.pw/?u=1
    and show the URL here.

  • @joekamprad

    ok, so i booted into a live usb, and tried fsck to fix it

    [[email protected] ~]$ fsck -c /dev/sda3
    fsck from util-linux 2.32
    e2fsck 1.44.1 (24-Mar-2018)
    Checking for bad blocks (read-only test):   0.00% done, 0:00 elapsed. (0/0done                                                 
    ant: Updating bad block inode.
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information
    
    ant: ***** FILE SYSTEM WAS MODIFIED *****
    ant: 218862/2260992 files (0.8% non-contiguous), 2419000/9036032 blocks
    
    [[email protected] ~]$ fsck /dev/sda3
    fsck from util-linux 2.32
    e2fsck 1.44.1 (24-Mar-2018)
    ant: clean, 218862/2260992 files, 2419000/9036032 blocks
    
    [[email protected] ~]$ fsck /dev/sda3
    fsck from util-linux 2.32
    e2fsck 1.44.1 (24-Mar-2018)
    ant: clean, 218862/2260992 files, 2419000/9036032 blocks
    
    [[email protected] ~]$ fsck -cvp /dev/sda3
    fsck from util-linux 2.32
    ant: Updating bad block inode.
    
          218862 inodes used (9.68%, out of 2260992)
            1691 non-contiguous files (0.8%)
             117 non-contiguous directories (0.1%)
                 # of inodes with ind/dind/tind blocks: 0/0/0
                 Extent depth histogram: 186551/133
         2419000 blocks used (26.77%, out of 9036032)
               0 bad blocks
               1 large file
    
          169282 regular files
           15622 directories
               0 character device files
               0 block device files
               0 fifos
            2412 links
           33943 symbolic links (32164 fast symbolic links)
               6 sockets
    ------------
          221265 files
    
    [[email protected] ~]$ fsck /dev/sda3
    fsck from util-linux 2.32
    e2fsck 1.44.1 (24-Mar-2018)
    ant: clean, 218862/2260992 files, 2419000/9036032 blocks
    
    [[email protected] ~]$ fsck /dev/sda3
    fsck from util-linux 2.32
    e2fsck 1.44.1 (24-Mar-2018)
    estragon: clean, 218862/2260992 files, 2419000/9036032 blocks
    

    as you can see, the problem still remains even after filesystemcheck and renaming to estragon!

    should i clone my antergos install to a new partition?
    or will this clone the errors too?

  • no issue, the check on filesystems will be proceeded on every bood to check if filesystem is clean and if not to invoke to check for orphaned inodes. so if it shows “clean” nothing is wrong.
    It is shown on every Antergos and arch install as usual on bootup…

    [updates once a week] = [90% less problems]
    antergos:_rescue
    how to add system logs:
    wget http://bit.ly/2GCG9k2 && sh 2GCG9k2
    :handshake: donate antergos

  • ok thanks - i wrongly assumed it was some sort of error message.

    i am trying to get a completely silent ‘tidy’ clean boot, following some ideas from the Arch wiki.

    this is the only thing getting in the way of my dream.

    i’ll guess i’ll have to close my eyes for a few seconds while the system boots 😖

    thanks again SOLVED

boot255 clean5 ant1 Posts 12Views 283
Log in to reply
Bloom Email Optin Plugin

Looks like your connection to Antergos Community Forum was lost, please wait while we try to reconnect.