You are not logged in.
Dear,
installed Devuan Jessie 1.0.0 using the download of devuan_jessie_1.0.0_arm64_raspi3.img.
The installation is setting up the filesystems as:
root@pi-hole:/home/os# mount | grep mmc
/dev/mmcblk0p2 on / type ext4 (ro,noatime,block_validity,delalloc,nojournal_checksum,norecovery,barrier,user_xattr,acl,errors=remount-ro)
/dev/mmcblk0p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)
/ partition is being resized to match the entire SD-card space.
Unfortunately / or /dev/mmcblk0p2 is using the flag metadata_csum
root@pi-hole:/home/os# tune2fs -l /dev/mmcblk0p2
tune2fs 1.42.12 (29-Aug-2014)
Filesystem volume name: <none>
Last mounted on: /
Filesystem UUID: 3be31ccf-eda0-4239-bad7-2ca304abe1b9
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype extent 64bit flex_bg sparse_super large_file huge_file dir_nlink extra_isize metadata_csum
This flag is not support by e2fsprogs 1.42.12-2+b1 which is part of the installation image.
Thus, when the SD card fails there is no chance at all to get it fixed. e2fsck refuses to run, there is not sufficient time or no possibility to upgrade (as / is mounted ro). Therefore a single issue with the SD card (and there are many on a Pi) will break the entire system and require re-installation.
Suggested solution: please update the installation image to not use metadata_csum.
Thanks, -MN
Offline
e2fsprogs from jessie-backports helps:
(yeti@pi3-0:1)~$ sudo tune2fs -l /dev/mmcblk0p2 | fgrep 'checked'
Last checked: Thu Feb 8 17:54:50 2018
(yeti@pi3-0:1)~$ apt-cache policy e2fsprogs
e2fsprogs:
Installed: 1.43.3-1~bpo8+1
Candidate: 1.43.3-1~bpo8+1
Version table:
*** 1.43.3-1~bpo8+1 0
100 http://pkgmaster.devuan.org/merged/ jessie-backports/main arm64 Packages
100 /var/lib/dpkg/status
1.42.12-2+b1 0
500 http://pkgmaster.devuan.org/merged/ jessie/main arm64 Packages
Last edited by yeti (2018-02-08 20:02:40)
*๐๐๐๐๐๐!*
Offline
That looks good.
Then e2fsprogs 1.43.3 should be included into the main Raspberry Pi arm64 image?
Ciao, -MN
Offline
It should...
But until then installing the newer e2fsprogs from backports is the faster cure...
Last edited by yeti (2018-02-08 18:24:10)
*๐๐๐๐๐๐!*
Offline
How many people/users will fail for the same trap and curse the image when they lose data?
It may work for the both of us now as we are aware - but everyone else using RPI with Devuan is at risk.
Ciao, -MN
Offline
We need pages for that in the wiki...
One for each image and/or board.
*๐๐๐๐๐๐!*
Offline
And in addition to the backports e2fsprog update /etc/fstab needs an update
From:
## rootfs
/dev/mmcblk0p2 / ext4 errors=remount-ro,sync,noatime 0 0
To:
## rootfs
/dev/mmcblk0p2 / ext4 errors=remount-ro,sync,noatime 0 1
Also /dev/mmcblk0p2 has been configured to -1 for maximum mount count. For armhf64 and the buggy SD card I used:
root@devuan:~# tune2fs -c 10 /dev/mmcblk0p2
to check the filesystem every 10th mount time and to enable /forcefsck.
It also seems that the downloaded image for RPI3 is tagged dirty
[ 3.495755] EXT4-fs (mmcblk0p2): warning: mounting unchecked fs, running e2fsck is recommended
[ 3.499284] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro
Ciao, -MN
Offline
Also /dev/mmcblk0p2 has been configured to -1 for maximum mount count.
The devuan_ascii_2.0.0-beta_arm64_raspi3.img.xz image has this setting too...
That's not a default setting I expect in a unixlike OS.
This definitely should be documented.
Is it?
Which URL should I visit?
*๐๐๐๐๐๐!*
Offline