ddrescue clone failing hard drive
-
Clone hard drive with ddrescue
Testing a hard drive for failure via smartmontools
Install smartmontools if not already present: (debian)
apt-get install smartmontoolsLocate specific hard drives currently installed:
lsblk
In this case I choose device ‘sda’
smartctl --all /dev/sda -q errorsonlyExample of failing hard drive:
Preparing a used hard drive for cloning
Clearing existing partitions from destination hard drive:
In this case the destination drive is defined as sdc:
I’ll use fdisk to clear all existing partitions:
fdisk /dev/sdcThen print partition existing on sdc by typing the letter pp
The above image shows some detail on the destination drive, including on FreeBSD partition named /dev/sdc4
Since there is only one partition on the destination drive, we simply need to type the letter d at the fdisk command prompt:
d
If there are more existing partitions on the destination drive, we are presented with them, and numbers to go along, we select which partition via numbers what we delete (in this case everything)
Once we’ve removed the partitions, we type the letter w to write the changes, (actually delete the partitions)
I type the letter p once again to make sure no partitions are still on the disk and then the letter w to write the changes:
Using ddrescue to clone the hard drive:
!Insure your drive letters are correct!
The command I use to simplify the procedure including reading the damaged drive and putting as little pressure on it as we can manage, while getting as much data as we can, are as follows:
Insure existing, or damaged hard drive first, and destination hard drive second (In other terms input file first and output file second)
ddrescue -f -n /dev/sda /dev/sdc /root/recovery.logFrom https://linux.die.net/man/1/ddrescue
-f, --force overwrite output device or partition
-n, --no-split do not try to split or retry failed blocks
We set a log file, which ddrescue can read later if for any reason the proceedure fails in the middle. Or also if we do not get as close to a 100% success rate when finished, the log file will set ddrescue to only attempt to get failed blocks on additional runs.
In this case 100% of the data was recovered, and transferred to the new hard drive:
I run lsblk once again to check partitions have been transferred:
I then restart the machine:
shutdown -r nowAfter a restart, the journal will be recovered as well as other routine scripts run. I remove other old, damaged hard drives during the restart just before the BIOS kicks up.
Again after a restart I run :
lsblk
Fin!
Note This local server is a test environment running ProxMox. Everything running as it should after the clone.
-
Clone hard drive with ddrescue
Testing a hard drive for failure via smartmontools
Install smartmontools if not already present: (debian)
apt-get install smartmontoolsLocate specific hard drives currently installed:
lsblk
In this case I choose device ‘sda’
smartctl --all /dev/sda -q errorsonlyExample of failing hard drive:
Preparing a used hard drive for cloning
Clearing existing partitions from destination hard drive:
In this case the destination drive is defined as sdc:
I’ll use fdisk to clear all existing partitions:
fdisk /dev/sdcThen print partition existing on sdc by typing the letter ppThe above image shows some detail on the destination drive, including on FreeBSD partition named /dev/sdc4
Since there is only one partition on the destination drive, we simply need to type the letter d at the fdisk command prompt:
dIf there are more existing partitions on the destination drive, we are presented with them, and numbers to go along, we select which partition via numbers what we delete (in this case everything)
Once we’ve removed the partitions, we type the letter w to write the changes, (actually delete the partitions)
I type the letter p once again to make sure no partitions are still on the disk and then the letter w to write the changes:
Using ddrescue to clone the hard drive:
!Insure your drive letters are correct!
The command I use to simplify the procedure including reading the damaged drive and putting as little pressure on it as we can manage, while getting as much data as we can, are as follows:
Insure existing, or damaged hard drive first, and destination hard drive second (In other terms input file first and output file second)
ddrescue -f -n /dev/sda /dev/sdc /root/recovery.logFrom https://linux.die.net/man/1/ddrescue
-f, --force overwrite output device or partition
-n, --no-split do not try to split or retry failed blocks
We set a log file, which ddrescue can read later if for any reason the proceedure fails in the middle. Or also if we do not get as close to a 100% success rate when finished, the log file will set ddrescue to only attempt to get failed blocks on additional runs.
In this case 100% of the data was recovered, and transferred to the new hard drive:
I run lsblk once again to check partitions have been transferred:
I then restart the machine:
shutdown -r nowAfter a restart, the journal will be recovered as well as other routine scripts run. I remove other old, damaged hard drives during the restart just before the BIOS kicks up.
Again after a restart I run :
lsblkFin!
Note This local server is a test environment running ProxMox. Everything running as it should after the clone.
-
3JUgg6grmbJ1wJ4mTU9fUxXGSMK6trSwKq
-
-
Create a shell script that will dump the Redis database
cd ~ mkdir redi-backups-script cd redis-backups-script nano redis_backups-script.shPaste the script below:
#!/bin/bash rdb_file="/Place-directory-of-rdb-here/redis/dump.rdb" redis_cli="/usr/bin/redis-cli" DIR=`date +%d-%m-%y` DEST=~/redis_backups/$DIR mkdir $DEST echo save| $redis_cli exit 1Set script to executable:
chmod +x ~/scripts/redis_backups-script.shCreate a cron to run daily:
Then create a cron job to run the script every day at midnight:
crontab -e 0 0 * * * ~/redis-backups-script/redis_backup.shRestore RDB backup
Disable Append Only in the config:
nano /etc/redis/redis.conf appendonly noStop redis:
sudo service redis-server stopRestore the redis backup:
rename the rdb file you wish sudo cp /home/redis/dump.rdb /home/redis/dump.rdb.bak
You can then copy the backup rdb file as follows:
sudo cp /redis_backups/------/dump.rdb /home/redis/dump.rdbApply the proper permissions to the dump.rdb file:
sudo chmod 660 /home/redis/dump.rdbRe-starting Redis server
sudo service redis-server start
-
Install Zabbix 7.2 repo
wget https://repo.zabbix.com/zabbix/7.2/release/debian/pool/main/z/zabbix-release/zabbix-release_latest_7.2+debian12_all.deb
dpkg -i zabbix-release_latest_7.2+debian12_all.deb
Update repos
apt update
Install Zabbix server and frontend
apt install zabbix-server-mysql zabbix-frontend-php zabbix-nginx-conf zabbix-sql-scripts zabbix-agent2
Install plugins
apt install zabbix-agent2-plugin-mongodb zabbix-agent2-plugin-mssql zabbix-agent2-plugin-postgresql
Install mysql
wget https://dev.mysql.com/get/mysql-apt-config_0.8.30-1_all.deb
sudo dpkg -i mysql-apt-config_0.8.30-1_all.deb
Error on this new install, where lsb-release is not installed
apt-get install lsb-release
Try again…
dpkg -i mysql-apt-config_0.8.30-1_all.debError, gnupg not installed
apt install gnupg2
Give it another go…
dpkg -i mysql-apt-config_0.8.30-1_all.deb
I had to list upgradable packages :
apt-list --upgradableWhich spit out : mysql-common/unknown 8.4.4-1debian12 all [upgradable from: 5.8+1.1.0]
Then installed mysql-common
apt-get install mysql-common
Had to uninstall Mariadb to resolve these conflicts
apt remove mariadb-client-coreThen install mysql-server:
apt install mysql-server
Enter your password, twice
Now enter mysql by typing :
mysql -u root -p
Enter the following command individually Where ‘password’ is where you type in your actual own password
mysql> create database zabbix character set utf8mb4 collate utf8mb4_bin; mysql> create user zabbix@localhost identified by 'password'; mysql> grant all privileges on zabbix.* to zabbix@localhost; mysql> set global log_bin_trust_function_creators = 1; mysql> quit;Populate the database with zabbix script
zcat /usr/share/zabbix/sql-scripts/mysql/server.sql.gz | mysql --default-character-set=utf8mb4 -uzabbix -p zabbix mysql --u root -p set global log_bin_trust_function_creators = 0; quit;Edit file /etc/zabbix/zabbix_server.conf You can use nano
nano /etc/zabbix/zabbix_server.confUncomment the DBPassword section, and type your password
Then hold ctrl and tap x, it will ask if you want to save changes.
Enable services:
systemctl enable zabbix-server zabbix-agent2 nginx php8.2-fpm systemctl restart zabbix-server zabbix-agent2 nginx php8.2-fpmCheck that zabbix service has started
journalctl -xeu zabbix-server.service
Delete the 'default site in nginx
sudo rm -rf /etc/nginx/sites-enabled/defaultMake sure the symbolic link to the zabbix nginx file is present
ln -s /etc/zabbix/nginx.conf /etc/nginx/sites-enabled/zabbix.confCheck that the zabbix nginx file is in the includes in nginx config
nano /etc/nginx/nginx.confLook for :
include /etc/nginx/sites-enabled/*Now restart nginx
systemctl restart nginxHit the browser and type in the IP (or URL that you may have put in the zabbix nginx config file)
Make sure to configure locales
sudo dpkg-reconfigure locales
Reboot the system
sudo shutdown -r now
Add your database password
Add a server name
The default username is Admin, and the password is zabbix
-
Unable to negotiate with 10.10.1.35 port 22: no matching host key type found. Their offer: ssh-rsa,ssh-dss
While attempting ssh this error is generally due to mismatched versions of ssh, where an up to date version is attempting to access an older version
Add the following to your command :
The proper way:
ssh -o KexAlgorithms=diffie-hellman-group14-sha1 -oHostKeyAlgorithms=+ssh-dss 10.10.1.35The cheap way:
Example :
ssh -oHostKeyAlgorithms=+ssh-dss 10.10.1.35or ssh -oHostKeyAlgorithms=+ssh-dss user@10.10.1.35
This can be added to the ~/.ssh/config file
Host my-server HostName 10.10.1.35 HostKeyAlgorithms=+ssh-dss
