Leaderboard

That just tells you what is on cache. It doesn't tell you whether or not any of it would be moved to the array; i.e, files from cache-only or cache-prefer user shares would not be moved from cache. And it doesn't tell you if any files would be moved from the array to cache; i.e, files from cache-prefer user shares. Another approach would be to disable mover for the duration of the test.

If you haven’t signed up or missed our July digest, check it out here 🤙🤙

Hey guys, everone who`s trying to passthrough a Vega 10 card to a VM will know this issue. Restarting a VM isn't possible without resetting the whole server. The card will stuck in a D3 power state until Unraid is rebootet. The early adopters of TR4 and AM4 might already know this guy from fixing some bugs which made it into the kernel and a lot of people using Unraid benefit from his work. He did it again and fixed the reset bug together with AMD for the mentioned cards. This might be a useful information for a couple users and might also be something @limetech is interested in to implement into the next releases. https://forum.level1techs.com/t/vega-10-and-12-reset-application/145666 Here is a short video from him showing that it is working right now with a MacOS Mojave VM.

Via Tools->Diagnostics.

That's still the syslog It's not unRaid. It's Marvel. They are a company that bangs out cheap controllers en masse and don't particularly care about driver support (similar to Realtek) As kernel versions increase, problems become more prevalent. LSI is recommended But, sans diagnostics, you may (if not using VMs with passthrough) get better success by disabling VT-x and IOMMU (VT-d) in the BIOS.

Not quite, here is the explanation of how parity is calculated: https://wiki.unraid.net/index.php/UnRAID_Manual_6#Network_Attached_Storage Let's assume that you have an 8TB parity drive. Your array consists of several different size data drives (-- all 8TB or smaller). One of these data disks is a 500GB hard drive and that HD has the drive motor fail. To be rebuild this disk, only the first 500GB of the parity data is used (or needed). (A small bit of trivia knowledge for you-- The the actual calculation that is performed on the data to get the parity bit is called is an XOR operator. The XOR operator has been a member of the basic microprocessor instruction set since the 8008 days-- 1972.) While you may think that building parity (by writing 'zeros' to the portion of the parity drive that is not be actively used for calculating data parity) is a waste of time and resources, it makes sense from the logical software development standpoint of what has to happen when you add a data drive that has a larger capacity than any of the currently installed data disks. When this happens, you don't have to 'adjust' parity if you write all zeros to the drive being installed. Parity will always be correct. This 'zeroing' of the new drive is the first thing that Unraid will do. Then, if it finishes without error, Unraid will add the disk to the array and format it (can't remember if it asks permission or not). As this formatting (adding the basic file system structure) occurs, parity (less than 1% of the total data disk's capacity) will be updated as this formatting is being done.

This ones a monster

Sure, no matter what file system, sometimes I will re-arrange and then rebuild parity. Pls also take care on power splitter/adapter, I like build all by DIY. Good luck.

Cool stuff

EUREKA! Now able to pass primary GPU to VM. I got the idea from Spaceinvader One's latest videos about the AMD GPU Bug work-around. So, Here's what I did.... Booted unraid (watching it boot on primary display) All VMs were stopped Ran User Script (edited with my GPU info) (this script disconnects the GPU from Unraid. Puts Unraid to sleep [requiring you to press the power button to quickly turn Unraid /system back on]. The primary monitor turns off or reports "No signal". Once the system is back on, the script has Unraid re-scan for GPUs. The primary monitor remains off/no signal) Once you press the power button to wake the system, wait for the Script to report "Done" (takes 45 to 60 seconds for me). Start VM linked to Primary GPU = WORKS! (Note: I pre-installed the GPU drivers and it WOULD NOT work if I linked the "Graphics ROM BIOS". Leave it blank) Alright Community, I need you to help me figure out how to get this to work automatically, on boot up, without having to turn it back on from sleep. Also, this causes an issue when rebooting/shutting down Unraid. Unraid will not successfully reboot or shut down after running the script (on the primary GPU). It does seem to stop the Array correctly whey you select Reboot or Power Off. It just doesn't seem to shut all the way down. Pressing the "Restart" button on the front of the PC successfully restarts Unraid and Unraid reports no issue with the array or parity upon boot. *UPDATE: I have discovered that this has the unintended consequence of also disconnecting my PCIe TV Tuner from Plex. I have not yet come up with a fix. Again, Shout out to Spaceinvader One! I would be nowhere with out his work. CPU: 1950x Mobo: rog zenith extreme RAM: 8x4GB ECC GPU: GIGABYTE GeForce GT 1030 (in Primary Slot....for now), and ZOTAC GeForce GTX 1050 Ti (in secondary slot, passed thru to VMs [unfortunately covering a PCIe1x slot]) Storage: 500GB m.2 (Cache); 1TB m.2 (Dockers & VMs); 500GB m.2 (Games); 12x HDDs (Storage)

You want to enable bridging in the network settings. This will set up a bridge (probably called br0). Then in the VM settings you want to change the network adapter from virbr0 to br0.

Well, I guess I’ll be the first to put in a request. It’s a Rosewill RSV-L4411 4U rackmount case. This one has the front cover removed for easier access.

Why is this your first post to our forum? There are solutions to the "dealbreaker" you mention, and probably solutions to any other problem you might encounter. There are a lot of friendly and helpful people here on this forum that give FREE support. Why haven't you taken advantage of it? There is a plugin that will run mover based on how full cache is here: https://forums.unraid.net/topic/70783-plugin-mover-tuning/ Another solution to your problem is more careful consideration of what you cache. Mover can't move to the slower array as fast as you can fill the faster cache, regardless of how frequently mover runs. So not caching some user shares or not caching very large transfers, for example are ways to deal with that. I don't get why you haven't taken advantage of our forum. This user community is one of the very best on the internet, and one of the very best features of Unraid.

This worked for me too - BUT - I had to update the firmware on my UPS first. I have a Smart-UPS 1500 which was reporting firmware 8.3. There was no Modbus option in the advanced configuration menu until I updated to current firmware (version 9.4 as I write this). Download from Schneider's site here... https://www.apc.com/us/en/faqs/content/?id=FA281865 Note - you need to have the PC doing the update (and ideally its monitor) powered direct from the mains, since the UPS outputs will be turned off during the update process. It takes just two or three minutes. My screen was still on the UPS so I lost that during the update, and although I could see that it had completed on the UPS screen, I then had to manually re-enable the output on the UPS to get the screen back. 🙄

@bubo & @Masterism Colony Server is now fixed and works fine, i recomend you to delete the container completely and redownload it from the Community Applications (write down your settings and don't delete the folder in your appdata) since i had to change the template a little bit for the ports. But should now work as bevor.

Disk looks fine, try swapping it around with a disk on a different controller.

https://forums.unraid.net/topic/76878-support-josh5-unmanic-library-optimiser/

Back in the day unraid was limited to 2.2TB, so the largest drive was practically a 2TB. That changed with the advent of unraid 5.0 I believe, and the new limit was ReiserFS, at 16TB. Since 6.0, or whenever XFS and BTRFS were added, the limits aren't really in sight any more, at least not for several years. If you are still using ReiserFS, you will have performance issues with larger drives, 2TB is stretching it performance wise. There is still an issue with older hardware that can't see more than 2.2TB, but that's not anything that unraid can bypass.

I've got a test in progress, I'll let you know the outcome. 1. Set up container on unraid at location A. - done 2. Install client on Windows 7 VM running on unraid with urbackup server. - done 3. Run default backup on VM. No restart, just install and start backup. - done 4. Configure port forwarding. (All 3 ports, was that necessary?) - done 5. Spin up blank VM with iso bare metal restore image at location B. - done 6. Connect to urbackup server, select backup completed in step 3. - done 7. Restore backup and compare VM at location B. - 6% complete, may be waiting a while due to internet speed. Test cancelled indefinitely. SSD cache at location B disappeared. 😪

The only size limit you will encounter for many more years is hardware compatibility. Unraid software can handle any size disk your hardware can support.

I'm trying 6.6.7 and there are no issues like the above.. I couldn't even install or update a docker image - let alone goto the docker page in the GUI while copying data via SMB or the mover running... 6.6.7 i can happily do that - and have plex running as it should. So whats broken in 6.7.x...

I moved this to the new thread: Just a hint: I moved my appdata-directories (the ones who are using sqlite) to an external drive using the "Unassigned Devices"-plugin. Normally appdata is on /mnt/disk1/. Upgraded from 6.6.7 to 6.7.2 and have no database corruption since. I do not have a cache drive. I think the database corruption must be something to do with array-functionality. I will downgrade tonight and move the appadata-directories back to /mnt/disk1 and then upgrade to 6.7.3-rc2.

So I had the same issue but the solution made me feel like an absolute idiot....spent a good 20-30 minutes trying to figure this out but eventually got it: 1. Enable advanced config options on your UPS via the on screen display 2. Open configuration options and scroll down until you find ModBus 3. Change ModBus to Enabled. It is disabled by default on all APC UPS units. 4. In unRAID UPS Setting menu, set the "UPS Cable" to USB and set "UPS Type" to ModBus. No additional settings like /dev/tty** are required. It may take a minute or two for the info to load but it will. ***Make sure you use the USB-A to USB-B cable to connect your UPS to the server, not the RJ-45 to USB-A. ModBus does not seem to work with the RJ-45 port on the UPS***

Controller is being detected as PATA only, not AHCI, see if this helps:

The normal recommendation is to do a New Config and assign all disks as data disks (I.e. No parity disk). If you then start the array one drive should show as unmountable - that will be the parity disk. You can now stop the array; do another New Config; and this time assign the disks correctly. When you now start the array the system will rebuild parity. The order of data disks is not significant unless you have User Shares set to use specific disks, but this is easily correctable It will be a good idea to take the chance to record all the serial numbers of your drives in case this happens again. A screenshot of the Main tab is the easiest way to do this.

Had this running overnight during my monthly parity check, and it seems to be doing great! I had my projects set to defaults for resource usage just to see what would happen in docker, and there doesn't seem to be any impact to the rest of the system. My CPU does stay pegged but it didn't affect my parity check at all. I also had some torrents seeding but they don't usually have any impact anyway. Tonight I will try with NZBget running at the same time and see what happens when unpacking some rars. I highly recommend this docker for anyone interested. BOINC has a lot of scientific projects to choose from.