September 14, 20214 yr I upgraded my parity drive to larger drive while at the same time replacing a failed disk with my old parity drive. It looks the parity has rebuilt correctly, but the system seems to have stalled in rebuilding the failed data drive. Unraid shows the array as started, but the main dashboard and docker show it as stopped. The parity copy action is at 100% completed, but has the warning next to it saying stopped. My cpu is maxing and my log file instantly filled even after increasing it. Attached is my sys log. Edit: Is it safe to just reboot? unraidserver-diagnostics-20210914-1023.zip Edited September 14, 20214 yr by Saint_Prophet
September 14, 20214 yr Author I believe is just died, I logged in and the disk was marked as disabled and I was unable to run a SMART test on it either in unraid or while connect to my PC via and external enclosure. Here is one of logs from attempting to run a smart test. Quote smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.10.28-Unraid] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: ST4000VN000 Serial Number: #REMOVED# LU WWN Device Id: 5 000c50 0655e420c Firmware Version: SC43 User Capacity: 137,438,952,960 bytes [137 GB] Sector Size: 512 bytes logical/physical Rotation Rate: 7200 rpm Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s Local Time is: Fri Sep 3 13:32:37 2021 CDT SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: Disabled, NOT FROZEN [SEC1] Read SCT Status failed: scsi error aborted command Wt Cache Reorder: Unknown (SCT Feature Control command failed) Read SMART Data failed: scsi error aborted command === START OF READ SMART DATA SECTION === SMART Status command failed: scsi error aborted command SMART overall-health self-assessment test result: UNKNOWN! SMART Status, Attributes and Thresholds cannot be read. Read SMART Log Directory failed: scsi error aborted command ATA_READ_LOG_EXT (addr=0x00:0x00, page=0, n=1) failed: scsi error aborted command Read GP Log Directory failed SMART Extended Comprehensive Error Log (GP Log 0x03) not supported Read SMART Error Log failed: scsi error aborted command SMART Extended Self-test Log (GP Log 0x07) not supported Read SMART Self-test Log failed: scsi error aborted command Selective Self-tests/Logging not supported Read SCT Status failed: scsi error aborted command Read SCT Status failed: scsi error aborted command SCT (Get) Error Recovery Control command failed Device Statistics (GP/SMART Log 0x04) not supported Pending Defects log (GP Log 0x0c) not supported ATA_READ_LOG_EXT (addr=0x11:0x00, page=0, n=1) failed: scsi error aborted command Read SATA Phy Event Counters failed
September 14, 20214 yr Your log is spammed but it does not seem to have anything to do with your drives. (unless some stuff about drives is hidden between all the call traces) Sep 14 10:16:10 UnraidServer kernel: WARNING: CPU: 1 PID: 13609 at mm/truncate.c:447 truncate_inode_pages_range+0x39d/0x438 Sep 14 10:16:10 UnraidServer kernel: Modules linked in: md_mod macvlan xt_nat xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle nf_tables veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs i915 iosf_mbi i2c_algo_bit drm_kms_helper drm intel_gtt agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops it87 hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables bonding x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper rapl intel_cstate intel_uncore i2c_i801 i2c_smbus i2c_core ahci wmi video input_leds atl1c led_class e1000e backlight libahci fan thermal button [last unloaded: md_mod] Sep 14 10:16:10 UnraidServer kernel: CPU: 1 PID: 13609 Comm: emhttpd Tainted: G U W 5.10.28-Unraid #1 Sep 14 10:16:10 UnraidServer kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./Z77X-UD5H, BIOS F16k 04/11/2018 Sep 14 10:16:10 UnraidServer kernel: RIP: 0010:truncate_inode_pages_range+0x39d/0x438 Sep 14 10:16:10 UnraidServer kernel: Code: fc 08 4e 8b b4 fc 88 00 00 00 4d 39 ec 77 d8 4c 8d 6b ff eb 34 4c 89 f7 e8 04 f8 ff ff 4c 89 f7 e8 c2 f6 ff ff 4c 39 e8 74 02 <0f> 0b 4c 89 f7 e8 d3 ab ff ff 48 89 ef 4c 89 f6 e8 0b fc ff ff 4c Sep 14 10:16:10 UnraidServer kernel: RSP: 0018:ffffc900004dfca8 EFLAGS: 00010216 Sep 14 10:16:10 UnraidServer kernel: RAX: 00000000cbb7406d RBX: 0000000000000000 RCX: 0000000000000018 Sep 14 10:16:10 UnraidServer kernel: RDX: ffffea001ad7f008 RSI: 0000000040000040 RDI: ffffea0014bd1c80 Sep 14 10:16:10 UnraidServer kernel: RBP: ffff88810486c828 R08: 0000000000000000 R09: 0000000000000000 Sep 14 10:16:10 UnraidServer kernel: R10: ffffc900004dfc30 R11: ffffc900004dfc30 R12: ffffffffffffffff Sep 14 10:16:10 UnraidServer kernel: R13: 000000001d99c85e R14: ffffea0014bd1c80 R15: 0000000000000000 Sep 14 10:16:10 UnraidServer kernel: FS: 000014adae1be700(0000) GS:ffff8887ff280000(0000) knlGS:0000000000000000 Sep 14 10:16:10 UnraidServer kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 14 10:16:10 UnraidServer kernel: CR2: 000014ac65e62050 CR3: 0000000103abc006 CR4: 00000000001706e0 Sep 14 10:16:10 UnraidServer kernel: Call Trace: Sep 14 10:16:10 UnraidServer kernel: ? mce_intel_cmci_poll+0x20/0x3d Sep 14 10:16:10 UnraidServer kernel: __blkdev_put+0x73/0x199 Sep 14 10:16:10 UnraidServer kernel: blkdev_close+0x1d/0x20 Sep 14 10:16:10 UnraidServer kernel: __fput+0xf7/0x1ba Sep 14 10:16:10 UnraidServer kernel: task_work_run+0x70/0x81 Sep 14 10:16:10 UnraidServer kernel: exit_to_user_mode_prepare+0x51/0xc6 Sep 14 10:16:10 UnraidServer kernel: syscall_exit_to_user_mode+0x45/0x53 Sep 14 10:16:10 UnraidServer kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Sep 14 10:16:10 UnraidServer kernel: RIP: 0033:0x14adae9575bb Sep 14 10:16:10 UnraidServer kernel: Code: 0f 05 48 3d 00 f0 ff ff 77 45 c3 0f 1f 40 00 48 83 ec 18 89 7c 24 0c e8 13 fc ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2f 44 89 c7 89 44 24 0c e8 51 fc ff ff 8b 44 Sep 14 10:16:10 UnraidServer kernel: RSP: 002b:000014adae1bdc40 EFLAGS: 00000293 ORIG_RAX: 0000000000000003 Sep 14 10:16:10 UnraidServer kernel: RAX: 0000000000000000 RBX: 0000000000421876 RCX: 000014adae9575bb Sep 14 10:16:10 UnraidServer kernel: RDX: 000014ad9c000e00 RSI: 0000000000000002 RDI: 0000000000000008 Sep 14 10:16:10 UnraidServer kernel: RBP: 000014adae1bdf00 R08: 0000000000000000 R09: 0000000000000001 Sep 14 10:16:10 UnraidServer kernel: R10: 0000000000004000 R11: 0000000000000293 R12: 00007ffd7941586e Sep 14 10:16:10 UnraidServer kernel: R13: 00007ffd7941586f R14: 000014adae1bdfc0 R15: 000014adae1be700 Sep 14 10:16:10 UnraidServer kernel: ---[ end trace 903f783f2067e73e ]--- Looks more like a networking thing.
September 14, 20214 yr Author By network thing, would that be a plugin I might be using, a router setting or a unraid config? Glad to hear it does not look like a disk issue, but it obviously presents a problem. Given the new parity drive seems to be established would it make sense to reboot the box?
September 14, 20214 yr Docker containers that are assigned a unique IP instead of sharing Unraid's IP can cause those kinds of call traces.
September 14, 20214 yr Community Expert You should disable Docker in Settings until you get your array stable again. macvlan call traces has a fix (ipvlan) in 6.10rc1
September 14, 20214 yr Community Expert Sep 12 19:19:29 UnraidServer emhttpd: copy: disk2 to disk0 running Sep 13 20:57:38 UnraidServer emhttpd: copy: disk2 to disk0 completed Immediately after that macvlan call traces began to fill log 16 minutes ago, Saint_Prophet said: new parity drive seems to be established would it make sense to reboot the box? I think you have no choice, but disable Docker as I mentioned before rebooting.
September 14, 20214 yr Author Rebooted, looks like I lost the copy progress. I did disable docker all together this time around. I guess move to 6.10.0-rc1 and retry the parity copy process? Edited September 14, 20214 yr by Saint_Prophet
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.