Beijergard Posted February 7, 2022 Share Posted February 7, 2022 (edited) Hi there. I'm pretty novice when it comes to Unix systems, but I have an Unraid server where Disk 1 failed during Parity check. After a reboot the drive is Unmountable. I did both short and long SMART test and both came out without any apparent error. See spoiler for report. I'm about to go buy a replacement disk to try and make a rebuild, but if its possible I would prefer to keep this one if its possible. I have never done a disk replacement or a rebuild so I'm really nervous about what will happen and I really don't want to mess this up. Can you guys see if there is any hope for this disk or shall I just wait for the replacement? Spoiler 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 Device Model: ST8000VN004-2M2101 Serial Number: ******* LU WWN Device Id: 5 000c50 0c28f3c13 Firmware Version: SC60 User Capacity: 8,001,563,222,016 bytes [8.00 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: Mon Feb 7 00:13:54 2022 PST 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, frozen [SEC2] Write SCT (Get) Feature Control Command failed: scsi error badly formed scsi parameters Wt Cache Reorder: Unknown (SCT Feature Control command failed) === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 567) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 730) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x50bd) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-- 083 064 044 - 208065798 3 Spin_Up_Time PO---- 083 080 000 - 0 4 Start_Stop_Count -O--CK 099 099 020 - 1135 5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0 7 Seek_Error_Rate POSR-- 088 060 045 - 4917885815 9 Power_On_Hours -O--CK 083 083 000 - 15223 10 Spin_Retry_Count PO--C- 100 100 097 - 0 12 Power_Cycle_Count -O--CK 099 099 020 - 1087 18 Head_Health PO-R-- 100 100 050 - 0 187 Reported_Uncorrect -O--CK 100 100 000 - 0 188 Command_Timeout -O--CK 100 100 000 - 0 190 Airflow_Temperature_Cel -O---K 066 054 040 - 34 (Min/Max 32/40) 192 Power-Off_Retract_Count -O--CK 100 100 000 - 1033 193 Load_Cycle_Count -O--CK 099 099 000 - 2310 194 Temperature_Celsius -O---K 034 046 000 - 34 (0 22 0 0 0) 195 Hardware_ECC_Recovered -O-RC- 083 064 000 - 208065798 197 Current_Pending_Sector -O--C- 100 100 000 - 0 198 Offline_Uncorrectable ----C- 100 100 000 - 0 199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0 240 Head_Flying_Hours ------ 100 253 000 - 14875 (218 188 0) 241 Total_LBAs_Written ------ 100 253 000 - 56132239366 242 Total_LBAs_Read ------ 100 253 000 - 529303988460 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] Address Access R/W Size Description 0x00 GPL,SL R/O 1 Log Directory 0x01 SL R/O 1 Summary SMART error log 0x02 SL R/O 5 Comprehensive SMART error log 0x03 GPL R/O 5 Ext. Comprehensive SMART error log 0x04 GPL R/O 256 Device Statistics log 0x04 SL R/O 8 Device Statistics log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x08 GPL R/O 2 Power Conditions log 0x09 SL R/W 1 Selective self-test 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 0x15 GPL R/W 1 Rebuild Assist 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,SL R/O 9 IDENTIFY DEVICE data log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xa1 GPL,SL VS 24 Device vendor specific log 0xa2 GPL VS 16320 Device vendor specific log 0xa4 GPL,SL VS 160 Device vendor specific log 0xa6 GPL VS 192 Device vendor specific log 0xa8-0xa9 GPL,SL 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,SL VS 8 Device vendor specific log 0xc3 GPL,SL VS 32 Device vendor specific log 0xc9 GPL,SL VS 8 Device vendor specific log 0xca GPL,SL VS 16 Device vendor specific log 0xd1 GPL VS 336 Device vendor specific log 0xd2 GPL VS 10000 Device vendor specific log 0xd4 GPL VS 2048 Device vendor specific log 0xda GPL,SL VS 1 Device vendor specific log 0xe0 GPL,SL R/W 1 SCT Command/Status 0xe1 GPL,SL R/W 1 SCT Data Transfer SMART Extended Comprehensive Error Log Version: 1 (5 sectors) No Errors Logged SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 15213 - # 2 Extended offline Aborted by host 90% 15202 - # 3 Extended offline Aborted by host 90% 15202 - # 4 Short offline Completed without error 00% 15201 - # 5 Extended offline Aborted by host 90% 15201 - # 6 Short offline Completed without error 00% 15200 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. SCT Status Version: 3 SCT Version (vendor specific): 522 (0x020a) Device State: Active (0) Current Temperature: 34 Celsius Power Cycle Min/Max Temperature: 32/40 Celsius Lifetime Min/Max Temperature: 22/46 Celsius Under/Over Temperature Limit Count: 0/22 SMART Status: 0xc24f (PASSED) Vendor specific: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 03 00 00 00 00 00 00 00 00 00 00 00 SCT Temperature History Version: 2 Temperature Sampling Period: 3 minutes Temperature Logging Interval: 59 minutes Min/Max recommended Temperature: 10/25 Celsius Min/Max Temperature Limit: 5/70 Celsius Temperature History Size (Index): 128 (4) Index Estimated Time Temperature Celsius 5 2022-02-01 18:58 38 ******************* 6 2022-02-01 19:57 38 ******************* 7 2022-02-01 20:56 38 ******************* 8 2022-02-01 21:55 34 *************** 9 2022-02-01 22:54 29 ********** 10 2022-02-01 23:53 28 ********* 11 2022-02-02 00:52 28 ********* 12 2022-02-02 01:51 28 ********* 13 2022-02-02 02:50 33 ************** 14 2022-02-02 03:49 28 ********* 15 2022-02-02 04:48 35 **************** 16 2022-02-02 05:47 35 **************** 17 2022-02-02 06:46 27 ******** 18 2022-02-02 07:45 31 ************ 19 2022-02-02 08:44 28 ********* 20 2022-02-02 09:43 28 ********* 21 2022-02-02 10:42 27 ******** 22 2022-02-02 11:41 27 ******** 23 2022-02-02 12:40 29 ********** 24 2022-02-02 13:39 27 ******** ... ..( 3 skipped). .. ******** 28 2022-02-02 17:35 27 ******** 29 2022-02-02 18:34 26 ******* ... ..( 4 skipped). .. ******* 34 2022-02-02 23:29 26 ******* 35 2022-02-03 00:28 27 ******** 36 2022-02-03 01:27 27 ******** 37 2022-02-03 02:26 27 ******** 38 2022-02-03 03:25 35 **************** 39 2022-02-03 04:24 34 *************** 40 2022-02-03 05:23 35 **************** 41 2022-02-03 06:22 28 ********* 42 2022-02-03 07:21 33 ************** 43 2022-02-03 08:20 33 ************** 44 2022-02-03 09:19 32 ************* 45 2022-02-03 10:18 34 *************** 46 2022-02-03 11:17 27 ******** ... ..( 12 skipped). .. ******** 59 2022-02-04 00:04 27 ******** 60 2022-02-04 01:03 28 ********* 61 2022-02-04 02:02 28 ********* 62 2022-02-04 03:01 31 ************ 63 2022-02-04 04:00 35 **************** 64 2022-02-04 04:59 36 ***************** 65 2022-02-04 05:58 29 ********** 66 2022-02-04 06:57 30 *********** 67 2022-02-04 07:56 29 ********** 68 2022-02-04 08:55 28 ********* 69 2022-02-04 09:54 28 ********* 70 2022-02-04 10:53 35 **************** 71 2022-02-04 11:52 29 ********** 72 2022-02-04 12:51 35 **************** 73 2022-02-04 13:50 29 ********** ... ..( 4 skipped). .. ********** 78 2022-02-04 18:45 29 ********** 79 2022-02-04 19:44 34 *************** 80 2022-02-04 20:43 28 ********* ... ..( 3 skipped). .. ********* 84 2022-02-05 00:39 28 ********* 85 2022-02-05 01:38 34 *************** 86 2022-02-05 02:37 37 ****************** 87 2022-02-05 03:36 36 ***************** 88 2022-02-05 04:35 37 ****************** 89 2022-02-05 05:34 33 ************** 90 2022-02-05 06:33 31 ************ 91 2022-02-05 07:32 28 ********* 92 2022-02-05 08:31 28 ********* 93 2022-02-05 09:30 29 ********** 94 2022-02-05 10:29 29 ********** 95 2022-02-05 11:28 28 ********* ... ..( 2 skipped). .. ********* 98 2022-02-05 14:25 28 ********* 99 2022-02-05 15:24 27 ******** 100 2022-02-05 16:23 30 *********** 101 2022-02-05 17:22 27 ******** ... ..( 2 skipped). .. ******** 104 2022-02-05 20:19 27 ******** 105 2022-02-05 21:18 28 ********* ... ..( 2 skipped). .. ********* 108 2022-02-06 00:15 28 ********* 109 2022-02-06 01:14 37 ****************** 110 2022-02-06 02:13 ? - 111 2022-02-06 03:12 32 ************* 112 2022-02-06 04:11 39 ******************** 113 2022-02-06 05:10 39 ******************** 114 2022-02-06 06:09 38 ******************* ... ..( 4 skipped). .. ******************* 119 2022-02-06 11:04 38 ******************* 120 2022-02-06 12:03 37 ****************** 121 2022-02-06 13:02 37 ****************** 122 2022-02-06 14:01 36 ***************** 123 2022-02-06 15:00 34 *************** 124 2022-02-06 15:59 33 ************** ... ..( 7 skipped). .. ************** 4 2022-02-06 23:51 33 ************** SCT Error Recovery Control: Read: 70 (7.0 seconds) Write: 70 (7.0 seconds) Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 1087 --- Lifetime Power-On Resets 0x01 0x010 4 15223 --- Power-on Hours 0x01 0x018 6 56120386054 --- Logical Sectors Written 0x01 0x020 6 298550254 --- Number of Write Commands 0x01 0x028 6 526584548308 --- Logical Sectors Read 0x01 0x030 6 763040972 --- Number of Read Commands 0x01 0x038 6 - --- Date and Time TimeStamp 0x03 ===== = = === == Rotating Media Statistics (rev 1) == 0x03 0x008 4 14991 --- Spindle Motor Power-on Hours 0x03 0x010 4 14947 --- Head Flying Hours 0x03 0x018 4 2310 --- Head Load Events 0x03 0x020 4 0 --- Number of Reallocated Logical Sectors 0x03 0x028 4 0 --- Read Recovery Attempts 0x03 0x030 4 0 --- Number of Mechanical Start Failures 0x03 0x038 4 0 --- Number of Realloc. Candidate Logical Sectors 0x03 0x040 4 1033 --- Number of High Priority Unload Events 0x04 ===== = = === == General Errors Statistics (rev 1) == 0x04 0x008 4 0 --- Number of Reported Uncorrectable Errors 0x04 0x010 4 0 --- Resets Between Cmd Acceptance and Completion 0x05 ===== = = === == Temperature Statistics (rev 1) == 0x05 0x008 1 34 --- Current Temperature 0x05 0x010 1 33 --- Average Short Term Temperature 0x05 0x018 1 33 --- Average Long Term Temperature 0x05 0x020 1 46 --- Highest Temperature 0x05 0x028 1 0 --- Lowest Temperature 0x05 0x030 1 43 --- Highest Average Short Term Temperature 0x05 0x038 1 27 --- Lowest Average Short Term Temperature 0x05 0x040 1 40 --- Highest Average Long Term Temperature 0x05 0x048 1 32 --- Lowest Average Long Term Temperature 0x05 0x050 4 0 --- Time in Over-Temperature 0x05 0x058 1 70 --- Specified Maximum Operating Temperature 0x05 0x060 4 450 --- Time in Under-Temperature 0x05 0x068 1 5 --- Specified Minimum Operating Temperature 0x06 ===== = = === == Transport Statistics (rev 1) == 0x06 0x008 4 146 --- Number of Hardware Resets 0x06 0x010 4 25 --- Number of ASR Events 0x06 0x018 4 0 --- Number of Interface CRC Errors 0xff ===== = = === == Vendor Specific Statistics (rev 1) == 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) No Defects Logged 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 February 12, 2022 by Beijergard Solved Quote Link to comment
itimpi Posted February 7, 2022 Share Posted February 7, 2022 Cabling issues (power or SATA) are much more frequent reasons for a disk being disabled than actual disk failure, so these is a good chance the disk is fine. Handling of disks being unmountable is covered here in the online documentation that can be accessed via the Manual link at the bottom of the GUI. Quote Link to comment
Beijergard Posted February 7, 2022 Author Share Posted February 7, 2022 (edited) I actually replaced all cables, power and sata but the problem is still there. I will take a look at the documentation.. The sata cables I found was some random cables that came with my motherboard, unused and still in their plastic bags. Edited February 7, 2022 by Beijergard Quote Link to comment
Beijergard Posted February 7, 2022 Author Share Posted February 7, 2022 So, I have checked the XFS file system with the option -n now and these are the results. I do not know how to read this info. Spoiler Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... block (1,414548-414548) multiply claimed by cnt space tree, state - 2 block (1,9817-9817) multiply claimed by cnt space tree, state - 2 agf_freeblks 69965104, counted 69965116 in ag 1 agi_freecount 87, counted 90 in ag 1 agi unlinked bucket 50 is 383972722 in ag 1 (inode=2531456370) agf_freeblks 8805144, counted 8805149 in ag 7 sb_ifree 887, counted 896 sb_fdblocks 633181712, counted 646815531 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 data fork in ino 415890952 claims free block 121079803 imap claims a free inode 967996424 is in use, would correct imap and clear inode imap claims a free inode 968429338 is in use, would correct imap and clear inode imap claims a free inode 968429347 is in use, would correct imap and clear inode imap claims a free inode 1446280125 is in use, would correct imap and clear inode imap claims a free inode 1446280127 is in use, would correct imap and clear inode - agno = 1 data fork in ino 2147573505 claims free block 268445271 data fork in ino 2147573506 claims free block 268445272 imap claims a free inode 2150800954 is in use, would correct imap and clear inode imap claims a free inode 2150800955 is in use, would correct imap and clear inode imap claims a free inode 2162026750 is in use, would correct imap and clear inode imap claims a free inode 2186188557 is in use, would correct imap and clear inode imap claims a free inode 2186188562 is in use, would correct imap and clear inode imap claims a free inode 2186188570 is in use, would correct imap and clear inode imap claims a free inode 2186188572 is in use, would correct imap and clear inode imap claims a free inode 2531456341 is in use, would correct imap and clear inode imap claims a free inode 2531456343 is in use, would correct imap and clear inode imap claims in-use inode 2531456355 is free, would correct imap imap claims in-use inode 2531456371 is free, would correct imap imap claims in-use inode 2531456372 is free, would correct imap imap claims a free inode 2559354427 is in use, would correct imap and clear inode imap claims a free inode 2559354428 is in use, would correct imap and clear inode imap claims a free inode 2559354429 is in use, would correct imap and clear inode imap claims a free inode 2559354430 is in use, would correct imap and clear inode imap claims a free inode 2559354431 is in use, would correct imap and clear inode data fork in ino 2559366213 claims free block 319920772 data fork in ino 2559366214 claims free block 319920773 data fork in ino 2559366215 claims free block 319920774 data fork in ino 2559366216 claims free block 319920775 - agno = 2 - agno = 3 - agno = 4 data fork in ino 8856043336 claims free block 1935474394 data fork in ino 8856043337 claims free block 1922587378 data fork in ino 8856043338 claims free block 1922636137 data fork in ino 8856043339 claims free block 1922637481 data fork in ino 8856043340 claims free block 1922647241 - agno = 5 - agno = 6 - agno = 7 data fork in ino 15381180090 claims free block 1922647247 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... free space (1,414547-414547) only seen by one free space btree free space (1,4680939-4680939) only seen by one free space btree - check for inodes claiming duplicate blocks... - agno = 0 - agno = 4 - agno = 1 - agno = 5 - agno = 2 - agno = 3 - agno = 6 - agno = 7 entry "GoP-0.xml" in shortform directory 2552659806 references free inode 2162026750 would have junked entry "GoP-0.xml" in directory inode 2552659806 entry "GoP-0.xml" in shortform directory 2557517577 references free inode 2150800954 would have junked entry "GoP-0.xml" in directory inode 2557517577 entry "GoP-3.xml" in shortform directory 2557517577 references free inode 2150800955 would have junked entry "GoP-3.xml" in directory inode 2557517577 entry "GoP-0.xml" in shortform directory 2558349525 references free inode 2531456341 would have junked entry "GoP-0.xml" in directory inode 2558349525 entry "GoP-0.xml" in shortform directory 2558370556 references free inode 2559354427 would have junked entry "GoP-0.xml" in directory inode 2558370556 entry "GoP-0.xml" in shortform directory 2558376658 references free inode 2559354428 would have junked entry "GoP-0.xml" in directory inode 2558376658 entry "GoP-3.xml" in shortform directory 2558376658 references free inode 2559354429 would have junked entry "GoP-3.xml" in directory inode 2558376658 entry "GoP-4.xml" in shortform directory 2558376658 references free inode 2559354430 would have junked entry "GoP-4.xml" in directory inode 2558376658 entry "GoP-5.xml" in shortform directory 2558376658 references free inode 2559354431 would have junked entry "GoP-5.xml" in directory inode 2558376658 entry "GoP-2.xml" in shortform directory 2559237101 references free inode 2186188557 would have junked entry "GoP-2.xml" in directory inode 2559237101 entry "GoP-3.xml" in shortform directory 2559237101 references free inode 2186188562 would have junked entry "GoP-3.xml" in directory inode 2559237101 entry "GoP-4.xml" in shortform directory 2559237101 references free inode 2186188570 would have junked entry "GoP-4.xml" in directory inode 2559237101 entry "GoP-5.xml" in shortform directory 2559237101 references free inode 2186188572 would have junked entry "GoP-5.xml" in directory inode 2559237101 entry "GoP-1.xml" in shortform directory 943000127 references free inode 968429347 would have junked entry "GoP-1.xml" in directory inode 943000127 entry "com.plexapp.plugins.library.db-2022-01-28" at block 0 offset 456 in directory inode 952552260 references free inode 967996424 would clear inode number in entry at offset 456... entry "com.plexapp.plugins.library.blobs.db-2022-01-28" at block 0 offset 512 in directory inode 952552260 references free inode 968429338 would clear inode number in entry at offset 512... setting reflink flag on inode 13419939838 Missing reference count record for (6/67020783) len 23 count 2 setting reflink flag on inode 13419941093 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... entry "GoP-1.xml" in shortform directory inode 943000127 points to free inode 968429347 would junk entry entry "com.plexapp.plugins.library.db-2022-01-28" in directory inode 952552260 points to free inode 967996424, would junk entry entry "com.plexapp.plugins.library.blobs.db-2022-01-28" in directory inode 952552260 points to free inode 968429338, would junk entry bad hash table for directory inode 952552260 (no data entry): would rebuild would rebuild directory inode 952552260 entry "GoP-0.xml" in shortform directory inode 2552659806 points to free inode 2162026750 would junk entry entry "GoP-0.xml" in shortform directory inode 2557517577 points to free inode 2150800954 would junk entry entry "GoP-3.xml" in shortform directory inode 2557517577 points to free inode 2150800955 would junk entry entry "GoP-0.xml" in shortform directory inode 2558349525 points to free inode 2531456341 would junk entry entry "GoP-0.xml" in shortform directory inode 2558370556 points to free inode 2559354427 would junk entry entry "GoP-0.xml" in shortform directory inode 2558376658 points to free inode 2559354428 would junk entry entry "GoP-3.xml" in shortform directory inode 2558376658 points to free inode 2559354429 would junk entry entry "GoP-4.xml" in shortform directory inode 2558376658 points to free inode 2559354430 would junk entry entry "GoP-5.xml" in shortform directory inode 2558376658 points to free inode 2559354431 would junk entry entry "GoP-2.xml" in shortform directory inode 2559237101 points to free inode 2186188557 would junk entry entry "GoP-3.xml" in shortform directory inode 2559237101 points to free inode 2186188562 would junk entry entry "GoP-4.xml" in shortform directory inode 2559237101 points to free inode 2186188570 would junk entry entry "GoP-5.xml" in shortform directory inode 2559237101 points to free inode 2186188572 would junk entry - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 1446280202, would move to lost+found disconnected inode 1446280205, would move to lost+found disconnected inode 1446280206, would move to lost+found disconnected inode 2150800951, would move to lost+found disconnected inode 2150800960, would move to lost+found disconnected inode 2531456370, would move to lost+found disconnected inode 2559354391, would move to lost+found disconnected inode 2559354426, would move to lost+found disconnected inode 4745493083, would move to lost+found disconnected inode 7445354885, would move to lost+found disconnected inode 7445354887, would move to lost+found disconnected inode 7445362671, would move to lost+found disconnected inode 8856043328, would move to lost+found disconnected inode 8856043329, would move to lost+found disconnected inode 13419945435, would move to lost+found disconnected inode 15381180076, would move to lost+found disconnected inode 15382248683, would move to lost+found Phase 7 - verify link counts... would have reset inode 2531456370 nlinks from 0 to 1 No modify flag set, skipping filesystem flush and exiting. Quote Link to comment
itimpi Posted February 7, 2022 Share Posted February 7, 2022 That is indicating that a significant amount of corruption is being found on the emulated drive which could lead to data loss if you simply rebuild the disk. I would suggest try mounting the physical drive in read-only mode using Unassigned Devices to see if that mounts OK. If it does then the best way forward is likely to be to assume the physical disk is OK and rebuild parity instead. If you still have the disabled disk plugged in then you could also try running xfs_repair -n /dev/sdX1 from a console session (where X corresponds to the drive on the Main tab) to see what that reports. What is the state of your backup strategy? You should always have backups (preferably offline) of anything important. Quote Link to comment
Beijergard Posted February 7, 2022 Author Share Posted February 7, 2022 (edited) Ok, I will try and mount it in Unassigned Devices. I'm a bit confused by "which could lead to data loss if you simply rebuild the disk" and "assume the physical disk is OK and rebuild parity instead". Is there a difference between rebuild the disk and rebuild party? I do not have disabled disk plugin yet. Well my backup is probably a bit optimistic, I have about 1TB of photos in raw format in this array. If they were jpegs i would have compressed them on my Google drive, but that wont work with raw. Edit. Now come to think of it, could this corrupted data be mismatches in the parity caused by moving folders manually in MC from a cache drive I wanted to stop using about one week ago? Edited February 7, 2022 by Beijergard Quote Link to comment
trurl Posted February 7, 2022 Share Posted February 7, 2022 5 hours ago, Beijergard said: Disk 1 failed during Parity check. After a reboot the drive is Unmountable. Was this a correcting parity check? For future reference, it would have been better if you had gotten diagnostics before rebooting (and with the array started) and posted them. Then we would have had a good idea what caused disk1 to become disabled and other details about your situation, some of which you may not have noticed. The reason I asked if it was a correcting parity check, is because you may have corrupted parity due to whatever problems you have, and it is possible the array can't emulate the disabled disk now so that is the reason it is unmountable. Or you may still be having hardware problems which makes emulation not work well. After trying to mount the physical disk as an Unassigned device, and with the array started, get diagnostics and attach them to your NEXT post in this thread. Quote Link to comment
itimpi Posted February 7, 2022 Share Posted February 7, 2022 1 hour ago, Beijergard said: Is there a difference between rebuild the disk and rebuild party Yes - an important one rebuilding the disk makes the contents of the physical disk match what you see on the emulated disk. Therefore any problems on the emulated disk (e.g. file system corruption) will also apply to the physical disk after a rebuild. rebuilding the parity assumes the physical disk contents are Ok and makes parity agree with what is on the physical disk. Quote Link to comment
Beijergard Posted February 7, 2022 Author Share Posted February 7, 2022 46 minutes ago, trurl said: Was this a correcting parity check? I do not know, it was a scheduled montly check.. 46 minutes ago, trurl said: After trying to mount the physical disk as an Unassigned device, and with the array started, get diagnostics and attach them to your NEXT post in this thread. I tried to mount it in unassigned but nothing seemed to happen. Downloaded diagnostics, attaching it in this post. plexworm-diagnostics-20220207-1517.zip Quote Link to comment
trurl Posted February 7, 2022 Share Posted February 7, 2022 38 minutes ago, Beijergard said: I do not know, it was a scheduled montly check.. You can check the settings for the scheduled check in Settings - Scheduler. If it is set to correct, change it. You don't want unnoticed hardware problems to corrupt parity. Quote Link to comment
trurl Posted February 7, 2022 Share Posted February 7, 2022 1 hour ago, trurl said: with the array started, get diagnostics and attach them to your NEXT post in this thread. Quote Link to comment
Beijergard Posted February 7, 2022 Author Share Posted February 7, 2022 (edited) 12 minutes ago, trurl said: You can check the settings for the scheduled check in Settings - Scheduler. If it is set to correct, change it. You don't want unnoticed hardware problems to corrupt parity. Corrections are set to Yes. 7 minutes ago, trurl said: with the array started, get diagnostics and attach them to your NEXT post in this thread. Just to be clear, shall Disk 1 still be unassigned or shall I put the drive back as Disk 1? "Disk 1 Missing no device ST8000VN004-2M2101_WKD03SNJ - 8 TB Array Operation Stopped. Missing disk. Start will disable the missing disk and then bring the array on-line. Install a replacement disk as soon as possible. Yes, I want to do this" Edited February 7, 2022 by Beijergard Quote Link to comment
trurl Posted February 7, 2022 Share Posted February 7, 2022 25 minutes ago, Beijergard said: Corrections are set to Yes. 33 minutes ago, trurl said: If it is set to correct, change it. I don't need new diagnostics, I can see from syslog in those earlier diagnostics that emulated disk1 was unmountable, and the physical disk was also unmountable as an Unassigned Device. I guess at this point we will have to try to repair the filesystem of the emulated disk. 3 hours ago, Beijergard said: I have checked the XFS file system with the option -n now and these are the results. 3 hours ago, itimpi said: That is indicating that a significant amount of corruption is being found on the emulated drive We could also try filesystem repair on the physical disk as an Unassigned Device and see which gives the better results. 3 hours ago, itimpi said: If you still have the disabled disk plugged in then you could also try running xfs_repair -n /dev/sdX from a console session (where X corresponds to the drive on the Main tab) to see what that reports. sdX was sdb in those earlier diagnostics. You also have to specify the partition for disks that are not in the array, so it would be /dev/sdb1. Quote Link to comment
trurl Posted February 7, 2022 Share Posted February 7, 2022 Be sure to capture the output of filesystem checks so you can post them. Quote Link to comment
Beijergard Posted February 7, 2022 Author Share Posted February 7, 2022 11 minutes ago, trurl said: Be sure to capture the output of filesystem checks so you can post them. With the drive in Unassigned devices i pressed the checkmark which started a file system check with this output Spoiler FS: xfs Executing file system check: /sbin/xfs_repair -n /dev/sdb1 2>&1 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... block (1,414548-414548) multiply claimed by cnt space tree, state - 2 block (1,9817-9817) multiply claimed by cnt space tree, state - 2 agf_freeblks 8805144, counted 8805149 in ag 7 agf_freeblks 69965104, counted 69965116 in ag 1 agi_freecount 87, counted 90 in ag 1 agi unlinked bucket 50 is 383972722 in ag 1 (inode=2531456370) sb_ifree 887, counted 896 sb_fdblocks 633181712, counted 646815531 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 data fork in ino 415890952 claims free block 121079803 imap claims a free inode 967996424 is in use, would correct imap and clear inode imap claims a free inode 968429338 is in use, would correct imap and clear inode imap claims a free inode 968429347 is in use, would correct imap and clear inode imap claims a free inode 1446280125 is in use, would correct imap and clear inode imap claims a free inode 1446280127 is in use, would correct imap and clear inode - agno = 1 data fork in ino 2147573505 claims free block 268445271 data fork in ino 2147573506 claims free block 268445272 imap claims a free inode 2150800954 is in use, would correct imap and clear inode imap claims a free inode 2150800955 is in use, would correct imap and clear inode imap claims a free inode 2162026750 is in use, would correct imap and clear inode imap claims a free inode 2186188557 is in use, would correct imap and clear inode imap claims a free inode 2186188562 is in use, would correct imap and clear inode imap claims a free inode 2186188570 is in use, would correct imap and clear inode imap claims a free inode 2186188572 is in use, would correct imap and clear inode imap claims a free inode 2531456341 is in use, would correct imap and clear inode imap claims a free inode 2531456343 is in use, would correct imap and clear inode imap claims in-use inode 2531456355 is free, would correct imap imap claims in-use inode 2531456371 is free, would correct imap imap claims in-use inode 2531456372 is free, would correct imap imap claims a free inode 2559354427 is in use, would correct imap and clear inode imap claims a free inode 2559354428 is in use, would correct imap and clear inode imap claims a free inode 2559354429 is in use, would correct imap and clear inode imap claims a free inode 2559354430 is in use, would correct imap and clear inode imap claims a free inode 2559354431 is in use, would correct imap and clear inode data fork in ino 2559366213 claims free block 319920772 data fork in ino 2559366214 claims free block 319920773 data fork in ino 2559366215 claims free block 319920774 data fork in ino 2559366216 claims free block 319920775 - agno = 2 - agno = 3 - agno = 4 data fork in ino 8856043336 claims free block 1935474394 data fork in ino 8856043337 claims free block 1922587378 data fork in ino 8856043338 claims free block 1922636137 data fork in ino 8856043339 claims free block 1922637481 data fork in ino 8856043340 claims free block 1922647241 - agno = 5 - agno = 6 - agno = 7 data fork in ino 15381180090 claims free block 1922647247 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... free space (1,414547-414547) only seen by one free space btree free space (1,4680939-4680939) only seen by one free space btree - check for inodes claiming duplicate blocks... - agno = 0 - agno = 7 - agno = 6 - agno = 1 - agno = 3 - agno = 2 - agno = 5 - agno = 4 entry "GoP-0.xml" in shortform directory 2552659806 references free inode 2162026750 would have junked entry "GoP-0.xml" in directory inode 2552659806 entry "GoP-0.xml" in shortform directory 2557517577 references free inode 2150800954 would have junked entry "GoP-0.xml" in directory inode 2557517577 entry "GoP-3.xml" in shortform directory 2557517577 references free inode 2150800955 would have junked entry "GoP-3.xml" in directory inode 2557517577 entry "GoP-0.xml" in shortform directory 2558349525 references free inode 2531456341 would have junked entry "GoP-0.xml" in directory inode 2558349525 entry "GoP-0.xml" in shortform directory 2558370556 references free inode 2559354427 would have junked entry "GoP-0.xml" in directory inode 2558370556 entry "GoP-0.xml" in shortform directory 2558376658 references free inode 2559354428 would have junked entry "GoP-0.xml" in directory inode 2558376658 entry "GoP-3.xml" in shortform directory 2558376658 references free inode 2559354429 would have junked entry "GoP-3.xml" in directory inode 2558376658 entry "GoP-4.xml" in shortform directory 2558376658 references free inode 2559354430 would have junked entry "GoP-4.xml" in directory inode 2558376658 entry "GoP-5.xml" in shortform directory 2558376658 references free inode 2559354431 would have junked entry "GoP-5.xml" in directory inode 2558376658 entry "GoP-2.xml" in shortform directory 2559237101 references free inode 2186188557 would have junked entry "GoP-2.xml" in directory inode 2559237101 entry "GoP-3.xml" in shortform directory 2559237101 references free inode 2186188562 would have junked entry "GoP-3.xml" in directory inode 2559237101 entry "GoP-4.xml" in shortform directory 2559237101 references free inode 2186188570 would have junked entry "GoP-4.xml" in directory inode 2559237101 entry "GoP-5.xml" in shortform directory 2559237101 references free inode 2186188572 would have junked entry "GoP-5.xml" in directory inode 2559237101 entry "GoP-1.xml" in shortform directory 943000127 references free inode 968429347 would have junked entry "GoP-1.xml" in directory inode 943000127 entry "com.plexapp.plugins.library.db-2022-01-28" at block 0 offset 456 in directory inode 952552260 references free inode 967996424 would clear inode number in entry at offset 456... entry "com.plexapp.plugins.library.blobs.db-2022-01-28" at block 0 offset 512 in directory inode 952552260 references free inode 968429338 would clear inode number in entry at offset 512... Missing reference count record for (6/67020783) len 23 count 2 setting reflink flag on inode 13419939838 setting reflink flag on inode 13419941093 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... entry "GoP-1.xml" in shortform directory inode 943000127 points to free inode 968429347 would junk entry entry "com.plexapp.plugins.library.db-2022-01-28" in directory inode 952552260 points to free inode 967996424, would junk entry entry "com.plexapp.plugins.library.blobs.db-2022-01-28" in directory inode 952552260 points to free inode 968429338, would junk entry bad hash table for directory inode 952552260 (no data entry): would rebuild would rebuild directory inode 952552260 entry "GoP-0.xml" in shortform directory inode 2552659806 points to free inode 2162026750 would junk entry entry "GoP-0.xml" in shortform directory inode 2557517577 points to free inode 2150800954 would junk entry entry "GoP-3.xml" in shortform directory inode 2557517577 points to free inode 2150800955 would junk entry entry "GoP-0.xml" in shortform directory inode 2558349525 points to free inode 2531456341 would junk entry entry "GoP-0.xml" in shortform directory inode 2558370556 points to free inode 2559354427 would junk entry entry "GoP-0.xml" in shortform directory inode 2558376658 points to free inode 2559354428 would junk entry entry "GoP-3.xml" in shortform directory inode 2558376658 points to free inode 2559354429 would junk entry entry "GoP-4.xml" in shortform directory inode 2558376658 points to free inode 2559354430 would junk entry entry "GoP-5.xml" in shortform directory inode 2558376658 points to free inode 2559354431 would junk entry entry "GoP-2.xml" in shortform directory inode 2559237101 points to free inode 2186188557 would junk entry entry "GoP-3.xml" in shortform directory inode 2559237101 points to free inode 2186188562 would junk entry entry "GoP-4.xml" in shortform directory inode 2559237101 points to free inode 2186188570 would junk entry entry "GoP-5.xml" in shortform directory inode 2559237101 points to free inode 2186188572 would junk entry - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 1446280202, would move to lost+found disconnected inode 1446280205, would move to lost+found disconnected inode 1446280206, would move to lost+found disconnected inode 2150800951, would move to lost+found disconnected inode 2150800960, would move to lost+found disconnected inode 2531456370, would move to lost+found disconnected inode 2559354391, would move to lost+found disconnected inode 2559354426, would move to lost+found disconnected inode 4745493083, would move to lost+found disconnected inode 7445354885, would move to lost+found disconnected inode 7445354887, would move to lost+found disconnected inode 7445362671, would move to lost+found disconnected inode 8856043328, would move to lost+found disconnected inode 8856043329, would move to lost+found disconnected inode 13419945435, would move to lost+found disconnected inode 15381180076, would move to lost+found disconnected inode 15382248683, would move to lost+found Phase 7 - verify link counts... would have reset inode 2531456370 nlinks from 0 to 1 No modify flag set, skipping filesystem flush and exiting. I feel like i'm way out of my comfort zone here when it comes to command lines, yes of course I can just copy and paste them but I have almost no idea what I am doing. I don't know if i'm supposed to run xfs_repair -n /dev/sd1 or xfs_repair -n /dev/sdb1. Quote Link to comment
trurl Posted February 7, 2022 Share Posted February 7, 2022 2 minutes ago, Beijergard said: With the drive in Unassigned devices i pressed the checkmark which started a file system check with this output That's OK, didn't remember you could do that in the webUI with Unassigned. Unfortunately those results don't look great either. I guess we will just have to hope for the best. Go ahead and remove -n (nomodify) and repair the emulated filesystem md1. Probably will have to also add -L Quote Link to comment
Beijergard Posted February 7, 2022 Author Share Posted February 7, 2022 2 minutes ago, trurl said: Go ahead and remove -n (nomodify) and repair the emulated filesystem md1. Probably will have to also add -L Would you be so kind to hand me the full terminal commandline for that? I will surely mess it up. Quote Link to comment
trurl Posted February 7, 2022 Share Posted February 7, 2022 You don't need to do it from the command line. Just start the array in maintenance mode, click on disk1 and under Check Filesystem, replace -n with -L then press the button Quote Link to comment
Beijergard Posted February 7, 2022 Author Share Posted February 7, 2022 Ok, now that is done, here is the output. Spoiler Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... agf_freeblks 8805144, counted 8805149 in ag 7 block (1,414548-414548) multiply claimed by cnt space tree, state - 2 block (1,9817-9817) multiply claimed by cnt space tree, state - 2 agf_freeblks 69965104, counted 69965116 in ag 1 agi_freecount 87, counted 90 in ag 1 agi unlinked bucket 50 is 383972722 in ag 1 (inode=2531456370) sb_ifree 887, counted 896 sb_fdblocks 633181712, counted 646815531 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 data fork in ino 415890952 claims free block 121079803 imap claims a free inode 967996424 is in use, correcting imap and clearing inode cleared inode 967996424 imap claims a free inode 968429338 is in use, correcting imap and clearing inode cleared inode 968429338 imap claims a free inode 968429347 is in use, correcting imap and clearing inode cleared inode 968429347 imap claims a free inode 1446280125 is in use, correcting imap and clearing inode cleared inode 1446280125 imap claims a free inode 1446280127 is in use, correcting imap and clearing inode cleared inode 1446280127 - agno = 1 data fork in ino 2147573505 claims free block 268445271 data fork in ino 2147573506 claims free block 268445272 imap claims a free inode 2150800954 is in use, correcting imap and clearing inode cleared inode 2150800954 imap claims a free inode 2150800955 is in use, correcting imap and clearing inode cleared inode 2150800955 imap claims a free inode 2162026750 is in use, correcting imap and clearing inode cleared inode 2162026750 imap claims a free inode 2186188557 is in use, correcting imap and clearing inode cleared inode 2186188557 imap claims a free inode 2186188562 is in use, correcting imap and clearing inode cleared inode 2186188562 imap claims a free inode 2186188570 is in use, correcting imap and clearing inode cleared inode 2186188570 imap claims a free inode 2186188572 is in use, correcting imap and clearing inode cleared inode 2186188572 imap claims a free inode 2531456341 is in use, correcting imap and clearing inode cleared inode 2531456341 imap claims a free inode 2531456343 is in use, correcting imap and clearing inode cleared inode 2531456343 correcting imap correcting imap correcting imap imap claims a free inode 2559354427 is in use, correcting imap and clearing inode cleared inode 2559354427 imap claims a free inode 2559354428 is in use, correcting imap and clearing inode cleared inode 2559354428 imap claims a free inode 2559354429 is in use, correcting imap and clearing inode cleared inode 2559354429 imap claims a free inode 2559354430 is in use, correcting imap and clearing inode cleared inode 2559354430 imap claims a free inode 2559354431 is in use, correcting imap and clearing inode cleared inode 2559354431 data fork in ino 2559366213 claims free block 319920772 data fork in ino 2559366214 claims free block 319920773 data fork in ino 2559366215 claims free block 319920774 data fork in ino 2559366216 claims free block 319920775 - agno = 2 - agno = 3 - agno = 4 data fork in ino 8856043336 claims free block 1935474394 data fork in ino 8856043337 claims free block 1922587378 data fork in ino 8856043338 claims free block 1922636137 data fork in ino 8856043339 claims free block 1922637481 data fork in ino 8856043340 claims free block 1922647241 - agno = 5 - agno = 6 - agno = 7 data fork in ino 15381180090 claims free block 1922647247 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 2 - agno = 5 - agno = 4 - agno = 6 - agno = 3 - agno = 0 - agno = 1 - agno = 7 entry "GoP-0.xml" in shortform directory 2552659806 references free inode 2162026750 junking entry "GoP-0.xml" in directory inode 2552659806 entry "GoP-0.xml" in shortform directory 2557517577 references free inode 2150800954 junking entry "GoP-0.xml" in directory inode 2557517577 entry "GoP-3.xml" in shortform directory 2557517577 references free inode 2150800955 junking entry "GoP-3.xml" in directory inode 2557517577 entry "GoP-0.xml" in shortform directory 2558349525 references free inode 2531456341 junking entry "GoP-0.xml" in directory inode 2558349525 entry "GoP-0.xml" in shortform directory 2558370556 references free inode 2559354427 junking entry "GoP-0.xml" in directory inode 2558370556 entry "GoP-0.xml" in shortform directory 2558376658 references free inode 2559354428 junking entry "GoP-0.xml" in directory inode 2558376658 entry "GoP-3.xml" in shortform directory 2558376658 references free inode 2559354429 junking entry "GoP-3.xml" in directory inode 2558376658 entry "GoP-4.xml" in shortform directory 2558376658 references free inode 2559354430 junking entry "GoP-4.xml" in directory inode 2558376658 entry "GoP-5.xml" in shortform directory 2558376658 references free inode 2559354431 junking entry "GoP-5.xml" in directory inode 2558376658 entry "GoP-2.xml" in shortform directory 2559237101 references free inode 2186188557 junking entry "GoP-2.xml" in directory inode 2559237101 entry "GoP-3.xml" in shortform directory 2559237101 references free inode 2186188562 junking entry "GoP-3.xml" in directory inode 2559237101 entry "GoP-4.xml" in shortform directory 2559237101 references free inode 2186188570 junking entry "GoP-4.xml" in directory inode 2559237101 entry "GoP-5.xml" in shortform directory 2559237101 references free inode 2186188572 junking entry "GoP-5.xml" in directory inode 2559237101 entry "GoP-1.xml" in shortform directory 943000127 references free inode 968429347 junking entry "GoP-1.xml" in directory inode 943000127 entry "com.plexapp.plugins.library.db-2022-01-28" at block 0 offset 456 in directory inode 952552260 references free inode 967996424 clearing inode number in entry at offset 456... entry "com.plexapp.plugins.library.blobs.db-2022-01-28" at block 0 offset 512 in directory inode 952552260 references free inode 968429338 clearing inode number in entry at offset 512... setting reflink flag on inode 13419939838 Missing reference count record for (6/67020783) len 23 count 2 setting reflink flag on inode 13419941093 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... bad hash table for directory inode 952552260 (no data entry): rebuilding rebuilding directory inode 952552260 - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 1446280202, moving to lost+found disconnected inode 1446280205, moving to lost+found disconnected inode 1446280206, moving to lost+found disconnected inode 2150800951, moving to lost+found disconnected inode 2150800960, moving to lost+found disconnected inode 2531456370, moving to lost+found disconnected inode 2559354391, moving to lost+found disconnected inode 2559354426, moving to lost+found disconnected inode 4745493083, moving to lost+found disconnected inode 7445354885, moving to lost+found disconnected inode 7445354887, moving to lost+found disconnected inode 7445362671, moving to lost+found disconnected inode 8856043328, moving to lost+found disconnected inode 8856043329, moving to lost+found disconnected inode 13419945435, moving to lost+found disconnected inode 15381180076, moving to lost+found disconnected inode 15382248683, moving to lost+found Phase 7 - verify and correct link counts... Maximum metadata LSN (41:3549503) is ahead of log (1:2). Format log to cycle 44. done Quote Link to comment
trurl Posted February 7, 2022 Share Posted February 7, 2022 OK, looks like repair completed on emulated disk1. Start the array in normal mode (not maintenance) and post new diagnostics. Quote Link to comment
Beijergard Posted February 7, 2022 Author Share Posted February 7, 2022 Ok, the disk is now visible and the array is back online. Here is the diagnostics. plexworm-diagnostics-20220207-1740.zip Quote Link to comment
trurl Posted February 7, 2022 Share Posted February 7, 2022 That's confusing. The diagnostics shows physical disk1 assigned, not disabled, and mounted. We were supposed to be repairing the emulated disk1 with the physical disk unassigned because it had been disabled. What did you do to get to this state? Have you looked at your lost+found share? Quote Link to comment
trurl Posted February 7, 2022 Share Posted February 7, 2022 1 minute ago, trurl said: What did you do to get to this state? You haven't had time to actually rebuild disk1 or to rebuild parity, so what did you do? Quote Link to comment
trurl Posted February 7, 2022 Share Posted February 7, 2022 I can only guess that disk1 was never disabled to begin with. If that is the case, then what exactly did you mean by this? 9 hours ago, Beijergard said: Disk 1 failed during Parity check Quote Link to comment
Beijergard Posted February 7, 2022 Author Share Posted February 7, 2022 (edited) 12 minutes ago, trurl said: That's confusing. The diagnostics shows physical disk1 assigned, not disabled, and mounted. We were supposed to be repairing the emulated disk1 with the physical disk unassigned because it had been disabled. What did you do to get to this state? Have you looked at your lost+found share? I never saw the disk as disabled. The lost and found just contained 17 files named with a lot of numbers, and filesize from 20-100kB, so I guess nothing too important. 8 minutes ago, trurl said: Disk 1 failed during Parity check I might have used wrong words(if so, im sorry), the Parity check said Disk 1 has read errors, see jpg. Edited February 7, 2022 by Beijergard 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.