December 17, 20241 yr I installed an HBA card (2x miniSAS to 8x sata. ) i got everythign up and the array was running. A couple hours later I get an error about disk errors on disk 6 and 7 (7 was a new disk i added to the array before installing the HBA card, its pretty much empty, and has no important files) shutdown the server and reseated the sata connectors on 6 and 7 aswell as reseated the miniSAS side of the cables. i booted the server backup and it said (iirc) disk7 was there but was unmountable. I knew i didn't have important data on it so I told it to format. After the format it still says disk 7 is "Device disabled, Contents Emulated" which i assume means its figuring it out based off parity. i have an option to a "Read-Check" I wasn't sure if it was the new HBA card so i moved disk7 back to a sata port on the motherboard, but no change in unraid. I did stop the array, unassigned the drive, mounted it with unassigned devices and saw the folder's for the two movies that would have been recently added. Which... doesn't make sense, since I just allegedly reformatted it? but it does seem to mean it CAN access data in the drive, so why is it disabled and emulated? I'm not really sure what to do here. I'd like to just readded the blank drive if i can. Maybe zero the drive?I'm sure its probably fairly simple, but I'm gonna stop touching it so i don't break anything, if i haven't already. Thanks crusty-diagnostics-20241217-1645.zip
December 17, 20241 yr Author did a xfs filesystem check. here are the results 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 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - agno = 17 - agno = 18 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 1 - agno = 3 - agno = 16 - agno = 7 - agno = 6 - agno = 10 - agno = 11 - agno = 8 - agno = 9 - agno = 4 - agno = 13 - agno = 17 - agno = 14 - agno = 15 - agno = 18 - agno = 5 - agno = 12 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.
December 18, 20241 yr Community Expert Solution Diags are after a reboot so we can't see why the disk got disabled, but after a disk gets disable it needs to be rebuilt: https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself
December 18, 20241 yr Author Ahh, i knew it would be simple, just couldn't find that article. rebuilding now. I will keep in mind that I need to take diagnostics BEFORE a reboot in the future. Thanks
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.