dodgeman

I am running Powertop and only able to see C states C1 & C2. I have changed the boot zenstates to enabled and set the BIOS to "Typical Idle". I am on the Gigabyte Aorus B550 AORUS ELITE AX V2. Am I missing something ?

Thank you for checking and your docker.

docker run -d --name='xteve' --net='host' -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="TowerMHS" -e HOST_CONTAINERNAME="xteve" -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:34400]/web/' -l net.unraid.docker.icon='https://avatars0.githubusercontent.com/u/53275662?s=460&v=4' -v '/mnt/user/appdata/xteve/':'/root/.xteve':'rw' -v '/mnt/user/appdata/xteve':'/config':'rw' -v '':'/tmp/xteve':'rw' -v '':'/TVH':'rw' 'alturismo/xteve' b6d28717c00b3a20d910baf3905ae47ca3b2cd17fe2c18274958dd6e325f6f9c The command finished successfully! Yes I am using http://hostip:34400/web

Just did a setup in host mode and the web interface is blank. Last log entries 2023/04/22 19:07:54 [xTeVe] System Folder: /root/.xteve/ 2023/04/22 19:07:54 [xTeVe] Load Settings: /root/.xteve/settings.json 2023/04/22 19:07:54 [xTeVe] Temporary Folder: /tmp/xteve/2023-04-U5GB-HRP3FG/ 2023/04/22 19:07:54 [xTeVe] GitHub: https://github.com/xteve-project 2023/04/22 19:07:54 [xTeVe] Git Branch: master [xteve-project] 2023/04/22 19:07:54 [xTeVe] SSDP / DLNA: true 2023/04/22 19:07:55 [xTeVe] UUID: 2023-04-U5GB-HRP3FG 2023/04/22 19:07:55 [xTeVe] Tuner (Plex / Emby): 1 2023/04/22 19:07:55 [xTeVe] EPG Source: PMS 2023/04/22 19:07:55 [xTeVe] Plex Channel Limit: 480 2023/04/22 19:07:55 [xTeVe] Unfiltered Chan. Limit: 480 2023/04/22 19:07:55 [xTeVe] All streams: 0 2023/04/22 19:07:55 [xTeVe] Active streams: 0 2023/04/22 19:07:55 [xTeVe] Filter: 0 2023/04/22 19:07:55 [xTeVe] DVR IP: 172.17.0.1:34400 2023/04/22 19:07:55 [xTeVe] Web Interface: http://172.17.0.1:34400/web/ | xTeVe is also available via the other 25 IP's. /config/cronjob.sh does not exist For help run: ./xteve -h /config/cronjob.sh exist For help run: ./xteve -h Tried the link and the host ip neither works. I am not sure what's missing

Here is the template I saw your post in this thread How to make an UnRAID Docker Image/Template ? - Pre-Sales Support - Unraid so I set the WebUI to 8080

I am trying to setup this docker image klschaefer/channels-dvr-plex-xmltv-proxy Tags | Docker Hub however when I do it starts on port 80 and port 8080 does not answer. Log shows it listening on port 80 {"EventId":14,"LogLevel":"Information","Category":"Microsoft.Hosting.Lifetime","Message":"Now listening on: http://[::]:80","State":{"Message":"Now listening on: http://[::]:80","address":"http://[::]:80","{OriginalFormat}":"Now listening on: {address}"}} I've specified the WebUI as http://[IP]:[PORT:8080]

Well it looks like the issue was the EPC Feature of the Seagate 12 TB drive. I found this other thread 6.9.x, LSI Controllers & Ironwolf Disks Disabling - Summary & Fix - Page 5 - General - Unraid and ran the SeaChest tools to disable it and its been running for about 40 minutes, it would only run a minute or two prior.

This is the latest attempt to sync this morning. towermhs-diagnostics-20230327-0708.zip

