jfrancais

Been running solid since Monday with no errors thus far.

diagnostics attached gobo-diagnostics-20220530-1123.zip

https://support.hp.com/ie-en/product/hp-z800-workstation/3718645/document/c01709726

Thanks for the reply and the catch. disabling VT-d in bios brought me back up but now I need to figure out what to do. I have VMs running on this that I need for production so disabling VT-d leaves me non functional. I wasn't having any issues since going to 6.10 so I'm wondering if it is safe to bypass the blacklist.

Good morning, looking for some assistance. I upgraded top the newest release this morning and my machine came back up missing the NICS. netxtreme bcm5764m gigabit ethernet pcie "lshw -class network" shows the NICs as unclaimed. can anyone assist? No hardware changes, just the most recent update (just a small revision jump as I was on the latest release prior to this upgrade.

I'm getting this error with Fix Common Issues plugin but I think the use case I'm using, this is expected behavior. Wanted to throw it out there in case someone has some recommendations to alternatives or if they think it is safe to ignore. I want to be able to mount my google drive as a file share to be able to use in at least one of my containers. I found a Docker container that does just that (mitcdh/google-drive-ocamlfuse). So what I've down is use this container to mount the google drive to a location on unRaid (I used /mnt/disks/gdrive) and then setup a volume in the other container(s) to use that location as a volume. It seems to work great (as long as I start the containers in order). A couple behavior things: - the owner of /mnt/disks/gdrive seem to revert to root on reboot. I'd like it to stay nobody so this all works. Right now I'm manually fixing that on reboot. Would a different mount location be more appropriate? - the Fix Common Issues throws an error asking for it to be setup as slave in the container. Doing that causes it to not work, the drive that is mounted in the google-drive container isn't visible from unraid and therefore isn't visible in the other containers. Anyone have any thoughts on this? Any bad side effects to what I'm doing? Can I safely ignore the warning? Is that the best location to do the mount and is there a way to keep that nobody:users ownership at the mount point? Thanks in advance for any thoughts and suggestions.

Thanks UNRAID support for being super fast. They have resolved the key issue and I'm back up and running. Thank goodness for great backups as my data on the key was fully recovered and I don't have to re-setup anything. A friendly reminder, now would be a great time for you to install and setup "CA Backup / Restore Appdata" to backup both your appdata and your USB key.

I submitted on the webform on the website. Hopefully someone will be get back to me soon. In the mean time I will try the trial method. Thanks

Just had my USB stick die. This is the second one within a year so it won't let me transition my license key. What is the best way to get this expedited? My entire system is down at the moment.

Thanks for the suggestions. A couple nervous days but after running 3 parity checks, the 3rd came back clean.

nothing in the log pointing to an issue? Should I bring it back up and run parity and correct one more time and see if it fixes?

running a memory test now. Also remembered when the system came back up I got an error that the bios was reset to defaults and needed the date. I replaced the bios battery and reset to defaults. Could be a bios setting playing havoc as well.

Partly corrected, ran another one and it is finding more parity errors. Not good.

Had a power outage last night and when the server came back up there were some issues. First, USB was completely corrupt. Pulled another into rotation and rebuilt from my USB backup. Booted up and partity check ran. When it completed I got Last check completed on Mon 06 Jul 2020 06:30:00 PM CST (today), finding 1645 errors That has me really worried. I have attached my diagnostics. Any thoughts as to what might be the cause? gobo-diagnostics-20200706-2011.zip

I'm sure this has been answered before but for the life of me I can't figure it out. Heres my PHP info from the admin screen: Version: 7.3.17 Memory Limit: 2 GB Max Execution Time: 3600 Upload max size: 3 GB I was able to set memory limit and upload max size without issue, but that max execution time I can't find a way to change it. I need that bumped up but I haven't been able to find any configuration file setting to make it stick. Can anyone assist? I'm running into issues because of it.