wonderbread24
-
Posts
25 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by wonderbread24
-
-
I have Unraid on an R720 that's been rock solid for a long time. Then recently (like 3 or 4 months ago) I've have been getting random kernel panics. Most recently was today. Its always random and I can't recreate it. I've been super busy with work the last few months to even try to take a look at it. Thank goodness for remote console via the iDRAC.
I've been getting sense key logs on my cache drive since I put it in. I thought that maybe it was causing the issue but I don't think it is. I have asked about it before but never got an answer for it and google turns up nothing useful.
Let me know if anything else is needed. I will attach a diag and syslog.
unraid-diagnostics-20220331-2046.zip syslog-192.168.1.38.log
-
-
I've tried to find answers to what this is but I can't find anything on it.
I have an R720xd with almost all SAS drives including my cache drive. I'm not sure its an actual error but I'd like to know what it is.
Nov 29 17:06:13 Unraid kernel: sd 1:0:8:0: [sdj] tag#1375 Sense Key : 0x1 [current]
Nov 29 17:06:13 Unraid kernel: sd 1:0:8:0: [sdj] tag#1375 ASC=0x1c ASCQ=0x2
Nov 29 17:36:35 Unraid kernel: sd 1:0:8:0: [sdj] tag#1427 Sense Key : 0x1 [current]
Nov 29 17:36:35 Unraid kernel: sd 1:0:8:0: [sdj] tag#1427 ASC=0x1c ASCQ=0x2
Nov 29 18:06:57 Unraid kernel: sd 1:0:8:0: [sdj] tag#1447 Sense Key : 0x1 [current]
Nov 29 18:06:57 Unraid kernel: sd 1:0:8:0: [sdj] tag#1447 ASC=0x1c ASCQ=0x2
Nov 29 18:37:19 Unraid kernel: sd 1:0:8:0: [sdj] tag#1524 Sense Key : 0x1 [current]
Nov 29 18:37:19 Unraid kernel: sd 1:0:8:0: [sdj] tag#1524 ASC=0x1c ASCQ=0x2
Nov 29 19:07:42 Unraid kernel: sd 1:0:8:0: [sdj] tag#1414 Sense Key : 0x1 [current]
Nov 29 19:07:42 Unraid kernel: sd 1:0:8:0: [sdj] tag#1414 ASC=0x1c ASCQ=0x2
Nov 29 19:38:04 Unraid kernel: sd 1:0:8:0: [sdj] tag#1475 Sense Key : 0x1 [current]
Nov 29 19:38:04 Unraid kernel: sd 1:0:8:0: [sdj] tag#1475 ASC=0x1c ASCQ=0x2
Nov 29 20:08:26 Unraid kernel: sd 1:0:8:0: [sdj] tag#1486 Sense Key : 0x1 [current]
Nov 29 20:08:26 Unraid kernel: sd 1:0:8:0: [sdj] tag#1486 ASC=0x1c ASCQ=0x2
Nov 29 20:38:48 Unraid kernel: sd 1:0:8:0: [sdj] tag#1514 Sense Key : 0x1 [current]
Nov 29 20:38:48 Unraid kernel: sd 1:0:8:0: [sdj] tag#1514 ASC=0x1c ASCQ=0x2
-
Thanks @JorgeB
I figured out what it was.
There is a bug with 6.9.2 where it ignores the shutdown time-out in disk settings during a graceful shutdown. This was causing the parity check when powered back on. Simply updating the time-out fixes the bug from what I've read.
The errors, like you said, were coming from the docker.img. Turns out it was not located on my cache drive like I thought. It somehow ended up on disk4 in the array. Since Unraid was failing to shutdown properly it was causing the docker.img to become corrupt after each shutdown.
I've changed my cache drive just in case, relocated the docker.img location to the cache drive and increased the shutdown time-out to make sure everything powers down properly.
When I manually run the script to power down everything comes back happy. We'll see if does so automatically later today.
-
Quote
May 12 20:36:42 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 12862088 off 0 csum 0x8941f998 expected csum 0x0aa50e9a mirror 1
May 12 20:36:42 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 99, gen 0
May 12 20:36:42 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 19091 off 0 csum 0x8941f998 expected csum 0xeba93014 mirror 1
May 12 20:36:42 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 100, gen 0
May 12 20:36:45 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 12862088 off 0 csum 0x8941f998 expected csum 0x0aa50e9a mirror 1
May 12 20:36:45 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 101, gen 0
May 12 20:36:45 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 19091 off 0 csum 0x8941f998 expected csum 0xeba93014 mirror 1
May 12 20:36:45 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 102, gen 0
May 12 20:36:49 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 272 off 20480 csum 0x8941f998 expected csum 0x3b588bdd mirror 1
May 12 20:36:49 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 103, gen 0
May 12 20:36:49 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 272 off 20480 csum 0x8941f998 expected csum 0x3b588bdd mirror 1
May 12 20:36:49 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 104, gen 0
May 12 20:37:00 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 272 off 20480 csum 0x8941f998 expected csum 0x3b588bdd mirror 1
May 12 20:37:00 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 105, gen 0
May 12 20:37:00 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 272 off 20480 csum 0x8941f998 expected csum 0x3b588bdd mirror 1
May 12 20:37:00 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 106, gen 0
May 12 20:37:10 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 272 off 20480 csum 0x8941f998 expected csum 0x3b588bdd mirror 1
May 12 20:37:10 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 107, gen 0
May 12 20:37:10 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 272 off 20480 csum 0x8941f998 expected csum 0x3b588bdd mirror 1
May 12 20:37:10 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 108, gen 0 -
I've tried it with the command specifying the partition. Nothing changed. I still wasn't able to mount the drive.
I looked in the logs again and I saw a new error saying there was a duplicate UUID for /dev/sdo.
I rebooted the array and everything is fine again. Not sure what happened. -
Running it on the drive I was trying to mount:
root@Unraid:~# xfs_repair -v /dev/sdo Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing...Now it appears to be scanning the rest of the drive.
-
Nov 6 10:29:02 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0xffc940 len 32 error 5 Nov 6 10:29:02 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:02 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0xffc940 len 32 error 5 Nov 6 10:29:02 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:02 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0xffc940 len 32 error 5 Nov 6 10:29:02 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:02 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0xffc940 len 32 error 5 Nov 6 10:29:02 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:02 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0xffdb40 len 32 error 5 Nov 6 10:29:02 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:02 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0xffdb40 len 32 error 5 Nov 6 10:29:02 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:02 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x127b9b00 len 32 error 5 Nov 6 10:29:02 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:02 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x127b9b00 len 32 error 5 Nov 6 10:29:02 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:02 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x6dfb580 len 32 error 5 Nov 6 10:29:02 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:02 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x6dfb580 len 32 error 5 Nov 6 10:29:02 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:02 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x127b9b00 len 32 error 5 Nov 6 10:29:02 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:02 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x127b9b00 len 32 error 5 Nov 6 10:29:02 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:02 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x6dfc360 len 32 error 5 Nov 6 10:29:02 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:02 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x6dfc360 len 32 error 5 Nov 6 10:29:02 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:02 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0xffdb60 len 32 error 5 Nov 6 10:29:02 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:02 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0xffdb60 len 32 error 5 Nov 6 10:29:02 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:02 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x1058ae0 len 32 error 5 Nov 6 10:29:02 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:02 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x1058ae0 len 32 error 5 Nov 6 10:29:02 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:02 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x5d27ce0 len 32 error 5 Nov 6 10:29:02 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:02 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x5d27ce0 len 32 error 5 Nov 6 10:29:02 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:02 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x1182dca0 len 32 error 5 Nov 6 10:29:02 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:02 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x1182dca0 len 32 error 5 Nov 6 10:29:02 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:13 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x5d27ce0 len 32 error 5 Nov 6 10:29:13 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:13 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x5d27ce0 len 32 error 5 Nov 6 10:29:13 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:13 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0xba7e240 len 32 error 5 Nov 6 10:29:13 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Nov 6 10:29:13 Unraid kernel: XFS (sde1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0xba7e240 len 32 error 5 Nov 6 10:29:13 Unraid kernel: XFS (sde1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5.I'm not sure what this error is. I've attached diags. The only thing I see is that I can't mount a drive via unassigned devices.
-
I found that setting the WCE flag was not persistent after a reboot. I had to set the -S flag as well.
-
Thats what I thought I needed to do, but I wanted to confirm so I didn't kill my server.
Its all up and running.
Thanks!
-
I have an Dell PowerEdge R720xd.
I've been running on an H310 Mini Mono in Non-RAID mode. I just picked up one of the H310 Mini Mono's in IT mode from ArtOfServer.
After plugging in the new controller, I checked in the RAID BIOS to make sure all my disks were seen. They were so I proceeded to boot into Unraid.
It failed to start. I have 2 "missing disks" as well as the Cache missing.
I can add the cache drive back and its happy, but when I add the other two missing disks it says they're wrong even though their SN's match the missing disk info. It looks like a GUID or some kind of ID number is missing.
Not sure what to do. I do notice that the drive letters ie. sdb, sdc, etc are different than with the other controller.
Do I need to put the old controller back in, identify which disk is associated with its letter or path? Then put the new controller back in and do a new config on the array and redo parity?
Edit: Added diags with IT Mode H310 mini installed.
-
That was one thing I looked at.
As a test I fired up 6 transcodes and set the fans to 44%. Not a hiccup on the transcodes and temps hit 75c in a room that was 78f. I'll never run 6 transcodes may 3 or 4 at the most so my temps will be fine.
-
I figured it out! Under the IDRAC for the server, there was a power cap policy set to limit the power usage to 210w. Any load that hit the server would make the server throttle because it hit that load. I changed it to 400w and the CPUs are boosting now.
QuoteNote that closing this window will abort the execution of this script CPU 1: 2.93 GHz CPU 2: 2.36 GHz CPU 3: 2.59 GHz CPU 4: 2.54 GHz CPU 5: 2.91 GHz CPU 6: 2.06 GHz CPU 7: 2.93 GHz CPU 8: 1.94 GHz CPU 9: 2.92 GHz CPU 10: 1.73 GHz CPU 11: 2.86 GHz CPU 12: 2.57 GHz CPU 13: 2.84 GHz CPU 14: 2.73 GHz CPU 15: 2.86 GHz CPU 16: 2.40 GHz CPU 17: 2.82 GHz CPU 18: 2.60 GHz CPU 19: 2.82 GHz CPU 20: 2.17 GHz CPU 21: 2.81 GHz CPU 22: 2.15 GHz CPU 23: 2.94 GHz CPU 24: 2.65 GHz CPU 25: 2.74 GHz CPU 26: 1.51 GHz CPU 27: 2.78 GHz CPU 28: 2.14 GHz CPU 29: 2.81 GHz CPU 30: 2.18 GHz CPU 31: 2.77 GHz CPU 32: 1.62 GHz-
1
-
-
Grabbing a random core show this:
root@Unraid:/sys/devices/system/cpu/cpu21/cpufreq# cat scaling_min_freq 1200000 -
CPU 1: .95 GHz CPU 2: 2.09 GHz CPU 3: 1.28 GHz CPU 4: 2.19 GHz CPU 5: 1.36 GHz CPU 6: 2.16 GHz CPU 7: 1.15 GHz CPU 8: 2.13 GHz CPU 9: 1.67 GHz CPU 10: 1.84 GHz CPU 11: 1.31 GHz CPU 12: 1.83 GHz CPU 13: 1.30 GHz CPU 14: 2.18 GHz CPU 15: 1.45 GHz CPU 16: 2.19 GHz CPU 17: 1.68 GHz CPU 18: 2.01 GHz CPU 19: 1.71 GHz CPU 20: 1.91 GHz CPU 21: 1.12 GHz CPU 22: 2.07 GHz CPU 23: .96 GHz CPU 24: 2.07 GHz CPU 25: .87 GHz CPU 26: 2.10 GHz CPU 27: 1.14 GHz CPU 28: 1.97 GHz CPU 29: 1.54 GHz CPU 30: 2.08 GHz CPU 31: 1.42 GHz CPU 32: 2.00 GHzThats at Idle. Below is with 2 Transcodes.
Note that closing this window will abort the execution of this script CPU 1: 1.33 GHz CPU 2: 1.57 GHz CPU 3: 1.86 GHz CPU 4: 1.92 GHz CPU 5: .77 GHz CPU 6: .98 GHz CPU 7: 1.96 GHz CPU 8: 1.48 GHz CPU 9: 1.87 GHz CPU 10: .72 GHz CPU 11: 2.05 GHz CPU 12: .66 GHz CPU 13: 1.70 GHz CPU 14: .62 GHz CPU 15: 1.85 GHz CPU 16: 1.44 GHz CPU 17: 1.54 GHz CPU 18: .59 GHz CPU 19: .81 GHz CPU 20: .67 GHz CPU 21: 1.69 GHz CPU 22: 1.05 GHz CPU 23: 1.49 GHz CPU 24: .96 GHz CPU 25: 1.76 GHz CPU 26: 1.17 GHz CPU 27: 1.88 GHz CPU 28: 1.24 GHz CPU 29: 2.06 GHz CPU 30: 1.49 GHz CPU 31: 2.01 GHz CPU 32: .77 GHz -
I'm guessing I need to add this to User scripts?
This is the output I get:
Script location: /tmp/user.scripts/tmpScripts/CPU Freq/script Note that closing this window will abort the execution of this script /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 1: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 2: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 3: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 4: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 5: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 6: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 7: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 8: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 9: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 10: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 11: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 12: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 13: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 14: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 15: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 16: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 17: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 18: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 19: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 20: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: echo: write error: Broken pipe CPU 21: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 22: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 23: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 24: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 25: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 26: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 27: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 28: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 29: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 30: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 31: GHz /tmp/user.scripts/tmpScripts/CPU Freq/script: line 9: bc: command not found CPU 32: GHz -
When the server is under load (2 transcodes for this example) CPU Speeds drop to under 200MHz and stay there. Once I stop the transcodes the CPU speeds go back up. It doesn't make any sense to me.
-
Temps are 53-58c. I have the fans set slow for noise control.
-
I built a new server a few months back thinking it was going to handle everything I needed as my storage/media server.
My results have been mediocre to frustrating with it. I've exhuasted my knowledge and I cant seem to figure out where my issue is.
I am running an R720xd LFF
2x E5-2660
128GB ECC (8x16GB)
PERC H310 Mini (Non-RAID mode)
Mix of 2TB & 3TB Drives (25TB)Samsung 850 Evo 250GB SSD cache drive.
Overall This thing is great, it just seems way slower than I feel it should be. Switching between tabs takes a while. Trying to update dockers can take up to 20 minutes sometimes for it to finish. Loading the plugins page takes 2-3 minutes every time I try to access it.
Writing and reading data from the array seems to be unaffected. I can copy to and from at full Gigabit speeds.
When it comes to Plex, I see my biggest issues. I can't even transcode one movie. I get errors on my Roku TV saying the server is not powerful enough. I can direct play all day, but I'm a subtitles fan so transcoding is a must. I've moved transcode to /tmp. I've even tried installing plex on an SAS SSD mounted through unassigned drives to see if it made a difference with no success.
CPU speeds seem like it could be the issue. "Tips and Tweaks" shows the intel Pstate driver is installed and set to Performace with Enable Intel Turbo set to yes and BIOS is set to Performance mode OS Controlled. But when I try to transcode more than 2 movies at a time my CPU Core speeds drop from 1.2GHz to 180Mhz. I almost never see it sit at it base clock speed of 2.2GHz and its never hit 3Ghz boost. I'm starting to get frustrated because I know these CPUs should be able to handle about 4 1080p transcodes per CPU and I can only get one 720p transcode that will still sometimes fail.
Not sure where to go from here. I've asked on the Plex forums but got no help there. Reddit has helped me find the CPU frequency issue but I'm still lost.
-
Title says it all. Not sure what the issue is. I used to be able to get max speeds to the 850EVO cache drive.
-
Whats the downside to not flashing to IT mode? I've searched and found a guide for the H310 mini but its a little above my pay grade and I don't have the budget to replace the card if I screw up.
At this point I don't see any issue, since I can see smart data...
-
As far as I know then Perc H310 mini can't be flashed to IT mode.
-
Is that the only disk with this issue or are there other disks? Where in the logs did you find this?
-
I have an R720xd
2 E5-2643
128GB RAM
Perc H310 Mini in Non-RAID mode
9 2TB SATA (some SATA2 some SATA3)
1 3TB SATA
1 3TB SAS
1 250GB 950 EVO SATA
1 200GB SAS SSD
I replaced one of the 2TB drives with a 3TB SAS disk. Once I started the rebuild it said it was going to take nearly 3 days with a rebuild speed of 14.2MB/s. I'm about 75% through but I'm curious why its taking so long? Nothing seems to be wong with the server. I've shut down all my dockers but there was no change.
Unable to determine what is causing Kernel Panics
in General Support
Posted
I've updated and set to IPVLAN, lets see if I can more than a week without a crash.
What is the difference between MACVLAN and IPVLAN?
Anyone have an idea about the sense key logs I'm getting in my syslog? Is that just the PERC H310 mono (IT mode) not happy with the HP drive (cache drive)?
Mar 31 21:53:38 Unraid kernel: sd 1:0:8:0: [sdj] tag#2399 Sense Key : 0x1 [current] Mar 31 21:53:38 Unraid kernel: sd 1:0:8:0: [sdj] tag#2399 ASC=0x1c ASCQ=0x2