SuperDodge
-
Posts
15 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by SuperDodge
-
-
How do I know when the rebuild is done and it's safe to replace the next drive?How do I know when the rebuild is done and it's safe to replace the next drive?
-
I have the newest BIOS on the board and I have Unraid 6.11.1 installed. Same issue.
Open to any ideas...
-
I was able to temporarily fix this issue by adding
Quotepci=nommconf
to my syslinux configuration. This is letting me limp along for now but it appears to be causing issues with some of my VMs.
I got the idea from this thread:
Still searching for the right answer.
-
1
-
-
If I add acpi=off to the syslinux configuration then I see the sata drives but have no iommu groups and can't pass through my graphics cards to vfio
-
Adding additional context here. I checked and this motherboard is actually Rev1.1 vs Rev1 that it replaced. I have another similar setup in place with no SATA drives (all NVMEs) using Rev1.1 of the motherboard and it apparently has the same error.
Do I seriously have a SATA controller that unraid isn't compatible with?
-
I was able to create a new flash drive with the old configuration and a newly purchased license as outlined by JonathanM. Also the LimeTech team responded in much less than 3 days. Thanks all.
-
1
-
-
Title says it all. I have checked and the SATA controller is not in an IOMMU group with any of my GPUs which are passed through.
To give some background, my motherboard bricked (Asus Pro WS WRX80E-SAGE SE WIFI) and I have replaced it with a new one. All drives and NVMEs are in the same location. All of the NVMEs show up correctly but neither of the hard drives do.
As the title says I can see the SATA drives in the BIOS and the SATA mode is set to AHCI.
I see this in the logs but of course I can't figure out where to go from here:
Oct 30 10:59:27 Workstation kernel: ahci: probe of 0000:26:00.0 failed with error -22
Oct 30 10:59:27 Workstation kernel: ahci: probe of 0000:27:00.0 failed with error -22
Diagnostics attached.
-
1
-
-
16 minutes ago, ChatNoir said:
Did you try to first contact support ?
There is a limit for the automatic flashdrive change, but Limetech can probably help you out if you provide enough information to identify you (email address, etc.)
As mentioned in my post I sent an email where the wiki says to send one and got an auto reply that they would respond within 3 business days. The cost of an Unraid Pro license is inconsequential to me compared to the labor cost I will lose if I wait three days. That's why I made this post asking if there was another way to move my configuration over to a new flash drive with a new license, etc.
-
I am using Unraid to run VMs for employees in my small engineering firm to utilize. I love unraid but have had terrible luck with flash drives. When I first set this system up I took note of this post:
Based on this post I bought a Samsung Fit Plus drive which lasted for a few months before it began dying randomly and causing issues. I followed the standard procedure at https://wiki.unraid.net/Manual/Changing_The_Flash_Device to move my system to a new Samsung Fit Plus thinking that I just got a lemon.
That second Samsung Fit Plus has now encountered the same problem as the original. I need to get this up asap so I emailed the requested information to [email protected] per the wiki post above and got an automated reply that it may take 3 days for me to get a response. 3 days without this system will cost me thousands of dollars so I need to find another path.
I have a backup of my flash drive. Is there just a way to buy another unraid license and move my configuration over without the key or something like that?
Thanks for the help, guys.
-
9 hours ago, trurl said:
And what do you get with this?
ls -lah /var/log
total 121M
drwxr-xr-x 12 root root 640 Jun 28 04:40 ./
drwxr-xr-x 14 root root 340 Jun 14 13:32 ../
-rw------- 1 root root 0 Jun 14 13:30 btmp
-rw-r--r-- 1 root root 0 Apr 28 2021 cron
-rw-r--r-- 1 root root 0 Apr 28 2021 debug
-rw-r--r-- 1 root root 114K Jun 27 16:12 dmesg
-rw-r--r-- 1 root root 828 Jun 27 16:13 docker.log
-rw-r--r-- 1 root root 0 Feb 13 2021 faillog
-rw-r--r-- 1 root root 0 Apr 7 2000 lastlog
drwxr-xr-x 4 root root 140 Jun 27 16:13 libvirt/
-rw-r--r-- 1 root root 0 Apr 28 2021 maillog
-rw-r--r-- 1 root root 0 Apr 28 2021 messages
drwxr-xr-x 2 root root 40 Jun 15 2021 nfsd/
drwxr-x--- 2 nobody root 60 Jun 27 16:13 nginx/
lrwxrwxrwx 1 root root 24 Jun 14 13:29 packages -> ../lib/pkgtools/packages/
drwxr-xr-x 4 root root 80 Dec 20 2021 pkgtools/
drwxr-xr-x 2 root root 280 Jun 27 16:13 plugins/
drwxr-xr-x 2 root root 60 Jun 27 16:13 preclear/
drwxr-xr-x 2 root root 40 Jun 28 08:20 pwfail/
lrwxrwxrwx 1 root root 25 Jun 14 13:30 removed_packages -> pkgtools/removed_packages/
lrwxrwxrwx 1 root root 24 Jun 14 13:30 removed_scripts -> pkgtools/removed_scripts/
drwxr-xr-x 3 root root 160 Jun 27 16:13 samba/
lrwxrwxrwx 1 root root 23 Jun 14 13:29 scripts -> ../lib/pkgtools/scripts/
-rw-r--r-- 1 root root 0 Apr 28 2021 secure
lrwxrwxrwx 1 root root 21 Jun 14 13:29 setup -> ../lib/pkgtools/setup/
-rw-r--r-- 1 root root 0 Apr 28 2021 spooler
drwxr-xr-x 3 root root 60 Apr 30 15:47 swtpm/
-rw-r--r-- 1 root root 0 Jun 28 08:20 syslog
-rw-r--r-- 1 root root 121M Jun 28 03:40 syslog.1
drwxr-xr-x 2 root root 60 Jun 27 16:13 unraid-api/
-rw-r--r-- 1 root root 3.2K Jun 27 16:12 vfio-pci
-rw-rw-r-- 1 root utmp 6.8K Jun 27 16:13 wtmp -
On 6/26/2022 at 7:47 PM, trurl said:
The logs in your diagnostics aren't large.
What do you get from the command line with this?
du -h -d 1 /var/log
0 /var/log/pwfail
0 /var/log/unraid-api
0 /var/log/preclear
0 /var/log/swtpm
20K /var/log/samba
0 /var/log/plugins
0 /var/log/pkgtools
0 /var/log/nginx
0 /var/log/nfsd
7.1M /var/log/libvirt
128M /var/log -
I need some help determining what my issue is.
-
I dumped the attached vbios from my Zotac RTX 3060 Amp White Edition. I have the FHR (Non-LHR) version. Please add to the repository.
Software Detecting VM.
in VM Engine (KVM)
Posted
I am attempting to install a software program on an existing, working Windows 10 VM.
When installing the program it detects the use of a Hypervisor and will not boot. I have shut down the VM, turned Hyper-V off in the VM template and restarted the machine. I get the same results.
If I boot the VM and open the "add or remove Windows features" pane it does not show Hyper-V installed/working. I have run the following command in an elevated PowerShell session"Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Hypervisor".
What else do I need to do?