Squid

What was the drive? Spinner? SSD? Could be no connection. Could be dead...

It's not assigned at the moment....

Do you (or did you) have a cache drive/pool?

Does anything show if you hover over it? It's most likely showing the * though because the installed RAM is greater than what the motherboard tells the OS that it supports.

Jan 26 10:25:10 Tower kernel: sd 2:0:2:0: attempting task abort!scmd(0x00000000e31eeef1), outstanding for 30382 ms & timeout 30000 ms Jan 26 10:25:10 Tower kernel: sd 2:0:2:0: [sdd] tag#3057 CDB: opcode=0x2a 2a 08 3a 38 3e a8 00 00 08 00 Jan 26 10:25:10 Tower kernel: scsi target2:0:2: handle(0x000a), sas_address(0x4433221101000000), phy(1) Jan 26 10:25:10 Tower kernel: scsi target2:0:2: enclosure logical id(0x5000000080000000), slot(2) Jan 26 10:25:11 Tower kernel: sd 2:0:2:0: task abort: SUCCESS scmd(0x00000000e31eeef1) Jan 26 10:25:11 Tower kernel: sd 2:0:2:0: Power-on or device reset occurred ### [PREVIOUS LINE REPEATED 1 TIMES] ### Jan 26 10:25:13 Tower rc.diskinfo[8139]: SIGHUP received, forcing refresh of disks info. Jan 26 10:25:46 Tower kernel: sd 2:0:2:0: attempting task abort!scmd(0x0000000038bf96d8), outstanding for 30329 ms & timeout 30000 ms Jan 26 10:25:46 Tower kernel: sd 2:0:2:0: [sdd] tag#3072 CDB: opcode=0x2a 2a 08 3a 38 3e a8 00 00 08 00 Jan 26 10:25:46 Tower kernel: scsi target2:0:2: handle(0x000a), sas_address(0x4433221101000000), phy(1) Jan 26 10:25:46 Tower kernel: scsi target2:0:2: enclosure logical id(0x5000000080000000), slot(2) Jan 26 10:25:47 Tower kernel: sd 2:0:2:0: task abort: SUCCESS scmd(0x0000000038bf96d8) Jan 26 10:25:47 Tower kernel: sd 2:0:2:0: Power-on or device reset occurred ### [PREVIOUS LINE REPEATED 1 TIMES] ### Jan 26 10:25:50 Tower rc.diskinfo[8139]: SIGHUP received, forcing refresh of disks info. ### [PREVIOUS LINE REPEATED 1 TIMES] ### Jan 26 10:27:21 Tower kernel: sd 2:0:2:0: attempting task abort!scmd(0x0000000074c99a4d), outstanding for 30139 ms & timeout 30000 ms Jan 26 10:27:21 Tower kernel: sd 2:0:2:0: [sdd] tag#3107 CDB: opcode=0x2a 2a 08 3a 38 3e b0 00 00 08 00 Jan 26 10:27:21 Tower kernel: scsi target2:0:2: handle(0x000a), sas_address(0x4433221101000000), phy(1) Jan 26 10:27:21 Tower kernel: scsi target2:0:2: enclosure logical id(0x5000000080000000), slot(2) Jan 26 10:27:21 Tower kernel: sd 2:0:2:0: task abort: SUCCESS scmd(0x0000000074c99a4d) Jan 26 10:27:21 Tower kernel: sd 2:0:2:0: Power-on or device reset occurred Jan 26 10:27:22 Tower rc.diskinfo[8139]: SIGHUP received, forcing refresh of disks info. Jan 26 10:27:22 Tower kernel: sd 2:0:2:0: Power-on or device reset occurred

sdd (disk 1) seems to have connection problems and is suffering from device resets slowing everything down. Reseat the cabling

Most of the apps have a /config path entry defined. The host path is automatically created using whatever you've defined in Settings - Docker for the default appdata path. Its when there's additional path mappings that the system can't automatically fill them out because it has no idea what those paths are supposed to be (ie: are they additional config entries that should be in appdata, or are they paths to media etc) Also, if you (at some point) change the settings (or say you've had to delete docker.cfg on the flash drive for some reason), the system will not adjust any paths for anything already installed (or on previously installed templates)

It's something with the script that he's got running to set stuff up. No idea. Post in the support thread.

pkexec doesn't exist in the standard OS itself, and the nice thing about containers is that you'd be pretty much safe since only files / folders you've given them access to would be able to take advantage of Besides, this exploit is about running a particular dangerous command to then provide root level access for another non-root user. In order to take advantage of this exploit, any hacker would first have to take advantage of another (or multiple) exploits in order to actually run a command in the first place. All in all, you're probably safe, and most of the authors of the containers regularly update their containers to take advantage of any security updates.

Probably best to post in the relevant support thread for the container (click on it's icon and select support etc)

Look in your download client for an option to set permissions (advanced view?) Then change it to 0777

"deadbeef" was referenced in the syslog dump Jan 24 22:42:48 BelK kernel: [Hardware Error]: 000000d0: deadbeef deadbeef deadbeef 0006c004 ................ It's a "joke" by the programmers In your case if there's nothing in a system event log etc in the BIOS, I'm not sure where to go or what it means.

Memory ballooning is an advanced VM technique, and I believe that there are additional drivers required on the VM side. But, on a quick google search what you're seeing seems pretty common with all hypervisors with no real solution.

It's suggesting to install it (for the better logging) because one or more mce (hardware errors) have been issued.

Anything that is an email address (or can be construed as an email address -> Appdata Backup/Restore has it's log entries changed to [email protected] because of how it forms the destination tar filename) is automatically changed.

Nothing particularly wrong in configuration. Is this server directly accessible from the internet? What ports are forwarded to it itself? To create a "fresh" boot, simply delete everything from /config/ on the flash drive except for super.dat and your .key file and reboot

You're going to have to post the docker run command at a minimum and we'd go from there

Because there's another entry in advanced view that defines the URL for the WebUI. It always refers to the container port, and if the port is mapped (bridge) then it gets adjusted accordingly

You are. Email addresses appearing in diagnostics are automatically removed (substituted for the above)

Can you show a picture to put this into context

Those messages on the screen are from the vmbackup plugin and aren't anything to worry about I don't see anything particularly obvious about libvirt. There were a couple of problems with one of you btrfs drives, but the system corrected it. Can you install ANY vm?

Probably best to hit up linuxserver or @binhex or @ich777

Is it stopped or paused?

Is that how your VM page actually looks? With cutoff text on "Main" (and still highlighted) while you're on the VM tab? Try it in safe mode from the boot menu

Are you sure the VM is still running? (VM tab)