bonienl

Thanks for the suggestion about the disks , I will update my examples. Small gotcha ... omitting disks still requires to alter the list! It is true that -D 1 assumes the script runs on daily basis and if a day is skipped for whatever reason it would miss information. Changing to -D 2 would prevent that situation. Leaving the -D option out has only an impact on execution time when there are many files to be examined. For example I have one disk with 300K+ files and running bunker without -D option takes about 45 minutes, while the same thing with -D 1 is a few seconds.

Icon sizes in the GUI have been standardized on 48x48 across all pages. How large are your proposed icons?

I presume you know you can already set them as non-exportable by simply clicking on the disk on the main GUI page. In version 6 this has moved under Shares -> Disk Shares

A n00b Q&A Why don't you move the data off of your 400/500GB disks to the new 3TB disk, reducing the likelyhood of multiple disk failure (and freeing up SATA ports in the process)? Having another 3TB disk as spare may be an option as future investment...

Looks like you don't have proper internet access from that system. Does it have manual network settings and is DNS included ? An easy verification, telnet into the system and do: ping google.com

This looks like an error while writing the extended file attributes. Are you using ReiserFS ?

I created version 1.12 which has a new option -L, this allows bunker to create log entries only when changes are present. See OT for download. As a convenience, together with the bunker script I have also included the bunker-daily and bunker-monthly scripts in the zip file.

The calculation of the ETA works progressive and may be off with the first files, but should become more accurate as more files are processed.

Ctrl-C

Thx archedraft, I have made version 1.11 available with the bug fix for the reporting. See OT.

I do believe that moderators play a large part in the way this forum runs. Thumbs up for them too

Ok, your observations have helped me to determine the error. As a workaround you can run without the -q option.

Or perhaps some cron job defined in the go file ?

The line if [[ $array == STARTED && $rsync -eq 0 ]]; then Ensures that execution only takes place when the array is started and no parity operation is in progress. The monthly cron is executed on the first day of the month at 04:40am, the easiest way to avoid conflicts is to schedule the parity check on another day.

Your daily script looks alright. The error comes from bunker itself, but I can't say what causes it. As a verification what version of bunker are you using (or perhaps redownload and try again) ?

I never had the resolution delay previously and the only thing that did change was I upgrade to V6. Maybe it is inherent to V6. It is not a crucial problem, but within my own LAN DNS resolution usually was instant. I'll try adding the server to my hosts file to see if that makes a difference. Set your unRAID as local domain master, see Settings -> SMB -> Workgroup settings -> Local Master = yes You may need to restart your other devices on the network in order to have this effective.

Here you go ...

I would think that the basic license would continue to work in v7 and beyond - but have not examined the fine print. LimeTech certainly has the ability to limit future features and functions based on the licensed version. Hmm, really? Check out this page: http://lime-technology.com/registrationkeys/ It says "Single unRAID® Server Basic Registration key … $59 (unRAID 6 only)". I don't mind paying for this software. It's excellent and I've been using it since 2009. Although I am bummed that I missed the sale prices Basic license was introduced with version 6 and can't be used with version 5, this is explained on the Limetech page. Where do you read basic license is not valid for any newer version beyond version 6? I'm just basing that off of the text I quoted from the linked Licensing page. I was pretty sure I was right to interpret that to mean the Basic wouldn't be good for future versions, but it was unclear enough for me to pose the question here. I'm glad I did because it sounds like the Basic license is good for future versions! I need to get a more definitive answer from Limetech though before purchasing. Perhaps the explanation isn't clear enough, but the remark unRAID 6 only needs be read in context of the current availability of version 5 and version 6.

I would think that the basic license would continue to work in v7 and beyond - but have not examined the fine print. LimeTech certainly has the ability to limit future features and functions based on the licensed version. Hmm, really? Check out this page: http://lime-technology.com/registrationkeys/ It says "Single unRAID® Server Basic Registration key … $59 (unRAID 6 only)". I don't mind paying for this software. It's excellent and I've been using it since 2009. Although I am bummed that I missed the sale prices Basic license was introduced with version 6 and can't be used with version 5, this is explained on the Limetech page. Where do you read basic license is not valid for any newer version beyond version 6?

You won't be able to do PCI passthrough So does that mean any PCI add-on cards would not be accessible to the VMs if I wanted to do that or does it mean something else? Would the VMs still have access to available USB ports on the motherboard? I also don't have IOMMU, this would do hardware emulation, Windows shows me the USB ports (haven't connected anything to it though)...

One mighty case you have, I like the cabling too... very neat!

You can click on disabled and read more details in the wiki.

I bought drive cages right from the beginning and initially I didn't need all slots, but adding or replacing drives without opening the case is really worth the investment, personally I never regretted.

After a reboot files will be gone, you need to copy them back. I have the following in my go file # Copy scheduler programs cp /boot/custom/bin/bunker-daily /etc/cron.daily cp /boot/custom/bin/bunker-monthly /etc/cron.monthly