tf0083

It seems to be stiil at this interface all the time. I have a account but not payment.

Unraid is installed under Esxi. When Unraid is restarted, the Host will automatically restart,and there is a certain probability that the host will be restarted when Unraid is turned on

我发现Unraid只要进行重启操作就会直接造成宿主机重新引导，网上查了下好像和cpu核心数设置有关，但好像还是不能彻底解决这个问题，不知道有什么解决方法啊

tower-diagnostics-20210413-0733.zip

This is diagnostic information，my sever Model is HP ML350P，Thanks for help!

I don‘t know why，Please help！ Disk logo Apr 8 13:30:06 Tower kernel: sd 33:0:22:0: [sdt] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) Apr 8 13:30:06 Tower kernel: sd 33:0:22:0: [sdt] Write Protect is off Apr 8 13:30:06 Tower kernel: sd 33:0:22:0: [sdt] Mode Sense: 46 00 10 08 Apr 8 13:30:06 Tower kernel: sd 33:0:22:0: [sdt] Write cache: enabled, read cache: enabled, supports DPO and FUA Apr 8 13:30:14 Tower kernel: sdt: sdt1 Apr 8 13:30:14 Tower kernel: sd 33:0:22:0: [sdt] Attached SCSI disk Apr 8 15:53:55 Tower unassigned.devices: Adding disk '/dev/sdt1'... Apr 8 15:53:55 Tower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdt1' '/mnt/disks/ATA_ST4000NM0033-9ZM' Apr 8 15:53:55 Tower kernel: XFS (sdt1): Filesystem has duplicate UUID 2dfd2d09-0a4c-4bda-9442-304e8eeba1a1 - can't mount Apr 8 15:53:55 Tower unassigned.devices: Mount of '/dev/sdt1' failed. Error message: mount: /mnt/disks/ATA_ST4000NM0033-9ZM: wrong fs type, bad option, bad superblock on /dev/sdt1, missing codepage or helper program, or other error. Apr 8 15:56:00 Tower emhttpd: ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 (sdt) 512 7814037168 Apr 8 15:56:01 Tower kernel: mdcmd (5): import 4 sdt 64 3907018532 0 ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 Apr 8 15:56:01 Tower kernel: md: import disk4: (sdt) ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 size: 3907018532 Apr 8 15:56:01 Tower emhttpd: read SMART /dev/sdt Apr 8 15:57:22 Tower emhttpd: ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 (sdt) 512 7814037168 Apr 8 15:57:22 Tower kernel: mdcmd (5): import 4 sdt 64 3907018532 0 ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 Apr 8 15:57:22 Tower kernel: md: import disk4: (sdt) ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 size: 3907018532 Apr 8 15:57:22 Tower emhttpd: read SMART /dev/sdt Apr 8 15:57:29 Tower emhttpd: ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 (sdt) 512 7814037168 Apr 8 15:57:30 Tower kernel: mdcmd (5): import 4 sdt 64 3907018532 0 ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 Apr 8 15:57:30 Tower kernel: md: import disk4: (sdt) ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 size: 3907018532 Apr 8 15:57:30 Tower emhttpd: read SMART /dev/sdt Apr 8 15:58:07 Tower emhttpd: ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 (sdt) 512 7814037168 Apr 8 15:58:07 Tower kernel: mdcmd (5): import 4 sdt 64 3907018532 0 ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 Apr 8 15:58:07 Tower kernel: md: import disk4: (sdt) ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 size: 3907018532 Apr 8 15:58:07 Tower emhttpd: read SMART /dev/sdt Apr 8 16:01:40 Tower emhttpd: read SMART /dev/sdt Apr 8 16:02:29 Tower emhttpd: ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 (sdt) 512 7814037168 Apr 8 16:02:29 Tower kernel: mdcmd (5): import 4 sdt 64 3907018532 0 ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 Apr 8 16:02:29 Tower kernel: md: import disk4: (sdt) ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 size: 3907018532 Apr 8 16:02:29 Tower emhttpd: read SMART /dev/sdt Apr 8 16:02:49 Tower emhttpd: ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 (sdt) 512 7814037168 Apr 8 16:02:49 Tower kernel: mdcmd (5): import 4 sdt 64 3907018532 0 ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 Apr 8 16:02:49 Tower kernel: md: import disk4: (sdt) ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 size: 3907018532 Apr 8 16:02:49 Tower emhttpd: read SMART /dev/sdt Apr 8 16:02:54 Tower emhttpd: ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 (sdt) 512 7814037168 Apr 8 16:02:54 Tower kernel: mdcmd (5): import 4 sdt 64 3907018532 0 ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 Apr 8 16:02:54 Tower kernel: md: import disk4: (sdt) ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 size: 3907018532 Apr 8 16:02:54 Tower emhttpd: read SMART /dev/sdt Apr 8 16:03:33 Tower emhttpd: ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 (sdt) 512 7814037168 Apr 8 16:03:33 Tower kernel: mdcmd (5): import 4 sdt 64 3907018532 0 ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 Apr 8 16:03:33 Tower kernel: md: import disk4: (sdt) ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 size: 3907018532 Apr 8 16:03:34 Tower emhttpd: read SMART /dev/sdt Apr 8 16:03:54 Tower emhttpd: ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 (sdt) 512 7814037168 Apr 8 16:03:54 Tower kernel: mdcmd (5): import 4 sdt 64 3907018532 0 ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 Apr 8 16:03:54 Tower kernel: md: import disk4: (sdt) ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 size: 3907018532 Apr 8 16:03:54 Tower emhttpd: read SMART /dev/sdt Apr 8 16:04:01 Tower emhttpd: ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 (sdt) 512 7814037168 Apr 8 16:04:02 Tower kernel: mdcmd (5): import 4 sdt 64 3907018532 0 ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 Apr 8 16:04:02 Tower kernel: md: import disk4: (sdt) ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 size: 3907018532 Apr 8 16:04:02 Tower emhttpd: read SMART /dev/sdt Apr 8 16:04:06 Tower emhttpd: ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 (sdt) 512 7814037168 Apr 8 16:04:06 Tower kernel: mdcmd (5): import 4 sdt 64 3907018532 0 ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 Apr 8 16:04:06 Tower kernel: md: import disk4: (sdt) ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 size: 3907018532 Apr 8 16:04:06 Tower emhttpd: read SMART /dev/sdt Apr 8 16:30:58 Tower emhttpd: spinning down /dev/sdt Apr 8 20:57:41 Tower emhttpd: spinning up /dev/sdt Apr 8 20:57:53 Tower emhttpd: read SMART /dev/sdt Apr 8 20:58:17 Tower emhttpd: ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 (sdt) 512 7814037168 Apr 8 20:58:17 Tower kernel: mdcmd (5): import 4 sdt 64 3907018532 0 ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 Apr 8 20:58:17 Tower kernel: md: import disk4: (sdt) ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 size: 3907018532 Apr 8 20:58:18 Tower emhttpd: read SMART /dev/sdt Apr 8 21:00:08 Tower emhttpd: ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 (sdt) 512 7814037168 Apr 8 21:00:08 Tower kernel: mdcmd (5): import 4 sdt 64 3907018532 0 ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 Apr 8 21:00:08 Tower kernel: md: import disk4: (sdt) ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 size: 3907018532 Apr 8 21:00:09 Tower emhttpd: read SMART /dev/sdt Apr 8 21:00:12 Tower emhttpd: ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 (sdt) 512 7814037168 Apr 8 21:00:12 Tower kernel: mdcmd (5): import 4 sdt 64 3907018532 0 ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 Apr 8 21:00:12 Tower kernel: md: import disk4: (sdt) ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 size: 3907018532 Apr 8 21:00:12 Tower emhttpd: read SMART /dev/sdt Apr 8 21:07:38 Tower emhttpd: ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 (sdt) 512 7814037168 Apr 8 21:07:38 Tower kernel: mdcmd (5): import 4 sdt 64 3907018532 0 ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 Apr 8 21:07:38 Tower kernel: md: import disk4: (sdt) ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 size: 3907018532 Apr 8 21:07:38 Tower emhttpd: read SMART /dev/sdt Apr 8 21:08:06 Tower emhttpd: ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 (sdt) 512 7814037168 Apr 8 21:08:06 Tower kernel: mdcmd (5): import 4 sdt 64 3907018532 0 ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 Apr 8 21:08:06 Tower kernel: md: import disk4: (sdt) ST4000NM0033-9ZM_S1Z2Q0J2_35000c5008cf05814 size: 3907018532 Apr 8 21:08:06 Tower emhttpd: read SMART /dev/sdt Apr 8 21:36:09 Tower emhttpd: spinning down /dev/sdt Apr 8 21:38:54 Tower emhttpd: read SMART /dev/sdt Apr 8 21:55:17 Tower emhttpd: spinning down /dev/sdt Apr 8 22:01:30 Tower kernel: sd 33:0:22:0: [sdt] Synchronizing SCSI cache Apr 8 22:01:30 Tower kernel: sd 33:0:22:0: [sdt] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Apr 8 22:02:16 Tower emhttpd: read SMART /dev/sdt Apr 8 22:17:17 Tower emhttpd: spinning down /dev/sdt Apr 8 22:32:18 Tower emhttpd: spinning down /dev/sdt Apr 8 22:47:19 Tower emhttpd: spinning down /dev/sdt Apr 8 23:02:20 Tower emhttpd: spinning down /dev/sdt Apr 8 23:17:21 Tower emhttpd: spinning down /dev/sdt Apr 8 23:32:22 Tower emhttpd: spinning down /dev/sdt Apr 8 23:47:23 Tower emhttpd: spinning down /dev/sdt Apr 9 00:02:24 Tower emhttpd: spinning down /dev/sdt Apr 9 00:17:26 Tower emhttpd: spinning down /dev/sdt Apr 9 00:32:27 Tower emhttpd: spinning down /dev/sdt Apr 9 00:47:28 Tower emhttpd: spinning down /dev/sdt Apr 9 01:02:29 Tower emhttpd: spinning down /dev/sdt Apr 9 01:17:30 Tower emhttpd: spinning down /dev/sdt Apr 9 01:32:31 Tower emhttpd: spinning down /dev/sdt Apr 9 01:47:32 Tower emhttpd: spinning down /dev/sdt DONE

