Jump to content

The same disk appears in Array Devices and Unassigned Devices at the same time


Recommended Posts

Posted

I don‘t know why,Please help!

 WX20210412-173146@2x.thumb.png.38074322c1ef95d82da96688d939caa6.png

 

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

Posted

This normally means the disk dropped offline and then came back online with a different ID (the diagnostics would confirm this).   How is it connected - this is not atypical of USB connected devices which is why USB is normally not recommended for array drives.

 

Posted (edited)
13 hours ago, JorgeB said:

请发布诊断信息:工具->诊断

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

20210412215825.png

 

Edited by tf0083
Posted

Difficult to see what the problem is, your visualizing Unraid which is not supported and I have no experience with, also using a RAID controller which is not recommended.

 

Are you using SAS interposers with the SATA disks?

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...