thirtythreemangos
Members
-
Joined
-
Last visited
Solutions
-
thirtythreemangos's post in "Device is disabled, contents emulated" error. Continuing issues was marked as the answer@trurl So I got it figured out, more or less. I removed that drive, reapplied the kapton tape to the 3.3v pin making extra effort to be thorough and complete and have it stick well and appropriately, reinstalled the drive, booted into safe mode, ran another SMART check on the drive (which again produced no error messages), started the array in maintenance mode and added the drive to the array, performed an XFS filesystem check first with the -nv and then again without, and then again re-built the drive onto itself. I can only guess that the original kapton tape was the true culprit, as when initially trying to re-build the drive produced a slew of UDMA CRC errors and an array failure, but booting in safe mode, starting array in maintenance mode, running the checks, and then re-building in that mode seemed to fix it. When rebuilding the drive, I DID get maybe another 10 UDMA CRC errors, but nothing like the 4744 of them that caused this whole debacle. But thank you everyone for the input. Hopefully anyone finding this post may consider the kapton tape as a potential culprit for similar issues. I'll eventually phase out those shucked drives that require the 3.3v pin fix (or perhaps there is an actually reliable adapter out there for this specific type use?), but the budget is not there presently.