cadamwil

Are the instructions below the correct procedure when using ZFS? Storage Management | Unraid DocsStorage Management | Unraid DocsTo assign devices to To perform the upgrade proceed as follows: Run a parity check if you have not done so recently and make sure that zero errors are reported. Attempting an upgrade if parity is not valid will result in the file system on the upgraded disk being corrupt. Stop the array. Unassign the disk you want to upgrade. Start the array to commit this change and make Unraid 'forget' the current assignment. Unraid will now tell you that the missing disk is being emulated. It does this using the combination of the remaining data drives and a parity drive to dynamically reconstruct the contents of the emulated drive. From a user perspective the system will act as if the drive was still present albeit with a reduced level of protection against another drive failing. If you started the array in Maintenance mode then this will ensure no new files can be written to the drive during the upgrade process If you started the drive in Normal mode then you will be able to read and write to the Emulated drive as if it was still physically present Stop the array. At this point the array is in the same state as it would be if the drive you have stopped using had failed instead of being unassigned as part of the upgrade process. Assign the (larger) replacement drive to the slot previously used for the drive you are upgrading. Start the array to begin rebuilding the contents of the emulated drive on to the upgraded drive. Since the replacement drive is larger than the one it is replacing when the contents of the emulated drive have been put onto the replacement drive Unraid will automatically expand the file system on the drive so the full capacity of the drive becomes available for storing data.

That worked, what's the correct way to replace the last drive and autoexpand the array when the resilvering is done?

Here you go... root@Beast:~# zpool import pool: prossd id: 10603483798625687601 state: ONLINE status: Some supported features are not enabled on the pool. (Note that they may be intentionally disabled if the 'compatibility' property is set.) action: The pool can be imported using its name or numeric identifier, though some features will not be available without an explicit 'zpool upgrade'. config: prossd ONLINE mirror-0 ONLINE sdb ONLINE sdc ONLINE pool: bigblue id: 5709855171605561477 state: ONLINE status: Some supported features are not enabled on the pool. (Note that they may be intentionally disabled if the 'compatibility' property is set.) action: The pool can be imported using its name or numeric identifier, though some features will not be available without an explicit 'zpool upgrade'. config: bigblue ONLINE raidz2-0 ONLINE ata-ST16000NM001G-2KK103_ZL2558AN ONLINE sdn ONLINE sde ONLINE sdf ONLINE sdg ONLINE sdd ONLINE sdm ONLINE sdi ONLINE root@Beast:~#

Hello All, I have been in the process of swapping the drives in my 8 drive ZFS2 array named Bigblue. The reason was two fold. The first being another 4TB drive had started to show errors, the second being I had already previously swapped two of the 4 TB drives for 16TB. I have purchased 6 more 16TB drives and have swapped all but one using zpool offline bigblue GUID > followed by zpool replace bigblue GUID sd#. Earlier I asked on discord why the drives weren't showing in the interface and were listed as dev, and was told the way I had swapped them was wrong. So I stopped the array and when selecting the correct drives for replacing in the UI, I see a wrong label. What is the correct process to remedy this? Remove the array (not delete) and then re-add? Let me know if I need to attach any logs.

Ditto, I am having this on my eth3 all of the sudden.

This doesn't mean anything to me, but all 4 nics have the same firmware and only an unused NIC is showing the error. root@Beast:/mnt# ethtool -i eth2 driver: ixgbe version: 6.1.106-Unraid firmware-version: 0x800003e1 expansion-rom-version: bus-info: 0000:03:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes root@Beast:/mnt# ethtool -i eth3 driver: ixgbe version: 6.1.106-Unraid firmware-version: 0x800003e1 expansion-rom-version: bus-info: 0000:03:00.1 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes

It has been suggested in other places to update the firmware, but I can't seem to find anything older than X550 and the X550 update software shows the following. root@Beast:/mnt/bigblue/BlueDrive/X550Nic/X550/Linux_x64# sudo ./nvmupdate64e Intel(R) Ethernet NVM Update Tool NVMUpdate version 1.40.5.5 Copyright(C) 2013 - 2023 Intel Corporation. WARNING: To avoid damage to your device, do not stop the update or reboot or power off the system during this update. Inventory in progress. Please wait [|.........] Num Description Ver.(hex) DevId S:B Status === ================================== ============ ===== ====== ============== 01) Intel(R) Ethernet Controller N/A(N/A) 1528 00:002 Update not X540-AT2 available 02) Intel(R) Ethernet Controller N/A(N/A) 1528 00:003 Update not X540-AT2 available Tool execution completed with the following status: Device not found. Press any key to exit.

Hello, after a recent reboot I am seeing the following error repeatedly in the event log. NIC is X540-AT2 ixgbe 0000:03:00.1: Warning firmware error detected FWSM: 0x00070000 Any suggestions on resolution? I have a Supermicro X10DRi-T4+ motherboard and previously have not observed this issue. However, it now seems to occur every 2 seconds.