刚买的专业版，所有硬盘都已经配知道阵列，但最近老是在未分配列表中发现其中的个别磁盘，然后点右边的mount挂载也无反应，以下是该磁盘的日志，有一行是报错信息，不知道有没有人碰到过此类问题 Apr 8 12:53:38 Tower emhttpd: read SMART /dev/sdf Apr 8 13:09:39 Tower emhttpd: spinning down /dev/sdf Apr 8 15:55:12 Tower emhttpd: spinning up /dev/sdf Apr 8 15:55:24 Tower emhttpd: read SMART /dev/sdf Apr 8 15:56:00 Tower emhttpd: ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 (sdf) 512 7814037168 Apr 8 15:56:01 Tower kernel: mdcmd (7): import 6 sdf 64 3907018532 0 ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 Apr 8 15:56:01 Tower kernel: md: import disk6: (sdf) ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 size: 3907018532 Apr 8 15:56:01 Tower emhttpd: read SMART /dev/sdf Apr 8 15:57:22 Tower emhttpd: ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 (sdf) 512 7814037168 Apr 8 15:57:22 Tower kernel: mdcmd (7): import 6 sdf 64 3907018532 0 ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 Apr 8 15:57:22 Tower kernel: md: import disk6: (sdf) ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 size: 3907018532 Apr 8 15:57:22 Tower emhttpd: read SMART /dev/sdf Apr 8 15:57:29 Tower emhttpd: ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 (sdf) 512 7814037168 Apr 8 15:57:30 Tower kernel: mdcmd (7): import 6 sdf 64 3907018532 0 ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 Apr 8 15:57:30 Tower kernel: md: import disk6: (sdf) ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 size: 3907018532 Apr 8 15:57:30 Tower emhttpd: read SMART /dev/sdf Apr 8 15:58:07 Tower emhttpd: ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 (sdf) 512 7814037168 Apr 8 15:58:07 Tower kernel: mdcmd (7): import 6 sdf 64 3907018532 0 ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 Apr 8 15:58:07 Tower kernel: md: import disk6: (sdf) ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 size: 3907018532 Apr 8 15:58:07 Tower emhttpd: read SMART /dev/sdf Apr 8 16:01:40 Tower emhttpd: read SMART /dev/sdf Apr 8 16:02:29 Tower emhttpd: ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 (sdf) 512 7814037168 Apr 8 16:02:29 Tower kernel: mdcmd (7): import 6 sdf 64 3907018532 0 ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 Apr 8 16:02:29 Tower kernel: md: import disk6: (sdf) ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 size: 3907018532 Apr 8 16:02:29 Tower emhttpd: read SMART /dev/sdf Apr 8 16:02:49 Tower emhttpd: ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 (sdf) 512 7814037168 Apr 8 16:02:49 Tower kernel: mdcmd (7): import 6 sdf 64 3907018532 0 ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 Apr 8 16:02:49 Tower kernel: md: import disk6: (sdf) ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 size: 3907018532 Apr 8 16:02:49 Tower emhttpd: read SMART /dev/sdf Apr 8 16:02:54 Tower emhttpd: ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 (sdf) 512 7814037168 Apr 8 16:02:54 Tower kernel: mdcmd (7): import 6 sdf 64 3907018532 0 ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 Apr 8 16:02:54 Tower kernel: md: import disk6: (sdf) ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 size: 3907018532 Apr 8 16:02:54 Tower emhttpd: read SMART /dev/sdf Apr 8 16:03:33 Tower emhttpd: ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 (sdf) 512 7814037168 Apr 8 16:03:33 Tower kernel: mdcmd (7): import 6 sdf 64 3907018532 0 ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 Apr 8 16:03:33 Tower kernel: md: import disk6: (sdf) ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 size: 3907018532 Apr 8 16:03:34 Tower emhttpd: read SMART /dev/sdf Apr 8 16:03:54 Tower emhttpd: ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 (sdf) 512 7814037168 Apr 8 16:03:54 Tower kernel: mdcmd (7): import 6 sdf 64 3907018532 0 ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 Apr 8 16:03:54 Tower kernel: md: import disk6: (sdf) ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 size: 3907018532 Apr 8 16:03:54 Tower emhttpd: read SMART /dev/sdf Apr 8 16:04:02 Tower emhttpd: ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 (sdf) 512 7814037168 Apr 8 16:04:02 Tower kernel: mdcmd (7): import 6 sdf 64 3907018532 0 ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 Apr 8 16:04:02 Tower kernel: md: import disk6: (sdf) ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 size: 3907018532 Apr 8 16:04:02 Tower emhttpd: read SMART /dev/sdf Apr 8 16:04:06 Tower emhttpd: ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 (sdf) 512 7814037168 Apr 8 16:04:06 Tower kernel: mdcmd (7): import 6 sdf 64 3907018532 0 ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 Apr 8 16:04:06 Tower kernel: md: import disk6: (sdf) ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 size: 3907018532 Apr 8 16:04:06 Tower emhttpd: read SMART /dev/sdf Apr 8 16:30:58 Tower emhttpd: spinning down /dev/sdf Apr 8 17:30:30 Tower kernel: sd 33:0:5:0: [sdf] Synchronizing SCSI cache Apr 8 17:30:30 Tower kernel: sd 33:0:5:0: [sdf] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Apr 8 17:31:19 Tower emhttpd: read SMART /dev/sdf Apr 8 17:46:20 Tower emhttpd: spinning down /dev/sdf Apr 8 18:01:21 Tower emhttpd: spinning down /dev/sdf Apr 8 18:16:22 Tower emhttpd: spinning down /dev/sdf Apr 8 18:31:23 Tower emhttpd: spinning down /dev/sdf Apr 8 18:46:24 Tower emhttpd: spinning down /dev/sdf Apr 8 19:01:25 Tower emhttpd: spinning down /dev/sdf Apr 8 19:16:26 Tower emhttpd: spinning down /dev/sdf Apr 8 19:31:27 Tower emhttpd: spinning down /dev/sdf Apr 8 19:46:28 Tower emhttpd: spinning down /dev/sdf Apr 8 20:01:29 Tower emhttpd: spinning down /dev/sdf Apr 8 20:16:30 Tower emhttpd: spinning down /dev/sdf Apr 8 20:31:31 Tower emhttpd: spinning down /dev/sdf Apr 8 20:46:32 Tower emhttpd: spinning down /dev/sdf Apr 8 20:57:53 Tower emhttpd: read SMART /dev/sdf Apr 8 21:07:37 Tower kernel: sd 33:0:25:0: [sdf] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) Apr 8 21:07:37 Tower kernel: sd 33:0:25:0: [sdf] Write Protect is off Apr 8 21:07:37 Tower kernel: sd 33:0:25:0: [sdf] Mode Sense: 46 00 10 08 Apr 8 21:07:37 Tower kernel: sd 33:0:25:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA Apr 8 21:07:37 Tower kernel: sdf: sdf1 Apr 8 21:07:37 Tower kernel: sd 33:0:25:0: [sdf] Attached SCSI disk Apr 8 21:07:38 Tower emhttpd: ST4000NM0033-9ZM_S1Z2Q06D_35000c5008cf0558a (sdf) 512 7814037168 Apr 8 21:07:38 Tower emhttpd: import 30 cache device: (sdf) ST4000NM0033-9ZM_S1Z2Q06D_35000c5008cf0558a Apr 8 21:07:38 Tower emhttpd: read SMART /dev/sdf Apr 8 21:08:06 Tower emhttpd: ST4000NM0033-9ZM_S1Z2Q06D_35000c5008cf0558a (sdf) 512 7814037168 Apr 8 21:08:06 Tower emhttpd: import 30 cache device: (sdf) ST4000NM0033-9ZM_S1Z2Q06D_35000c5008cf0558a Apr 8 21:08:06 Tower emhttpd: read SMART /dev/sdf Apr 8 21:09:38 Tower emhttpd: shcmd (4016): blkid -t TYPE='xfs' /dev/sdf1 &> /dev/null Apr 8 21:09:38 Tower emhttpd: shcmd (4017): blkid -t TYPE='btrfs' /dev/sdf1 &> /dev/null Apr 8 21:09:38 Tower emhttpd: shcmd (4018): mount -t btrfs -o noatime,space_cache=v2 /dev/sdf1 /mnt/ptdownload Apr 8 21:09:38 Tower kernel: BTRFS info (device sdf1): using free space tree Apr 8 21:09:38 Tower kernel: BTRFS info (device sdf1): has skinny extents Apr 9 01:05:18 Tower emhttpd: spinning down /dev/sdf Apr 8 01:37:19 Tower kernel: sd 33:0:5:0: [sdf] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) Apr 8 01:37:19 Tower kernel: sd 33:0:5:0: [sdf] Write Protect is off Apr 8 01:37:19 Tower kernel: sd 33:0:5:0: [sdf] Mode Sense: 46 00 10 08 Apr 8 01:37:19 Tower kernel: sd 33:0:5:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA Apr 8 01:37:19 Tower kernel: sdf: sdf1 Apr 8 01:37:19 Tower kernel: sd 33:0:5:0: [sdf] Attached SCSI disk Apr 8 01:38:34 Tower emhttpd: ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 (sdf) 512 7814037168 Apr 8 01:38:34 Tower kernel: mdcmd (7): import 6 sdf 64 3907018532 0 ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 Apr 8 01:38:34 Tower kernel: md: import disk6: (sdf) ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 size: 3907018532 Apr 8 01:38:34 Tower emhttpd: read SMART /dev/sdf Apr 8 01:38:49 Tower emhttpd: ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 (sdf) 512 7814037168 Apr 8 01:38:49 Tower kernel: mdcmd (7): import 6 sdf 64 3907018532 0 ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 Apr 8 01:38:49 Tower kernel: md: import disk6: (sdf) ST4000NM0033-9ZM_S1Z2QYGS_35000c5008cf06f85 size: 3907018532 Apr 8 01:38:49 Tower emhttpd: read SMART /dev/sdf Apr 8 02:06:07 Tower emhttpd: spinning down /dev/sdf

