offroadguy56
-
Posts
35 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by offroadguy56
-
-
Unraid 6.11.5
I have some weird happening with my array. I will try and describe the series of events the best I can.
TL;DR I tried to bring my disk1 online. It and parity disk took turns being offline. After 3 or 4 parity syncs and disk rebuilds. Parity disk will not go online after parity sync. Unraid has multiple notices saying Disk1 Disk2 can't be written to. Disk1 has read errors. Parity disk is disabled.
Before I began my upgrade I have 7 disks total with 1 being parity. I have 1 cache drive NVME.
I had planned to install a 2nd cache drive and assign it to the same pool.
I install the 2nd cache drive. On bootup it asks me to assign it BTRFS. I click yes and that brings my 1st cache drive offline because it was formatted XFS. At the same time my Disk1 showed it was offline. I restarted Unraid multiple times and tried different cables and SATA ports. I though the disk being offline meant that it was not recognized by the OS/BIOS. I learn that was not the case and that the disk had to be rebuilt by the parity data. I take the array offline remove the disk, start the array, stop the array, add the disk back. Rebuild begins. After rebuild unraid says all disks + parity are online. I remove the 2nd cache slot and set the cache pool back to XFS and assign my cache drive back to the pool. I move the data off the cache drive by invoking mover and setting all of my "prefer cache" disks to "yes cache". All the data moves successfully. I also as a precaution copy the appdata folder contents to my main PC via SMB.
I notice that my VM list and Docker list are empty. I restart unraid. I should mention at this point and before during the restarts Unraid was not able to properly shut down. It would either hang on trying to stop the array, and do absolutely nothing for 30 minutes or more. Or it would spit out on the local console that it had IO errors. I didn't think anything of it. 3 times now upon boot up my computer would not recognize any bootable devices including the unraid USB except for the 2nd cache drive which had a windows install. After a restart unraid would boot.
After actually booting into unraid if I had rebuilt disk1, the parity disk would be offline and I would take the array down and back up to get it to parity sync. If I had previously done a parity sync before a restart disk1 would be offline and I would take the array offline and back online to rebuild it. Now after each restart and parity sync, the parity disk remains offline even before the restart and the "successful" parity sync. Also as of now there is no longer a parity sync button, it has been replaced with a read-check button.
I'm sure some info has been left out and that certain things aren't very clear. Please ask me questions and point me in the correct direction to recover my array. My only hypothesis is that I somehow swapped my parity and disk1 positions.
I have attached some diagnostic dumps and here are screenshots of my current webui. I also have a flash backup of unraid from 02-15-2023 I believe it is version 6.9.5 in that backup?
Thanks in advance for all that yall do here.
waffle-diagnostics-20230303-1230.zip waffle-diagnostics-20230303-1932 after parity sync.zip waffle-diagnostics-20230303-2004 after restart to normal OS mode.zip
-
2 hours ago, SimonF said:
I think the issue is size of you memory on the card.
The card is 24gb. I didn't think it would be an issue on address size. I still don't really know how all that works. When I was searching for code 12 errors I didn't see any direct correlation to address size so I pushed those results aside. It didn't help that most results weren't for my use case anyway.
Again, thanks a bunch.
-
I ended up finding my solution:
Corsair Commander Pro for USB control of a single PWM fan. Pass the USB device through to the VM.
iCUE unfortunately would not detect my GPU temperature. Instead I used this software which detected both the fan and GPU temperature. https://github.com/Rem0o/FanControl.ReleasesNot the 100% free and purely software solution I was hoping for, but it works.
-
7 hours ago, SimonF said:
Not sure if this is related. Its the qemu options at the bottom to increate to 64 from 32 default.
Holy smokes, it's worked. I'll begin testing actual functions of the card, but for now Windows is no longer complaining and GPUZ/Afterburner have recognized it. Even Nvidia control panel is working.
How did you end up finding that post? I didn't think a card from 2016 would have resizable bar. My GPUZ says it does.
Thanks so much!
-
I recently bought a used Tesla P40 for AI work with Stable Diffusion. I planned to run it in my Windows 10 Pro VM. However after installing the Telsa P40 data center drivers from Nvidia Windows will recognize the card but will display a Code 12 error saying it cannot find enough free resources.
I am completely stumped at this point. The GPU works perfectly fine when running bare metal. But as soon as it's passed to a VM it's not functioning. I tried Linux Mint at one point, drivers installed successfully (as far as I could tell) but Mint would notify that it can't detect an appropriate GPU.
Any help would be appreciated.
If you have questions let me know.
Here is my VM setup and the XML
Spoiler<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm'>
<name>Windows 10</name>
<uuid>b9a3338e-5c66-c478-c4d0-bd9ea543a7c9</uuid>
<metadata>
<vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
</metadata>
<memory unit='KiB'>33554432</memory>
<currentMemory unit='KiB'>33554432</currentMemory>
<memoryBacking>
<nosharepages/>
</memoryBacking>
<vcpu placement='static'>30</vcpu>
<cputune>
<vcpupin vcpu='0' cpuset='1'/>
<vcpupin vcpu='1' cpuset='17'/>
<vcpupin vcpu='2' cpuset='2'/>
<vcpupin vcpu='3' cpuset='18'/>
<vcpupin vcpu='4' cpuset='3'/>
<vcpupin vcpu='5' cpuset='19'/>
<vcpupin vcpu='6' cpuset='4'/>
<vcpupin vcpu='7' cpuset='20'/>
<vcpupin vcpu='8' cpuset='5'/>
<vcpupin vcpu='9' cpuset='21'/>
<vcpupin vcpu='10' cpuset='6'/>
<vcpupin vcpu='11' cpuset='22'/>
<vcpupin vcpu='12' cpuset='7'/>
<vcpupin vcpu='13' cpuset='23'/>
<vcpupin vcpu='14' cpuset='8'/>
<vcpupin vcpu='15' cpuset='24'/>
<vcpupin vcpu='16' cpuset='9'/>
<vcpupin vcpu='17' cpuset='25'/>
<vcpupin vcpu='18' cpuset='10'/>
<vcpupin vcpu='19' cpuset='26'/>
<vcpupin vcpu='20' cpuset='11'/>
<vcpupin vcpu='21' cpuset='27'/>
<vcpupin vcpu='22' cpuset='12'/>
<vcpupin vcpu='23' cpuset='28'/>
<vcpupin vcpu='24' cpuset='13'/>
<vcpupin vcpu='25' cpuset='29'/>
<vcpupin vcpu='26' cpuset='14'/>
<vcpupin vcpu='27' cpuset='30'/>
<vcpupin vcpu='28' cpuset='15'/>
<vcpupin vcpu='29' cpuset='31'/>
</cputune>
<os>
<type arch='x86_64' machine='pc-q35-5.1'>hvm</type>
<loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
<nvram>/etc/libvirt/qemu/nvram/b9a3338e-5c66-c478-c4d0-bd9ea543a7c9_VARS-pure-efi.fd</nvram>
</os>
<features>
<acpi/>
<apic/>
<hyperv>
<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='15' 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/domains/Windows 10/vdisk1.img'/>
<target dev='hdc' bus='virtio'/>
<boot order='1'/>
<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/Windows 10/Windows 10 64bit.iso'/>
<target dev='hda' bus='sata'/>
<readonly/>
<boot order='2'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/mnt/user/isos/virtio-win-0.1.229.iso'/>
<target dev='hdb' bus='sata'/>
<readonly/>
<address type='drive' controller='0' bus='0' target='0' unit='1'/>
</disk>
<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>
<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='0x10'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
</controller>
<controller type='pci' index='2' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='2' port='0x11'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
</controller>
<controller type='pci' index='3' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='3' port='0x12'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
</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='0x14'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/>
</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>
<interface type='bridge'>
<mac address='52:54:00:0c:70:42'/>
<source bridge='br0'/>
<model type='virtio-net'/>
<address type='pci' domain='0x0000' bus='0x01' 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='2'/>
</input>
<input type='mouse' bus='ps2'/>
<input type='keyboard' bus='ps2'/>
<graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'>
<listen type='address' address='0.0.0.0'/>
</graphics>
<video>
<model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
</video>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x09' slot='0x00' function='0x0'/>
</source>
<rom file='/mnt/user/isos/GPU ROM/NVIDIA.TeslaP40.24576.161020.rom'/>
<address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x1b1c'/>
<product id='0x0c2a'/>
</source>
<address type='usb' bus='0' port='1'/>
</hostdev>
<memballoon model='none'/>
</devices>
</domain>
-
unRAID version 6.9.2
I am looking at getting a datacenter GPU for ai image training for cheap. Much cheaper than what is normally available as a normal graphics card. It has no fan or headers on the graphics card board. I plan to 3D print a duct and attach my own fan and connect it to my motherboard's case fan header. I have Dynamix Autofan and temperature plugins. There doesn't seem to be any option to reference a specific temperature, I just see mainboard or CPU. And Autofan just lists options for connected drives.
Is there a plugin or some software I could run at unRAID's level to control a case fan determined by the temperature of a specific probe, like the GPU?
The only other solutions I can think of is a.) external fan controller with some auto fan curve and a temp probe stuffed into the GPU. or b.) USB fan controller, like Corsair Commander, and pass the USB device to a windows VM.
The performance of the external fan controllers I can find on amazon aren't great. Users complain of not being able to adjust the fan curve or that the curve is incorrect for their use case. And for my Windows VM, I am not able to currently pass through fan speed and temperature info for the software without that USB controller.
And of course last resort is just power the fan at 100%. But this server is in a public space in the house, I have no server room near a LAN jack. So I've only been able to keep it around with how little noise it makes.
-
Ok thanks for the explanation. I have a bit better understanding now and will play around with your suggestions in time.
-
Ok I deleted ProFTP and restarted the server. I can regular FTP into the server now with all of my users after I add them to the list. But SSH isn't working for any of my users.
I made some users for testing before I deleted the plugin and made another one after.
'offroadguy56' has ftpuser description and was made before restart.
'smurf' has no description and was made before restart.
'test' has no description and was made after restart.
This is probably beyond the scope of the plugin thread but this is the log I see when attempting SSH connection with any user:
Jul 23 23:47:23 UR-SERVER sshd[11681]: Connection from 192.168.1.150 port 52457 on 192.168.1.151 port 22 rdomain "" Jul 23 23:47:25 UR-SERVER sshd[11681]: User test from 192.168.1.150 not allowed because not listed in AllowUsers Jul 23 23:47:25 UR-SERVER sshd[11681]: Postponed keyboard-interactive for invalid user test from 192.168.1.150 port 52457 ssh2 [preauth] Jul 23 23:47:26 UR-SERVER sshd[11687]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.150 user=test Jul 23 23:47:28 UR-SERVER sshd[11681]: error: PAM: Authentication failure for illegal user test from 192.168.1.150 Jul 23 23:47:28 UR-SERVER sshd[11681]: Failed keyboard-interactive/pam for invalid user test from 192.168.1.150 port 52457 ssh2 Jul 23 23:47:28 UR-SERVER sshd[11681]: Postponed keyboard-interactive for invalid user test from 192.168.1.150 port 52457 ssh2 [preauth] Jul 23 23:47:32 UR-SERVER sshd[11681]: Connection closed by invalid user test 192.168.1.150 port 52457 [preauth] Jul 23 23:49:00 UR-SERVER sshd[12036]: Connection from 192.168.1.150 port 52535 on 192.168.1.151 port 22 rdomain "" Jul 23 23:49:01 UR-SERVER sshd[12036]: User test from 192.168.1.150 not allowed because not listed in AllowUsers Jul 23 23:49:01 UR-SERVER sshd[12036]: Postponed keyboard-interactive for invalid user test from 192.168.1.150 port 52535 ssh2 [preauth] Jul 23 23:49:02 UR-SERVER sshd[12040]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.150 user=test Jul 23 23:49:04 UR-SERVER sshd[12036]: error: PAM: Authentication failure for illegal user test from 192.168.1.150 Jul 23 23:49:04 UR-SERVER sshd[12036]: Failed keyboard-interactive/pam for invalid user test from 192.168.1.150 port 52535 ssh2 Jul 23 23:49:04 UR-SERVER sshd[12036]: Postponed keyboard-interactive for invalid user test from 192.168.1.150 port 52535 ssh2 [preauth]I was actually hoping to make use of SFTP and the folder restrictions ProFTP offers. I don't want family members seeing the entirety of the server folder structure. And I did want to temporarily open FTP access over internet to get friend's backups on my drives. If you have a better solution than encrypting their iso and using SFTP, let me know. The only thing I can think of is running Synology in a VM and leveraging their software.
To sum up, SSH is not working (except for root in the webUI), FTP is working with default service, I want SFTP for temporary use across internet, I would like to have folder restrictions for users.
Sorry for all the trouble. This stuff is super cool but still new to me and I would like to do it as properly as I can.
Thanks.
-
I'm getting a Authentication Failed on my FTP client trying to connect. When I check the server log I see this:
Jul 22 18:58:01 SERVER sshd[9885]: Connection from 192.168.1.150 port 59333 on 192.168.1.151 port 22 rdomain "" Jul 22 18:58:01 SERVER sshd[9885]: User offroadguy56 from 192.168.1.150 not allowed because not listed in AllowUsers Jul 22 18:58:01 SERVER sshd[9885]: Postponed keyboard-interactive for invalid user offroadguy56 from 192.168.1.150 port 59333 ssh2 [preauth] Jul 22 18:58:01 SERVER sshd[9887]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.150 user=offroadguy56 Jul 22 18:58:03 SERVER sshd[9885]: error: PAM: Authentication failure for illegal user offroadguy56 from 192.168.1.150 Jul 22 18:58:03 SERVER sshd[9885]: Failed keyboard-interactive/pam for invalid user offroadguy56 from 192.168.1.150 port 59333 ssh2 Jul 22 18:58:03 SERVER sshd[9885]: Postponed keyboard-interactive for invalid user offroadguy56 from 192.168.1.150 port 59333 ssh2 [preauth] Jul 22 18:58:03 SERVER sshd[9885]: Connection closed by invalid user offroadguy56 192.168.1.150 port 59333 [preauth]I have already added my user account in unRAID and gave the "ftpuser" description. My username is not in the ftpusers file.
Any ideas to get this working?
Here's my proftpd.conf file:
GNU nano 5.3 proftpd.conf Modified ServerType standalone DefaultServer on PidFile /var/run/ProFTPd/ProFTPd.pid # Port 21 is the standard FTP port. You propably should not connect to the # internet with this port. Make your router forward another port to # this one instead. Port 21 # Set the user and group under which the server will run. User nobody Group users # Prevent DoS attacks MaxInstances 30 # Speedup Login UseReverseDNS off # Control Logging - comment and uncomment as needed # If logging Directory is world writeable the server won't start! # If no SystemLog is defined proftpd will log to servers syslog. #SystemLog NONE #SystemLog /boot/config/plugins/ProFTPd/slog TransferLog NONE #TransferLog /boot/config/plugins/ProFTPd/xferlog WtmpLog NONE # As a security precaution prevent root and other users in # /etc/ftpuser from accessing the FTP server. UseFtpUsers on RootLogin off # Umask 022 is a good standard umask to prevent new dirs and files # from being group and world writable. Umask 022 # "Jail" FTP-Users into their home directory. (chroot) # The root directory has to be set in the description field # when defining an user: # ftpuser /mnt/cache/FTP # See README for more information. DefaultRoot ~ # Shell has to be set when defining an user. As a security precaution # it is set to "/bin/false" as FTP-Users should not have shell access. # This setting makes proftpd accept invalid shells. RequireValidShell no # Normally, we want files to be overwriteable. AllowOverwrite on
Parity disk won't enable after parity check
in General Support
Posted · Edited by offroadguy56
My VMs list is currently empty. I should have a windows 10 VM there. Any suggestions to accomplish what you recommended above?
I feel like I've done enough potential damage. I'd like to play is slow and safe and see what the community suggests first.
I assume I could fix this problem by disabling the VM manager?