I had a 4TB drive that was nearly full, so I upgraded it to 12 TB to match my parity drives. I shut down the array and replaced the drive. Then switched to the new drive in the array configuration. I brought the array up and it started to sync ran for a few minutes then paused. It would not resume. I brought the array down again and tried it in maintenance mode and the same result. I then tested the drive using SEAtools with the short and long tests no issues found. I then tried to sync the array again in maintenance mode and it failed. Mar 27 07:04:43 TowerMHS kernel: md: disk4 write error, sector=39147800 Mar 27 07:04:43 TowerMHS kernel: md: disk4 write error, sector=39147808 Mar 27 07:04:43 TowerMHS kernel: md: disk4 write error, sector=39147816 Mar 27 07:04:43 TowerMHS kernel: md: disk4 write error, sector=39147824 Mar 27 07:04:43 TowerMHS kernel: md: disk4 write error, sector=39147832 Mar 27 07:04:43 TowerMHS kernel: md: disk4 write error, sector=39147840 Mar 27 07:04:43 TowerMHS kernel: md: disk4 write error, sector=39147848 Mar 27 07:04:43 TowerMHS kernel: md: disk4 write error, sector=39147856 Mar 27 07:04:43 TowerMHS kernel: Buffer I/O error on dev sdv1, logical block 23437770496, async page read Mar 27 07:04:43 TowerMHS kernel: Buffer I/O error on dev sdv1, logical block 23437770497, async page read Mar 27 07:04:43 TowerMHS kernel: Buffer I/O error on dev sdv1, logical block 23437770498, async page read Mar 27 07:04:43 TowerMHS kernel: Buffer I/O error on dev sdv1, logical block 23437770499, async page read Mar 27 07:04:43 TowerMHS kernel: Buffer I/O error on dev sdv1, logical block 23437770500, async page read Mar 27 07:04:43 TowerMHS kernel: Buffer I/O error on dev sdv1, logical block 23437770501, async page read Mar 27 07:04:43 TowerMHS kernel: Buffer I/O error on dev sdv1, logical block 23437770502, async page read Mar 27 07:04:43 TowerMHS kernel: Buffer I/O error on dev sdv1, logical block 23437770503, async page read Mar 27 07:04:43 TowerMHS kernel: sd 7:0:20:0: [sdv] Synchronizing SCSI cache Mar 27 07:04:43 TowerMHS kernel: sd 7:0:20:0: [sdv] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK Mar 27 07:04:43 TowerMHS kernel: mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x5001e677b7084fe7) Mar 27 07:04:43 TowerMHS kernel: mpt2sas_cm0: removing handle(0x001f), sas_addr(0x5001e677b7084fe7) Mar 27 07:04:43 TowerMHS kernel: mpt2sas_cm0: enclosure logical id(0x5001e677b7084fff), slot(7) Mar 27 07:04:43 TowerMHS kernel: md: recovery thread: exit status: -4 Mar 27 07:04:57 TowerMHS kernel: mpt2sas_cm0: handle(0x1f) sas_address(0x5001e677b7084fe7) port_type(0x1) Mar 27 07:04:58 TowerMHS kernel: scsi 7:0:26:0: Direct-Access ATA ST12000NM001G-2M SN04 PQ: 0 ANSI: 6 Mar 27 07:04:58 TowerMHS kernel: scsi 7:0:26:0: SATA: handle(0x001f), sas_addr(0x5001e677b7084fe7), phy(7), device_name(0x0000000000000000) Mar 27 07:04:58 TowerMHS kernel: scsi 7:0:26:0: enclosure logical id (0x5001e677b7084fff), slot(7) Mar 27 07:04:58 TowerMHS kernel: scsi 7:0:26:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) Mar 27 07:04:58 TowerMHS kernel: scsi 7:0:26:0: qdepth(32), tagged(1), scsi_level(7), cmd_que(1) Mar 27 07:04:58 TowerMHS kernel: sd 7:0:26:0: Attached scsi generic sg22 type 0 Mar 27 07:04:58 TowerMHS kernel: end_device-7:1:9: add: handle(0x001f), sas_addr(0x5001e677b7084fe7) Mar 27 07:04:58 TowerMHS kernel: sd 7:0:26:0: Power-on or device reset occurred Mar 27 07:04:58 TowerMHS kernel: sd 7:0:26:0: [sdaa] 23437770752 512-byte logical blocks: (12.0 TB/10.9 TiB) Mar 27 07:04:58 TowerMHS kernel: sd 7:0:26:0: [sdaa] 4096-byte physical blocks Mar 27 07:04:58 TowerMHS kernel: sd 7:0:26:0: [sdaa] Write Protect is off Mar 27 07:04:58 TowerMHS kernel: sd 7:0:26:0: [sdaa] Mode Sense: 7f 00 10 08 Mar 27 07:04:58 TowerMHS kernel: sd 7:0:26:0: [sdaa] Write cache: enabled, read cache: enabled, supports DPO and FUA Mar 27 07:04:58 TowerMHS kernel: sdaa: sdaa1 Mar 27 07:04:58 TowerMHS kernel: sd 7:0:26:0: [sdaa] Attached SCSI disk Mar 27 07:04:59 TowerMHS unassigned.devices: Disk with ID 'Sabrent_296D07911DDE06527222 (nvme0n1)' is not set to auto mount. Mar 27 07:04:59 TowerMHS unassigned.devices: Disk with ID 'ST12000NM001G-2MV103_ZLW1YV50 (sdaa)' is not set to auto mount. Mar 27 07:05:00 TowerMHS emhttpd: error: hotplug_devices, 1730: No such file or directory (2): Error: tagged device ST12000NM001G-2MV103_ZLW1YV50 was (sdv) is now (sdaa) Mar 27 07:05:00 TowerMHS emhttpd: read SMART /dev/sdaa This same backplane bay etc was used by the smaller drive for many months with no issues.

