Great thanks Lonnie. Just had me a little worried.

Regards
Michael Knill

On 7/4/20, 6:52 am, "Lonnie Abelbeck" <li...@lonnie.abelbeck.com> wrote:

    
    
    > On Apr 6, 2020, at 3:01 PM, Michael Knill 
<michael.kn...@ipcsolutions.com.au> wrote:
    > 
    > Hi Group
    >  
    > I'm surprised I haven’t seen this before on my APU’s (possibly other 
systems), but when an e2fsck disk check is forced on an unclean unmount (power 
reset), it actually needs to fix errors every time on all the systems I have 
tested e.g.:
    > ------
    > ASTURW was not cleanly unmounted, check forced.
    > 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
    > ASTURW: 2489/65536 files (0.7% non-contiguous), 70516/262144 blocks       
    
    > Fsck detected and repaired errors on /dev/sda2
    >  
    > ASTKD was not cleanly unmounted, check forced.
    > 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                                
     
    > Free blocks count wrong (14168129, counted=14168099).                     
    
    > Fix? yes
    >  
    > Free inodes count wrong (3635651, counted=3635632).                       
    
    > Fix? yes
    >  
    >  
    > ASTKD: ***** FILE SYSTEM WAS MODIFIED *****
    > ASTKD: 1616/3637248 files (0.6% non-contiguous), 354755/14522854 blocks
    > /dev/sda3 was checked and is now clean.
    > ---------
    >  
    > So my questions are:
    >   • Is this a bad thing or is it normal? Could a power reset actually 
cause a disk error?
    >   • Is there any way for this not to happen? Is it the type of mSATA I am 
using?
    >  
    > Thanks all.
    >  
    > Regards
    > Michael Knill
    
    Yes, that is normal from what I have seen, in fact whenever we upgrade the 
e2fsprogs package I power-cycle my APU2 test box and look for the e2fsck disk 
check response.
    
    The e2fsck check fix should never require human interaction.
    
    Possibly the type of mSATA SSD could make a difference.  No data to support 
that though.
    
    Lonnie
    
    
    
    
    
    _______________________________________________
    Astlinux-users mailing list
    Astlinux-users@lists.sourceforge.net
    https://lists.sourceforge.net/lists/listinfo/astlinux-users
    
    Donations to support AstLinux are graciously accepted via PayPal to 
pay...@krisk.org.


_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to 
pay...@krisk.org.

Reply via email to