odroid xu4 / hc1: fsck ! works at boot


Recommended Posts

Quote

Hi I have flashed an armbian 4.14 on µsd & switch system on a ssd sandisk 120Gb with nand-sata-install which works fine.
I try without success to do a fsck on boot on mmcblk &  sda, only mmcblk is checked, not /dev/sda1, however all seems fine.
Below config used and armbian log zipped.
Any help would be appeciated

Quote


dmesg extract
-------------
[    0.000000] Booting Linux on physical CPU 0x100
[    0.000000] Linux version 4.14.176-odroidxu4 (root@ubuntu4armbian) (gcc version 7.4.1 20181213 [linaro-7.4-2019.02 revision 56ec6f6b99cc167ff0c2f8e1a2eed33b1edc85d4] (Linaro GCC 7.4-2019.02)) #15 SMP PREEMPT Wed Apr 15 08:03:33 CEST 2020
[    0.000000] CPU: ARMv7 Processor [410fc073] revision 3 (ARMv7), cr=50c5387d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: Hardkernel Odroid XU4
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] cma: Reserved 128 MiB at 0xb6800000
[    0.000000] Samsung CPU ID: 0xe5422001

root@SVRLOC-IQB:/var/log# dmesg | grep mmcblk
[   15.339553] mmcblk1: mmc1:1234 SA16G 14.4 GiB
[   15.340824]  mmcblk1: p1
[   25.691854] EXT4-fs (mmcblk1p1): mounted filesystem with writeback data mode. Opts: commit=600,errors=remount-ro

root@SVRLOC-IQB:/var/log# dmesg | grep sda
[   16.705101] sd 0:0:0:0: [sda] 234455040 512-byte logical blocks: (120 GB/112 GiB)
[   16.705111] sd 0:0:0:0: [sda] 4096-byte physical blocks
[   16.705338] sd 0:0:0:0: [sda] Write Protect is off
[   16.705347] sd 0:0:0:0: [sda] Mode Sense: 53 00 00 08
[   16.705801] sd 0:0:0:0: [sda] Disabling FUA
[   16.705811] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   16.706294] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
[   16.709480]  sda: sda1
[   16.714168] sd 0:0:0:0: [sda] Attached SCSI disk
[   18.934347] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[   19.815763] EXT4-fs (sda1): re-mounted. Opts: commit=600,errors=remount-ro

root@SVRLOC-IQB:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 10 (buster)
Release:        10
Codename:       buster

root@SVRLOC-IQB:~# uname -a
Linux SVRLOC-IQB 4.14.176-odroidxu4 #15 SMP PREEMPT Wed Apr 15 08:03:33 CEST 2020 armv7l GNU/Linux


root@SVRLOC-IQB:/var/log# cat /etc/fstab
# <file system>                                 <mount point>   <type>  <options>                                                       <dump>  <pass>
tmpfs                                           /tmp            tmpfs   defaults,nosuid                                                 0       0
UUID=87887d05-2ce6-4959-a4ba-59d7ed36e7c1       /media/mmcboot  ext4    defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide    0       1
/media/mmcboot/boot                             /boot           none    bind                                                            0       0
UUID=b86978b6-aac1-4547-9a2d-378e6b69dd9e       /               ext4    defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide    0       1

root@SVRLOC-IQB:/var/log# lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda           8:0    0 111.8G  0 disk
└─sda1        8:1    0 111.8G  0 part /
mmcblk1     179:0    0  14.4G  0 disk
└─mmcblk1p1 179:1    0  14.3G  0 part /media/mmcboot
zram0       253:0    0    50M  0 disk /var/log
zram1       253:1    0   998M  0 disk [SWAP]

root@SVRLOC-IQB:/var/log# blkid
/dev/mmcblk1p1: UUID="87887d05-2ce6-4959-a4ba-59d7ed36e7c1" TYPE="ext4" PARTUUID="639d21b3-01"
/dev/zram0: LABEL="log2ram" UUID="e9451ae1-a82b-4976-b4f3-74aeb892a5da" TYPE="ext4"
/dev/mmcblk1: PTUUID="639d21b3" PTTYPE="dos"
/dev/sda1: UUID="b86978b6-aac1-4547-9a2d-378e6b69dd9e" TYPE="ext4" PARTUUID="47d60e09-01"
/dev/zram1: UUID="63d9f06e-ea12-4679-afb5-6c86e66cb6f1" TYPE="swap"

