aquariuz23

Got it, thank you very much for the assist

Got it! As always, appreciate your clear and to the point answers! Thank you.

hi @itimpi thank you for your reply. Are you referring to this portion of the Parity Check settings? I was thinking that this meant that the check can run at any day of any week of the selected months. If that's not the case, then I am gravely incorrect lol! Should I just manually select a day and a week that I want it to run, rather than leaving it as "every xxxx "? And after I change the settings, should I start the check over again from scratch, or will the plugin pause/resume normally after the change? Hi @JorgeB I almost certain I don't have any 12 year old Seagates in my array (knock on wood) so I guess it would be fine to leave correcting check on

Hello all, apologies for resurrecting an old thread but thought I should ask these questions here since it's quite related. I have several m.2 nvme SSDs in XFS format as well as a couple of 2.5" SSDs in btrfs format. Both 2.5" SSDs already have autotrim enabled in their respective settings. One of the nvme SSDs have autotrim enabled while the other two don't. These settings were all set automatically by the system. My questions are: 1. Should I enable autotrim on the other two nvme SSDs? 2. If autotrim are enabled on all SSDs, do I need to enable TRIM schedule under TRIM settings? 3. What would be the difference between autotrim vs trim that is scheduled via trim settings? If there is a difference, which would be a better one to use? Thank you

Hello all, I've recently attempted to run a parity check with the parity check tuning plugin installed and using the increments setting to try and split the parity check into a few days of work. However, I seem to be running into a weird situation. It has been over 4 days now and it seems that it keeps starting over from the beginning rather than resuming from where it was paused. Allow me to explain a bit from the start of my journey. I configured parity check and parity check tuning settings so that it runs every quarter (Jan, Apr, Jul, Oct) at any day or week of said months. I would like it to increment the check daily from 00:15 to 09:30. I set that increments will be used for scheduled and manual parity checks only, as the other checks throws me an alert that it's not wise to set increments for those. When the check first ran automatically, I noticed that it did not pause at 09:30 and I thought I had done something wrong. But then I noticed that my timezone was incorrect (PDT instead of EST) and so it would've paused at 12:30 instead. At this point I had already manually paused the check. The progress at this point was already around 31-32% complete. After fixing the timezone issue, I observed the following day whether the check will automatically pause at 09:30 EST, and sure enough, it did. The progressed showed somewhere around 64%, and I thought everything was good at this point and the whole parity check will complete in the next day or so. At some point in the night, I recalled that I had manually resumed the parity check earlier than scheduled to allow the check to complete sooner. However, yesterday when I checked on the progress, the percentage count had gone back down to 30ish %, seemingly indicating that the process had started all over again. I was annoyed but was like, that's alright, let's just get through this. But today, I woke up to see the same thing happening again. The progress is back to the 30ish % again. At this point, I'm not sure what is causing this. My server didn't restart or lost power (to the best of my knowledge) and I can't seem to see a cause for this other than it restarting over when it resumes. It is possible that my settings are incorrect and that my action of manually resuming it caused some kind of issue, but it is still odd that it started over twice now. I'm worried that my parity check will never complete at this point unless I remove the increment settings. I've attached my most recent diagnostisc, as well as screenshots of my settings. I hope there's a solution to this. Thank you. magi-unraid-diagnostics-20241011-0857.zip

@JorgeB, wonderful! Thank you so much for the guidance, everything is working perfectly normal now!

Hi @JorgeB, good day to you I finally had a chance to move my external 2.5" SSDs internally into my Unraid server. As expected, the device IDs on these pools are now "wrong" and I can't proceed to enabling the array. You mentioned that I can re-import the pool, but I'm not sure how I should go about doing that. My apologies if this is a very straightforward process. I'm just worried of doing the wrong steps and making a bigger mess. Just as a refresher, I am not swapping the drives for those pools with new drives, just moving those same drives from an external enclosure into the server and connecting them directly via sata ports. My only real concern is messing around with the pool and having to reconfigure my docker apps so they all work again normally. Please let me know how I should proceed from here. Thank you very much for all your help.

