sincero

This is a follow up to: I replaced Disk 4 since it was already throwing a ton of errors and reading at 1MB/s. I still have another 12TB drive that I would like to add to the array but I don't want to expand the number of drives (power is one aspect, but there is also the failure rate of having too many drives, plus I don't trust some of these drives anymore), so I would like to replace another drive. I've attached new diagnostics; promathia-diagnostics-20231219-1401.zip I'm thinking disk1 should go as it has had some spurious "errors" (from the dashboard) at times, though the SMART data is clean. tldr; you have to replace one of these drives, which would you choose? I will be draining the disks to swap filesystems later.

All the disks in this machine are from 2014/2015. I figure they're probably going to all be dying over the next few years so I'm considering whether it makes sense to replace them all with 6TBs or 8TBs to get fresh drives and another 5-10 years out of them. Thoughts? My server lately grows at about 1.2TB per year, so I'll need more space eventually anyhow.

Thanks! I'm planning maybe to upgrade over half the disks anyway (or maybe replace them all with 8TB) so I think this should take care of it since they'll have all new filesystems. I'll probably just wait until Black Friday for some of them.

Thanks! So if I understand correctly, I can proceed with a parity swap once I order a new disk?

promathia-diagnostics-20230929-0159.zip

It looks like I should replace Disk 4 which has terrible performance and is barely able to read data from (though, I can.. I did manage to copy a few files off it to test). Disk 2 seems fine from a performance standpoint. unRAID has not marked Disk 4 as bad. However, the syslog has a ton of sector read errors. It has to be replaced, clearly. How should I proceed? Should I manually remove this disk from the array and let parity take over? The disk is not marked as bad. Can I buy a couple 8TB disks to take over? This should give me a bit more room and get some of the ageing disks out of the array. Or should I shut it down and replace them then? I have a full backup at home on another machine, so there is no concern there. But it would be nice to avoid needing to copy all 14TB back over gigabit slowly

FYI this is a bit older but make sure to to the Config in Sab and go to "Special" and scroll down to the bottom. There's a section for a whitelist, make sure it reads "tower" or "Tower" depending on how you are trying to access it (or whatever hostname you use for your Sab box) The case sensitivity is key -- it matters.

Hi all, I've recently been using Huginn for a few things and wanted to share an unRAID Template to use it: http://vaughanhilts.me/blog/2018/04/26/setting-up-huggins-on-unraid-for-automation.html I also wrote a guide on using it under unRAID for those less familar. I also wrote a blog post on how to utilize it for something fun here. I hope the community gets some enjoyment out of it.

You can use the -u command in combination with the -D <time> option, this allows you to update only files which have been modified in the last <time> period. Eg. bunker -u -D 1h /mnt/user/files Will update those files modified in the last hour. Note: files must have initially been added using the -a command My worry was more along the lines of I changed 50 documents in the last week for example, and now I need to manually verify each is OK before changing their checksums, no? I can't just let it auto update or it might have gone bad since and it'l get the "bad" checksum and I might not know until it's too late.

Thanks a lot! That's a shame for some of my more frequently changing files. I'll have to think about it, most of the media should be fine, though.

When using the -u or -U command it will only update those files which have been previously added by the -a command. This means that any files which don't have a checksum value in their extended attributes are skipped. If you want to ensure all files have a checksum then run the -a command first. Mismatches can be logged in the syslog (-l option) or in a designated file (-f option). The program will abort execution immediately with an error message when sha256 or md5 executables are not present. If you want to see missing files then you need to make use of the export (-e) and check (-c) commands. This allows you to store the checksums in an external file, which can be checked later for any mismatching or missing files. You need version 1.6 to do this. How does one add files that have not been indexed yet, then? Do I need to run -a over the entire mount again? Then follow up with -U? Sorry... just one more question. How will this prevent against corruptions? I'm trying to come to terms with this situation: 1) I put a file on my drive, call it A, get the checksum 2) A is corrupted silently 3) I run the checksum again and it's marked as "changed" / failed to verify. But... What if 1) I put a file on my drive, call it A, get the checksum 2) I run a checksum 3) I change the file 4) It gets corrupted 5) I run verify / it's marked as changed but I knew I changed it. How does that work?

I'm running unraid 5. I ran... time bunker -U -md5 /mnt/user/Media/ and it finished in about 3 minutes and 40s. I don't know if I have the sha256 package or MD5, really. Is there anything I need to do before running that? It seemed a little too quick. I don't see a .log file in temp, either. Additional question: How does this handle deleted files with -U / exporting?