-
Posts
3 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by dyedfire
-
-
I've encountered an issue on my hard drive where it produces errors like this on the disk log:
Mar 21 16:42:04 TemposRAID kernel: ata1.00: exception Emask 0x10 SAct 0x30000 SErr 0x4090000 action 0xe frozen Mar 21 16:42:04 TemposRAID kernel: ata1.00: irq_stat 0x00400040, connection status changed Mar 21 16:42:04 TemposRAID kernel: ata1: SError: { PHYRdyChg 10B8B DevExch } Mar 21 16:42:04 TemposRAID kernel: ata1.00: failed command: READ FPDMA QUEUED Mar 21 16:42:04 TemposRAID kernel: ata1.00: cmd 60/00:80:c8:2a:e6/01:00:9d:00:00/40 tag 16 ncq dma 131072 in Mar 21 16:42:04 TemposRAID kernel: ata1.00: status: { DRDY } Mar 21 16:42:04 TemposRAID kernel: ata1.00: failed command: READ FPDMA QUEUED Mar 21 16:42:04 TemposRAID kernel: ata1.00: cmd 60/00:88:c8:29:e6/01:00:9d:00:00/40 tag 17 ncq dma 131072 in Mar 21 16:42:04 TemposRAID kernel: ata1.00: status: { DRDY } Mar 21 16:42:04 TemposRAID kernel: ata1: hard resetting linkThis accompanies with a sound coming from the hard drive itself, as if it's skipping inside.
At first, I thought it was because of my Sata expansion card but I've eliminated that from the equation.
I also thought it was the sata cable / port from the motherboard to the drive, but simply switching it didn't change anything.
I was in the middle of moving all my files off there a new thing appear on the Array Devices list: errors... About 36. So, I thought turning off "Turbo Write" to test if it was that. No.
After an extended test on the drive itself, S.M.A.R.T. came back with nothing. Before that, Check Filesystem showed nothing.
Before I go through the exhausting method of testing this new Seagate IronWolf with their software (perhaps sending in a warranty claim), are there any other steps that I need to take?
If not, then should I not touch my files (or move them off) and instead replace, then allow the parity to build them back?
Thank you for your time
temposraid-diagnostics-20240322-0739.zip temposraid-smart-20240322-0740.zip
-
On 9/5/2023 at 10:51 PM, Swarles said:
Tagging some people this is relevant for (don't have to do it if you don't want): @Robbie G78, @Kloudz, @sourCream, @wibble, @WWGT, @knights_of_pine, @Chunks, @Taddeusz, and @Magic815
Okay so for everyone where the Mover Tuning Plugin is no longer working and the mover wont run please follow these steps to help me figure this out
Fill out this quick template:
Troubleshooting - Try each step one at a time, if it does not fix your issue try the next one:
- Enable mover logging! "Settings>Scheduler>Mover Settings"
-
(Manual Moves Only): Is "Move Now button follows plug-in filters:" (In "Settings>Scheduler>Mover Tuning") set to Yes? If not, make this change and run the mover again.
If this now works, PLEASE LET ME KNOW. -
Check to see if "share.cfg" exists.
-
Check to see if "ca.mover.tuning.cfg" exists.
ls "/boot/config/plugins/ca.mover.tuning"If it does not exist, go to "Settings>Scheduler>Mover Tuning", make some changes and save and see if it exists now.
If it STILL doesn't exist make a note to tell me and do the following:echo -e "moverDisabled=\"no\"\nmoverNice=\"0\"\nmoverIO=\"-c 2 -n 0\"\nthreshold=\"0\"\nage=\"no\"\nsizef=\"no\"\nsparsnessf=\"no\"\nfilelistf=\"no\"\nfiletypesf=\"no\"\nparity=\"yes\"\nenableTurbo=\"no\"\nlogging=\"no\"\nforce=\"no\"\nignoreHidden=\"no\"\nbeforeScript=\"\"\nafterScript=\"\"\nomovercfg=\"no\"\nmovenow=\"yes\"\ntestmode=\"no\"" >> /boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfgFeel free to change the settings back to what you want and now run the mover again.
If it works now, please let me know. -
Check to see if all your user shares exist in "/boot/config/shares"
ls "/boot/config/shares"All your shares should exist here with the exact same name they have in your "Shares" tab (including capital letters). If the name isn't there or isn't the same, try renaming completely and saving, then renaming back.
Run the mover. If it works now, please let me know. -
If all else hasn't worked please try make changes to the "mover.php" file.
nano "/usr/local/emhttp/plugins/ca.mover.tuning/mover.php"Find the following lines (line 162/163):
logger("ionice $ioLevel nice -n $niceLevel /usr/local/emhttp/plugins/ca.mover.tuning/age_mover $options"); passthru("ionice $ioLevel nice -n $niceLevel /usr/local/emhttp/plugins/ca.mover.tuning/age_mover $options");and replace with the following:
logger("ionice $ioLevel nice -n $niceLevel /usr/local/sbin/mover.old $options"); passthru("ionice $ioLevel nice -n $niceLevel /usr/local/sbin/mover.old $options");Once done, save the file with "ctrl+o" "enter" and then "ctrl+x" to exit.
Try running the mover again. In this case, I would like for you to try run the mover twice, once with "step 2" setting disabled and once with it enabled.
It is important to know that these changes will revert when your server restarts.
If this now works, please let me know and which one or both it worked for.
If you run through these steps and it is WORKING please add the following to your starting template:
If you run through all the steps and the is is still NOT WORKING, please add the following to your starting template:
Thanks guys, doing these steps and reporting back to us will really help us figure out what exactly is wrong. None of these issues are occurring for me personally so it is very hard to troubleshoot.
I just wanted to say that #5 on this list was the culprit for me. There were a lot of old share configurations that the mover was getting hung up on, therefore never running. After a clean up, the move now worked with the proper filters in place.
Thank you for this checklist.
Hard drive on array shows errors
in General Support
Posted
I admit that I do have a few power splitters used for my setup. I'll try re-arranging them to see if I can spot the bad splitter or if there's an overdraw in the power usage. (Leaning more on the former than the latter)