fsck errors for /home - is it safe to choose to 'Fix' ?

ratzi · April 12, 2014, 9:40pm

Hi all!

After having problems copying a few of the files from my home directory (EXT3) to an external hard disk (with NTFS),
I ran fsck.ext3 on my home drive.

I did get

host:~ # 
host:~ # 
host:~ # fsck.ext3 -n -f /dev/sda8
e2fsck 1.42.6 (21-Sep-2012)
Warning!  /dev/sda8 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
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
Block bitmap differences:  +15503307 -17508053
Fix? no

Free blocks count wrong for group #473 (23608, counted=23612).
Fix? no

Free blocks count wrong for group #534 (21431, counted=21434).
Fix? no

Free blocks count wrong for group #969 (23841, counted=23834).
Fix? no

Free blocks count wrong (27527017, counted=27801868).
Fix? no

Free inodes count wrong (10308961, counted=10335197).
Fix? no


home123: ********** WARNING: Filesystem still has errors **********

home123: 176799/10485760 files (6.3% non-contiguous), 14402711/41929728 blocks
host:~ # 
host:~ #

Now, would it be safe to choose to ‘Fix’ ?

Thanks in advance
Mike

hcvv · April 12, 2014, 10:24pm

As you must have seen, it warns you that /dev/sda8 is mounted. Thus there is no garantee that the remarks are valid.

Only fsck unmounted file systems.

nrickert · April 12, 2014, 10:27pm

It’s normal to see “fsck” problems on a mounted file system. To really check, you need to unmount. It may be easier to boot a live CD for the “fsck”, where nothing on your hard drive would be mounted.

ratzi · April 13, 2014, 12:35am

Thanks for your replies!

I tried to boot openSUSE 12.1 from the same HD,
which has a triple boot (openSUSE 12.3, openSUSE 12.1, windows 7) installed.

I was struck by the result:
openSUSE 12.1 still shows the startup messages,
and in this case the last ones were:

    77.729682] systemd_fsck[719]: fsck failed with error code 4.
Welcome to emergency mode.
Use "systemctl default" or ^D to activate default mode.
Give root password for login:

I wiped my eyes and tried another reboot with pretty much the same result.

I have used that /home of 12.1 as one location for backups of my /home of 12.3.

I still wonder if copying faulty files there may have caused the problem.

The hard disk is only about 2 years old.

So I formatted that /home partition of 12.1,
and booting 12.1 indeed worked afterwards - logging in as root.

Running fsck on the same partition of my current 12.3 as before I then get

HMiBri:~ # 
HMiBri:~ # 
HMiBri:~ # fsck.ext3 -n -f /dev/sda8
e2fsck 1.41.14 (22-Dec-2010)
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
home123: 150848/10485760 files (7.4% non-contiguous), 14129386/41929728 blocks
HMiBri:~ #                                                                                                                           
HMiBri:~ #

I’m puzzled.

How come the repeatable errors copying certain few (4-5) files from my /home of 12.3
to a backup drive?

Could they be due to the applications that created them

only 3 applications, as it seems for now:
(1) Thunderbird
(2) Acrobat Reader
(3) Firefox

Thanks again
Mike

nrickert · April 13, 2014, 1:37am

Passing “fsck” does not prove that there are no problems.

“fsck” checks the metadata (inodes, directory entries, free spaces, etc). It does not check whether every data sector is readable without error.

Have you run “smartctl” tests on the drive?

ratzi · April 13, 2014, 12:21pm

Hi again!

The original question in the title of the thread seems to be answered:
as I observed from the startup messages still displayed booting 12.1,
fsck is run automatically during startup without that the user is asked.

So it is “safe” to choose to ‘Fix’ running fsck,
because the errors found running fsck
will anyway be ‘fixed’ automatically by fsck during the next boot.
I dislike that!

Is there a way to change that behaviour?
I’d rather like fsck to warn about errors,
but not to ‘fix’ them silently.

Right …

I indeed may have to face the fact that my hard disk is failing.

I made 2 runs, the second run 5 hours after the first.
In that time the error count increased from 115 to 129.
Sh…!

The physical part of the hard disk that I’m usually working with
(I’m almost always runnung openSUSE 12.3),
however, is a small fraction of the total size (2TB) of the disk.

