August 10, 20178 yr I was showing a buddy my setup. He inquired about my storage system and how the drives connected. Without thinking, I popped a drive out to show him. Now the drive is showing "device disabled, contents emulated". I'm confident the drive is fine. How can I enable it and make it part of the array again? I just kicked off a parity check, but that will take 12+ hours to run. Thanks.
August 10, 20178 yr Community Expert 44 minutes ago, pman said: I was showing a buddy my setup. He inquired about my storage system and how the drives connected. Without thinking, I popped a drive out to show him. Now the drive is showing "device disabled, contents emulated". I'm confident the drive is fine. How can I enable it and make it part of the array again? I just kicked off a parity check, but that will take 12+ hours to run. Thanks. Unless you have dual parity it's not actually possible to do a parity check with a disabled disk. Are you sure you aren't rebuilding the disk you removed instead? That would actually be the correct thing to do in this case and you should let it complete. Post a screenshot of Main - Array Devices showing the read/write columns of all disks, and also a screenshot of Main - Array Operation.
August 10, 20178 yr Community Expert 6 hours ago, pman said: How can I enable it and make it part of the array again? See below: https://wiki.lime-technology.com/Troubleshooting#Re-enable_the_drive
August 10, 20178 yr 10 hours ago, pman said: I popped a drive out to show him. Now the drive is showing "device disabled, contents emulated". I'm confident the drive is fine. The drive is probably fine, yes, but the contents could have changed. When the slot is emulated, it can still be read, and more importantly, written to. How sure are you that no background process (docker, plugin, network machine) didn't access that drive slot while it was emulated?
August 10, 20178 yr Community Expert 2 minutes ago, jonathanm said: The drive is probably fine, yes, but the contents could have changed. When the slot is emulated, it can still be read, and more importantly, written to. How sure are you that no background process (docker, plugin, network machine) didn't access that drive slot while it was emulated? Exactly why I said you should rebuild the drive. If the emulated drive was written, then the physical drive is no longer valid. It is out of sync with parity, and even possibly corrupt if filesystem metadata is out of sync.
Archived
This topic is now archived and is closed to further replies.