kilo Posted January 7, 2022 Share Posted January 7, 2022 (edited) EDIT: All sorted. Disk got RMA'd, replacement installed and working I got an error on the 1st from the scheduled monthly array check: Warning [UNRAID] - array has errors Array has 1 disk with read errors Parity disk in error state (disk dsbl) ST12000NE0008 (sdb) The Parity disk was then showing as Disabled I did an Array check - all good: Notice [UNRAID] - Parity check finished (0 errors) I tried the following to see if it would return to normal: 1. Stop array 2. Un-assign disabled disk 3. Start array with disabled disk unassigned 4. Stop array 5. Reassign disabled disk 6. Start array to begin rebuild Got to step 5 - selected the parity disk from the dropdown, but it immediately disappeared from the dropdown list and now just shows 'unassigned'. I do see the disk listed in the Preclear disk plugin. Downloading the Diagnostics, I did get a SMART log, seems to have a number of errors with "Read SCT Status failed: scsi error badly formed scsi parameters" - full log below. I may try replacing the disk cable to see if that is an issue - I did try and reseat it yesterday. Does it look like a disk RMA ? Thanks 😀 smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.10.28-Unraid] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate IronWolf Pro Device Model: ST12000NE0008-2PK103 Serial Number: XXX LU WWN Device Id: 5 000c50 0c8afb3e5 Firmware Version: EN02 User Capacity: 12,000,138,625,024 bytes [12.0 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Form Factor: 3.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-4 (minor revision not indicated) SATA Version is: SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Thu Jan 6 21:18:25 2022 GMT SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Disabled ATA Security is: Disabled, NOT FROZEN [SEC1] Read SCT Status failed: scsi error badly formed scsi parameters Wt Cache Reorder: Unknown (SCT Feature Control command failed) Read SMART Data failed: scsi error badly formed scsi parameters === START OF READ SMART DATA SECTION === SMART Status command failed: scsi error badly formed scsi parameters SMART overall-health self-assessment test result: UNKNOWN! SMART Status, Attributes and Thresholds cannot be read. Read SMART Log Directory failed: scsi error badly formed scsi parameters General Purpose Log Directory Version 1 Address Access R/W Size Description 0x00 GPL R/O 1 Log Directory 0x03 GPL R/O 5 Ext. Comprehensive SMART error log 0x04 GPL R/O 256 Device Statistics log 0x07 GPL R/O 1 Extended self-test log 0x08 GPL R/O 2 Power Conditions log 0x0a GPL R/W 8 Device Statistics Notification 0x0c GPL R/O 2048 Pending Defects log 0x10 GPL R/O 1 NCQ Command Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x13 GPL R/O 1 SATA NCQ Send and Receive log 0x21 GPL R/O 1 Write stream error log 0x22 GPL R/O 1 Read stream error log 0x24 GPL R/O 768 Current Device Internal Status Data log 0x2f GPL - 1 Set Sector Configuration 0x30 GPL R/O 9 IDENTIFY DEVICE data log 0x80-0x9f GPL R/W 16 Host vendor specific log 0xa1 GPL VS 160 Device vendor specific log 0xa2 GPL VS 16320 Device vendor specific log 0xa4 GPL VS 160 Device vendor specific log 0xa6 GPL VS 192 Device vendor specific log 0xa8-0xa9 GPL VS 136 Device vendor specific log 0xab GPL VS 1 Device vendor specific log 0xad GPL VS 16 Device vendor specific log 0xbe-0xbf GPL VS 65535 Device vendor specific log 0xc1 GPL VS 8 Device vendor specific log 0xc3 GPL VS 56 Device vendor specific log 0xc7 GPL VS 8 Device vendor specific log 0xc9 GPL VS 8 Device vendor specific log 0xca GPL VS 16 Device vendor specific log 0xcd-0xce GPL VS 1 Device vendor specific log 0xcf GPL VS 512 Device vendor specific log 0xd1 GPL VS 656 Device vendor specific log 0xd2 GPL VS 10000 Device vendor specific log 0xd4 GPL VS 2048 Device vendor specific log 0xda GPL VS 1 Device vendor specific log 0xe0 GPL R/W 1 SCT Command/Status 0xe1 GPL R/W 1 SCT Data Transfer 0xe2 GPL - 160 Reserved SMART Extended Comprehensive Error Log Version: 1 (5 sectors) Device Error Count: 1 CR = Command Register FEATR = Features Register COUNT = Count (was: Sector Count) Register LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8 LH = LBA High (was: Cylinder High) Register ] LBA LM = LBA Mid (was: Cylinder Low) Register ] Register LL = LBA Low (was: Sector Number) Register ] DV = Device (was: Device/Head) Register DC = Device Control Register ER = Error register ST = Status register Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 1 [0] occurred at disk power-on lifetime: 5421 hours (225 days + 21 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 53 00 00 00 00 01 94 26 e0 00 00 Error: UNC at LBA = 0x019426e0 = 26486496 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 00 00 80 00 00 01 94 41 d8 40 00 38d+15:25:51.057 READ FPDMA QUEUED 60 00 00 05 40 00 00 01 94 3c 98 40 00 38d+15:25:51.057 READ FPDMA QUEUED 60 00 00 05 40 00 00 01 94 37 58 40 00 38d+15:25:47.759 READ FPDMA QUEUED 60 00 00 05 40 00 00 01 94 32 18 40 00 38d+15:25:47.759 READ FPDMA QUEUED 60 00 00 05 40 00 00 01 94 2c d8 40 00 38d+15:25:47.590 READ FPDMA QUEUED SMART Extended Self-test Log Version: 1 (1 sectors) No self-tests have been logged. [To run self-tests, use: smartctl -t] Selective Self-tests/Logging not supported Read SCT Status failed: scsi error badly formed scsi parameters Read SCT Status failed: scsi error badly formed scsi parameters SCT (Get) Error Recovery Control command failed Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 15 --- Lifetime Power-On Resets 0x01 0x010 4 5562 --- Power-on Hours 0x01 0x018 6 38613107064 --- Logical Sectors Written 0x01 0x020 6 60174526 --- Number of Write Commands 0x01 0x028 6 202658166170 --- Logical Sectors Read 0x01 0x030 6 195536661 --- Number of Read Commands 0x01 0x038 6 - --- Date and Time TimeStamp 0x03 ===== = = === == Rotating Media Statistics (rev 1) == 0x03 0x008 4 5416 --- Spindle Motor Power-on Hours 0x03 0x010 4 4724 --- Head Flying Hours 0x03 0x018 4 11057 --- Head Load Events 0x03 0x020 4 3696 --- Number of Reallocated Logical Sectors 0x03 0x028 4 18 --- Read Recovery Attempts 0x03 0x030 4 0 --- Number of Mechanical Start Failures 0x03 0x038 4 272 --- Number of Realloc. Candidate Logical Sectors 0x03 0x040 4 134 --- Number of High Priority Unload Events 0x04 ===== = = === == General Errors Statistics (rev 1) == 0x04 0x008 4 18 --- Number of Reported Uncorrectable Errors 0x04 0x010 4 2 --- Resets Between Cmd Acceptance and Completion 0x04 0x018 4 0 -D- Physical Element Status Changed 0x05 ===== = = === == Temperature Statistics (rev 1) == 0x05 0x008 1 17 --- Current Temperature 0x05 0x010 1 20 --- Average Short Term Temperature 0x05 0x018 1 17 --- Average Long Term Temperature 0x05 0x020 1 48 --- Highest Temperature 0x05 0x028 1 10 --- Lowest Temperature 0x05 0x030 1 42 --- Highest Average Short Term Temperature 0x05 0x038 1 14 --- Lowest Average Short Term Temperature 0x05 0x040 1 37 --- Highest Average Long Term Temperature 0x05 0x048 1 17 --- Lowest Average Long Term Temperature 0x05 0x050 4 0 --- Time in Over-Temperature 0x05 0x058 1 60 --- Specified Maximum Operating Temperature 0x05 0x060 4 0 --- Time in Under-Temperature 0x05 0x068 1 5 --- Specified Minimum Operating Temperature 0x06 ===== = = === == Transport Statistics (rev 1) == 0x06 0x008 4 119 --- Number of Hardware Resets 0x06 0x010 4 50 --- Number of ASR Events 0x06 0x018 4 0 --- Number of Interface CRC Errors 0xff ===== = = === == Vendor Specific Statistics (rev 1) == 0xff 0x008 7 0 --- Vendor Specific 0xff 0x010 7 0 --- Vendor Specific 0xff 0x018 7 0 --- Vendor Specific |||_ C monitored condition met ||__ D supports DSN |___ N normalized value Pending Defects log (GP Log 0x0c) Index LBA Hours 0 26480640 5421 1 26480641 5421 2 26480642 5421 3 26480643 5421 4 26480644 5421 5 26480645 5421 6 26480646 5421 7 26480647 5421 8 26486504 5421 9 26486505 5421 10 26486506 5421 11 26486507 5421 12 26486508 5421 13 26486509 5421 14 26486510 5421 15 26486511 5421 16 26486512 5421 17 26486513 5421 18 26486514 5421 19 26486515 5421 20 26486516 5421 21 26486517 5421 22 26486518 5421 23 26486519 5421 24 26499240 5421 25 26499241 5421 26 26499242 5421 27 26499243 5421 28 26499244 5421 29 26499245 5421 30 26499246 5421 ... (241 entries not shown) SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x000a 2 2 Device-to-host register FISes sent due to a COMRESET 0x0001 2 0 Command failed due to ICRC error 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS Edited January 29, 2022 by kilo Quote Link to comment
ChatNoir Posted January 7, 2022 Share Posted January 7, 2022 Your diagnostics would provide more information. Quote Link to comment
kilo Posted January 7, 2022 Author Share Posted January 7, 2022 Here's the diagnostics zip - thanks What logs in particular are useful to look at ? unraid-diagnostics-20220106-2118.zip Quote Link to comment
JorgeB Posted January 7, 2022 Share Posted January 7, 2022 Read SMART Data failed: scsi error badly formed scsi parameters Disk isn't giving a full SMART report, this is usually a disk problem, you can try swapping cables just to confirm. Quote Link to comment
Solution kilo Posted January 29, 2022 Author Solution Share Posted January 29, 2022 It was the disk - repalcement in place and working Quote Link to comment
Recommended Posts
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.