感觉推出存储池和zfs的话就不叫Unraid了，虽然我也非常期待Uraid能直接支持zfs

多谢各位

阵列里有一块硬盘单独用作PT下载，然后其他共享目录都排除掉了这块硬盘，但是每次校验应该还是会读者快盘，有什么方法能让校验盘不去读取这块硬盘呢

zfs pool share NFS is error，like this: root@Tower:/mnt/pool/qnapbackup# zfs list NAME USED AVAIL REFER MOUNTPOINT pool 1.07M 10.2T 140K /mnt/pool pool/qnapbackup 140K 10.2T 140K /mnt/pool/qnapbackup root@Tower:/mnt/pool/qnapbackup# zfs set share=name=/pool/qnapbackup.prot=nfs pool/qnapbackup cannot set property for 'pool/qnapbackup': invalid property 'share' root@Tower:/mnt/pool/qnapbackup#

Successfully created pool，Thanks！

Hello, I'm new here, I try to creat raidz pool, but unsuccessful ，the following is what I executed root@Tower:/mnt/disk2# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:0 0 11.5M 1 loop /lib/modules loop1 7:1 0 19.8M 1 loop /lib/firmware loop2 7:2 0 20G 0 loop /var/lib/docker loop3 7:3 0 1G 0 loop /etc/libvirt sda 8:0 1 14.3G 0 disk └─sda1 8:1 1 14.3G 0 part /boot sdb 8:16 0 931.5G 0 disk └─sdb1 8:17 0 931.5G 0 part sdc 8:32 0 2.7T 0 disk └─sdc1 8:33 0 2.7T 0 part sdd 8:48 0 2.7T 0 disk └─sdd1 8:49 0 2.7T 0 part sde 8:64 0 2.7T 0 disk └─sde1 8:65 0 2.7T 0 part sdg 8:96 0 3.6T 0 disk └─sdg1 8:97 0 3.6T 0 part sdj 8:144 0 7.3T 0 disk └─sdj1 8:145 0 7.3T 0 part sdk 8:160 0 7.3T 0 disk └─sdk1 8:161 0 7.3T 0 part sdl 8:176 0 7.3T 0 disk └─sdl1 8:177 0 7.3T 0 part sdm 8:192 0 2.7T 0 disk └─sdm1 8:193 0 2.7T 0 part sdn 8:208 0 931.5G 0 disk └─sdn1 8:209 0 931.5G 0 part sdo 8:224 0 2.7T 0 disk └─sdo1 8:225 0 2.7T 0 part sdp 8:240 0 2.7T 0 disk └─sdp1 8:241 0 2.7T 0 part md1 9:1 0 7.3T 0 md /mnt/disk1 md2 9:2 0 7.3T 0 md /mnt/disk2 md3 9:3 0 3.6T 0 md /mnt/disk3 md4 9:4 0 3.6T 0 md /mnt/disk4 md5 9:5 0 3.6T 0 md /mnt/disk5 md6 9:6 0 3.6T 0 md /mnt/disk6 md7 9:7 0 2.7T 0 md /mnt/disk7 md8 9:8 0 2.7T 0 md /mnt/disk8 md9 9:9 0 2.7T 0 md /mnt/disk9 md10 9:10 0 2.7T 0 md /mnt/disk10 md11 9:11 0 2.7T 0 md /mnt/disk11 md12 9:12 0 2.7T 0 md /mnt/disk12 md13 9:13 0 2.7T 0 md /mnt/disk13 md14 9:14 0 2.7T 0 md /mnt/disk14 md15 9:15 0 931.5G 0 md /mnt/disk15 md16 9:16 0 931.5G 0 md /mnt/disk16 sr0 11:0 1 17M 0 rom sdq 65:0 0 2.7T 0 disk └─sdq1 65:1 0 2.7T 0 part sdr 65:16 0 2.7T 0 disk └─sdr1 65:17 0 2.7T 0 part sds 65:32 0 931.5G 0 disk └─sds1 65:33 0 931.5G 0 part sdt 65:48 0 3.6T 0 disk └─sdt1 65:49 0 3.6T 0 part sdu 65:64 0 3.6T 0 disk └─sdu1 65:65 0 3.6T 0 part sdv 65:80 0 3.6T 0 disk └─sdv1 65:81 0 3.6T 0 part root@Tower:/mnt/disk2# zpool create -m / mnt / 4TBPOOL sdg sdt sdu sdv cannot use '/': must be a block device or regular file root@Tower:/mnt/disk2#

I installed UNRAID 6.9.1 on VMWare ESXI6.7 (HP ML350P server), but the host will restart when I restart Unraid . Is this a BUG?

用Esxi6.7来跑Unraid6.9，其他一切正常，唯一的问题就是只要重启或者关闭Unraid系统，宿主机就会重启。我用的是HPE ML350P服务器。请问有什么解决方法吗？