当我试图向mdadm添加一个新磁盘时,我将返回一个错误:
sudo mdadm --添加/dev/md0 /dev/sdd -详细
mdadm: Failed to write metadata to /dev/sdd这是我的装置出问题了还是别的什么。
我购买了4张据报是新的替换磁盘,但我怀疑它们被擦去并标记为新的或工厂翻新,原因是我在使用这些磁盘时遇到了困难,并且列出了累积的时间。到目前为止,我只试过4张磁盘中的2张。我的安装程序是通过LSI2308连接的HB-1235磁盘外壳.通常使用多路径,然而,我已经禁用了多径,并断开了第二个电缆试图确定为什么我不能设置磁盘。尝试运行fdisk、mkfs.ext4或其他磁盘实用程序时,无法写入它。我做了个坏块扫描,没有坏的块。检查hdparm时,未设置只读标志。我发现的另一件奇怪的事情是,即使我禁用了multipath并重新启动,我仍然看到两个驱动器列出了它们的多路径别名。是否有第二个应用程序可以运行多路径?磁盘是密封的,但我知道任何人都可以将磁盘重新密封到静态袋中。翻新的磁盘显示工厂的时间吗?
/dev/md0:
Version : 1.2
Creation Time : Sat Feb 2 22:55:00 2019
Raid Level : raid6
Array Size : 19533824000 (18.19 TiB 20.00 TB)
Used Dev Size : 1953382400 (1862.89 GiB 2000.26 GB)
Raid Devices : 12
Total Devices : 11
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Sat Dec 31 04:39:07 2022
State : clean, degraded
Active Devices : 11
Working Devices : 11
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 512K
Consistency Policy : bitmap
Name : media:0 (local to host media)
UUID : 1599e3ae:2bb24f48:a9524f60:02b6cb8c
Events : 5824802
Number Major Minor RaidDevice State
0 8 144 0 active sync /dev/sdj
1 8 176 1 active sync /dev/sdl
2 8 128 2 active sync /dev/sdi
3 8 112 3 active sync /dev/sdh
4 8 96 4 active sync /dev/sdg
5 8 192 5 active sync /dev/sdm
- 0 0 6 removed
7 8 80 7 active sync /dev/sdf
8 8 160 8 active sync /dev/sdk
9 253 1 9 active sync /dev/dm-1
10 253 0 10 active sync /dev/dm-0
11 8 32 11 active sync /dev/sdc
cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid6 sdk[8] sdj[0] sdh[3] sdi[2] sdg[4] sdc[11] sdl[1] sdm[5] sdf[7] dm-1[9] dm-0[10]
19533824000 blocks super 1.2 level 6, 512k chunk, algorithm 2 [12/11] [UUUUUU_UUUUU]
bitmap: 15/15 pages [60KB], 65536KB chunksmartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.0-56-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: SEAGATE
Product: DKS2P-H2R0SS
Revision: 4F06
Compliance: SPC-3
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Logical block size: 512 bytes
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Logical Unit id: 0x5000c50041070d0b
Serial number: Z1P1AFWD0000S138114Q
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Sat Dec 31 12:31:04 2022 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Enabled
=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK
Current Drive Temperature: 23 C
Drive Trip Temperature: 68 C
Accumulated power on time, hours:minutes 54263:40
Manufactured in week 06 of year 2012
Specified cycle count over device lifetime: 10000
Accumulated start-stop cycles: 151
Specified load-unload count over device lifetime: 300000
Accumulated load-unload cycles: 151
Elements in grown defect list: 0
Vendor (Seagate Cache) information
Blocks sent to initiator = 89937483
Blocks received from initiator = 195186019
Blocks read from cache and sent to initiator = 750296
Number of read and write commands whose size <= segment size = 3072072
Number of read and write commands whose size > segment size = 0
Vendor (Seagate/Hitachi) factory information
number of hours powered up = 54263.67
number of minutes until next internal SMART test = 39
Error counter log:
Errors Corrected by Total Correction Gigabytes Total
ECC rereads/ errors algorithm processed uncorrected
fast | delayed rewrites corrected invocations [10^9 bytes] errors
read: 2324326148 0 0 2324326148 0 1149.377 0
write: 0 0 0 0 0 101.683 0
verify: 459775 0 0 459775 0 0.000 0
Non-medium error count: 0
[GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S on']
SMART Self-test log
Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ]
Description number (hours)
# 1 Background short Completed - 54215 - [- - -]
Long (extended) Self-test duration: 5 seconds [0.1 minutes]下面是我上次创建数组时的历史引用:多路径Raid 6- MDADM找不到超级块- 18.04
编辑:在在线查看了一些信息之后,我怀疑我的磁盘一度被格式化为520字节扇区磁盘。然而,目前的审查没有表明这一点:
参考文献:https://www.youtube.com/watch?v=DAaTfv96V9w&ab_channel=ArtofServer https://www.reddit.com/r/homelab/comments/9bu8tf/is_这_驾驶_实际上_坏的_或_做_我_螺丝/
我在几个不同的磁盘上运行sdparm -all /dev/sdd >> sdd_parm.txt。现有磁盘仅与磁盘id不同。但是,新磁盘有多个不同之处。
1c1
< /dev/sdc: SEAGATE ST2000NM0001 XRBA
---
> /dev/sdd: SEAGATE DKS2P-H2R0SS 4F06
10c10
< EER 0 [cha: y, def: 0, sav: 0] Enable early recovery (obsolete)
---
> EER 1 [cha: y, def: 0, sav: 1] Enable early recovery (obsolete)
18c18
< RRC 20 [cha: y, def: 20, sav: 20] Read retry count
---
> RRC 10 [cha: y, def: 20, sav: 10] Read retry count
28c28
< RTL 8000 [cha: y, def: -1, sav:8000] Recovery time limit (ms)
---
> RTL 2000 [cha: y, def: -1, sav:2000] Recovery time limit (ms)
41c41
< MBS 314 [cha: y, def:314, sav:314] Maximum burst size (512 bytes)
---
> MBS 1040 [cha: y, def:314, sav:1040] Maximum burst size (512 bytes)
54c54
< DBPPS 512 [cha: n, def:512, sav:512] Data bytes per physical sector
---
> DBPPS 512 [cha: n, def:520, sav:512] Data bytes per physical sector
75c75
< V_DTE 0 [cha: y, def: 0, sav: 0] Data terminate on error
---
> V_DTE 1 [cha: y, def: 0, sav: 1] Data terminate on error
77c77
< V_RC 20 [cha: y, def: 20, sav: 20] Verify retry count
---
> V_RC 5 [cha: y, def: 20, sav: 5] Verify retry count
79c79
< V_RTL 8000 [cha: y, def: -1, sav:8000] Verify recovery time limit (ms)
---
> V_RTL 1000 [cha: y, def: -1, sav:1000] Verify recovery time limit (ms)
92c92
< WCE 0 [cha: y, def: 0, sav: 0] Write cache enable
---
> WCE 0 [cha: y, def: 1, sav: 0] Write cache enable
118c118
< NCS 32 [cha: n, def: 32, sav: 32] Number of cache segments
---
> NCS 3 [cha: y, def: 32, sav: 3] Number of cache segments
126,127c126,127
< D_SENSE 1 [cha: y, def: 0, sav: 1] Descriptor format sense data
< GLTSD 0 [cha: y, def: 1, sav: 0] Global logging target save disable
---
> D_SENSE 0 [cha: y, def: 0, sav: 0] Descriptor format sense data
> GLTSD 1 [cha: y, def: 1, sav: 1] Global logging target save disable
155c155
< ESTCT 18500 [cha: n, def:18500, sav:18500] Extended self test completion time (sec)
---
> ESTCT 5 [cha: y, def: 14, sav: 5] Extended self test completion time (sec)
172,174c172,174
< IDLE_C 0 [cha: n, def: 0, sav: 0] Idle_c timer enable
< IDLE_B 1 [cha: y, def: 0, sav: 1] Idle_b timer enable
< IDLE 1 [cha: y, def: 0, sav: 1] Idle_a timer enable
---
> IDLE_C 0 [cha: y, def: 0, sav: 0] Idle_c timer enable
> IDLE_B 0 [cha: y, def: 0, sav: 0] Idle_b timer enable
> IDLE 0 [cha: y, def: 0, sav: 0] Idle_a timer enable
183c183
< ICCT 0 [cha: n, def: 0, sav: 0] Idle_c condition timer (100 ms)
---
> ICCT 18000 [cha: y, def:18000, sav:18000] Idle_c condition timer (100 ms)
195c195
< PERF 0 [cha: y, def: 0, sav: 0] Performance (impact of ie operations)
---
> PERF 1 [cha: y, def: 0, sav: 1] Performance (impact of ie operations)
202,203c202,203
< LOGERR 1 [cha: y, def: 0, sav: 1] Log informational exception errors
< MRIE 4 [cha: y, def: 0, sav: 4] Method of reporting informational exceptions
---
> LOGERR 0 [cha: y, def: 0, sav: 0] Log informational exception errors
> MRIE 0 [cha: y, def: 0, sav: 0] Method of reporting informational exceptions
207,217c207,208
< INTT 600 [cha: y, def: 0, sav:600] Interval timer (100 ms)
< REPC 0 [cha: y, def: 1, sav: 0] Report count (or Test flag number [SSC-3])
< Background control (SBC) [bc] mode page [PS=1]:
< S_L_FULL 0 [cha: n, def: 0, sav: 0] Suspend on log full
< LOWIR 0 [cha: n, def: 0, sav: 0] Log only when intervention required
< EN_BMS 1 [cha: n, def: 1, sav: 1] Enable background medium scan
< EN_PS 0 [cha: y, def: 0, sav: 0] Enable pre-scan
< BMS_I 72 [cha: y, def: 72, sav: 72] Background medium scan interval time (hour)
< BPS_TL 24 [cha: y, def: 24, sav: 24] Background pre-scan time limit (hour)
< MIN_IDLE 250 [cha: y, def:500, sav:250] Minumum idle time before background scan (ms)
< MAX_SUSP 0 [cha: y, def: 0, sav: 0] Maximum time to suspend background scan (ms)
---
> INTT 0 [cha: y, def: 0, sav: 0] Interval timer (100 ms)
> REPC 1 [cha: y, def: 1, sav: 1] Report count (or Test flag number [SSC-3])发布于 2023-01-05 03:01:18
在这里找到了一个解决方案:https://www.reddit.com/r/homelab/comments/9bu8tf/is_这_驾驶_实际上_坏的_或_做_我_螺丝/
注意:我怀疑是卖方还是向卖方提供驱动器的供应商,他们以前删除了驱动器并将其重新格式化为512,但从未刷新固件,因此磁盘正在寻找520扇区分区,但格式化为512。
https://askubuntu.com/questions/1448162
复制相似问题