Running Busybox fsck on the PLCnext

fblanchard

Hello,

I tried running fsck on the PLCnext, as root, but I got this error:

root@axcf2152:~# fsck -A
fsck (busybox 1.29.3)
fsck: fsck.auto: No such file or directory
root@axcf2152:~#

Thanks.

Eduard PLCnext Team

Hello,

I can't reproduce this error message without BusyBox installation, if I call this command I get the folling response:

root@axcf2152:~# fsck -A
fsck from util-linux 2.35.1

Is it possible to deinstall the "busybox"?

Best Regards

Eduard

fblanchard

I never installed Busybox.  It came defacto with all PLCnext firmware version I know of (up to 2020.0.1 at least)

Eduard PLCnext Team

Hello fblanchard,

is it possible to update the controller to FW 2020.6 ?

I used this vesrsion and have no problem to call this command.

~Eduard

fblanchard

After a factory reset and a FW upgrade to 2020.6.1, the behaviour of fsck changed (different message, but still no action), and busybox is again installed by default.

root@axcf2152:/opt# fsck -A
fsck from util-linux 2.35.1
root@axcf2152:/opt#

root@axcf2152:/opt# busybox
BusyBox v1.31.1 () multi-call binary.
BusyBox is copyrighted by many authors between 1998-2015.
Licensed under GPLv2. See source distribution for detailed
copyright notices.

Usage: busybox [function [arguments]...]
or: busybox --list
or: function [arguments]...

BusyBox is a multi-call binary that combines many common Unix
utilities into a single executable. Most people will create a
link to busybox for each function they wish to use and BusyBox
will act like whatever it was invoked as.

Currently defined functions:
[, [[, addgroup, adduser, arp, ash, awk, basename, blkid, bunzip2, bzcat, bzip2, cat, chattr, chgrp, chmod, chown, chroot, chrt, chvt, clear, cmp, cp,
cpio, cut, date, dc, dd, deallocvt, delgroup, deluser, depmod, df, diff, dirname, dmesg, dnsdomainname, du, dumpkmap, dumpleases, echo, egrep, env, expr,
false, fbset, fdisk, fgrep, find, flock, free, fsck, fstrim, fuser, getopt, getty, grep, groups, gunzip, gzip, head, hexdump, hostname, hwclock,
i2ctransfer, id, ifconfig, ifdown, ifup, inetd, insmod, ip, kill, killall, klogd, less, ln, loadfont, loadkmap, logger, logname, logread, losetup, ls,
lsmod, lzcat, md5sum, mesg, microcom, mkdir, mkfifo, mknod, mkswap, mktemp, modprobe, more, mount, mountpoint, mv, nc, netstat, nohup, nproc, nslookup,
od, openvt, patch, pidof, pivot_root, printf, pwd, rdate, readlink, realpath, reboot, renice, reset, resize, rm, rmdir, rmmod, route, run-parts, sed,
seq, setconsole, setsid, sh, sha1sum, sha256sum, shuf, sleep, sort, stat, strings, stty, sulogin, swapoff, swapon, switch_root, sync, sysctl, syslogd,
tail, tar, taskset, tee, telnet, test, tftp, time, top, touch, tr, true, ts, tty, udhcpc, udhcpd, umount, uname, uniq, unlink, unzip, uptime, users,
usleep, vi, watch, wc, wget, which, who, whoami, xargs, xzcat, yes, zcat
root@axcf2152:/opt#

Martin [PLCnext Technology Team]

Hi Frédéric,

Here is an example showing how to check the file system on an SD-card using fsck, from an AXC F 2152 FW 2021.0:

 

Note:

• The tool must be called by the root user
• sudo fsck with user admin is not possible, as the tool is not part of the sudoers file
• The partition to check must not be mounted

In the above example, the PLC was booted without an external SD card, and the SD card was then inserted. In this way, the file system on the SD card is unused/unmounted when calling fsck.

Hope this helps.

~ Martin.