TLDR: I am looking for help to make my server perform as good as possible in Plex, then my Desktop VM, and lastly in docker or file shares. Any help would be greatly appreciated. I have the following hardware: 2x Xeon E5-2660 10 core hyper threaded CPUs at 2.6Ghz 64 GB of ECC Ram 2 x 4TB drives in the unraid array (Xfs) 2x 1.6TB PCIe NVMe drives as the Cache drive in btrfs pool (Raid 1 equivalent, I think) 8x 4TB ZFS2 Pool for 22.6TB (Main data pool) 2x 256GB SSDs for VM in ZFS1 Pool The issue I am having is two fold. I use apple TVs for my TVs and Plex seems to hang during transcoding using the plex app, but plays fine through infuse. Even when using infuse, sometimes the movies glitch for a second or two. All of my network in my house is hard wired at 1GBps ethernet. Server has 10GB Nics running to a 10GB switch that then serves all other devices. I have pinned 4 CPU and the hyperthread cores to Plex and still seem to have an occasional hang. Should I config Plex to use /mnt/cache/appdata/Plex-Media-Server/Transcode for transcoding. It's currently set for /mnt/user/appdata/Plex-Media-Server. Also, the VM is configured for 6 cores plus the hyperthreaded core, and 16GB of ram. That said, sometimes the VM is pretty sluggish. If anyone has recommendations on ways to improve performance, please let me know.

With great troubleshooting help from @ljm42 we narrowed the issue down to an incorrect DNS setting which was likely causing a timeout. Once the DNS servers were all responding, the issue was resolved.

Just checking if this is still an issue. I am getting However, when I try to SSH to backup.unraid.net from the console, I get the However, when I try the Update button on the flash backup, I don't see SSH (TCP 22) traffic passing through my firewall, I only see it when I manually try from the console.

what would a typical setup be for appdata, domains, and system. In my setup, all are set to prefer. I do have a btrfs mirrored cache setup, but I also have space on the array as my real main storage is my ZFS array. Any downside to changing those from Prefer to yes?

after digging, scrub, same as ZFS.

Also, in unraid or btrfs what's resilvering/rebuilding an array called?

Solved both problems in the other post.

JorgeB, You are a gentleman and a scholar. Sure enough, after installing the PCIe NVMe SSDs, the number of the resource had changed and it was assigning one of the NVMe SSDs to my Windows 10 VM, instead of a USB 3.1 card as desired. Once I swapped that around, it fixed the NVMe disappearing when I started the VM (which I didn't correlate until you mentioned it). Then I was able to have both NVMe SSDs in the cache pool. Lastly, I was able to create a temp pool with one of the old cache drives and mount it, and copy off the data I needed. However, I do have a question. I thought data from the cache, was supposed to be flushed nightly to the array by the mover, is that not correct? The data wasn't on my array, only the old cache drive.

Hello All, I am suspecting I have a bad NVMe drive. But I wanted to check my logic. Here's what I have done and observed. Installed two used Intel PC3600s into my server. One looked happy, unconfigured, and showed a format button. The second showed the no symbol and array (I think). I figured it contained stuff that was recognized and ran a pre-clear, which it failed saying out of space. Thought this might be a fluke, but then it appeared in history. I stopped the array, and upon removal of the history and a restart of the array, I could see the drive. I then added it as my second cache drive. When I started a VM, I got an alert that the drive was missing from the array. It still showed in the MAIN page under cache. However, when the array was stopped, the drive would then show in history. If you restarted the array, I believe it showed up as a new ID? nvme1n2 or nvme2n1, and then again, when I restarted one of my VMs, alert of drive missing. Lastly, I removed the suspected bad drive from the cache array, and restated the array. Then I was able to start my VM without the drive missing alert. So do I have a bad drive or is something flaky in unraid? Diags attached. beast-diagnostics-20220521-2247.zip

clarification, when you try to start those VMs, the location referred to is mnt/user/domains/hassos_ova-5.12.qcow2 which no longer seems to exist, the other VM does the same with a different disk file.

OK, here's what happened, I purchased two used Intel PCIe SSDs and replaced my existing SSDs as cache drives. I then upgraded to 6.10. I am pretty sure this has nothing to do with the upgrade and everything to do with the cache disk replacement. Somehow, I have lost two of my three VMs. The other being stored on a ZFS array. The two affected VMs were stored on the cache drives. How can I get the disk images off the old cache drives, they were btrfs mirrored. They are still installed but will not mount. Diags attached. The old cache drives are sdk and sdl. Adam beast-diagnostics-20220521-2201.zip

Well, apparently not having a fan in FANA or hiding FANA was the issue. Now everything is working well.

OK, got everything close to working, however, I'm missing my ABC fans on my Supermicro X10 motherboard. It's just showing the 1234. Can I just add the lines to the fan.cfg? Can I get it to detect them? Thanks for your time.

any recommendations for editing smb-extra.conf to see the snapshots as shadow copies in windows? My snapshots look like %PoolName/%dataset@autosnap_%Y-%m-%d_%H:%M:%S_%snaptype with %snaptype being daily, weekly, hourly, or frequently. I tried shadow: format = autosnap_%Y-%m-%d_%H:%M:%S any help would be greatly appriciated.

Just FYI, I think I was having a similar issue to Marshalleq. On RC2, when I stopped the unRAID array, which stopped my VM, restarted the unraid array and attempted to restart my VM, it would hang the VM management page (white bottom, no uptime in unraid) and then if you attempted to reboot, it would not reboot successfully. You would have to reset the machine to reboot. However, with RC4, everything seems to be working correctly.

What's different between RC2-RC4?

the rm -rf mounting point got it. Thanks again!