KuniD

I'm preparing for a parity swap, so I've begun by running preclear on a new Western Digital Red Pro 16Tb drive. It is currently 70% the way through the first pre-read phase (15 hours to this point overnight). I noticed the drive seems to be making a ticking noise once a second, almost like a wall clock ticking. I've read that WD drives can tick every 5 seconds but wasn't sure if this was the same thing. I ran a SMART test prior to starting the preclear and nothing came up during that step. Not sure if I'm over reacting.. ! Thanks

So I've been operating 6 x Seagate Archive 8Tb drives for the last 6 or so years. For the most part they're still ticking along although the first has just failed (awful whirring sound), so I'm looking to replace the drive. I'm thinking now is a sensible time to start slowly transitioning the setup to larger volume drives, so will be starting with a parity swap out. While I was initially focused on the Seagate Ironwolf Pro and Western Digital Red Pro lineups, I noticed the Seagate EXOS X16 16Tb is on Amazon for a rather surreal £262; https://www.amazon.co.uk/Seagate-ST16000NM001G-EXOS-X16-Internal/dp/B07SPFPKF4/ Considering most the Ironwolf Pro and Red Pro 16Tb drives are £400-500 this seems like quite a bargain. My Unraid box (in a Fractal Design R5 case) is on the floor next to my desk. I have lived with the whir of the 6x Seagate Archive 8Tb drives without complaint, but am worried that these enterprise/data centre drives may be a lot louder. I can see a lot of comments only saying their very loud, on the other hand I came across this article (see bottom of page) which seems to suggest in a comparison that they're not too bad; https://www.nikktech.com/main/articles/pc-hardware/storage/hard-disk-drives/10110-seagate-exos-x16-16tb-sata-iii-hdd-review?start=7 Does anyone have any experience of these drives in close proximity regular use? Only other thing putting me off the Amazon link is that it mentions its an OEM drive / US sourced and the reviews seem to indicate Seagate won't honour the warranty. I suppose its a trade off on that much storage per £ vs much higher with a warranty.

ok thanks !

Hi all, After 5 years of running my unraid box I'm pretty sure I'm encountering my first drive failure (I can hear the drive struggling lol). Before I power things down, etc, I thought I'd pull the diagnostics and share here for any insights - have to admit I'm not very good at deciphering these ! Essentially I woke this morning to hear a new sound (a louder whirring sound, like a fan failing), and saw unraid had a "Disk 4 in error state" message. The drive has been disabled and I can't access any of the SMART reports, but I'm guessing if I can hear it its a lost cause. I have some questions regarding replacing the drive and rebuilding the array (apologies they are likely to be super basic/obvious, just never been through this process before). Right now I have 6x Seagate 8Tb drives, 1 parity, 5 storage. Firstly, I presume I can remove the failed drive for now, then when I receive a replacement drive the array will rebuild? Secondly, as 5 years has elapsed since building this setup, I want to get a larger drive (Ironwolf Pro 12Tb), so presume I'll need to follow this process (https://wiki.unraid.net/The_parity_swap_procedure) and make the 12tb drive the new parity? I'm a bit confused on whether the failed drive also needs to be present but disabled in this scenario, or unplugged and removed is ok Appreciate any advice and thanks in advance ultron-diagnostics-20211016-1211.zip

Selling a brand new, in box/unopened AMD Ryzen 5900X 12 Core / 24 thread processor. It's excess to needs as I have gone with a 5950X instead and only purchased this stupidly in a mad fit to secure a chip. £490 including next day delivery with DPD. If delivered bank transfer preferred or cash on collection (London, willing to meet half way within reason) UK only

Thank you both - following your replies I decided to get more organised and wrote up a series of elimination tests to isolate what the problem was. In the end I confirmed it was indeed the PSU. I ruled out GPU's ,cabling, CMOS battery, UPS v mains, etc. I borrowed an old Antec PSU from a friend and it ran the system fine without issue. If you can believe it I had 8 days left on my 5 year warranty from Super Flower. I have RMA'd it and am awaiting a replacement.

