Agamemnon
-
Posts
14 -
Joined
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Agamemnon
-
-
On 12/27/2023 at 4:59 PM, Agamemnon said:
Tower kernel: I/O error, dev sdh, sector 26866835136 op 0x0:(READ) flags 0x4000 phys_seg 128 prio class 2
I am just unsure if I need to run a parity check before upgrading the parity disk because of the I/O errors the data disk showed when the CRC errors occured.
I acknowledged the SMART warning and will set up email notifications.
-
On 12/27/2023 at 7:38 PM, JorgeB said:
That won't do it, reboot instead, but like mentioned replace the SATA cable also, I don't the need to replace the disk for now.
So far no more UDMA CRC Errors occured.
Should I run a parity check (without writing corrections) before updating Parity drive to 20TB? I am currently preclearing the disk and it will be done tomorrow.
Last parity check was 2 weeks ago before the CRC Errors came up.
-
Ok, thank you for looking at the diagnostics. I thought I would have to do a parity check to get rid of the disk errors.
What about the parity swap to use the new 20TB as parity and the parity drive to replace the data disk with issues?
-
-
I just want to make sure what the best course of action is for my situation.
Currently my parity drive is 18TB. I have a new 20TB drive ready and was planning to update the parity with it.
Now one of my 14TB data drives threw 12,310 Errors and disk log shows a lot of the following errors:
Tower kernel: I/O error, dev sdh, sector 26866835136 op 0x0:(READ) flags 0x4000 phys_seg 128 prio class 2
At the same time UDMA CRC error count jumped to 1813. So far it hasn't gone higher after switching to a different SATA cable.
When I switch out the drive with a new one the errors would get fixed from parity?
Problem is, I can't use the 20TB on hand unless I do a procedure I found that's called a parity swap, but I am unsure if this is advisable or even still supported.
Alternative would be to get another 18TB to replace the data disk first and then upgrade parity later.
-
Beautiful clean build.
Do you know how much power the whole system is drawing?
-
Looks great. How are the HDD temps?
-
Thank you. I canceled the parity check and started a new one with the option to write corrections to parity enabled.
EDIT: Parity check fixed all errors. Ran an additional parity check afterwards to make sure which came up with 0 errors. All good, thx.
-
I had an unclean shutdown while files where being written to the array (download docker was running). After restarting the server it automatically started a parity check and 4031 Errors where found.
Default setting in parity Options is to write corrections to parity but that didn't happen. After parity check was finished I rebooted the server and ran another parity check without the option to write corrections to parity ticked to make sure all is fine now.
It shows the same 4031 Errors at the same sectors.
I know parity sync errors are to be expected on hard shitdown when files where being written to the array but why didn't the sync errors get fixed during the first parity check, are auto parity checks run without the option to fix and I should just run another parity check with the option enabled?
None of the drives show any errors in the column on the main page and SMART looks good on all drives.
-
When I move files from one share to another with Krusader, they get moved OK and are accessible through SMB but the files are actually not moved to the correct disc assigned to the share. I don't know where this behaviour comes from.
source folder: /mnt/user/Downloads/extracted
Downlaods share assigned to disk 4
destination folder: /mnt/user/Movies
Movies share assigned to disks 1-3
Krusader mount: /mnt/user/ assigned to /media
In Krusader I move the files from on panel to the other using the /media folder on both panels but the files stay on disk 4.
-
42 minutes ago, jonathanm said:
spaceinvader one has a video on youtube about sending one container through another for exactly what you are talking about.
Thanks. I will check that out.
Would this method be in any way better than just using the qbittorrentvpn Docker with its own vpn connection?
-
Hello,
I set up the sabnzbd docker with PIA and everything is working great so far.
Next I want to add a qbittorrent Docker to my Unraid Server.
My question now is what would be better, use the qbittorrentvpn Docker or use Privoxy on the sabnzbdvpn Docker and route the traffic through there?
correct way to fix disk errors
in General Support
Posted
Thank you, I appreciate both of your help on this.
I somehow was thinking about data corruption protection like ZFS or BTRFS to fix potentially broken files, which parity doesn't give me.