April 18, 20215 yr My data drive is showing up as disabled due to unsafe shutdown. What can I do to bring the data disk back running. I tried following https://wiki.unraid.net/Manual/Storage_Management#Checking_a_File_System and did the check and got the following, but didnt know what to do next. Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - 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 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 3 - agno = 0 - agno = 2 - agno = 4 - agno = 5 - agno = 7 - agno = 6 - agno = 8 - agno = 9 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. I'm attaching my diagnostic and SMART report for the drive as well. Also noticing 1 more thing, I have 2 devices as cache (2x 500gb pool). But the cache is showing as only 1 device. Is that normal? When I bring array offline, I have the option to mount the 2nd cache drive unmhn-diagnostics-20210418-1316.zip unmhn-smart-20210418-1316.zip
April 18, 20215 yr Only reason for a disk to be disabled is because a write to it failed. Usual reason is poor cabling connections, but if there happened to be a power blip during a write and no UPS, then that could also explain it. Either way, to rebuild onto itself. Stop Array Unassign the disk Start Array Stop Array Reassign the disk Start Array It'll begin rebuilding the data
Archived
This topic is now archived and is closed to further replies.