ryanleeis

Could someone please help .. im trying to use the mmctl tool in Mattermost but keep getting this error goroutine 1 [running]: github.com/mattermost/mattermost/server/v8/cmd/mmctl/commands.init.1() github.com/mattermost/mattermost/server/v8/cmd/mmctl/commands/auth_utils.go:50 +0x58

So with virtualization disabled my virtual machines don’t work what’s the workaround for this

on my T420 I just went into the bios and changed virutliztion tech to disable and it fix the problem.. 6.10.2 booted,

should this be done before or after the upgrade.. and what if the OS did not install the eth0 driver?

Hello, I have a Dell PowerEdge T420 Server.. i have never experienced any problems when upgrading before, but when i Upgrade from 6.10.1 to 6.10.2 the interface will not load.. i cant access the server from the browser.. and the only way to fix it is to boot in GUI with safe mode and rollback to 6.10.1 I have tried many times and have even uninstalled any unnecessary plugins and dockers? could someone give me some insight please. Thanks Ryan

could someone please help me out . I’ve read the instructions on how to get two instances of this running with two different ports but I just can’t seem to get it to use the second port can someone please help me out here

why would I keep getting this error.. I have changed slots.. I've tried this with my 1070ti also.. I can't get the dump?? Script location: /tmp/user.scripts/tmpScripts/dump Vbios/script Note that closing this window will abort the execution of this script You have selected this device to dump the vbios from 41:00.0 VGA compatible controller: NVIDIA Corporation GP107GL [Quadro P400] (rev a1) This does look like a valid GPU to me. Continuing ......... Checking if location to put vbios file exists Vbios folder already exists I will try and dump the vbios without disconnecting and reconnecting the GPU This normally only works if the GPU is NOT the Primary or the only GPU I will check the vbios at the end. If it seems wrong I will then retry after disconnecting the GPU Defining temp vm with gpu attached Domain dumpvbios defined from /tmp/dumpvbios.xml Starting the temp vm to allow dump Domain dumpvbios started Waiting for a few seconds ..... Stopping the temp vm Domain dumpvbios destroyed Removing the temp vm Domain dumpvbios has been undefined Okay dumping vbios file named p400 gpu.rom to the location /mnt/user/isos/vbios/ cat: rom: Input/output error Um.... somethings gone wrong and I couldn't dump the vbios for some reason Sometimes when this happens all we need to do to fix this is 'stub' or 'bind to the vfio' the gpu and reboot the server This can be done in Unraid 6.8.3 with the use of the vfio config plugin or if you are on Unraid 6.9 or above it can be done directly from the gui in Tools/System Devices .....So please do this and run the script again

same problem here.. I've tried everything. can't get the script to work.. keep getting this error.. tried changing slots everything Script location: /tmp/user.scripts/tmpScripts/dump Vbios/script Note that closing this window will abort the execution of this script You have selected this device to dump the vbios from 41:00.0 VGA compatible controller: NVIDIA Corporation GP107GL [Quadro P400] (rev a1) This does look like a valid GPU to me. Continuing ......... Checking if location to put vbios file exists Vbios folder already exists I will try and dump the vbios without disconnecting and reconnecting the GPU This normally only works if the GPU is NOT the Primary or the only GPU I will check the vbios at the end. If it seems wrong I will then retry after disconnecting the GPU Defining temp vm with gpu attached Domain dumpvbios defined from /tmp/dumpvbios.xml Starting the temp vm to allow dump Domain dumpvbios started Waiting for a few seconds ..... Stopping the temp vm Domain dumpvbios destroyed Removing the temp vm Domain dumpvbios has been undefined Okay dumping vbios file named p400 gpu.rom to the location /mnt/user/isos/vbios/ cat: rom: Input/output error Um.... somethings gone wrong and I couldn't dump the vbios for some reason Sometimes when this happens all we need to do to fix this is 'stub' or 'bind to the vfio' the gpu and reboot the server This can be done in Unraid 6.8.3 with the use of the vfio config plugin or if you are on Unraid 6.9 or above it can be done directly from the gui in Tools/System Devices .....So please do this and run the script again

that worked . thanks so much !

thanks.. how do I change to that? is there something I can read about somewhere ?

Wondering if someone could shed some light on my situation.. I installed Macinabox Bigsur on a unassigned device as a vdisk and everything seems to working fine except when I try to copy files from the Bigsur vdisk to and from Unraid it just fails.. I don't know what im doing wrong.. file transfers work perfectly fine when I copy to and from my windows 10 vdisk?

did you get this done ?

Thanks I can't seem to find the option to do that.. is there an admin setting or something ? this would be great if it would show healthy then show error again if it increases.. Thanks..

I purchased 8 - 8TB WD Red Drives the other night for my unRAID server I built.. I put them all in a booted.. 5 of the 8 drives showed those errors with the error count of 1. that's all.. I tried to zero the drives. I moved them around and it didn't matter which bay they were placed in they always had the error.. I even placed them in the bays that the good ones were installed into.. I would just hate to waste money on my sata cables that go from my RAID card just to find out it doesn't work.. the count doesn't seem to be changing.. when I check the smart info in Crystaldiskinfo and other tools.. it all comes out perfect? is there anyway in unRAID to ignore the count if it stays the same and just mark the disk as healthy?

I have 5 of 8 8TB WD Red Drives that have a Cycle Count of 1 with this same error.. could this error correct itself in Unraid? or should I replace these Disks?