December 22, 20232 yr Hi, A few days ago, I got two 18 TB SAS drives to put as my parity (they are the biggest drives in my array). I just removed the old one from parity and put these new ones and started the array with parity check and automatically started to rebuild parity. Around 97% one of the drives got errors and got disabled, the other one worked fine. So I tried again to add the drive that failed as parity and the second time got to around 98.7% as I can see. Before that, I ran a SMART short test and it was fine. From what I can see from the logs it gets some errors like I/O error, dev sdw, sector 10223794696 op 0x1:(WRITE) flags 0x0 phys_seg 119 prio class 2 md: disk0 write error, sector=10223794632 md: disk0 write error, sector=10223794640 md: disk0 write error, sector=10223794648 md: disk0 write error, sector=10223794656 md: disk0 write error, sector=10223794664 I/O error, dev sdw, sector 34706499072 op 0x1:(WRITE) flags 0x0 phys_seg 32 prio class 2 md: disk0 write error, sector=34706499008 md: disk0 write error, sector=34706499016 md: disk0 write error, sector=34706499024 md: disk0 write error, sector=34706499032 md: disk0 write error, sector=34706499040 I don't know how can I check if the problem is the drive or if it can be the cable, controller, firmware, etc. The cable is new as these are my only SAS drives, the rest are SATA. These are my only 18TB drives the rest are 12 TB, 8 TB, and a few 4 TB drives. What I was thinking of trying was to put that drive on another head from the SAS cable, it has 4 and I only have two drives, so two are free. The other thing was to run a SMART extend test on that drive. If anybody has other suggestions or if you can see if the drive is the problem from the logs please let me know. I've attached the diagnostics file if that helps. Thank you. tower-diagnostics-20231222-1103.zip
December 22, 20232 yr Community Expert Solution You need to run the SMART Extended test to properly test the drive - the Short test is often insufficient in finding errors.
December 22, 20232 yr Author I've tried to run an extended test and it failed with error Failed in segment --> from the start. I can't even run a short test anymore, it failes around 8% with the same error, so I'm guessing the drive died. Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ] Description number (hours) # 1 Background short Failed in segment --> 3 91 - [- - -] # 2 Background long Failed in segment --> 3 91 - [- - -] # 3 Background short Failed in segment --> 3 91 - [- - -] # 4 Background short Failed in segment --> 3 91 - [- - -] # 5 Background long Failed in segment --> 3 91 - [- - -] # 6 Background short Failed in segment --> 3 91 - [- - -] # 7 Background short Failed in segment --> 3 91 - [- - -] # 8 Background long Failed in segment --> 3 91 - [- - -] # 9 Background short Completed - 45 - [- - -] #10 Background short Completed - 10 - [- - -] Edited December 22, 20232 yr by Velun
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.