madgino
-
Posts
9 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by madgino
-
-
Sorry Trul, I'll only know that when he wakes up - It's 6AM - sorry to waste your time. I'm trying to work out how it was created.
-
Yeah that share was created for his back up using Rsync, this is not something that was implemented recently though.
-
A mate had a rysnc docker container setup to connect to his debian box and do a backup.
We have a VPN between each other, it's his IP.
I can shutdown the tunnel if that would help, but I doubt it - sorry that the logs are full of that error message.
-
I have lost all my shares and unable to start docker or the VM Manager.
I've restarted multiple times, but it looks like the /mnt/user/system/docker/ and /mnt/user/appdata are not mapped to my physical drives
Please refer to the attached diagnositc dump, is anyone help to give me some direction.
This was in the process of creating some VM's and installing the Intel-GPU-TOP package.
Everything was working fine, until I performed a reboot.
tower-diagnostics-20240201-0421.zip tower-diagnostics-20240201-0353.zip tower-diagnostics-20240201-0309.zip
-
1 hour ago, codefaux said:
Your drive is reporting uncorrectable sectors. Twice at one address, once at another address. It hasn't marked the second address as a permanent-fail, thus only tagging 1 in the attributes column.
This is a big pre-warning state. Some drives may limp like this for years, but if this data or reliable performance are at all important, back it up and swap the drive.
Are you using Parity? If you're not, I'd like to note that this case was an early-warning case, and a Parity drive would've saved you even if you hadn't noticed.
Also an important question because it somewhat determines how you proceed, as does your experience with things like ssh and Linux in general.
Thanks for the reply,
I don't know if I've read this correctly or not, but it appears that that the 1st and 2nd smart error happened at the same time "29801 hours" on the same block "3894526032"
The third error happened some time later at at "48162 hours" on block "3166961520"
So from what I understand there has been "18361 hours" or 765 days just over 2 years since the second and third errors.
I'm assuming I can put move any critical data onto the other drives in my array and leave this drive just for media content that can be easily retrieved again if the drive ever decides to totally fail.
I currently have a 4 drives, with one used for parity
In regards to linux and ssh experience, I'm confident I'll manage.
Can you see any problem with this thought pattern?
-
Ran an extended test as you suggest, from what I can understand, it doesn't look good.
What you think?
-
Hello,
I've recently installed unraid and had some errors of one of my disks, refer to attached logs.
Can you please inform me of what steps I should take next, I have a spare disk of the same model that can be used as a replacement.
Is it time to replace the disk or can it be saved?
-
Hey mate,
Thanks for creating video - was very helpful.
Shares disappeared and unable to start docker and VM Manager
in General Support
Posted
Thank you both very much for pointing me in the right direction.
You were right, it was timing related.
Rebooting my server while the overnight backup was running meant the directory was created before unraid had finished booting.
After deleting the directory and rebooting my user share came back, and I was able to restore my docker containers by reinstalling them from "Previous Apps"
My friend has now adjusted his backup script to only run if the directory already exists.