Hello 

omicron-diagnostics-20200308-1751.zipg Unraid 6.8.2

 

Had an 8tb Drive Fail , was going to replace disk #8 (sdk) with the same size in my array ( picture attached ) 

Having issues trying to format the drive . (I have destructive mode enabled in Unassigned devices plus )

Drive simply fails to format after typing "Yes" in  the field ( also drive hasn't been fully pre-cleared yet ) 

 

To add to this my log quickly fills up to 100 % with fix common problems error coming up ( pic also attached ) 

Not sure if these are related or mutually exclusive as ive had a good run for a while and now things are starting to go south . 

 

Would like to re-build the array but this has me stuck . I have changed the physical SATA cable 1nce on the affected drive 

 

My searches span from possible SATA controller to power supply to just about anything down a rabbit hole 

Your expertise is appreciated . Logs are attached - Thanks in advance !

omicron-diagnostics-20200229-1256.zip

53 minutes ago, shagz said:

Drive simply fails to format after typing "Yes" in  the field ( also drive hasn't been fully pre-cleared yet ) 

That's not possible because UD+ is not installed:

statistics.sender.plg - 2017.09.22
unassigned.devices.plg - 2020.02.09
unbalance.plg - v2019.10.26
unRAIDServer.plg - 6.8.2

You are having disk issues.  This is only a sample of the log:

Feb 29 02:42:36 OMICRON kernel: ata10: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Feb 29 02:42:36 OMICRON kernel: ata10.00: link online but device misclassified
Feb 29 02:42:40 OMICRON kernel: ata10.00: failed to IDENTIFY (I/O error, err_mask=0x100)
Feb 29 02:42:40 OMICRON kernel: ata10.00: revalidation failed (errno=-5)
Feb 29 02:42:40 OMICRON kernel: ata10.00: disabled
Feb 29 02:42:41 OMICRON kernel: ata10: hard resetting link
Feb 29 02:42:51 OMICRON kernel: ata10: softreset failed (1st FIS failed)
Feb 29 02:42:51 OMICRON kernel: ata10: hard resetting link
Feb 29 02:43:01 OMICRON kernel: ata10: softreset failed (1st FIS failed)
Feb 29 02:43:01 OMICRON kernel: ata10: hard resetting link
Feb 29 02:43:36 OMICRON kernel: ata10: softreset failed (1st FIS failed)
Feb 29 02:43:36 OMICRON kernel: ata10: limiting SATA link speed to 3.0 Gbps
Feb 29 02:43:36 OMICRON kernel: ata10: hard resetting link
Feb 29 02:43:42 OMICRON kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Feb 29 02:43:42 OMICRON kernel: ata10.00: link online but device misclassified
Feb 29 02:43:42 OMICRON kernel: ata10: link online but 1 devices misclassified, device detection might fail
Feb 29 02:43:42 OMICRON kernel: sd 10:0:0:0: [sdk] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Feb 29 02:43:42 OMICRON kernel: sd 10:0:0:0: [sdk] tag#6 Sense Key : 0x5 [current] 
Feb 29 02:43:42 OMICRON kernel: sd 10:0:0:0: [sdk] tag#6 ASC=0x21 ASCQ=0x4 
Feb 29 02:43:42 OMICRON kernel: sd 10:0:0:0: [sdk] tag#6 CDB: opcode=0x88 88 00 00 00 00 01 36 aa 01 b8 00 00 01 00 00 00
Feb 29 02:43:42 OMICRON kernel: print_req_error: I/O error, dev sdk, sector 5212078520
Feb 29 02:43:42 OMICRON kernel: md: disk8 read error, sector=5212078456
Feb 29 02:43:42 OMICRON kernel: md: disk8 read error, sector=5212078464
Feb 29 02:43:42 OMICRON kernel: md: disk8 read error, sector=5212078472
Feb 29 02:43:42 OMICRON kernel: md: disk8 read error, sector=5212078480

Recommendations:

• Solve the disk issues before you do anything else to the array.  You'll make it worse.  Check cabling and disk controller.
• Update your plugins.  You are way behind.

Your disks are also running pretty hot.

Thanks for the insight 

 

I have purchased a new SATA controller and new SATA cord to the affected drive 

UD+ was installed and run at a later date than the 1st two logs , plugins updated as suggested

Still at the same crossroads trying to get the WDC tb drive to format to rebuild parity .

 

@dlandon two new logs have been added . Any suggestions ? 

omicron-diagnostics-20200311-1634.zip omicron-diagnostics-20200311-1914.zip omicron-smart-20200311-1909.zip

Edited March 11, 20206 yr by shagz
name

1 hour ago, shagz said:

trying to get the WDC tb drive to format to rebuild parity

Parity does not have a filesystem so there is no point in formatting it.

 

Looks like it's still having problems communicating with that disk.

Any recommendations as to the next step ? 

Errors start as soon as the disk is initialized, could be a connection problem (replace/swap) cables or it could be the controller, Marvell controllers are not recommended for Unraid.