wonderbread24

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

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

Nobody?

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 unraid-diagnostics-20211129-2208.zip

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.

unraid-diagnostics-20210512-2038.zip

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. unraid-diagnostics-20191106-1835.zip

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. unraid-diagnostics-20191008-0442.zip

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.

Grabbing a random core show this: root@Unraid:/sys/devices/system/cpu/cpu21/cpufreq# cat scaling_min_freq 1200000