I"d recommend staying with 22.04 LTS release. I have the same setup and I'm on an LTS release. No issues at all.
Type: Posts; User: erind; Keyword(s):
I"d recommend staying with 22.04 LTS release. I have the same setup and I'm on an LTS release. No issues at all.
One way to run your script as root is to enter the following line at the top of the script and adding this script into the SUDOERS file:
#!/bin/bash
[ $(whoami) = root ] || exec sudo $0
#...
It looks like a hardware (hard disk) error. Just run a disk check (GUI or command line) and see what it says. Maybe it's time to backup everything and replace the disk.
As it is a for loop will work only in the current directory, whereas find will descend recursively down the directory tree. 'Find' is a very powerful tool.
It works fine on my end. Here it is a proof of concept case:
$ ll
total 24
drwxrwxr-x 2 miri miri 4096 Jul 10 20:12 d1
drwxrwxr-x 2 miri miri 4096 Jul 10 20:35 d2
drwxrwxr-x 2 miri miri...
It should work. Arrays are the conventional way to pass wildcards to the scripts in these special cases. One advice though, when you declare the arrays you don't quote the wildcards, only the strings...
You could pass the EXCLUDE variable to the rsync command by using bash arrays for the EXCLUDE string value. Array values do not suffer from the shell's unwanted expansions. Something like:
...
You can write such a script by pinging the connection in regular intervals, say every 3 minutes, and if there's no connection restart Brave. If Brave can be started from the command line then the...
"Input/Output" error is usually caused by a problematic (damaged) hard drive, run a disk check on that drive. Also make sure that you're not running out of disk space, run df -h from a terminal.
Thanks hsweet2 for your efforts, it'll come in handy.... I don't like when notepads' software save their notes in hard-to-parse format.
To my knowledge the scripts run times don't get logged in the log files, unless one manually makes the script to write to a file. However to make sure your script runs only once there are generally...
This is what I found online related to your problem. You need to experiment with the command below, because I'm not sure it'll do what you're asking for:
...
You can get some results using Desktop Environment's interaction tools such as xdotool, xte, wmctrl. It's not the best solution but given your situation they're better than nothing. There's plenty of...
I think it should be something like so (untested):
MNT=/some/location
mountpoint -q "$MNT" || { /bin/mount -v /dev/vg1/data $MNT || { echo "$(date) mount storage data failed" >>...
Great that you found the place! Now you're not supposed to manually create directories in /media, that's because the system will create automatically the mount points (directories) for the external...
Try this command and post its output:
sudo du -sh /* | sort -h -k1
It'll show the directories with their disk usage sorted, with the biggest dir on the bottom. Then we can look further into...
I'm not sure if there's an error in your last line of the log. But let's try Gparted to format the drive, it's in the repositories, and see how it goes. If Gparted fails as well then we're dealing...
In this case backup the drive excluding lost+found directory, format the whole drive and rsync back all the files again. After that run a check disk again and rsync the whole drive and look for...
I strongly think there's a filesystem error regarding these lost+found files, especially #169083091 directory. That is if, God forbid, it's not a hard disk hardware error.
Before going the format...
It's got to be something wrong with these leftover files/directory. What's the filesystem of this 4TB-Blue drive? NTFS, EXT4? [ EDIT: It's got to be EXT4 ]
Can you run this command and post the...
Yes, you can delete lost+found directory, there's usually parts of previously corrupted files in there. The system will recreate that directory again.
...
Your first script was failing because you were chaining the rsync commands, the second runs only if the first succeeds (&&), and your first rsync was failing so the 2nd wouldn't run.
The second...
Exatcly, I needed to re-install Grub, but this time something happened and Boot-Repair got choked on that, but manually worked fine. Something good to know for the future.
Glad to help!
I solved it by manually installing GRUB:
sudo mount /dev/sdb8 /mnt
for i in /dev /dev/pts /proc /sys; do sudo mount -B $i /mnt$i; done
sudo chroot /mnt
grub-install /dev/sdb
update-grub...
Hi all,
After I restored linux mint 19.3 using fsarchiver on the linux partition of a dual-boot setup, I ran Boot-Repair to re-install grub, however I encountered a few errors shown below. Note...