Hi all, would appreciate your input on the following problem. I have been having hardware stability issues for a while and am struggling to pin down the cause. The issues usually materialise as: 1) Random reboots 2) Random reboots, that then get stuck in a constant cycle of trying to power on but failing to do so besides a brief flicker of fans/lights. I need to either (a) trip my UPS to battery mode (turning off then on wall switch) or (b) kill the switch on the PSU for a minute or so then turn back on to stop this. 3) Reboot triggered by loading a game in Windows bare metal (i.e. Star Wars Squadrons) 4) In some Windows 10 VM's I have noticed screen artefacts On the last point this could be a software issue as it only happens in Windows 10 VM's, not bare metal or MacOS / PopOS VMs. On point 3 I have removed my GTX 970, but still experienced random reboots running on just a GT 710. I have also left Memtest running in the past without issue. I thought I'd also test how my server behaves when I turn the wall socket off for my UPS. Even though doing so leads to my UPS going into battery mode, it still triggers a reboot of the server. This surprised me as my UPS is a 1500VA line interactive / pure sine wave, with nothing else connected to it besides the server. I'm thinking the issue may be either the UPS or my PSU. I'm wondering whether I have a config issue on the UPS or if I'm overloading my PSU / have a faulty PSU. I have put my specs below, including a rough calculation for power usage UPS: APC Spart-UPS 1500VA (SMT1500IC) PSU: Superflower Leadex 80 Plus Platinum 750w Motherboard: Asus X99-Deluxe (?w) CPU: Intel Xeon E5-2678v3 (12C/24T @ 2.5GHz, 120w TDP) RAM: 8x 8Gb Hynix DDR-2133 ECC (5w per stick?) GPU 1: Asus GTX 970 STRIX OC 4Gb (148w TDP) GPU 2: Asus GT 710 2Gb (19w TDP) NVMe: 2x Samsung Evo 970 1Tb (one via PCIE add in board. 5w under load each?) SATA: 6x Seagate Archive 8Tb (ST8000AS0002, 7.5w at load each), 1x Samsung 850 1Tb (5w?) Fans: 4x 140mm fans (4w each?) USB devices: Logitech webcam, Jabra conference mic, sometimes an iPhone, Bluetooth dongle, sometimes recharging keyboard Estimating 400-450w load? Would have thought a 750w platinum PSU from Superflower should be able to handle this.

Hi David, Following Spaceinvader One's new Big Sur video I have just set up a new VM. Would you mind sharing the steps you took using CCC to migrate Big Sur to the NVMe? Thanks

Superfast -all done! Thanks !

thanks, will give the recovery method a try. Should I select the “Catalina” disk or “Catalina - Data”?

Hi all, I have setup a Catalina VM, using a vdisk with GPU and USB passthrough. I now want to migrate the vdisk boot drive to use a 1Tb NVMe. I have successfully passed through the controller and can see the drive available within MacOS. Where I am lost is what I need to do next; what needs to be setup, cloned, reconfigured, etc. I may be being blind but having had a search here and on Google I haven't come across any guidance for migrating an existing MacOS vdisk Any guidance would be appreciated!

<?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>MacinaboxHighSierra</name> <uuid></uuid> <description>MacOS High Sierra</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="default.png" os="HighSierra"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='12'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='13'/> <vcpupin vcpu='4' cpuset='2'/> <vcpupin vcpu='5' cpuset='14'/> <vcpupin vcpu='6' cpuset='3'/> <vcpupin vcpu='7' cpuset='15'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/d1862346-b4b2-4398-b17c-f6e6a82a023a_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='4' threads='2'/> <cache mode='passthrough'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/user/domains/MacinaboxHighSierra/Clover.qcow2'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/MacinaboxHighSierra/HighSierra-install.img'/> <target dev='hdd' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/MacinaboxHighSierra/macos_disk.img'/> <target dev='hde' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='4'/> </disk> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xa'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='6' model='pcie-to-pci-bridge'> <model name='pcie-pci-bridge'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:14:a8:f6'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0b05'/> <product id='0x180a'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='none'/> </devices> </domain>

Thanks for this great docker and guide. First time setting up a VM so please excuse the basic questions; i have setup a High Sierra VM as I have a Nvidia GTX970, but can I pass this through if I only have the one GPU? I have followed the guidance from one of your other videos on adding the associates sound card and changing the XML to mention multifunction. When I start the VM from the servers GUI I get a black screen. Appreciate I have taken the GPU away from Unraid but was expecting MacOS to appear. Any tips or guidance appreciated

Ok I have ordered a multimeter, will check voltage at wall and from output of UPS and report back.

Further update, relates to your second suggestion: I tried to boot the server up again with power connected via the UPS this evening and it successfully booted. I checked the screen on the APC at this time and it was showing input and output voltage at 249. Everything was operating as expected for about 7hrs, when I noticed I could no longer remote into the server. I went to take a look and found that the monitor was off and keyboard/mouse didn't wake the system, but server was on with no activity lights flashing. The screen on the APC now read input 249v, output 221v. I turned off the mains power socket leading to the APC, forcing it into battery mode. As soon as I did that the server came back to life and the monitor came on, showing that the system was rebooting, post/bios screen etc not sure if the output voltage dropping is an indicator of a problem or if the problem is setup elsewhere