FDMK
Members
-
Joined
-
Last visited
Everything posted by FDMK
-
It has been a while. Took a lot of testing and rebuilding but I think I have pinpointed the issue now. I applied the tunables from powertop and that seems to be the issue, especially the 'Enable SATA link power management', when those are applied it takes a couple of days and/or disk sleep cycles to 'fail' the disk.
-
fdmnas-diagnostics-20230501-0638.zip
-
Maybe not, after a day the disk errors again 😞 Apr 30 11:18:58 kernel: md: disk1 read error, sector=13464173520 Apr 30 11:19:08 kernel: md: disk1 write error, sector=13464173520
-
I replaced the cabling, performed an extended smart test and a FS-check/repair, everything seems to be working fine according to the logs. I decided to rebuild the original data-drive before replacing the parity disk with the 18TB.
-
Diag attached fdmnas-diagnostics-20230427-1047.zip
-
I intend to keep my data The way I see it is that the parity-disk contains all of my data, no? Can I execute the plan I wrote? What I meant by 'consume' is that I can play the media that is on the share. I will post the diag.
-
Yeah, I have read that article but I wasnt sure it was applicable to my situation. @trurl I can consume the data that is on the share that is hosted on the 12TBs.
-
I'm a bit in a squeeze, I have a array that consists of the following: P - WD12TB D - WD12TB - disabled because of read/write errors. D - MX500 D - MX500 I have ordered a 18TB disk to replace the disk with the IO-errors but found out that I have to replace the parity drive because the replacement is bigger than the data-drive. Can I do the following and keep all of my data? 1. Stop the array 2. Power down the system 3. Replace the faulty drive with the 18TB 4. Switch the old parity drive to the data-slot 5. assign the 18TB drive to the parity-slot 6, start the array
-
Here my diag fdmnas-diagnostics-20230125-1711.zip
-
I have the same issue. Dockerd and Containerd remain on the array although I stopped docker and set the cache setting for all shares to cache-only. Everything works fine but the result of this is that my HDD keeps being active.