root@SVRLOC-IQB:/var/log# mount | grep /dev/
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
/dev/sda1 on / type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600,data=ordered)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
mqueue on /dev/mqueue type mqueue (rw,relatime)
/dev/mmcblk1p1 on /media/mmcboot type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600,x-gvfs-hide)
/dev/mmcblk1p1 on /boot type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600)
/dev/sda1 on /var/log.hdd type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600,data=ordered)
/dev/zram0 on /var/log type ext4 (rw,relatime,discard)


root@SVRLOC-IQB:/var/log# dmesg | grep /dev/disk
[   25.636241] systemd[1]: Started File System Check on /dev/disk/by-uuid/87887d05-2ce6-4959-a4ba-59d7ed36e7c1.

root@SVRLOC-IQB:/var/log# grep /dev/disk/ *
armbian-hardware-monitor.log:[   25.910551] systemd[1]: Started File System Check on /dev/disk/by-uuid/87887d05-2ce6-4959-a4ba-59d7ed36e7c1.
armbian-hardware-monitor.log:[   24.612965] systemd[1]: Started File System Check on /dev/disk/by-uuid/87887d05-2ce6-4959-a4ba-59d7ed36e7c1.
armbian-hardware-monitor.log:[   26.166894] systemd[1]: Started File System Check on /dev/disk/by-uuid/87887d05-2ce6-4959-a4ba-59d7ed36e7c1.
armbian-hardware-monitor.log:[   24.898750] systemd[1]: Started File System Check on /dev/disk/by-uuid/87887d05-2ce6-4959-a4ba-59d7ed36e7c1.
armbian-hardware-monitor.log:[   25.636241] systemd[1]: Started File System Check on /dev/disk/by-uuid/87887d05-2ce6-4959-a4ba-59d7ed36e7c1.

root@SVRLOC-IQB:/var/log# grep systemd-fsck syslog
syslog:Apr 22 11:47:18 localhost systemd-fsck[317]: /dev/mmcblk1p1: Superblock last write time is in the future.
syslog:Apr 22 11:47:18 localhost systemd-fsck[317]: #011(by less than a day, probably due to the hardware clock being incorrectly set)
syslog:Apr 22 11:47:18 localhost systemd-fsck[317]: /dev/mmcblk1p1 has been mounted 1 times without being checked, check forced.
syslog:Apr 22 11:47:18 localhost systemd-fsck[317]: /dev/mmcblk1p1: 44867/920000 files (0.1% non-contiguous), 356440/3745832 blocks
syslog:Apr 22 11:47:43 localhost systemd[1]: systemd-fsckd.service: Succeeded.


root@SVRLOC-IQB:/var/log# cat /run/initramfs/fsck.log
Log of fsck -C -a -V -t ext4 /dev/sda1
Sat Jan  1 00:00:25 2000
fsck from util-linux 2.33.1
[/sbin/fsck.ext4 (1) -- /dev/sda1] fsck.ext4 -a -C0 /dev/sda1
/dev/sda1 has been mounted 1 times without being checked, check forced.
/dev/sda1: 44858/7331840 files (0.1% non-contiguous), 892892/29306624 blocks

Sat Jan  1 00:00:26 2000
----------------

root@SVRLOC-IQB:/var/log# tune2fs -l /dev/sda1
tune2fs 1.44.5 (15-Dec-2018)
Filesystem volume name:   <none>
Last mounted on:          /root
Filesystem UUID:          b86978b6-aac1-4547-9a2d-378e6b69dd9e
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery extent 64bit flex_bg sparse_super large_file huge_file dir_nlink extra_isize metadata_csum
Filesystem flags:         unsigned_directory_hash
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              7331840
Block count:              29306624
Reserved block count:     1465331
Free blocks:              28413732
Free inodes:              7286982
First block:              0
Block size:               4096
Fragment size:            4096
Group descriptor size:    64
Reserved GDT blocks:      1024
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Flex block group size:    16
Filesystem created:       Mon Apr 20 12:30:11 2020
Last mount time:          Sat Jan  1 01:00:26 2000
Last write time:          Sat Jan  1 01:00:26 2000
Mount count:              1
Maximum mount count:      1
Last checked:             Mon Apr 20 12:30:11 2020
Check interval:           0 (<none>)
Lifetime writes:          2691 MB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Required extra isize:     32
Desired extra isize:      32
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      ae131f81-b92d-4507-a9ba-e18d4a038750
Journal backup:           inode blocks
Checksum type:            crc32c
Checksum:                 0x8c28e750

