FSCK disk repair
-
-p Automatic repair (no questions) -n Make no changes to the filesystem -y Assume "yes" to all questions -c Check for bad blocks and add them to the badblock list -f Force checking even if filesystem is marked clean -v Be verbose -b superblock Use alternative superblock -B blocksize Force blocksize when looking for superblock -j external_journal Set location of the external journal -l bad_blocks_file Add to badblocks list -L bad_blocks_file Set badblocks list -
FSCK(8) System Administration FSCK(8)
NAME fsck - check and repair a Linux filesystem
SYNOPSIS fsck [-lrsAVRTMNP] [-C [fd]] [-t fstype] [filesystem…] [–] [fs-specific-options]
DESCRIPTION:
fsck is used to check and optionally repair one or more Linux filesystems. filesys can be a device name (e.g. /dev/hdc1, /dev/sdb2), a mount point (e.g. /, /usr, /home), or an ext2 label or UUID specifier (e.g.UUID=8868abf6-88c5-4a83-98b8-bfc24057f7bd or LABEL=root).
Normally, the fsck program will try to handle filesystems on different physical disk drives in parallel to reduce the total amount of time needed to check all of them.
If no filesystems are specified on the command line, and the -A option is not specified, fsck will default to checking filesystems in /etc/fstab serially. This is equivalent to the -As options.
The exit code returned by fsck is the sum of the following conditions: 0 No errors 1 Filesystem errors corrected 2 System should be rebooted 4 Filesystem errors left uncorrected 8 Operational error 16 Usage or syntax error 32 Checking canceled by user request 128 Shared-library errorThe exit code returned when multiple filesystems are checked is the bit-wise OR of the exit codes for each filesystem that is checked.
In actuality, fsck is simply a front-end for the various filesystem checkers (fsck.fstype) available under Linux.
The filesystem-specific checker is searched for in /sbin first, then in /etc/fs and /etc, and finally in the directories listed in the PATH environment variable. Please see the filesystem-specific checker manual pages for further details.
OPTIONS:
-lLock the whole-disk device by an exclusive flock(2). This option can be used with one device only (this means that -A and -l are mutually exclusive). This option is recommended when more fsck(8) instances are executed in the same time.
The option is ignored when used for multiple devices or for non-rotating disks.
fsck does not lock underlying devices when executed to check stacked devices (e.g. MD or DM) – this feature is not implemented yet.
-rReport certain statistics for each fsck when it completes. These statistics include the exit status, the maximum run set size (in kilobytes), the elapsed all-clock time and the user and system CPU time used by the fsck run.
For example:
/dev/sda1: status 0, rss 92828, real 4.002804, user 2.677592, sys 0.86186-sSerialize fsck operations. This is a good idea if you are checking multiple filesystems and the checkers are in an interactive mode. (Note: e2fsck(8) runs in an interactive mode by default.
To make e2fsck(8) run in a non-interactive mode, you must either specify the -p or -a option, if you wish for errors to be corrected automatically, or the -n option if you do not.)
-tfslist
Specifies the type(s) of filesystem to be checked. When the -A flag is specified, only filesystems that match fslist are checked. The fslist parameter is a comma-separated list of filesystems and options specifiers.
All of the filesystems in this comma-separated list may be prefixed by a negation operator ‘no’ or ‘!’, which requests that only those filesystems not listed in fslist will be checked. If none of the filesystems in fslist is prefixed by a negation operator, then only those listed filesystems will be checked.
Options specifiers may be included in the comma-separated fslist. They must have the format opts=fs-option. If an options specifier is present, then only filesystems which contain fs-option in their mount options field of /etc/fstab will be checked.
If the options specifier is prefixed by a negation operator, then only those filesystems that do not have fs-option in their mount options field of /etc/fstab will be checked.
For example, if opts=ro appears in fslist, then only filesystems listed in /etc/fstab with the ro option will be checked.
For compatibility with Mandrake distributions whose boot scripts depend upon an unauthorized UI change to the fsck program, if a filesystem type of loop is found in fslist, it is treated as if opts=loop were specified as an argument to the -t option.
Normally, the filesystem type is deduced by searching for filesys in the /etc/fstab file and using the corresponding entry.
If the type can not be deduced, and there is only a single filesystem given as an argument to the -t option, fsck will use the specified filesystem type. If this type is not available, then the default filesystem type (currently ext2) is used.
-AWalk through the /etc/fstab file and try to check all filesystems in one run. This option is typically used from the /etc/rc system initialization file, instead of multiple commands for checking a single filesystem.
The root filesystem will be checked first unless the -P option is specified (see below). After that, filesystems will be checked in the order specified by the fs_passno (the sixth) field in the /etc/fstab file.
Filesystems with a fs_passno value of 0 are skipped and are not checked at all. Filesystems with a fs_passno value of greater than zero will be checked in order, with filesystems with the lowest fs_passno number being checked first.
If there are multiple filesystems with the same pass number, fsck will attempt to check them in parallel, although it will avoid running multiple filesystem checks on the same physical disk.
fsck does not check stacked devices (RAIDs, dm-crypt, …) in parallel with any other device. See below for FSCK_FORCE_ALL_PARALLEL setting. The /sys filesystem is used to determine dependencies between devices.
Hence, a very common configuration in /etc/fstab files is to set the root filesystem to have a fs_passno value of 1 and to set all other filesystems to have a fs_passno value of 2. This will allow fsck to automatically run filesystem checkers in parallel if it is advantageous to do so.
System administrators might choose not to use this configuration if they need to avoid multiple filesystem checks running in parallel for some reason — for example, if the machine in question is short on memory so that excessive paging is a concern.
fsck normally does not check whether the device actually exists before calling a filesystem specific checker. Therefore non-existing devices may cause the system to enter filesystem repair mode during boot if the filesystem specific checker returns a fatal error.
The /etc/fstab mount option nofail may be used to have fsck skip non-existing devices.
fsck also skips non-existing devices that have the special filesystem type auto.
-C [fd]Display completion/progress bars for those filesystem checkers (currently only for ext2 and ext3) which support them. fsck will manage the filesystem checkers so that only one of them will display a progress bar at a time.
GUI front-ends may specify a file descriptor fd, in which case the progress bar information will be sent to that file descriptor.
-MDo not check mounted filesystems and return an exit code of 0 for mounted filesystems.
-NDon’t execute, just show what would be done.
-PWhen the -A flag is set, check the root filesystem in parallel with the other filesystems.
This is not the safest thing in the world to do, since if the root filesystem is in doubt things like the e2fsck(8) executable might be corrupted!
This option is mainly provided for those sysadmins who don’t want to re partition the root filesystem to be small and compact (which is really the right solution).
-RWhen checking all filesystems with the -A flag, skip the root filesystem. (This is useful in case the root filesystem has already been mounted read-write.)
-TDon’t show the title on startup.
-VProduce verbose output, including all filesystem-specific commands that are executed.
fs-specific-options
Options which are not understood by fsck are passed to the filesystem-specific checker. These options must not take arguments, as there is no way for fsck to be able to properly guess which options take arguments and which don’t.
Options and arguments which follow the – are treated as filesystem-specific options to be passed to the filesystem-specific checker.
Please note that fsck is not designed to pass arbitrarily complicated options to filesystem-specific checkers.
If you’re doing something complicated, please just execute the filesystem-specific checker directly. If you pass fsck some horribly complicated options and arguments, and it doesn’t do what you expect, don’t bother reporting it as a bug. You’re almost certainly doing something that you shouldn’t be doing with fsck
Options to different filesystem-specific fsck’s are not standardized. If in doubt, please consult the man pages of the filesystem-specific checker.
Although not guaranteed, the following options are supported by most filesystem checkers:
-aAutomatically repair the filesystem without any questions (use this option with caution). Note that e2fsck(8) supports -a for backward compatibility only.
This option is mapped to e2fsck’s -p option which is safe to use, unlike the -a option that some filesystem checkers support.
-nFor some filesystem-specific checkers, the -n option will cause the fs-specific fsck to avoid attempting to repair any problems, but simply report such problems to stdout.
This is however not true for all filesystem-specific checkers. In particular, fsck.reiserfs(8) will not report any corruption if given this option.fsck.minix(8) does not support the -n option at all.
-rInteractively repair the filesystem (ask for confirmations). Note: It is generally a bad idea to use this option if multiple fsck’s are being run in parallel. Also note that this is e2fsck’s default behavior; it supports this option for backward compatibility reasons only.
-yFor some filesystem-specific checkers, the -y option will cause the fs-specific fsck to always attempt to fix any detected filesystem corruption automatically.
Sometimes an expert may be able to do better driving the fsck manually. Note that not all filesystem-specific checkers implement this option. In particular fsck.minix(8) and fsck.cramfs(8) do not support the -y option as of this writing.
FILES /etc/fstab.
ENVIRONMENT VARIABLES
The fsck program’s behavior is affected by the following environment variables:
FSCK_FORCE_ALL_PARALLEL
If this environment variable is set, fsck will attempt to check all of the specified filesystems in parallel, regardless of whether the filesystems appear to be on the same device. (This is useful for RAID systems or high-end storage systems such as those sold by companies such as IBM or EMC.) Note that the fs_passno value is still used.
FSCK_MAX_INST
This environment variable will limit the maximum number of filesystem checkers that can be running at one time. This allows configurations which have a large number of disks to avoid fsck starting too many filesystem checkers at once, which might overload CPU and memory resources available on the system.
If this value is zero, then an unlimited number of processes can be spawned. This is currently the default, but future versions of fsck may attempt to automatically determine how many filesystem checks can be run based on gathering accounting data from the operating system.
PATH
The PATH environment variable is used to find filesystem checkers. A set of system directories are searched first: /sbin, /sbin/fs.d, /sbin/fs, /etc/fs, and /etc. Then the set of directories found in the PATH environment are searched.
FSTAB_FILE
This environment variable allows the system administrator to override the standard location of the /etc/fstab file. It is also useful for developers who are testing fsck.
LIBBLKID_DEBUG=0xffff
enables debug output.
LIBMOUNT_DEBUG=0xffff
enables debug output.
SEE ALSO
fstab(5), mkfs(8), fsck.ext2(8) or fsck.ext3(8) or e2fsck(8), cramfsck(8), fsck.minix(8), fsck.msdos(8), fsck.jfs(8), fsck.nfs(8), fsck.vfat(8), fsck.xfs(8), fsck.xiafs(8), reiserfsck(8).
AUTHOR: Theodore Ts’o
AVAILABILITY The fsck command is part of the util-linux package and is available from Linux Kernel Archive ftp://ftp.kernel.org/pub/linux/utils/util-linux/.
-
R
755 - Owner has all permissions, and Group and Other can read and execute 700 - Owner has all permissions 644 - Owner can read and write, and Group and Other can read 600 - Owner can read and write 775 - Owner can read and write, and Group and Other can read 770 - Owner and Group have all, and Other can read and execute 750 - Owner has all permissions, and Group can read and execute 664 - Owner and Group can read and write, and Other can just read 660 - Owner and Group can read and write 640 - Owner can read and write, and Group can read
-
R
Re: Find or Locate a file or extension command line
Install locate command linux: Use your sudo command!
apt install mlocateOR:
apt-get install mlocateOR:
yum install mlocateUpdate the database:
updatedbDepending on the size of the complete filesystem this could take a few minutes
After the database has been populated:
locate mariadbWhere mariadb is the word your looking for
-
R
These commands are if you are in the scripts directory! Changing permissions can be done from anywhere in the structure.
Such as :
chmod +x /opt/so-elastic-agent_linux_amd64Terminal chmod to executable :
Permissions prior to chmod :
chmod +x so-elastic-agent_linux_amd64
Permissions following chmod :
Then execute :
./so-elastic-agent_linux_amd64Insure you are acting as the user you just gave permissions to (the file owner) or at least have sudo privileges
To make the script un-executable:
chmod -x so-elastic-agent_linux_amd64
-
R
sudo apt install lsb-release ca-certificates curl -y
GPG key and repo for php 7.4
sudo curl -sSLo /usr/share/keyrings/deb.sury.org-php.gpg https://packages.sury.org/php/apt.gpg sudo sh -c 'echo "deb [signed-by=/usr/share/keyrings/deb.sury.org-php.gpg] https://packages.sury.org/php/ $(lsb_release -sc) main" > /etc/apt/sources.list.d/php.list'Update the system with the new repository in place
sudo apt updateInstall the dependencies for OwnCloud (LAMP ect) Certbot, or LetsEncrypt is being installed as well, if you are using this installation in a public domain
sudo apt install apache2 mariadb-server imagemagick certbot python3-certbot-apache smbclient redis-server unzip rsync libapache2-mod-php7.4 php7.4 php7.4-intl php7.4-mysql php7.4-mbstring php7.4-imagick php7.4-igbinary php7.4-gmp php7.4-bcmath php7.4-curl php7.4-gd php7.4-zip php7.4-imap php7.4-ldap php7.4-bz2 php7.4-ssh2 php7.4-common php7.4-json php7.4-xml php7.4-dev php7.4-apcu php7.4-redis libsmbclient-dev php-pear php-phpseclibEnable apache2 and then verify it’s status
sudo systemctl is-enabled apache2 sudo systemctl status apache2
sudo systemctl is-enabled mariadb sudo systemctl status mariadb
Enable MariaDB and verify status
sudo systemctl is-enabled redis sudo systemctl status redis
Enable Redis and verify status
Configure default php version
sudo update-alternatives --config php
Configure php OwnCloud dependencies
sudo update-alternatives --set phar /usr/bin/phar7.4 sudo update-alternatives --set phar.phar /usr/bin/phar.phar7.4 sudo update-alternatives --set phpize /usr/bin/phpize7.4 sudo update-alternatives --set php-config /usr/bin/php-config7.4Upgrade Pear to OwnCloud4 requirements
sudo mkdir -p /tmp/pear/cache sudo pear upgrade --force --alldeps http://pear.php.net/get/PEAR-1.10.13
sudo pear clear-cache sudo pear update-channels sudo pear upgrade --force sudo pear upgrade-all
Verify Pear version
pear version
Configure MariaDB
sudo mariadb-secure-installation
Log into MariaDB
sudo mariadb -u root -pCreate the OwnCloud database:
This is where many go wrong, we do not use ‘password’ we replace password, with our own password.
CREATE DATABASE owncloud;We just created a database with the name owncloud
CREATE USER IF NOT EXISTS 'owncloud'@'localhost' IDENTIFIED BY 'password';We just created a database user called owncloud
GRANT ALL PRIVILEGES ON owncloud.* TO 'owncloud'@'localhost' WITH GRANT OPTION;We just allowed user owncloud, full privileges on database owncloud
FLUSH PRIVILEGES;Now verify what we have just done:
SHOW GRANTS FOR 'owncloud'@'localhost';You can see below I named this database ‘oc’ and the ‘oc’ user has privileges on database ‘owncloud’
quit;
wget the OwnCloud source
cd /var/www wget https://download.owncloud.com/server/stable/owncloud-complete-latest.tar.bz2Grab sha256 to verify the download
wget https://download.owncloud.com/server/stable/owncloud-complete-latest.tar.bz2.sha256BEFORE installing, verify if the download of OwnCloud matches what the OwnCloud team wanted you to have, this is important always.
sudo sha256sum -c owncloud-complete-latest.tar.bz2.sha256 < owncloud-complete-latest.tar.bz2Out put should say ‘OK’ if everything matches.
Change ownership of the directory to www-data user.
sudo chown -R www-data:www-data /var/www/owncloudConfigure Vhost for OwnCloud
This will open a new file in 'sites-available and name this file ‘owncloud.conf’
Change the ServerName and ServerAlias, as well as log file names, to whatever your domain is. There are many ways to do this keep in mind.
sudo nano /etc/apache2/sites-available/owncloud.conf <VirtualHost *:80> ServerName oc ServerAlias www.oc DocumentRoot /var/www/owncloud ErrorLog ${APACHE_LOG_DIR}/oc.io-error.log CustomLog ${APACHE_LOG_DIR}/oc.io-access.log combined Alias /owncloud "/var/www/owncloud/" <Directory /var/www/owncloud/> Options +FollowSymlinks AllowOverride All <IfModule mod_dav.c> Dav off </IfModule> SetEnv HOME /var/www/owncloud SetEnv HTTP_HOME /var/www/owncloud </Directory> </VirtualHost>Enable and verify the owncloud vhost
sudo a2ensite owncloud.conf sudo apachectl configtest
Now install OwnCloud
Change the database name, user, and password to whatever you named the OwnCloud database earlier;
Change the ‘admin user’ and ‘admin pass’ to whatever you want the new OwnCloud admin account to be.
sudo -u www-data /var/www/owncloud/occ maintenance:install \ --database "mysql" \ --database-name "owncloud" \ --database-user "owncloud"\ --database-pass "password" \ --admin-user "admin" \ --admin-pass "your new owncloud admin password"Edit the OwnCloud config file to add the domain you used earlier in the Apache2 vhost file:
sudo nano /var/www/owncloud/config/config.php 'trusted_domains' => array ( 0 => 'localhost', 1 => 'whatever your domain is goes here', ),Personally I restart the server at this point, which will restart all services. Then visit the domain / IP of your settings and you should see the OwnCloud login page. Use the credentials you setup for the admin user.
System cron setting:
sudo crontab -u www-data -e */15 * * * * /usr/bin/php -f /var/www/owncloud/occ system:cronMemcache with Redis we installed earlier:
sudo nano /var/www/owncloud/config/config.php 'filelocking.enabled' => true, 'memcache.local' => '\OC\Memcache\APCu', 'memcache.locking' => '\OC\Memcache\Redis', 'redis' => [ 'host' => 'localhost', 'port' => 6379, ],Go restart the server again and enjoy!
-
R
Comment out in=>
/usr/lib/python3/dist-packages/middlewared/plugins/vm/vms.py # elif flags['intel_vmx']: # if vcpus > 1 and flags['unrestricted_guest'] is False: # verrors.add(f'{schema_name}.vcpus', 'Only one Virtual CPU is allowed in this system.') # elif flags['amd_rvi']: # if vcpus > 1 and flags['amd_asids'] is False: # verrors.add( # f'{schema_name}.vcpus', 'Only one virtual CPU is allowed in this system.' # )At this point we must comment out each time we update the system.