fulknerra
-
Posts
10 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by fulknerra
-
-
On 11/23/2023 at 2:53 AM, JorgeB said:
Nov 20 05:02:29 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Nov 20 05:02:29 Tower kernel: ? _raw_spin_unlock+0x14/0x29 Nov 20 05:02:29 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]Macvlan call traces will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot.
This appears to have resolved the issue, going on more than 4 days of uptime now, which is the best I've seen all month.
Thanks
-
1
-
-
I use a the br0 network so that I can assign individual IPs to every docker and have them be accessible by the host, does ipvlan still allow the same type of setup?
-
Seems that every other day my unraid box is fully freezing and I have to hard power down, cant tell if its a kernel panic or something else. If I console into the box it just shows an unresponsive login prompt. Syslog (attached) shows a handful of error messages that seem concerning but nothing at the point of failure.
At first I was doing a backup of appdata/unraid every night, along with a TRIM, and plugin update check. I've since scheduled all my backups/trims to happen on different days, I also noticed that before every freeze the plugin updater was running, so I removed it, with these changes the freezing is still happening.
After the last crash I ran a parity check and noticed that it resolved 5K errors within the first few hours of running but none after that.
memtest passed 48/48 tests no errors
stresslinux showed no faults
ran full SMART tests on the drives, seems healthy.
Not sure what I should be looking at resolve this problem
-
6 hours ago, JorgeB said:
It's not, IT mode uses the mpt3sas driver, not megaraid_sas.
9341-8i is also megaraid, you'd need the 9300-8i firmware, but likely it will require crossflashing, it probably won't accept direct flashing, try googling "lsi 9340 it mode", instructions on how to should be easy to find.
It appears that the HBA was improperly flashed, after following a few online guides and flashing SAS9300_8i_IT.bin (via UEFI) I was able to get the device functioning and Unraid now detects the new drives. Thanks for your help JorgeB
-
1
-
-
8 hours ago, JorgeB said:
See if it can be flashed to IT mode, since it's using the SAS3008 chip there's a good chance it can, RAID is not recommended for Unraid.
The distributor I purchased from stated that the card was flashed in IT mode (and it's missing its bios rom) but I'm guessing it wasn't flashed correctly.
It's an LSI SAS9340-8i - But I can only find the FW for the LSI SAS9341-8i from my reading the only difference is that the sas ports on the 40 are on top and the 41 are on the side, if the SAAS3008 chip is the same do you know if I can just flash the SAS9341-8i FW to the card?
-
I am not able to get my newly installed HBA card to load on my box.
- changed pci ports
- updated bios
- forced pci to gen3
- disabled fast boot
- set pci=realloc=off & iommu=soft in syslinux.cfg
I can see the controller in lspci
Quote# lspci | grep RAID
01:00.0 RAID bus controller: Broadcom / LSI MegaRAID SAS-3 3008 [Fury] (rev 02)dmesg shows the following error
Quote# dmesg | grep mega
[ 14.302844] megasas: 07.714.04.00-rc1
[ 14.304204] megaraid_sas 0000:01:00.0: BAR:0x1 BAR's base_addr(phys):0x000000009fa00000 mapped virt_addr:0x0000000046fcd659
[ 14.304206] megaraid_sas 0000:01:00.0: Waiting for FW to come to ready state
[ 14.327315] megaraid_sas 0000:01:00.0: FW in FAULT state, Fault code:0x40000 subcode:0x0 func:megasas_transition_to_ready
[ 14.328552] megaraid_sas 0000:01:00.0: System Register set:
[ 14.393725] megaraid_sas 0000:01:00.0: Failed to transition controller to ready from megasas_init_fw![ 14.394201] megaraid_sas 0000:01:00.0: Failed from megasas_init_fw 6406
not sure what to try next, any direction is appreciated.
-
11 minutes ago, ich777 said:
Please don't set your graphics card like that, please read the second post on how to use GVT-g
Yup I read up to step 4 and assumed I knew the rest, sorry for wasting your time and thanks for the pointer.
-
1
-
-
11 hours ago, ich777 said:
Do you need this parameter in your syslinux.conf:
i915.alpha_support=1
if not, please remove it and report back please.
Removed it and rebooted, but still getting the same error when trying to set the GPU -
-
I can't seem to get passthrough to work
Intel® Core™ i3-10100
gpu_top works fine and reports performance
intel-gpu-top: Intel Cometlake (Gen9)
The intel gvt-g shows available modes and I am able to bind it to a vm
the vga controller is in its own iommu group
IOMMU group 1:[8086:9bc8] 00:02.0 VGA compatible controller: Intel Corporation CometLake-S GT2 [UHD Graphics 630] (rev 03)
but I am unable to bind the GPU to the vm when using Q35-5.1 machine type. I get an error
VM creation error XML error: 'model' attribute in <hostdev> is only supported when type='pci'
I've tried setting the guc/huc firmware to both 'default' and '2' but it hasnt made a difference, not quite sure what I'm doing wrong.
Server completely locking up every couple of days
in General Support
Posted
I had another similar outage last week and this week after disabling macvlan, full lock up but no kernel panics and nothing really in the syslog. This time I was able to specifically correlate it to the APPDATA BACKUP plugin unfortunately as that doesn't log to syslog I can't pinpoint what action the backup plugin was doing, Disabling the functions of the backup has stopped all lockups so I believe it was a mix of macvlan and the backup.
I have the following settings enabled
Checking on the backup directory for any of the previous backups, the container data is all there but what is missing is the flashbackup and the VM meta data, so I am assuming that the system locks up when it attempts to backup the flashdrive. I'm not entirely sure why this happens, but my system has been stable since disabling this function.
leaving this information here for anyone else who might stumble across the same issue.