johmei
-
Posts
75 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by johmei
-
-
1 hour ago, JonathanM said:
Go to the apps tab and search "torrent"?
So I guess that means doing this over SMB really isn't ideal....I'll give a search and pursue that route.
-
I've been running my torrents such that the client runs on my primary system, and I save the actual data on unraid via an SMB share via a network mapped drive (that is to say, when I open a torrent and qBittorrent asks me where I want to save the actual data, I choose my unraid SMB share that is mapped to a drive letter). I'm starting to think....maybe this isn't such a great idea. Am I on the right path with that thought?
If I am...what would be a suggested alternative method for torrenting on unraid? 🤔
Thank you kindly!!
-
7 minutes ago, trurl said:
The correct way to deal with this is check filesystem. Please ask for help if you get an unmountable disk that should have files on it.
Thank you!!
-
1 hour ago, trurl said:
I would much rather you ask, especially when Format is involved. Unraid will offer to format any unmountable disks, which is NOT what you want to do if the disk is supposed to have data on it.
People sometimes format a disk they are trying to rebuild, perhaps because they think you must always format a new disk (misunderstanding), or perhaps because the emulated disk is unmountable so Format is an option. After format in the array, the only thing it can rebuild is a formatted disk.
Thanks for the explanation there!
And that's a really good point. While I was loosely throwing around the term formatting incorrectly, the one thing I do know is that formatting will always obliterate the data (or at least the index) and in this case, it doesn't matter (the clearing would have destroyed any data already). But I can see where if I was replacing a drive, and it finished rebuilding and this popped up, I could have made a mistake. So I feel better about it now!
Thanks again so much!
-
Also, I feel REALLY stupid. The option to format them is RIGHT there in front of my face. I jumped to making a post WAY too fast which I usually avoid doing but....ughhh...the information is on the web, readily available, and I didn't bother checking. I am so sorry. 😕
-
12 minutes ago, trurl said:
Probably you are mistaken that it spent 12 hours formatting the old parity drives. Format doesn't take much time at all.
When you ADD disk(s) to new slot(s) in the parity array with valid parity, the new disk(s) must be cleared so parity will remain valid. Clearing the disks is probably what took 12 hours.
If they have finished clearing you can format them now. It will take a few minutes at most.
My mistake; I used to do full formats that would take hours so that's where my mind was.
10 minutes ago, trurl said:syslog confirms
Feb 14 15:21:29 Johnsnas kernel: md: recovery thread: clear ... ... Feb 15 07:50:37 Johnsnas kernel: md: recovery thread: exit status: 0
Awesome, thanks! Could you elaborate on what these log entries mean? I'd like to understand them a bit better.
Thanks again!!
-
Sometime last year or the year before I purchased 3 x 12 TB drives. I made two my new parity drives, and added the third one as a data drive. This year I discovered 18 TB drives were now the same cost as the 12 TB drives I purchased previously, and 12 TB drives were not that much cheaper, so I bought 2 x 18 TB to replace my 12 TB parity drives. All went well with that, but when I tried to add my 12 TB drives to the array as data drives I was greeted with that wonderful error after it spent over 12 hours formatting them both. So....things that are different; All my drives were previously connected to an LSI SAS2008 controller. It has a capacity of 8 SATA drives and since I just added 2 beyond that, my parity drives are now on the integrated controller, X370 Series Chipset SATA Controller. Those seem to be working fine and without issue. In fact, all the 12 TB drives aren't even on a different physical cable than they were previously...and I've heard that a bad cable can cause this issue. I've attached the Diag here. I could try again but I wanted to run it by some experts before I try again since I'm assuming if I try to add them again, it'll clear the drive again and will take another 12 plus hours to do so.
Thanks so much!
-
Hmmm....well I didn't change anything, but I did restart the entire server and it seems to be working? I guess it wasn't captured properly when it last started up *shrugs*. I still don't see the Nvidia audio in the device manager, but I don't need it so as long as that won't cause issues...I guess I'm okay
-
I'm at a complete loss here. I have an MSI X370 Gaming Carbon pro with a Ryzen 5 5600G. I was having trouble getting my NVIDIA card passed through but thanks to spaceinvader one's advanced GPU passthrough video, I got it working along with audio. Great! But I wanted to use the onboard realtek audio controller that the manual swears up and down it has (even though you won't see any mention of realteck in the below PCI device) but while I got it working without issue just a few days ago, I went to bootup my VM today and was surprised and confused to see no audio controller. I had to do some fiddling with the XML file for the video card to work, but I didn't for the audio....but now I'm guessing there is more I might have to do? I'm including my VM XML file below as well as my PCI Devices and IOMMU groups. Does anybody have any idea what might be going on? Please let me know if you want me to provide any specific information as well. Thanks so much!
QuoteIOMMU group 0:[1022:1632] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
IOMMU group 1:[1022:1633] 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
IOMMU group 2:[1022:1633] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
IOMMU group 3:[1022:1632] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
IOMMU group 4:[1022:1634] 00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge
IOMMU group 5:[1022:1632] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
IOMMU group 6:[1022:1635] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
IOMMU group 7:[1022:1635] 00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
IOMMU group 8:[1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51)
[1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
IOMMU group 9:[1022:166a] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 0
[1022:166b] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 1
[1022:166c] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 2
[1022:166d] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 3
[1022:166e] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 4
[1022:166f] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 5
[1022:1670] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 6
[1022:1671] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 7
IOMMU group 10:[10de:2182] 10:00.0 VGA compatible controller: NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] (rev a1)
[10de:1aeb] 10:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio Controller (rev a1)
[10de:1aec] 10:00.2 USB controller: NVIDIA Corporation TU116 USB 3.1 Host Controller (rev a1)
This controller is bound to vfio, connected USB devices are not visible.
[10de:1aed] 10:00.3 Serial bus controller: NVIDIA Corporation TU116 USB Type-C UCSI Controller (rev a1)
IOMMU group 11:[1000:0072] 12:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
[11:0:0:0] disk ATA ST12000VN0008-2P SC61 /dev/sdb 12.0TB
[11:0:1:0] disk ATA ST12000VN0008-2P SC61 /dev/sdc 12.0TB
[11:0:2:0] disk ATA Samsung SSD 850 1B6Q /dev/sdd 500GB
[11:0:3:0] disk ATA Samsung SSD 850 1B6Q /dev/sde 500GB
[11:0:4:0] disk ATA ST12000VN0008-2Y SC60 /dev/sdf 12.0TB
[11:0:5:0] disk ATA ST4000NM0033-9ZM SN06 /dev/sdg 4.00TB
[11:0:6:0] disk ATA ST4000VN000-1H41 SC46 /dev/sdh 4.00TB
[11:0:7:0] disk ATA ST4000VN000-1H41 SC46 /dev/sdi 4.00TB
IOMMU group 12:[1022:43b9] 16:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset USB 3.1 xHCI Controller (rev 02)
Bus 003 Device 001 Port 3-0 ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002 Port 3-10 ID 0781:55a5 SanDisk Corp. Cruzer U
Bus 004 Device 001 Port 4-0 ID 1d6b:0003 Linux Foundation 3.0 root hub
[1022:43b5] 16:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset SATA Controller (rev 02)
[4:0:0:0] disk ATA ST18000NE000-2YY EN01 /dev/sdj 18.0TB
[1022:43b0] 16:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset PCIe Upstream Port (rev 02)
[1022:43b4] 20:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
[1022:43b4] 20:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
[1022:43b4] 20:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
[1022:43b4] 20:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
[1022:43b4] 20:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
[1022:43b4] 20:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
[8086:1539] 21:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
[8086:10d3] 22:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
[8086:10fb] 25:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)
[1b21:2142] 26:00.0 USB controller: ASMedia Technology Inc. ASM2142/ASM3142 USB 3.1 Host Controller
Bus 005 Device 001 Port 5-0 ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001 Port 6-0 ID 1d6b:0003 Linux Foundation 3.0 root hub
IOMMU group 13:[1002:1638] 30:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] (rev c9)
IOMMU group 14:[1002:1637] 30:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller
IOMMU group 15:[1022:15df] 30:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor
IOMMU group 16:[1022:1639] 30:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1
This controller is bound to vfio, connected USB devices are not visible.
IOMMU group 17:[1022:1639] 30:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1
This controller is bound to vfio, connected USB devices are not visible.
IOMMU group 18:[1022:15e3] 30:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller
IOMMU group 19:[1022:7901] 31:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 81)
IOMMU group 20:[1022:7901] 31:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 81)
Quote<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' id='8'>
<name>Windows 10</name>
<uuid>4c545694-1383-b6de-7b6f-e5d87b5cbe0d</uuid>
<metadata>
<vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
</metadata>
<memory unit='KiB'>8388608</memory>
<currentMemory unit='KiB'>8388608</currentMemory>
<memoryBacking>
<nosharepages/>
</memoryBacking>
<vcpu placement='static'>6</vcpu>
<cputune>
<vcpupin vcpu='0' cpuset='1'/>
<vcpupin vcpu='1' cpuset='7'/>
<vcpupin vcpu='2' cpuset='3'/>
<vcpupin vcpu='3' cpuset='9'/>
<vcpupin vcpu='4' cpuset='5'/>
<vcpupin vcpu='5' cpuset='11'/>
</cputune>
<resource>
<partition>/machine</partition>
</resource>
<os>
<type arch='x86_64' machine='pc-q35-7.1'>hvm</type>
<loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
<nvram>/etc/libvirt/qemu/nvram/4c545694-1383-b6de-7b6f-e5d87b5cbe0d_VARS-pure-efi.fd</nvram>
</os>
<features>
<acpi/>
<apic/>
<hyperv mode='custom'>
<relaxed state='on'/>
<vapic state='on'/>
<spinlocks state='on' retries='8191'/>
<vendor_id state='on' value='none'/>
</hyperv>
</features>
<cpu mode='host-passthrough' check='none' migratable='on'>
<topology sockets='1' dies='1' cores='3' threads='2'/>
<cache mode='passthrough'/>
<feature policy='require' name='topoext'/>
</cpu>
<clock offset='localtime'>
<timer name='hypervclock' present='yes'/>
<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='raw' cache='writeback'/>
<source file='/mnt/user/ISOs/Windows 10 Pro VM/Windows 10/vdisk1.img' index='2'/>
<backingStore/>
<target dev='hdc' bus='virtio'/>
<boot order='1'/>
<alias name='virtio-disk2'/>
<address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/mnt/user/ISOs/virtio-win-0.1.229.iso' index='1'/>
<backingStore/>
<target dev='hdb' bus='sata'/>
<readonly/>
<alias name='sata0-0-1'/>
<address type='drive' controller='0' bus='0' target='0' unit='1'/>
</disk>
<controller type='usb' index='0' model='ich9-ehci1'>
<alias name='usb'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
</controller>
<controller type='usb' index='0' model='ich9-uhci1'>
<alias name='usb'/>
<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'>
<alias name='usb'/>
<master startport='2'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
</controller>
<controller type='usb' index='0' model='ich9-uhci3'>
<alias name='usb'/>
<master startport='4'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
</controller>
<controller type='sata' index='0'>
<alias name='ide'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
</controller>
<controller type='pci' index='0' model='pcie-root'>
<alias name='pcie.0'/>
</controller>
<controller type='pci' index='1' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='1' port='0x8'/>
<alias name='pci.1'/>
<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'/>
<alias name='pci.2'/>
<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='0xa'/>
<alias name='pci.3'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
</controller>
<controller type='pci' index='4' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='4' port='0xb'/>
<alias name='pci.4'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/>
</controller>
<controller type='pci' index='5' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='5' port='0xc'/>
<alias name='pci.5'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/>
</controller>
<controller type='pci' index='6' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='6' port='0xd'/>
<alias name='pci.6'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/>
</controller>
<controller type='pci' index='7' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='7' port='0xe'/>
<alias name='pci.7'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/>
</controller>
<controller type='pci' index='8' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='8' port='0xf'/>
<alias name='pci.8'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x7'/>
</controller>
<controller type='pci' index='9' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='9' port='0x10'/>
<alias name='pci.9'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
</controller>
<controller type='pci' index='10' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='10' port='0x11'/>
<alias name='pci.10'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
</controller>
<controller type='pci' index='11' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='11' port='0x12'/>
<alias name='pci.11'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
</controller>
<controller type='virtio-serial' index='0'>
<alias name='virtio-serial0'/>
<address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
</controller>
<interface type='bridge'>
<mac address='52:54:00:dd:ee:1d'/>
<source bridge='br0'/>
<target dev='vnet7'/>
<model type='virtio-net'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
</interface>
<serial type='pty'>
<source path='/dev/pts/13'/>
<target type='isa-serial' port='0'>
<model name='isa-serial'/>
</target>
<alias name='serial0'/>
</serial>
<console type='pty' tty='/dev/pts/13'>
<source path='/dev/pts/13'/>
<target type='serial' port='0'/>
<alias name='serial0'/>
</console>
<channel type='unix'>
<source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-8-Windows 10/org.qemu.guest_agent.0'/>
<target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/>
<alias name='channel0'/>
<address type='virtio-serial' controller='0' bus='0' port='1'/>
</channel>
<input type='mouse' bus='ps2'>
<alias name='input0'/>
</input>
<input type='keyboard' bus='ps2'>
<alias name='input1'/>
</input>
<audio id='1' type='none'/>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x10' slot='0x00' function='0x0'/>
</source>
<alias name='hostdev0'/>
<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='0x10' slot='0x00' function='0x1'/>
</source>
<alias name='hostdev1'/>
<address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x1'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x30' slot='0x00' function='0x6'/>
</source>
<alias name='hostdev2'/>
<address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x10' slot='0x00' function='0x2'/>
</source>
<alias name='hostdev3'/>
<address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x2'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x10' slot='0x00' function='0x3'/>
</source>
<alias name='hostdev4'/>
<address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x3'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x30' slot='0x00' function='0x3'/>
</source>
<alias name='hostdev5'/>
<address type='pci' domain='0x0000' bus='0x09' slot='0x00' function='0x0'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x30' slot='0x00' function='0x4'/>
</source>
<alias name='hostdev6'/>
<address type='pci' domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/>
</hostdev>
<memballoon model='none'/>
</devices>
<seclabel type='dynamic' model='dac' relabel='yes'>
<label>+0:+100</label>
<imagelabel>+0:+100</imagelabel>
</seclabel>
</domain> -
1 hour ago, itimpi said:
Theoretically you can write to the array, but the writing and parity build both have significantly degraded performance while they are running in parallel so you may prefer not to.
Yeah, I'd definitely prefer to just let it build without writing to it in that case. Thanks!!
1 hour ago, JorgeB said:Note that sometimes the board/controller can support hot plug but if were the drives are connected doesn't connecting a new device might create a slight voltage drop that can drope another disk.
Got ya. I'm gonna play it safe from this point forward!
-
Also, the extended smart test passed without any issues! So I'll go ahead and rebuild parity when I get home onto my new 18 TB...should I still refrain from writing to my server while rebuilding even if it's only 1 of the 2 parity drives?
-
1 hour ago, trurl said:
Since only parity (P) is disabled I would replace that one first.
Really probably not much risk to replacing both at once if you are careful with connections, don't write to your server while rebuilding, and keep the original parity disks so they could be used if necessary. And parity contains none of your data anyway.
All sounds good, thanks! I'll still probably replace it one at a time because I'm paranoid, but it's good to know it would be fine either way! Thanks again!
-
2 hours ago, trurl said:
Attach diagnostics to your NEXT post in this thread.
Hotswap is not supported well by all hardware. Usually best to avoid it.
I suspect attempted hotswap is exactly what disabled the other disk. It will have to be rebuilt.
I know this is not what you were trying to do, but in the more usual case of trying to replace a disk, Unraid won't do anything with the replacement until it is assigned, and you can't change assignments with the array started, so might as well shut down.
Is that general rule about hotswapping true even if the MB bios has settings for hotswap support? I still would rather not risk it in the future so I'll probably abandon that regardless, but I'm just curious.
I suppose if it has to be rebuilt anyway...I might as well have it rebuild onto the new 18 TB drive? I assume I should replace each parity drive only one at a time to reduce the risk of data loss should something go wrong?
Thanks!!
-
I currently have 2 x 12 TB parity drives, 1 x 12 TB data drive and 3 x 4 TB data drives (4 TB drives are by far the oldest). I am wanting to replace both 12 TB parity drives with 18 TB drives and either add the two 12 TB parity drives to the array as data drives, or replace two of the 4 TB drives with the 12 TB drives.
I wanted to preclear my 18 TB drives so I plugged one into my system (I have a dock at the top that plugs into the MB, the other drives are all on an "LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)" controller)....the very second I did this, I received the follow errors in my notification bar. So I'm running an extended SMART test on the parity drive now but I just can't imagine there is any connection to plugging in that drive...is that possible or is it a coincidence?
I have the errors below from the notification archive.
29-01-2023 20:23 Unraid array errors Warning [JOHNSNAS] - array has errors Array has 1 disk with read errors warning
Parity disk - ST12000VN0008-2PH103_ZS80483R (sdc) (errors 2048)
29-01-2023 20:23 Unraid Parity disk error Alert [JOHNSNAS] - Parity disk in error state (disk dsbl) ST12000VN0008-2PH103_ZS80483R (sdc) alertThanks!
-
10 hours ago, JorgeB said:
The pool is completely full, this is what btrfs is reporting, and it will be correct:
Pool: cache Used: 931.00GiB Free (estimated): 2.84MiB (min: 2.84MiB) Free (statfs, df): 0.00BSomething is using that space, as for the mover not working shares use cache setting might not be correctly configured, or there could be other issues, you can take a look here for some common ones, but until you free up some space pool won't work.
I found the something. Apparently Crashplan Pro decided to dump 400 plus GBs of files in the appdata/CrashPlanPRO/conf/tmp directory. 😕 took some digging to find it and that definitely explains things. I used MC to delete them and the space is back.
I also did an extended smart test and it said everything checked out. So I'm guessing everything is good, I just need to figure out wth Crashplan did that and stop it from doing that again.
Thanks a ton for the help and reassurance on this!! It's very much appreciated!
-
11 hours ago, JorgeB said:
Cache2 is showing some SMART issues but should be fine for now, you can run an extended SMART test to confirm, main problem is that the pool is completely full, you need to move/delete some data from there, avoid completely filling up any COW filesystem, like btrfs or zfs.
That's the weird thing though....I have the mover scheduled for every week and I know I don't load up 500 GB or even close in a week. This has never happened before and I tried to manually invoke the mover and nothing. And when I try to view the pool....there's no data on there other than about 10-20 GB worth for my Docker Plugins and that includes a 10 GB for the docker image, at least not that I can see. I have no idea how it is saying there is no space on it. It makes no sense. It's never gotten even remotely close to filling up since I first fired this system up about 6 or 7 years ago. Any thoughts?
-
When you set something up so long ago...you really forget so many things 😕 I'm not exactly sure what information is needed, but I'll start with the Diag File. In my Dashboard, one of my cache drives in the pool is stating it has an error. I guess that has something to do with the issue but I thought the point of having a mirrored cache drives was that when one breaks, the other continues to function but that doesn't seem to be the case. I need to take care of this and I'm worried about losing data that is still on the cache that hasn't been moved yet. The cache is just acting weird and I'm worried about losing data, otherwise, I'd just be reading the manual and messing with stuff myself. Please advise and/or ask follow up questions as I know I left important information out. Samsung_SSD_850_EVO_500GB_S21HNXAG941287N is the first cache drive and Samsung_SSD_850_EVO_500GB_S21HNXAG643841J is the second cache drive (the one with the errors)
Thanks so much
-
Thanks very much for confirming this! While I hope there won't be a next time any time soon, I won't do maintenance mode if I have to again just in case I need access to my files!
-
I don't know what happened (I only know it was related to plugging in my old bad drives to try and pre-clear/test them again just out of curiosity) but unraid decided that my first parity disk was bad or something 🙄 (it's brand new and went through no less than 1 full preclear) so I learned a lesson there. But I started the array in maintenance mode and hit sync with the intention of it helping to shave some time off, without realizing I actually needed to access some data before the 17 hours that I'd have to wait without mounting the array.
Is there a safe way to not have to start the parity sync over and still mount the array? Or will I have to start over? And if I do, how do I do that safely? I assume I would simply cancel the parity-sync, and then start the array only not in maintenance mode this time?
Thanks so much!
-
3 hours ago, JorgeB said:
I checked before and the parity swap procedure completed successfully without any errors, so all should be fine.
Thanks so much for the reassurance on that! And for everything! I couldn't have confidently done this without your guidance and feedback!
And thanks to everybody else also that chipped in and helped me on this issue. I greatly appreciate it! You're all awesome!
-
1
-
-
8 hours ago, JorgeB said:
Yep, you should replace it ASAP.
All the other drives did finish without errors luckily. It seems like this was a really close call. I'll be paying more attention to this stuff in the future and setup some alerts as trurl suggested. But I am concerned because the now failing disk was previously one of the two parity disks. Should I be concerned and if so, how can I verify the integrity of my data short of checking every single file in it's entirety?
-
5 hours ago, JorgeB said:
If you still need help with this post current diags.
Well it finished re-building and seemed to be successful but well....My Previous Parity 1 drive (RXYD) is my new Disk 1 and before I did the parity swap (the copy) I did an extended smart test on every drive and every drive (except for the known bad drives, P23S and RYB9) passed. After everything re-built, I received a read warning again for Disk 1 so I did an extended smart test again on all the drives in the new array and RXYD failed with 30% left (see smart log below). I went ahead and included a full diagnostics in case you wanna take a look also. The other extended tests are still running but it looks like I'll have to replace another drive as well so soon 😕
johnsnas-smart-20211018-1225.zip johnsnas-diagnostics-20211018-1809.zip
-
Okay it just did that because one disk was a bit behind. I'm now at the step where I have to start the Array but it's not exactly as described in the manual. The manual states, "The Start button will now be present, and the description will now indicate that it is ready to start a Data-Rebuild.
Put a check in the Yes I want to do this checkbox (older versions: Yes, I'm sure), and click the Start button"But it doesn't say that it's ready to rebuild data. It's talking about expanding the file system of the data disks first and I don't see a check box. I'm assuming it's fine to just hit start and it will still do what it's supposed to, but just in case, I want to make sure so I've included a screenshot below. Both Parity drives have a green dot on them (the new 12 TB drives) just since that's cut out at the top. Thanks!!
Well crap...things are not going as per the manual/instructions and I don't know what to do now (see attached image). I'm confused because it's still copying, but says it's not ready and that the content is being reconstructed? But that part isn't supposed to happen until after it's finished copying, right? So what is it doing? It shouldn't be reconstructing anything yet, right? Not sure what to do.
MYR4 is one of my old parity drives also, I took a screenshot of everything before I started so that I would know which drives were where.
-
1 hour ago, JorgeB said:
Correct, and the steps look good.
7 minutes ago, JorgeB said:Just a reminder that you can't interrupt the procedure after the copy and before pressing start by rebooting or powering down, or you'll need to start over the procedure from the beginning.
Awesome, thanks so much for verifying that! And thanks for the heads up/tip on that. I definitely wasn't planning on rebooting or powering down, but it's good to know it would have to start over anyway! I'll get this entire thing started as soon as these drives finish pre-clearing!
MYR4 is one of my old parity drives also, I took a screenshot of everything before I started so that I would know which drives were where.
torrenting with a shared drive via SMB? Maybe...not such a good idea?
in MacOS/SMB
Posted
I'm gonna go that route then for sure. Thanks very much for the input!