September 18Sep 18 I've gotten some odd errors with my hdds recently. One drive was showing as disabled, so i removed it and rebuilt it from parity. Was working ok for a few days and then added a second parity drive to ensure everything would be ok. Now the 2nd parity isn't showing up in the array and the original parity is showing disabled with the 1st original drive now showing as Unmountable: wrong or no file system. I tried replacing power cables, sas cables, and power supply. Anyone know what the best next steps are? diagnostics-20260918-1539.zip
September 19Sep 19 Community Expert Diags are after rebooting, so we can't see what happened. Start by check filesystem on disk1Parity SMART doesn't look very good; run an extended SMART test.
September 19Sep 19 Author results of the check disk 1 and another diagnostic found previously. I think that was after a reboot unfortunately. Will add the extended smart test after it completes. check_disk1_20260919.txt diagnostics-20260914-1842.zip
September 19Sep 19 Author When I attempt to fix disk1, should I continue with the zero log?Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If the filesystem is a snapshot of a mounted filesystem, you may need to give mount the nouuid option. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. Edited September 19Sep 19 by ricerony
September 19Sep 19 Community Expert Yep, continue; it's the only option since the disk doesn't mount and typically fine.
September 19Sep 19 Author Thank you, disk 1 is now back in the array. Will probably place the other drive in parity 2 after the smart test.
September 21Sep 21 Author Parity 1 was stuck at 100% yesterday after 30 hours. Restarted it yesterday and its showing up at 100% again, but not finishing. Does it need more time or is stuck somewhere? Here is the smartctl output=== START OF INFORMATION SECTION ===Vendor: IBM-ESXSProduct: ST14000NM0288 ERevision: ECH8Compliance: SPC-5User Capacity: 13,902,809,137,152 bytes [13.9 TB]Logical block size: 4096 bytesLU is fully provisionedRotation Rate: 7200 rpmForm Factor: 3.5 inchesLogical Unit id: 0x5000c500aec78203Serial number: ZHZ4Y02M0000J830VTSUDevice type: diskTransport protocol: SAS (SPL-4)Local Time is: Mon Sep 21 06:50:28 2026 CDTSMART support is: Available - device has SMART capability.SMART support is: EnabledTemperature Warning: Enabled=== START OF READ SMART DATA SECTION ===SMART Health Status: Data channel impending failure data error rate too high [asc=5d, ascq=32]Grown defects during certification <not available>Total blocks reassigned during format <not available>Total new blocks reassigned = 500Power on minutes since format <not available>Current Drive Temperature: 38 CDrive Trip Temperature: 65 CAccumulated power on time, hours:minutes 49038:18Elements in grown defect list: 505Error counter log:Errors Corrected by Total Correction Gigabytes TotalECC rereads/ errors algorithm processed uncorrectedfast | delayed rewrites corrected invocations [10^9 bytes] errorsread: 0 6615 0 6615 25278 796680.496 3581write: 0 0 0 0 0 379017.683 0verify: 0 0 0 0 0 17404.574 0Non-medium error count: 1Pending defect count:0 Pending DefectsSelf-test execution status: 0% of test remainingSMART Self-test logNum Test Status segment LifeTime LBA_first_err [SK ASC ASQ]Description number (hours)# 1 Background long Self test in progress ... - NOW - [- - -]# 2 Background long Aborted (by user command) - 49018 - [- - -]# 3 Background short Completed - 48667 - [- - -]# 4 Background short Completed - 30785 - [- - -]# 5 Background short Completed - 15604 - [- - -]# 6 Background short Aborted (by user command) - 2 - [- - -]Long (extended) Self-test duration: 80400 seconds [22.3 hours] Edited September 21Sep 21 by ricerony
September 21Sep 21 Community Expert Solution There's no rebuild/check in the logs, please reboot to clear them and start a new parity sync, if it stil fails, post new diags and a screesnhto from Main.
September 21Sep 21 Author Apologies, it looks like parity is still disabled. Attached are the diagnostics after reboot. Adding diagnostic when I added the other drive to parity 2.diagnostics-20260921-1120.zip diagnostics-20260921-1125.zip Edited September 21Sep 21 by ricerony
September 21Sep 21 Community Expert I see the parity2 sync now logged, see if it finishes; if not, post new diags.
September 23Sep 23 Author Thank you, parity finished with looks like 0 errors. Diagnostics attached. What should I do with the the original parity 1 drive? remove it from the array and re add it back to parity 1 to sync up again? diagnostics-20260922-1904.zip
September 23Sep 23 Community Expert 6 hours ago, ricerony said:What should I do with the the original parity 1 drive? remove it from the array and re add it back to parity 1 to sync up again?Yes, try again.
September 24Sep 24 Author Parity 1 completed with looks like 0 errors. Please do let me know if you see anything concerning. Does it make sense to have dual parity or just move parity 1 into the array until the drive dies? diagnostics-20260924-1816.zip
September 24Sep 24 Community Expert Single parity should be enough for so few array drives.You have some FCP errors and warnings you need to take care of:Sep 24 18:16:24 WOODOMUR root: Fix Common Problems: Warning: Deprecated plugin ca.mover.tuning.plg Sep 24 18:16:26 WOODOMUR root: Fix Common Problems: Error: Invalid folder cache contained within /mnt Sep 24 18:16:31 WOODOMUR root: Fix Common Problems: Warning: Share docker set to use pool cachepool, but files / folders exist on the cachhe pool Sep 24 18:16:31 WOODOMUR root: Fix Common Problems: Warning: Share system set to use pool cachepool, but files / folders exist on the cachhe poolYou should probably remove mover tuning at least until you get the other things taken care of. That version is too out-of-date to upgrade anyway.The invalid folder cache is a serious problem so it is flagged as an error. You don't have a pool named cache, instead it is named cachhe. But something is writing to the path /mnt/cache, probably some container host mapping. Since that path isn't actual storage, it is a path in rootfs, the RAM reserved for the OS. Since it is RAM, anything stored there won't survive reboot. And if you fill up that space by writing to it, it can cause problems for the OS since it will have no space to work with.The docker and system shares need to be on one pool or the other. Possibly you have duplicates you will need to clean up.
September 24Sep 24 Community Expert 7 minutes ago, trurl said:The docker and system shares need to be on one pool or the other. Possibly you have duplicates you will need to clean up.Nothing can move or delete open files so you have to go to Settings and disable Docker and disable VM Manager before you can work with those shares.
September 26Sep 26 Author Thank you, mover completed. I originally thought wrong and that I could lessen wear on the cache drive by splitting and moving it back to the array for different tasks.I still don't really understand the triggers for the disabled drives one after the other. Best guess was the power, but everything seems like it running and drives looked ok. Parity 1 has some uncorrected errors so will monitor that more closely. Edited September 26Sep 26 by ricerony
September 26Sep 26 Community Expert 13 minutes ago, ricerony said:Best guess was the powerMost likely a power/connection issue, if it happens again, make sure to grab the diags before rebooting.
September 28Sep 28 Author Let the long smart test finish out for parity 1 drive without aborting and it looks like there's an impending failure. Is the best course of action to just remove it or since I have 2 parity's just leave it and wait for it to die? SMART Health Status: Data channel impending failure data error rate too high [asc=5d, ascq=32] Pending defect count:1 Pending Defect, LBA and accumulated_power_on_hours follow 1: 0xa67d4559 , 49188SMART Self-test logNum Test Status segment LifeTime LBA_first_err [SK ASC ASQ] Description number (hours)# 1 Background long Failed in segment --> - 49188 2793227609 [0x3 0x11 0x0] smart-20260928-0630.zip
September 28Sep 28 Community Expert You can leave if for now since it's not totally failed, but since the SMART test failed, it should be replaced as soon as possible
October 2Oct 2 Author Parity 1 is back to being disabled, diagnostics attached. Looks to be a lot of errors tied to it. diagnostics-20261002-0736.zip
October 2Oct 2 Community Expert Parity also failed a SMART test, and has a lot of bad sectors, so it needs to be replaced as well.
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.