root@SVRLOC-IQB:/var/log# grep 87887d05 *
armbian-hardware-monitor.log:[   25.636241] systemd[1]: Started File System Check on /dev/disk/by-uuid/87887d05-2ce6-4959-a4ba-59d7ed36e7c1.
armbian-hardware-monitor.log:└─mmcblk1p1 ext4    14.3G /media/mmcboot 87887d05-2ce6-4959-a4ba-59d7ed36e7c1
kern.log:Apr 20 12:04:37 localhost kernel: [    0.000000] Kernel command line: console=ttySAC2,115200n8 console=tty1 consoleblank=0 loglevel=1 root=UUID=87887d05-2ce6-4959-a4ba-59d7ed36e7c1 rootfstype=ext4 rootwait rw  smsc95xx.macaddr=00:1e:06:61:7a:55 governor=performance hdmi_tx_amp_lvl=31 hdmi_tx_lvl_ch0=3 hdmi_tx_lvl_ch1=3 hdmi_tx_lvl_ch2=3 hdmi_tx_emp_lvl=6 hdmi_clk_amp_lvl=31 hdmi_tx_res=0 HPD=true vout=hdmi usb-storage.quirks=  s5p_mfc.mem=16M

root@SVRLOC-IQB:/var/log# grep b86978b6 *
armbian-hardware-monitor.log:[    0.000000] Kernel command line: console=ttySAC2,115200n8 console=tty1 consoleblank=0 loglevel=1 root=UUID=b86978b6-aac1-4547-9a2d-378e6b69dd9e rootfstype=ext4 rootwait rw  smsc95xx.macaddr=00:1e:06:61:7a:55 governor=performance hdmi_tx_amp_lvl=31 hdmi_tx_lvl_ch0=3 hdmi_tx_lvl_ch1=3 hdmi_tx_lvl_ch2=3 hdmi_tx_emp_lvl=6 hdmi_clk_amp_lvl=31 hdmi_tx_res=0 HPD=true vout=hdmi usb-storage.quirks=  s5p_mfc.mem=16M
armbian-hardware-monitor.log:setenv rootdev UUID=b86978b6-aac1-4547-9a2d-378e6b69dd9e
armbian-hardware-monitor.log:└─sda1      ext4   111.8G /              b86978b6-aac1-4547-9a2d-378e6b69dd9e
kern.log:Apr 22 11:47:18 localhost kernel: [    0.000000] Kernel command line: console=ttySAC2,115200n8 console=tty1 consoleblank=0 loglevel=1 root=UUID=b86978b6-aac1-4547-9a2d-378e6b69dd9e rootfstype=ext4 rootwait rw  smsc95xx.macaddr=00:1e:06:61:7a:55 governor=performance hdmi_tx_amp_lvl=31 hdmi_tx_lvl_ch0=3 hdmi_tx_lvl_ch1=3 hdmi_tx_lvl_ch2=3 hdmi_tx_emp_lvl=6 hdmi_clk_amp_lvl=31 hdmi_tx_res=0 HPD=true vout=hdmi usb-storage.quirks=  s5p_mfc.mem=16M

 

 

 

abm.tar.gz

Link to post
Share on other sites
  • 4 weeks later...
Want Armbian t-shirt or a cup?

Hi, my 50ct:

You have disabled automatic checking by setting:

Check interval to 0 (<none>) so no automatic time dependent checking after a day or week or month or so will take place.

 

Also you have :

Mount count set to 1 and Maximum mount count also set to 1.

At the first mount nothing will happen because 1 is equal to 1 not greater. According to the manual only the second time it is mounted it will be checked because mount count will be 2 and maximum mount count still 1.

Afterwards the counter Mount count will be reset.

 

See: http landoflinux.com/linux_tune2fs_command.html

 

tune2fs options

     -c max-mount-counts Adjust the number of mounts after which the filesystem will be checked by e2fsck(8).

         If max-mount-counts is 0 or -1, the number of times the filesystem is mounted will be disregarded by e2fsck(8) and the kernel.

 

     -C mount-count Set the number of times the filesystem has been mounted. If set to a greater value than the max-mount-counts parameter set by the -c option,

          e2fsck(8) will check the filesystem at the next reboot.

 

     -i interval-between-checks[d|m|w] Adjust the maximal time between two filesystem checks. No postfix or d result in days, m in months, and w in weeks.

        A value of zero will disable the time-dependent checking. It is strongly recommended that either -c (mount-count-dependent) or -i (time-depen- dent) checking be enabled to force periodic full e2fsck(8) checking of the filesystem.

        Failure to do so may lead to filesystem corruption (due to bad disks, cables, memory, or kernel bugs) going unnoticed, ultimately resulting in data loss or corruption.

 

Have Fun!

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...