Squid

I've long since moved on, but I did have success with an AMD 5450 years ago. Most people still have them sitting in their junk bins

Fixed for next release

There is a similar item (not the exact same as what was in the contest) available in LT's Swag Shop.

True. With the right amount of motivation i will force an update

Every two hours

Ran into a very quick almost show stopper (but will be an actual show stopper for many users) Unassigned Devices is listed as being incompatible with this. Since this release is identical to 6.8.3 except for the kernel, UD has to have it's maximum OS value changed. @dlandon For my work flow it's not an explicit show stopper as I can manually mount the SMB shares, its a bit of a PITA right now. Have to downgrade until there's no one wanting to use the server. EDIT: Just edited the .plg on the flash instead

I would open a new thread in the General Support section. Last time I ran into this is when installed denyhosts / ssh config plugin installed, and it trashed everything and once I got the system functional, had the same rebinding error occur. As I recall, I just kept on messing around with various settings until it magically started working.

It's not that FCP thinks that the DNS is messed up, but rather that it can't communicate with the outside world (in this case GitHub) which is a necessity for many subsystems within unRaid. The DNS suggestion is simply a suggestion as that's the most common problem for this issue. Admittedly I'm not a network guy, but shouldn't the server's IP address be on the same subnet as the gateway to limit problems? IPADDR[0]="10.20.1.1" NETMASK[0]="255.0.0.0" GATEWAY[0]="10.10.0.0"

It would be the container logs as to why it's not starting. But it may be related to the order if it's directly referencing another container. I'll look at it.

Now theres problems on disk 2 wanting you to run the checks on it. Wouldn't be a bad idea to run a memtest via the boot menu to rule it out as a possible cause.

Command prompt Something akin to tail -f /tmp/user.scripts/tmpScripts/Set permissions on Downloads/log.txt

If the log is insanely long, any browser will choke on it.

The SSL folder is recreated upon every reboot. Question though becomes did you by chance have any of the SSL related plugins installed (ie: denyhosts etc)?

Post your diagnostics

Some combinations of hardware (cpu and motherboard), in conjunction with the architecture of your domicile (Indian graveyard, pyramid etc) will issue an MCE when initializing the CPU's. ie: in your case this is nothing, is normal, and is perfectly safe to ignore

Looks like this drive ata12.00: ATA-9: WDC WD80EZZX-11CSGA0, VK0J335Y, 83.H0A03, max UDMA/133 is continually resetting Mar 7 19:20:06 MEDIASERVER1 kernel: ata12.00: failed command: READ FPDMA QUEUED Mar 7 19:20:06 MEDIASERVER1 kernel: ata12.00: cmd 60/40:40:20:e8:0c/00:00:05:00:00/40 tag 8 ncq dma 32768 in Mar 7 19:20:06 MEDIASERVER1 kernel: res 40/00:00:20:e8:0c/00:00:05:00:00/40 Emask 0x10 (ATA bus error) Mar 7 19:20:06 MEDIASERVER1 kernel: ata12.00: status: { DRDY } Mar 7 19:20:06 MEDIASERVER1 kernel: ata12: hard resetting link Mar 7 19:20:12 MEDIASERVER1 kernel: ata12: link is slow to respond, please be patient (ready=0) Mar 7 19:20:16 MEDIASERVER1 kernel: ata12: COMRESET failed (errno=-16) Mar 7 19:20:16 MEDIASERVER1 kernel: ata12: hard resetting link Mar 7 19:20:17 MEDIASERVER1 kernel: ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Mar 7 19:20:17 MEDIASERVER1 kernel: ata12.00: configured for UDMA/133 Mar 7 19:20:17 MEDIASERVER1 kernel: ata12: EH complete Odds on caused by bad / loose sata cabling to the drive or the p/s connector to the drive. Reseat everything. Just be aware that SATA cables by their very design are garbage, and it is quite possible that when you reseat or change this one that you will disturb another and cause the same issue on a different drive. Be careful

My first guess would be to delete the contents of /config/ssl on the flash drive and then reboot and try again.

Then post your diagnostics

It tests your memory. You run it via the boot menu

Email Limetech https://unraid.net/contact

That's the same process as the guides you've already found. Basically, copy all of the files from one stick to another, boot the system up and it'll complain that the registration isn't for that stick and walk you through getting a replacement key. The registration is tied to the stick not the server.

Are you overclocking? Have you run a memtest yet?

If its a bug and if the additional settings in syslinux.cfg don't help you out, then it's a bug with linux itself and not unRaid.

IOMMU and virtualization while related are not the same thing and are 2 separate entries in your BIOS. Enabling virtualization within the BIOS enables vt-x which is a requirement for any VM to run period. Enabling IOMMU (or vt-d) enables vt-d which is a requirement for hardware passthrough to a VM Virtualization is usually handled by CPU settings, whereas IOMMU will usually be in Advanced / Chipset settings or the like

Mar 7 14:11:09 SG-UNRAID root: mount: /mnt/cache: wrong fs type, bad option, bad superblock on /dev/sdi1, missing codepage or helper program, or other error. The cache drive is corrupted I'll leave it to the experts ( @johnnie.black ) to help you out