macmanluke

Is there anyway to use this to run Mac OS 10.6? trying to replace a physical machine that is running printer software that requires appletalk

Just had same issue, turned file activity on last night for the first time in ages This morning it was just hammering the CPU to the point i almost couldnt do anything Managed to kill inotifywait and then do a graceful reboot

Been trying to use this but the config path eg /home/fpp does not seem to be getting written to appdata as its meant to meaning each time the docker is updated etc the configs are getting nuked, anyone else? any ideas?

Prefer not to as there is too much private information included them (eg file names, IPs etc in log files) even with anonymize on What specific information do you want?

Over the week end I got 4 read errors on one of my drives It is one of the older drives in the system with 30273 power on hours (WD Red 6TB) Has since passed a extended smart test and no more errors Following error in syslog looks to me more like a disk problem than cabling (which has not been touched/moved in 6-12months) Nov 13 04:36:23 Vault kernel: ata4.00: exception Emask 0x0 SAct 0x2100 SErr 0x0 action 0x0 Nov 13 04:36:23 Vault kernel: ata4.00: irq_stat 0x40000008 Nov 13 04:36:23 Vault kernel: ata4.00: failed command: READ FPDMA QUEUED Nov 13 04:36:23 Vault kernel: ata4.00: cmd 60/c0:40:f8:b9:16/00:00:be:00:00/40 tag 8 ncq dma 98304 in Nov 13 04:36:23 Vault kernel: res 41/40:00:98:ba:16/00:00:be:00:00/00 Emask 0x409 (media error) <F> Nov 13 04:36:23 Vault kernel: ata4.00: status: { DRDY ERR } Nov 13 04:36:23 Vault kernel: ata4.00: error: { UNC } Nov 13 04:36:23 Vault kernel: ata4.00: configured for UDMA/133 Nov 13 04:36:23 Vault kernel: sd 4:0:0:0: [sde] tag#8 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=4s Nov 13 04:36:23 Vault kernel: sd 4:0:0:0: [sde] tag#8 Sense Key : 0x3 [current] Nov 13 04:36:23 Vault kernel: sd 4:0:0:0: [sde] tag#8 ASC=0x11 ASCQ=0x4 Nov 13 04:36:23 Vault kernel: sd 4:0:0:0: [sde] tag#8 CDB: opcode=0x88 88 00 00 00 00 00 be 16 b9 f8 00 00 00 c0 00 00 Nov 13 04:36:23 Vault kernel: I/O error, dev sde, sector 3189160600 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 0 Nov 13 04:36:23 Vault kernel: md: disk1 read error, sector=3189160536 Nov 13 04:36:23 Vault kernel: md: disk1 read error, sector=3189160544 Nov 13 04:36:23 Vault kernel: md: disk1 read error, sector=3189160552 Nov 13 04:36:23 Vault kernel: md: disk1 read error, sector=3189160560 Nov 13 04:36:23 Vault kernel: ata4: EH complete Thinking I should still swap out the drive? thoughts?

I'll try to grab them when I have a chance Uninstalled the plugin on Friday and GUI has stayed up since. Guessing it was something in the latest update causing it.

I have also been loosing my GUI this week and use Tailscale, nothing useful in my syslog though

Hello all Came home tonight to my unraid box playing up First noticed my home assistant seemed to not be functioning Logged in and found a bunch of dockers stopped that are normally running (unfortunately didn't think to take notice of what was and was not. Most were not running anymore) Noticed the CPU was maxed and top revealed a process 'node' (x12) maxing the CPU https://imgur.com/a/hAsl3M8 Stopped docker trying to narrow it down and that stopped the CPU usage but overall the server was acting up - all my shares were not showing up in the UI etc Rebooted and all appears good but like to find out what happened Any suggestions? not sure what would cause it List of dockers I run: https://imgur.com/a/Srul7nx Only thing in Tailscale before the reboot and the usual nightly stuff is from Tailscale but does not look like anything of concern Still running 6.11.5 thanks!

Well its been ~10 days and still up (best so far in a while) Only change i made this time was unplugging the monitor from the integrated graphics - not the first time iv had this issue Had forgotten about it and had only plugged i back in to troubleshoot the previous crashing issue So i think i had 2 problems: 1) macvlan crashes that appeared out of no where. 2) monitor plugged into intel igpu causes crashes. Have had the issue on 2 seperate systems since 6.9 or 6.10 (was fine in 6.8 or 6.9, cant remember when it started)

sorry didnt read that one, previous message before the reinstall didnt have starting tailscale line. Seem to have gotten it working now after the reinstall and reauth

after updating to the latest version on one of my machines im getting Tried removing and reinstalling no luck. Is on 6.12rc2 Other machine is fine (but 6.11.5)

Still broke in 6.12rc2

My unraid server started crashing approx 1 month ago Its crashing on average once every 2-7 days. Has been super stable for 1 year plus prior. No new hardware additions. Last software update was 6.11.5 around the time that came out Intel 10400, z590, 32GB DDR4 no XMP. iGPU used for plex RTX3060 passed to VM (thats not been running during this time) Syslog has either had nothing around time of crash, or btrfs errors (which i think is more a symptom of the crash than the cause) See thread below: Have run memtest on the ram that was in the server (24hrs, 16 passes) all passed Ram swapped with 32gb from my desktop. Still crashed. Latest crash was this morning at 7:13am (only know time because my security server notifies me when it comes backup when it went down) Last syslog entries before i rebooted it were at 3:30am from CA Backup running and completing. Nothing much is happening on the server at 7:13 Any suggestions before i start swapping out more hardware? lack of anything in syslogs makes troubleshooting a nightmare Diags attached

Looks like there was never a solution to this mess? macvlan = network works, box crashes every few days (out of no where, has been stable for ages) ipvlan + allow hosts = messed up network connectivity, stable server ip vlan + no allow hosts = working network, stable server but my reverse proxy does not work if a docker is bridged.