Hence the question,
of whether errors of ext3 on one partition can be exported to another partition
by copying files affected by ext3 errors?

I once saw such a kind of behaviour on an old MacOS (version 7 or 8).

Thanks again for your replies!
Mike

P.S.: I can not append the output of smartctl in this posting because the forum server complains:
Errors
The following errors occurred with your submission
The text that you have entered is too long (20904 characters). Please shorten it to 15000 characters long.

I’ll try to send a shortened version of the output in a separate posting.

ratzi · April 13, 2014, 12:42pm

Here’s the (shortened) smartctl output:

host:~ # smartctl -x /dev/sda
smartctl 6.0 2012-10-10 r3643 [x86_64-linux-3.7.10-1.28-desktop] (SUSE RPM)
Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Hitachi Deskstar 7K3000
Device Model:     Hitachi HDS723020BLA642
Serial Number:    MN3220F33TJJDE
LU WWN Device Id: 5 000cca 369f56d77
Firmware Version: MN6OA800
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 2.6, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Apr 13 02:11:51 2014 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM feature is:   Disabled
Rd look-ahead is: Enabled
Write cache is:   Enabled
ATA Security is:  Disabled, frozen [SEC2]

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x84) Offline data collection activity
                                        was suspended by an interrupting command from host.
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever                            
                                        been run.                                                         
Total time to complete Offline                                                                            
data collection:                (17953) seconds.                                                          
Offline data collection                                                                                   
capabilities:                    (0x5b) SMART execute Offline immediate.                                  
                                        Auto Offline data collection on/off support.                      
                                        Suspend Offline collection upon new                               
                                        command.                                                          
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine 
recommended polling time:        (   1) minutes.
Extended self-test routine
recommended polling time:        ( 300) minutes.
SCT capabilities:              (0x003d) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     PO-R--   100   100   016    -    0
  2 Throughput_Performance  P-S---   136   136   054    -    83
  3 Spin_Up_Time            POS---   137   137   024    -    405 (Average 429)
  4 Start_Stop_Count        -O--C-   100   100   000    -    2227
  5 Reallocated_Sector_Ct   PO--CK   100   100   005    -    44
  7 Seek_Error_Rate         PO-R--   100   100   067    -    0
  8 Seek_Time_Performance   P-S---   135   135   020    -    26
  9 Power_On_Hours          -O--C-   100   100   000    -    5720
 10 Spin_Retry_Count        PO--C-   100   100   060    -    0
 12 Power_Cycle_Count       -O--CK   100   100   000    -    2222
192 Power-Off_Retract_Count -O--CK   099   099   000    -    2227
193 Load_Cycle_Count        -O--C-   099   099   000    -    2227
194 Temperature_Celsius     -O----   166   166   000    -    36 (Min/Max 14/42)
196 Reallocated_Event_Count -O--CK   100   100   000    -    45
197 Current_Pending_Sector  -O---K   100   100   000    -    29
198 Offline_Uncorrectable   ---R--   100   100   000    -    0
199 UDMA_CRC_Error_Count    -O-R--   200   200   000    -    0
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
GP/S  Log at address 0x00 has    1 sectors [Log Directory]
... ((REST OF THIS LIST DELETED)) ...

SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
Device Error Count: 129 (device log contains only the most recent 4 errors)
        CR     = Command Register
        FEATR  = Features Register
        COUNT  = Count (was: Sector Count) Register
        LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
        LH     = LBA High (was: Cylinder High) Register    ]   LBA
        LM     = LBA Mid (was: Cylinder Low) Register      ] Register
        LL     = LBA Low (was: Sector Number) Register     ]
        DV     = Device (was: Device/Head) Register
        DC     = Device Control Register
        ER     = Error register
        ST     = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 129 [0] occurred at disk power-on lifetime: 5716 hours (238 days + 4 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 40 00 00 12 71 7e e0 02 00  Error: UNC 64 sectors at LBA = 0x12717ee0 = 309427936

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 00 00 00 40 00 00 12 71 7e e0 e0 08     03:28:58.189  READ DMA EXT
  35 00 00 04 00 00 00 24 96 d4 00 e0 08     03:28:58.186  WRITE DMA EXT
  35 00 00 04 00 00 00 24 96 d0 00 e0 08     03:28:58.183  WRITE DMA EXT
  35 00 00 04 00 00 00 24 96 cc 00 e0 08     03:28:58.180  WRITE DMA EXT
  35 00 00 04 00 00 00 24 96 c8 00 e0 08     03:28:58.177  WRITE DMA EXT

Error 128 [3] occurred at disk power-on lifetime: 5716 hours (238 days + 4 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 20 00 00 12 71 7e e0 02 00  Error: UNC 32 sectors at LBA = 0x12717ee0 = 309427936

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 00 00 00 40 00 00 12 71 7e c0 e0 08     03:28:55.114  READ DMA EXT
  35 00 00 04 00 00 00 24 96 2c 00 e0 08     03:28:55.111  WRITE DMA EXT
  35 00 00 04 00 00 00 24 96 28 00 e0 08     03:28:55.108  WRITE DMA EXT
  35 00 00 04 00 00 00 24 96 24 00 e0 08     03:28:55.105  WRITE DMA EXT
  35 00 00 04 00 00 00 24 96 20 00 e0 08     03:28:55.101  WRITE DMA EXT

Error 127 [2] occurred at disk power-on lifetime: 5716 hours (238 days + 4 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 01 28 00 00 12 71 7e e0 02 00  Error: UNC 296 sectors at LBA = 0x12717ee0 = 309427936

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 00 00 02 88 00 00 12 71 7d 80 e0 08     03:28:49.460  READ DMA EXT
  35 00 00 04 00 00 00 24 90 cf a8 e0 08     03:28:49.457  WRITE DMA EXT
  35 00 00 04 00 00 00 24 90 cb a8 e0 08     03:28:49.454  WRITE DMA EXT
  35 00 00 04 00 00 00 24 90 c7 a8 e0 08     03:28:49.450  WRITE DMA EXT
  35 00 00 04 00 00 00 24 90 c3 a8 e0 08     03:28:49.447  WRITE DMA EXT

Error 126 [1] occurred at disk power-on lifetime: 5716 hours (238 days + 4 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 3e 00 00 12 53 85 82 02 00  Error: UNC 62 sectors at LBA = 0x12538582 = 307463554

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 00 00 00 40 00 00 12 53 85 80 e0 08     03:14:57.151  READ DMA EXT
  35 00 00 04 00 00 00 1f b7 61 f8 e0 08     03:14:57.150  WRITE DMA EXT
  35 00 00 04 00 00 00 1f b7 65 f8 e0 08     03:14:57.053  WRITE DMA EXT
  35 00 00 00 10 00 00 1f b7 6a 00 e0 08     03:14:57.053  WRITE DMA EXT
  35 00 00 00 60 00 00 1f b7 6b 80 e0 08     03:14:57.053  WRITE DMA EXT

SMART Extended Self-test Log Version: 1 (1 sectors)
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

SCT Status Version:                  3
SCT Version (vendor specific):       256 (0x0100)
SCT Support Level:                   1
Device State:                        SMART Off-line Data Collection executing in background (4)
Current Temperature:                    36 Celsius
Power Cycle Min/Max Temperature:     36/37 Celsius
Lifetime    Min/Max Temperature:     14/42 Celsius
Under/Over Temperature Limit Count:   0/0
SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        1 minute
Min/Max recommended Temperature:      0/60 Celsius
Min/Max Temperature Limit:           -40/70 Celsius
Temperature History Size (Index):    128 (69)

Index    Estimated Time   Temperature Celsius
... ((DELETED SOME ENTRIES HERE)) ...
  51    2014-04-13 01:53    36  *****************
  52    2014-04-13 01:54    37  ******************
  53    2014-04-13 01:55    37  ******************
  54    2014-04-13 01:56    36  *****************
 ...    ..( 14 skipped).    ..  *****************
  69    2014-04-13 02:11    36  *****************

SCT Error Recovery Control:
           Read: Disabled
          Write: Disabled

Device Statistics (GP Log 0x04)
Page Offset Size         Value  Description
  1  =====  =                =  == General Statistics (rev 1) ==
  1  0x008  4             2222  Lifetime Power-On Resets
  1  0x010  4             5720  Power-on Hours
  1  0x018  6       6542822979  Logical Sectors Written
  1  0x020  6         65190689  Number of Write Commands
  1  0x028  6       9073609759  Logical Sectors Read
  1  0x030  6        116542489  Number of Read Commands
  3  =====  =                =  == Rotating Media Statistics (rev 1) ==
  3  0x008  4             5711  Spindle Motor Power-on Hours
  3  0x010  4             5711  Head Flying Hours
  3  0x018  4             2227  Head Load Events
  3  0x020  4               44  Number of Reallocated Logical Sectors
  3  0x028  4             3133  Read Recovery Attempts
  3  0x030  4                7  Number of Mechanical Start Failures
  4  =====  =                =  == General Errors Statistics (rev 1) ==
  4  0x008  4              129  Number of Reported Uncorrectable Errors
  4  0x010  4                1  Resets Between Cmd Acceptance and Completion
  5  =====  =                =  == Temperature Statistics (rev 1) ==
  5  0x008  1               36  Current Temperature
  5  0x010  1               34~ Average Short Term Temperature
  5  0x018  1               32~ Average Long Term Temperature
  5  0x020  1               42  Highest Temperature
  5  0x028  1               14  Lowest Temperature
  5  0x030  1               39~ Highest Average Short Term Temperature
  5  0x038  1               25~ Lowest Average Short Term Temperature
  5  0x040  1               37~ Highest Average Long Term Temperature
  5  0x048  1               25~ Lowest Average Long Term Temperature
  5  0x050  4                0  Time in Over-Temperature
  5  0x058  1               60  Specified Maximum Operating Temperature
  5  0x060  4                0  Time in Under-Temperature
  5  0x068  1                0  Specified Minimum Operating Temperature
  6  =====  =                =  == Transport Statistics (rev 1) ==
  6  0x008  4             4822  Number of Hardware Resets
  6  0x010  4             2600  Number of ASR Events
  6  0x018  4                0  Number of Interface CRC Errors
                              |_ ~ normalized value

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x0009  2            3  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2            3  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x000d  2            0  Non-CRC errors within host-to-device FIS

host:~ #

hcvv · April 13, 2014, 12:44pm

No it is not save in the situation you posted because it is mounted! You seem to fail to understand that you van not check the consistancy of something that is in use and that may be changing constantly. fsck will then find false problems, that will probably be different next millisecond. And when it then goes and “repairs” things, it will possibly damage beyonf repair.

The fsck at boot is of course done before the fs is mounted.

ratzi · April 13, 2014, 4:25pm

Hi Henk!

[quote="“hcvv,post:8,topic:99586”]

No it is not save in the situation you posted because it is mounted! You seem to fail to understand that you van not check the consistancy of something that is in use and that may be changing constantly. fsck will then find false problems, that will probably be different next millisecond. And when it then goes and “repairs” things, it will possibly damage beyonf repair.[/QUOTE]

You’re right.
One can easily shoot the complete file system doing it the wrong way.

You mean the fs of /home?
That would be a convenient way to do it.

On the other hand, what if there’s no separate /home ?

The fs of / must be mounted before boot, I would say,
because otherwise not even the kernel could be read.

However, the point that I wanted to make is
that I dislike that fsck is run silently!
There isn’t any notification that fsck is fixing things on /home
while booting 64bit openSUSE 12.3 on my core i5-2500 PC.

This was different for older versions of openSUSE
when installed on ReiserFS partitions.
In these cases I at least got a lot of ‘journal replayed’ messages during boot
if the system hadn’t been shut down properly beforehand.

Particularly with respect to changes of the file system I prefer
to at least get noticed about what’s going on!

To get a list of the files affected by the fsck fixes would be very, very helpful.

A prompt asking if booting should be continued including fsck fixes
or if booting should be aborted (in order to be able to boot from another device)
would even be better.

Best wishes
Mike

nrickert · April 13, 2014, 4:35pm

The way it actually works, is that “/” is initially mounted read-only. And then “fsck” is done. And only then is it remounted read-write.

The “fsck” during boot will only correct minor errors. If there are major errors, you will find yourself in an emergency repari session and having to do “fsck” manually. (Been there, done that). If the problem is on the root file system, it will still be mounted read-only for the emergency session. And, after you have done the fixing, you have to reboot. You cannot continue to a normal boot.

The kind of minor errors that “fsck” will fix without asking, are the problems that occur when you power off the computer without a clean shutdown. And, even in the power-off situation, you will occasionally get errors that “fsck” will not automatically fix.

If I power-off without clean shutdown (not recommended, by the way), and watch the startup screen, I will usually see a report about writing journal entries to file system (for “/” and “/home”), and details of what was fixed for “/boot” where I don’t use journaling.

hcvv · April 13, 2014, 5:39pm

fsck before mounting at boot is not “a convenient way to do it”. It is done so for ages. It is part of the boot sequence.

Because the system is not as stupid programmed as you seem to think. The general rule is of course: eevry fs that should be mounted at boot, because /etc/fstab says so, is first fsck’ed. So no entry for /home, then no fsck and no mount.

No, it is not. GRUB reads the kernel from the partition because it is told so in the boot configuration. Grub knows enough of the file system type used (and that explains why not all file system types are fit for this and sometimes people have to revert to a separate /boot partition) to find the kernel.

Somewhat later (when the kernel has the appropriate fs dribers loaded) the root file system is mounted read-only to be able to load a lot of stuff. Because of it being mounted read-only, an fsck can be done (and is done). Then the root file system will be re-mounted writable.

This is all nice to know (and it works like that for about 30 - 40 years), but it is far off topic IMHO.
The topic being (again IMHO) that you, for some reason, try to fsck a file system. You did it wrong and we explained you how to do it correct.

About your quest to meddle around with the fsck part of the boot process, my advice is not to change anything there before you have an in depth knowledge about the boot process, and the internals of file systems and what can go wrong there.

And this is from my /var/log/boot…log:

fsck from util-linux 2.23.2
[/sbin/fsck.ext4 (1) -- /] fsck.ext4 -a /dev/sda2
System_A: clean, 168117/1313280 files, 1483970/5242880 blocks
fsck succeeded. Mounting root device read-write.
Mounting root /dev/root
mount -o rw,acl,user_xattr -t ext4 /dev/root /root

And this is later on when it comes to mounting my other file systems:

systemd-fsck[420]: Home_A: clean, 57156/6094848 files, 13768466/24352531 blocks
^[32m  OK  ^[[0m] Activated swap /dev/disk/by-id/ata-Hitachi_HDT725032VLA380_VFJ201R23XUEXW-part1.
^[32m  OK  ^[[0m] Reached target Swap.
^[32m  OK  ^[[0m] Started File System Check on /dev/disk/by-id/ata-Hitachi_HDT725032VLA380_VFJ201R23XUEXW-part3.
         Mounting /home...
^[32m  OK  ^[[0m] Found device Hitachi_HDT725032VLA380.
         Starting File System Check on /dev/disk/by-id/ata-Hitachi_HDT725032VLA380_VFJ201R23XUEXW-part6...
^[32m  OK  ^[[0m] Mounted /home.
^[32m  OK  ^[[0m] Found device Hitachi_HDT725032VLA380.
         Starting File System Check on /dev/disk/by-id/ata-Hitachi_HDT725032VLA380_VFJ201R23XUEXW-part5...
systemd-fsck[426]: Home_B: clean, 55796/6553600 files, 18259908/26214055 blocks
^[32m  OK  ^[[0m] Started File System Check on /dev/disk/by-id/ata-Hitachi_HDT725032VLA380_VFJ201R23XUEXW-part6.
systemd-fsck[433]: System_B: clean, 163320/1313280 files, 1487704/5242880 blocks

I can assure yoou that any warnings and/or arrors and/or error reporst will be thre when applicable. Thus when want to inspect that after a boot, you are free to do so.

ratzi · April 13, 2014, 6:27pm

Hi Henk!

Hmm, not fully true:
I looked at the man pages before running fsck.ext3,
and as a result, I used the fsck.ext3 option -n (see 1st post),
in order not to have any changes taking effect!

Then I posted here.

which I greatly appreciate!

Greets
Mike

robin_listas · April 13, 2014, 6:53pm

On 2014-04-13 17:46, hcvv wrote:
> I can assure yoou that any warnings and/or arrors and/or error reporst
> will be thre when applicable. Thus when want to inspect that after a
> boot, you are free to do so.

By the way, this is an improvement provided by systemd. With system V,
fsck activity during boot is not logged, because there is no filesystem
to write it to.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)