I get the full download and erase the drive to format with Big Sur but I cannot install because the network is not found. The network utility shows Virtio ethernet with a 169.. address. I have ran this container before but I now have a different motherboard. Gigabyte Technology Co., Ltd. B550 AORUS ELITE AX V2, Version Default string American Megatrends International, LLC., Version F14 BIOS dated: Mon 01 Nov 2021 12:00:00 AM PDT.

Frank you were correct it was the 12+ it was 54A and I moved to a new one with 82A and the problem is gone, so I do not think the PS were delivery less than stated, I just think it was just not enough on 12v legs. Thanks

Well I had a bad drive in cache pool, could not repair the issue so I purchased a new drive to replace it followed the steps in this thread for drive upgrade [SOLVED] unRAID v6.9.2 - Upgrading Cache Pool Drive - General Support - Unraid and now the pool will not start without the "Unmountable disk present:"

OK so one other thing I just did changed the ip address to 192.168.0.66 as DHCP, Then everything works, I changed it back to a reserved .107 at it fails, again. I change it to .108 and it fails, change it to .66 and it works as a static address. I have not made changes to my router so I am not sure what is going on.

mhs-diagnostics-20220223-1343.zip

So I've been dealing with several issue, I believe stem from a failing motherboard and or faulty boot media. I fixed the boot media and now the server starts without a kernel fault. I ran the Fix Common Problems Plug-in to see what issues I may still have and it reported bad DNS configuration. I checked that out and found I cannot ping or traceroute to my DNS/Gateway. I can ping other machines on the same subnet. I can PING 192.168.0.24 (192.168.0.24) 56(84) bytes of data. 64 bytes from 192.168.0.24: icmp_seq=1 ttl=128 time=0.155 ms 64 bytes from 192.168.0.24: icmp_seq=2 ttl=128 time=0.187 ms Ping to the gateway ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. From 192.168.0.107 icmp_seq=10 Destination Host Unreachable So that rules out cable issues, The routes look ok route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 192.168.0.1 0.0.0.0 UG 208 0 0 eth0 192.168.0.0 0.0.0.0 255.255.255.0 U 208 0 0 eth0 I did have bonding error reported but the network setting in the GUI did not show it, but the network.cfg did, so I reset the network.cfg. IFNAME[0]="eth0" PROTOCOL[0]="ipv4" USE_DHCP[0]="yes" DHCP_KEEPRESOLV="yes" DNS_SERVER1="8.8.8.8" DNS_SERVER2="8.8.4.4" USE_DHCP6[0]="yes" DHCP6_KEEPRESOLV="no" SYSNICS="1"