Jump to content

emuhack

Members
  • Content Count

    52
  • Joined

  • Last visited

Community Reputation

3 Neutral

1 Follower

About emuhack

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yeah I'm going to switch to a nvme this weekend, I have a backup of my appdata folder and will restore the dockers when I install the nvme. I appreciate the help and the time spend on looking at the diags.
  2. I ran a scrub on the pool and it seems to be stable, but when I try to delete a certain folder in appdata, it freaks out and gives these error. I have ordered a 1tb NVME drive for use with my cache to get the sata ssd's out of the system, but would be interested on if i can delete the folder before i migrate to the NVME also I know disk 5 in the array is bad, waiting until the nvme is here to take out and rebuild the array as asked diags attached emu-unraid-diagnostics-20200330-2123.zip
  3. also to add [1/7] checking root items [2/7] checking extents ref mismatch on [194688524288 65536] extent item 0, found 1 data backref 194688524288 root 5 owner 11000 offset 24625152 num_refs 0 not found in extent tree incorrect local backref count on 194688524288 root 5 owner 11000 offset 24625152 found 1 wanted 0 back 0x1062f950 backpointer mismatch on [194688524288 65536] ref mismatch on [194688557056 65536] extent item 1, found 0 incorrect local backref count on 194688557056 root 5 owner 11000 offset 24625152 found 0 wanted 1 back 0x9344620 backref disk bytenr does not match extent record, bytenr=194688557056, ref bytenr=0 backpointer mismatch on [194688557056 65536] owner ref check failed [194688557056 65536] ERROR: errors found in extent allocation tree or chunk allocation [3/7] checking free space cache [4/7] checking fs roots root 5 inode 11000 errors 1000, some csum missing ERROR: errors found in fs roots Opening filesystem to check... Checking filesystem on /dev/sdm1 UUID: 544aa70e-af02-4453-8115-da59be8c2580 found 536521904128 bytes used, error(s) found total csum bytes: 452987428 total tree bytes: 796852224 total fs tree bytes: 163954688 total extent tree bytes: 75792384 btree space waste bytes: 107032372 file data blocks allocated: 3968869117952 referenced 497898889216
  4. Slowly this has been getting worse, and it seems like I may have to scrub my cache pool. Can anybody help me with the follow errors. I can seem to do anything in relation to my dockers and they are not responding? Mar 30 14:06:53 eMu-Unraid kernel: loop: Write error at byte offset 844144640, length 4096. Mar 30 14:06:53 eMu-Unraid kernel: print_req_error: I/O error, dev loop2, sector 1648720 Mar 30 14:06:53 eMu-Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 152, rd 0, flush 0, corrupt 0, gen 0 Mar 30 14:07:21 eMu-Unraid kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] Mar 30 14:07:21 eMu-Unraid kernel: caller _nv000908rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs Mar 30 14:07:23 eMu-Unraid root: Fix Common Problems: Error: Unable to write to cache Mar 30 14:07:23 eMu-Unraid root: Fix Common Problems: Error: Unable to write to Docker Image Mar 30 14:07:23 eMu-Unraid kernel: loop: Write error at byte offset 844144640, length 4096. Mar 30 14:07:23 eMu-Unraid kernel: print_req_error: I/O error, dev loop2, sector 1648720 Mar 30 14:07:23 eMu-Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 153, rd 0, flush 0, corrupt 0, gen 0 Mar 30 14:07:24 eMu-Unraid kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] Mar 30 14:07:24 eMu-Unraid kernel: caller _nv000908rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs Mar 30 14:07:52 eMu-Unraid kernel: sd 2:1:13:0: [sdf] tag#638 UNKNOWN(0x2003) Result: hostbyte=0x05 driverbyte=0x00 Mar 30 14:07:52 eMu-Unraid kernel: sd 2:1:13:0: [sdf] tag#638 CDB: opcode=0x28 28 00 74 7a 31 20 00 00 08 00 Mar 30 14:07:52 eMu-Unraid kernel: print_req_error: I/O error, dev sdf, sector 1954165024 Mar 30 14:07:52 eMu-Unraid kernel: md: disk5 read error, sector=1954164960 Mar 30 14:07:54 eMu-Unraid kernel: loop: Write error at byte offset 844144640, length 4096. Mar 30 14:07:54 eMu-Unraid kernel: print_req_error: I/O error, dev loop2, sector 1648720 Mar 30 14:07:54 eMu-Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 154, rd 0, flush 0, corrupt 0, gen 0 Mar 30 14:08:01 eMu-Unraid sSMTP[16065]: Creating SSL connection to host Mar 30 14:08:01 eMu-Unraid sSMTP[16065]: SSL connection using TLS_AES_256_GCM_SHA384 Mar 30 14:08:04 eMu-Unraid sSMTP[16065]: Sent mail for xxxxxxxxxx (221 2.0.0 closing connection p38sm12204726qtf.50 - gsmtp) uid=0 username=root outbytes=785 Mar 30 14:08:14 eMu-Unraid kernel: mdcmd (44): spindown 5 Mar 30 14:08:15 eMu-Unraid root: Fix Common Problems: Warning: Write Cache is disabled on disk5 Mar 30 14:08:25 eMu-Unraid kernel: loop: Write error at byte offset 844144640, length 4096. Mar 30 14:08:25 eMu-Unraid kernel: print_req_error: I/O error, dev loop2, sector 1648720 Mar 30 14:08:25 eMu-Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 155, rd 0, flush 0, corrupt 0, gen 0 Mar 30 14:08:53 eMu-Unraid kernel: sd 2:1:13:0: [sdf] tag#196 UNKNOWN(0x2003) Result: hostbyte=0x05 driverbyte=0x00 Mar 30 14:08:53 eMu-Unraid kernel: sd 2:1:13:0: [sdf] tag#196 CDB: opcode=0x2a 2a 00 74 7a 31 20 00 00 08 00 Mar 30 14:08:53 eMu-Unraid kernel: print_req_error: I/O error, dev sdf, sector 1954165024 Mar 30 14:08:53 eMu-Unraid kernel: md: disk5 write error, sector=1954164960 Mar 30 14:08:56 eMu-Unraid kernel: loop: Write error at byte offset 844144640, length 4096. Mar 30 14:08:56 eMu-Unraid kernel: print_req_error: I/O error, dev loop2, sector 1648720 Mar 30 14:08:56 eMu-Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 156, rd 0, flush 0, corrupt 0, gen 0 Mar 30 14:09:04 eMu-Unraid sSMTP[16687]: Creating SSL connection to host Mar 30 14:09:04 eMu-Unraid sSMTP[16687]: SSL connection using TLS_AES_256_GCM_SHA384 Mar 30 14:09:06 eMu-Unraid sSMTP[16687]: Sent mail for emuhackwii@gmail.com (221 2.0.0 closing connection h11sm11384241qta.44 - gsmtp) uid=0 username=root outbytes=756 Mar 30 14:09:26 eMu-Unraid kernel: loop: Write error at byte offset 844144640, length 4096. Mar 30 14:09:26 eMu-Unraid kernel: print_req_error: I/O error, dev loop2, sector 1648720 Mar 30 14:09:26 eMu-Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 157, rd 0, flush 0, corrupt 0, gen 0 Mar 30 14:09:57 eMu-Unraid kernel: loop: Write error at byte offset 844144640, length 4096. Mar 30 14:09:57 eMu-Unraid kernel: print_req_error: I/O error, dev loop2, sector 1648720 Mar 30 14:09:57 eMu-Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 158, rd 0, flush 0, corrupt 0, gen 0 Mar 30 14:10:28 eMu-Unraid kernel: loop: Write error at byte offset 3260116992, length 4096. Mar 30 14:10:28 eMu-Unraid kernel: print_req_error: I/O error, dev loop2, sector 6367416 Mar 30 14:10:28 eMu-Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 159, rd 0, flush 0, corrupt 0, gen 0 Mar 30 14:10:58 eMu-Unraid kernel: loop: Write error at byte offset 844144640, length 4096. Mar 30 14:10:58 eMu-Unraid kernel: print_req_error: I/O error, dev loop2, sector 1648720 Mar 30 14:10:58 eMu-Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 160, rd 0, flush 0, corrupt 0, gen 0 Mar 30 14:11:12 eMu-Unraid kernel: mdcmd (45): spindown 5 Mar 30 14:11:29 eMu-Unraid kernel: loop: Write error at byte offset 844144640, length 4096. Mar 30 14:11:29 eMu-Unraid kernel: print_req_error: I/O error, dev loop2, sector 1648720 Mar 30 14:11:29 eMu-Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 161, rd 0, flush 0, corrupt 0, gen 0 Mar 30 14:12:00 eMu-Unraid kernel: loop: Write error at byte offset 844144640, length 4096. Mar 30 14:12:00 eMu-Unraid kernel: print_req_error: I/O error, dev loop2, sector 1648720 Mar 30 14:12:00 eMu-Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 162, rd 0, flush 0, corrupt 0, gen 0 Mar 30 14:12:31 eMu-Unraid kernel: loop: Write error at byte offset 844144640, length 4096. Mar 30 14:12:31 eMu-Unraid kernel: print_req_error: I/O error, dev loop2, sector 1648720 Mar 30 14:12:31 eMu-Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 163, rd 0, flush 0, corrupt 0, gen 0 Mar 30 14:12:32 eMu-Unraid kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] Mar 30 14:12:32 eMu-Unraid kernel: caller _nv000908rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs Mar 30 14:12:34 eMu-Unraid kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] Mar 30 14:12:34 eMu-Unraid kernel: caller _nv000908rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs Mar 30 14:12:37 eMu-Unraid kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] Mar 30 14:12:37 eMu-Unraid kernel: caller _nv000908rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs Mar 30 14:13:01 eMu-Unraid kernel: loop: Write error at byte offset 844144640, length 4096. Mar 30 14:13:01 eMu-Unraid kernel: print_req_error: I/O error, dev loop2, sector 1648720 Mar 30 14:13:01 eMu-Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 164, rd 0, flush 0, corrupt 0, gen 0 Mar 30 14:13:32 eMu-Unraid kernel: loop: Write error at byte offset 844144640, length 4096. Mar 30 14:13:32 eMu-Unraid kernel: print_req_error: I/O error, dev loop2, sector 1648720 Mar 30 14:13:32 eMu-Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 165, rd 0, flush 0, corrupt 0, gen 0 Mar 30 14:14:03 eMu-Unraid kernel: loop: Write error at byte offset 844144640, length 4096. Mar 30 14:14:03 eMu-Unraid kernel: print_req_error: I/O error, dev loop2, sector 1648720 Mar 30 14:14:03 eMu-Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 166, rd 0, flush 0, corrupt 0, gen 0
  5. I have dug up an older T5500 from my "stash" and I am building a buddy his first plex server I have a 3900x and another XEON based system and all the CPU stats have shown up. This new system though I have this issue where the cpu is Not Specified. I have the latest BIOS update for this machine. This is the System Device Page System Devices PCI Devices and IOMMU Groups IOMMU group 0: [8086:3406] 00:00.0 Host bridge: Intel Corporation 5520 I/O Hub to ESI Port (rev 22) IOMMU group 1: [8086:3408] 00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 (rev 22) IOMMU group 2: [8086:340a] 00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 (rev 22) IOMMU group 3: [8086:340e] 00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 22) IOMMU group 4: [8086:342e] 00:14.0 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub System Management Registers (rev 22) [8086:3422] 00:14.1 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers (rev 22) [8086:3423] 00:14.2 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub Control Status and RAS Registers (rev 22) IOMMU group 5: [8086:3a37] 00:1a.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 [8086:3a38] 00:1a.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 [8086:3a39] 00:1a.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 [8086:3a3c] 00:1a.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 IOMMU group 6: [8086:3a3e] 00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller IOMMU group 7: [8086:3a40] 00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 1 [8086:3a4a] 00:1c.5 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 6 [14e4:1681] 06:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5761 Gigabit Ethernet PCIe (rev 10) IOMMU group 8: [8086:3a34] 00:1d.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1 [8086:3a35] 00:1d.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2 [8086:3a36] 00:1d.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3 [8086:3a3a] 00:1d.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1 IOMMU group 9: [8086:244e] 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90) IOMMU group 10: [8086:3a16] 00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller [8086:3a22] 00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller [8086:3a30] 00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller IOMMU group 11: [12d8:e130] 01:00.0 PCI bridge: Pericom Semiconductor PCI Express to PCI-XPI7C9X130 PCI-X Bridge (rev 04) IOMMU group 12: [1002:68c8] 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Redwood XT GL [FirePro V4800] [1002:aa60] 03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Redwood HDMI Audio [Radeon HD 5000 Series] IOMMU group 13: [8086:340e] 20:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 22) IOMMU group 14: [8086:3410] 20:09.0 PCI bridge: Intel Corporation 7500/5520/5500/X58 I/O Hub PCI Express Root Port 9 (rev 22) IOMMU group 15: [8086:342e] 20:14.0 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub System Management Registers (rev 22) [8086:3422] 20:14.1 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers (rev 22) [8086:3423] 20:14.2 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub Control Status and RAS Registers (rev 22) IOMMU group 16: [8086:2c70] 3e:00.0 Host bridge: Intel Corporation Xeon 5600 Series QuickPath Architecture Generic Non-core Registers (rev 02) [8086:2d81] 3e:00.1 Host bridge: Intel Corporation Xeon 5600 Series QuickPath Architecture System Address Decoder (rev 02) IOMMU group 17: [8086:2d90] 3e:02.0 Host bridge: Intel Corporation Xeon 5600 Series QPI Link 0 (rev 02) [8086:2d91] 3e:02.1 Host bridge: Intel Corporation Xeon 5600 Series QPI Physical 0 (rev 02) [8086:2d92] 3e:02.2 Host bridge: Intel Corporation Xeon 5600 Series Mirror Port Link 0 (rev 02) [8086:2d93] 3e:02.3 Host bridge: Intel Corporation Xeon 5600 Series Mirror Port Link 1 (rev 02) [8086:2d94] 3e:02.4 Host bridge: Intel Corporation Xeon 5600 Series QPI Link 1 (rev 02) [8086:2d95] 3e:02.5 Host bridge: Intel Corporation Xeon 5600 Series QPI Physical 1 (rev 02) IOMMU group 18: [8086:2d98] 3e:03.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Registers (rev 02) [8086:2d99] 3e:03.1 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Target Address Decoder (rev 02) [8086:2d9a] 3e:03.2 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller RAS Registers (rev 02) [8086:2d9c] 3e:03.4 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Test Registers (rev 02) IOMMU group 19: [8086:2da0] 3e:04.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Control (rev 02) [8086:2da1] 3e:04.1 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Address (rev 02) [8086:2da2] 3e:04.2 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Rank (rev 02) [8086:2da3] 3e:04.3 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Thermal Control (rev 02) IOMMU group 20: [8086:2da8] 3e:05.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Control (rev 02) [8086:2da9] 3e:05.1 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Address (rev 02) [8086:2daa] 3e:05.2 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Rank (rev 02) [8086:2dab] 3e:05.3 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Thermal Control (rev 02) IOMMU group 21: [8086:2db0] 3e:06.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Control (rev 02) [8086:2db1] 3e:06.1 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Address (rev 02) [8086:2db2] 3e:06.2 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Rank (rev 02) [8086:2db3] 3e:06.3 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Thermal Control (rev 02) IOMMU group 22: [8086:2c70] 3f:00.0 Host bridge: Intel Corporation Xeon 5600 Series QuickPath Architecture Generic Non-core Registers (rev 02) [8086:2d81] 3f:00.1 Host bridge: Intel Corporation Xeon 5600 Series QuickPath Architecture System Address Decoder (rev 02) IOMMU group 23: [8086:2d90] 3f:02.0 Host bridge: Intel Corporation Xeon 5600 Series QPI Link 0 (rev 02) [8086:2d91] 3f:02.1 Host bridge: Intel Corporation Xeon 5600 Series QPI Physical 0 (rev 02) [8086:2d92] 3f:02.2 Host bridge: Intel Corporation Xeon 5600 Series Mirror Port Link 0 (rev 02) [8086:2d93] 3f:02.3 Host bridge: Intel Corporation Xeon 5600 Series Mirror Port Link 1 (rev 02) [8086:2d94] 3f:02.4 Host bridge: Intel Corporation Xeon 5600 Series QPI Link 1 (rev 02) [8086:2d95] 3f:02.5 Host bridge: Intel Corporation Xeon 5600 Series QPI Physical 1 (rev 02) IOMMU group 24: [8086:2d98] 3f:03.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Registers (rev 02) [8086:2d99] 3f:03.1 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Target Address Decoder (rev 02) [8086:2d9a] 3f:03.2 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller RAS Registers (rev 02) [8086:2d9c] 3f:03.4 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Test Registers (rev 02) IOMMU group 25: [8086:2da0] 3f:04.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Control (rev 02) [8086:2da1] 3f:04.1 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Address (rev 02) [8086:2da2] 3f:04.2 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Rank (rev 02) [8086:2da3] 3f:04.3 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Thermal Control (rev 02) IOMMU group 26: [8086:2da8] 3f:05.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Control (rev 02) [8086:2da9] 3f:05.1 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Address (rev 02) [8086:2daa] 3f:05.2 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Rank (rev 02) [8086:2dab] 3f:05.3 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Thermal Control (rev 02) IOMMU group 27: [8086:2db0] 3f:06.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Control (rev 02) [8086:2db1] 3f:06.1 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Address (rev 02) [8086:2db2] 3f:06.2 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Rank (rev 02) [8086:2db3] 3f:06.3 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Thermal Control (rev 02) CPU Thread Pairings Pair 1: cpu 0 / cpu 8 Pair 2: cpu 1 / cpu 9 Pair 3: cpu 2 / cpu 10 Pair 4: cpu 3 / cpu 11 Pair 5: cpu 4 / cpu 12 Pair 6: cpu 5 / cpu 13 Pair 7: cpu 6 / cpu 14 Pair 8: cpu 7 / cpu 15 USB Devices Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 05dc:a81d Lexar Media, Inc. LJDTT16G [JumpDrive 16GB] Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub SCSI Devices [0:0:0:0] disk Lexar USB Flash Drive 1100 /dev/sda 16.0GB [1:0:0:0] disk ATA Samsung SSD 850 2B6Q /dev/sdb 250GB [2:0:0:0] disk ATA WDC WD1003FBYZ-0 1V03 /dev/sdc 1.00TB [3:0:0:0] disk ATA ST3000DM001-1ER1 CC25 /dev/sdd 3.00TB [4:0:0:0] disk ATA WDC WD10EARS-00M AB51 /dev/sde 1.00TB [5:0:0:0] disk ATA WDC WD1003FZEX-0 1A01 /dev/sdf 1.00TB Diags Attached kg-diagnostics-20200317-2359.zip
  6. I have a Poweredge Blade Server and want to make it my VM and Docker Unraid Machine, currently windows server 2012 with hyper-V (my other machine is in my signature) - The machine in my signature is going to be PLEX and storage machine. I don't really need storage in the new machine. I read that a SSD array is not "recommended" or "supported" - has anybody had an experience with that or tested? I was thinking of keeping 2x of the 512gb 10k drives for data array with parity, and 2-3 SSD drives for a cache pool for VM storage and Docker Storage. I would do 4-5 SSD's if it was OK to do that, but like I have read its not supported. I just want to have SSD speed for the entire system, I will use CA/Backup for Data retention of the dockers. Just looking for anybody who has a similar system and what they did and or give me some insight. Thanks!
  7. For what its worth I have Samsung SSD's working... No Issues
  8. Anybody help with why these temps are so wonky... 262F and why nct6797 is so different from k10temp ?
  9. Updated from 6.8.2 -- Took 3:27 to get the gui back No issues as of yet... My temp sensors are showing up now for my ryzen 3900x I updated my UD plugin before my upgrade and no issues ---------------------------- Anybody know why the temps are so different for the CPU Also if needed i can start a new thread.
  10. @limetech - any rough eta. Also waiting for 5.x kernel for amd 3000 temp monitoring
  11. I know there is a lot on this, and from what I have read this will be fixed in the next iteration of unraid, but im seeing that sensors-detect is picking up the sensors but still no temps, can someone explain why that is? Also how would i make this work? Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): yes Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors for initialization at boot time. You should now start the lm_sensors service to load the required kernel modules. root@eMu-Unraid:~# sensors-detect # sensors-detect version 3.6.0 # System: Micro-Star International Co., Ltd. MS-7C37 [2.0] # Board: Micro-Star International Co., Ltd. MPG X570 GAMING PLUS (MS-7C37) # Kernel: 4.19.98-Unraid x86_64 # Processor: AMD Ryzen 9 3900X 12-Core Processor (23/113/0) This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): yes Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 16h thermal sensors... No AMD Family 17h thermal sensors... Success! (driver `k10temp') AMD Family 15h power sensors... No AMD Family 16h power sensors... No Hygon Family 18h thermal sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... No Some Super I/O chips contain embedded sensors. We have to write to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): yes Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes Found `Nuvoton NCT6797D Super IO Sensors' Success! (address 0xa20, driver `nct6775') Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, we have to read from arbitrary I/O ports to probe for such interfaces. This is normally safe. Do you want to scan for IPMI interfaces? (YES/no): no Some hardware monitoring chips are accessible through the ISA I/O ports. We have to write to arbitrary I/O ports to probe them. This is usually safe though. Yes, you do have ISA I/O ports even if you do not have any ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): yes Probing for `National Semiconductor LM78' at 0x290... No Probing for `National Semiconductor LM79' at 0x290... No Probing for `Winbond W83781D' at 0x290... No Probing for `Winbond W83782D' at 0x290... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): no Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `nct6775': * ISA bus, address 0xa20 Chip `Nuvoton NCT6797D Super IO Sensors' (confidence: 9) Driver `k10temp': * Chip `AMD Family 17h thermal sensors' (confidence: 9) Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): yes Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors for initialization at boot time. You should now start the lm_sensors service to load the required kernel modules.
  12. updated 6.8.0 ----> 6.8.2 Upgrade went fine, server rebooted normally. Will check in later to see how it runs. EDIT: 30hr in no issues