Hello all. I have a Synology NAS that I use to backup my personal PC and still have some empty space in it that I would like to use as an external backup for the critical components in my Unraid server. While the array itself is "protected", I don't have any backups to anything else outside of the array, such as my cache, docker cache, and VM drives. These drives are nvme m.2 drives and while I trust them to be very reliable, I noticed that a few of them have already have a high count of reads and writes on them. Well, high as in the 20s-30s thousand writes; probably not that high, but again, I don't want to risk having a quick way to restore them if they ever decide to keel over. What would be the best way for me to back up these pool devices to my Synology NAS? They're in the same network so hopefully it's not too complicated. It could be something automated once every week or even once a month, since I rarely install new apps or update them. I have a Home Assistant VM that is probably the most active thing on my Unraid, so that's also critical. Any suggestions is appreciated. Thank you. Oh, and if I need to upload my diagnostic file, please let me know.

Hi @JorgeB, thank you very much for your guidance. Let me give it a try and hopefully it's pretty straightforward without any surprises.

Hello all, first off, my apologies if this topic has been discussed ad nauseam elsewhere here; if something close to what I'm in need of help with has been discussed, please help point me to the right direction. It's been quite sometime since I last had to dabble with my unraid server, which I guess is a good sign regarding the reliability and stability of Unraid. As such, my knowledge on how to manuever around Unraid is somewhat rusty right now. This year, it seems the storms have gotten quite a bit stronger and more often in my area, and as a result, we tend to lose power more often than we're used to. I have a battery backup for the server, but the power outage almost always outlasts the battery itself. Part of the problem with my setup is that I have two Pool devices that are situated outside of the server itself, in an external drive enclosure. While this enclosure is also connected to the battery backup, when it runs out of juice, the external drive enclosure will not power up by itself when the power is restored, whereas the server will do so. This results in the array not being able to start by itself due to missing devices. And so, my question is: What would be the best way for me to migrate these external pool devices internally into the server itself, so everything can start back up the moment power is restored? I need to double check my connections inside the server, but I'm forseeing two options - 1. Move those existing external 2.5" SSDs into the server and connect them as is if I have available SATA ports and power cables ....or..... 2. Completely copy the content of those two external drives to two different internal drives, maybe m.2 SSDs I'm leaning more towards the first option, since I'm assuming this will be just plug and play. But I also think it won't be that simple, because the hardware ID for these external pool devices will be different once I remove those drives from the enclosure. Currently, IDs show the controller of the external enclosure, and when I remove the drives and connect them internally, the IDs would switch to that of the drives themselves, if I'm not mistaken. Any recommendations on what I should do? And if I should include diagnostic file for this question, please let me know and I'll include one. Thank you.

HAH! How did I completely miss that line? LOL. Thank you so much, and yes it is now working perfectly fine like before

Hi Rysz, I figured out what I did wrong, but it seem to not have fixed the issue. I seemed to have accidentally linked the USB connection for the UPS to one of my VMs, which would explain why NUT can no longer see the UPS. However, even after disassociating the UPS from the VM and rebooted my server, NUT's status still shows as Stopped. I'm not sure what else is preventing it from working properly. Is there a way to restart the NUT service without having to reboot unraid altogether?

Hello Rysz (and everyone else here), I seem to be running into a strange issue with NUT. I'm not sure when this started occuring with NUT on my Unraid server, but for some reason, it would not want to run, at least I think it's not running. I enabled the footer and it disappeared. When I go to the NUT settings, and restart NUT, I get an error and it asked me to check syslog. I also decided to restart unraid to see if that fixed it, and while it did for a the first few minutes where the footer shows up and shows the correct UPS reading, it all of a sudden disappeared and the same issue happened again. I'm not even sure what to look for or try to do to fix this. I want to avoid rebooting unraid since it takes the server about 4-5 minutes to go through the whole cycle, so if there's any way for me to restart NUT without rebooting, that'll be great. I mean, of course I don't mind rebooting if it's really necessary, I just meant that I don't want to keep rebooting my server. I'm including some screenshots below, along with diagnostic file and nut debug file. Hopefully they can help. Thank you. magi-unraid-diagnostics-20240130-1617.zip nut-debug-20240130132107.zip

Wonderful! Glad to hear it! I hope this last. Appreciate all the help Jorge!

Thank you again Jorge. I just updated to v6.12.6 and rebooted. It seems it rebooted just fine but I can't really tell. The only thing I noticed is that Parity Check is no longer running and that the last check is incomplete and Error Code says aborted. Should I run Parity Check again? I'm generated a new diagnostic in case you'd like to see it. If everything seems good, I'll proceed to mark this as resolved. magi-unraid-diagnostics-20231227-1324.zip