As far as non patrol edit permissions, my rule is to make it high enough to prevent new/inactive users from editing without going through Patrol but not preventing experienced users from editing without approval. This is why I set it to 10k for normal guides and 20k for guides I want to take more precautions with.
-
I'm guessing it's a C2D system since it had a 7200.12 drive. That drive was released to replace the nightmare 7200.11 (it has a tendency to lock in a BSY state) and typically doesn't show in the BIOS in that condition. It was more effective then the .11 firmware patch, but it still happened; just less often. I've seen some years later that fail to load the SMART data as well; the .11/.12 drives were terrible.
+
I'm guessing it's a C2D system since it had a 7200.12 drive. That drive was released to replace the nightmare 7200.11 (it has a tendency to lock in a BSY state) and typically doesn't show in the BIOS in that condition. It was more effective then the .11 firmware patch, but it still happened; just less often. I've seen some years later that fail to load the SMART data as well; the .11/.12 drives were both impacted.
If I had to guess at the failure it probably had a BSY failure rather then a mechanical failure. However, the drives are old enough it's now a plausible theory. Seeing 7200.11/12 is enough to get me to replace it regardless of functionality.
I've thought about doing a teardown of a drive (and have some pictures from a dead 7200.11) but I never did anything with it. I figured someone would pick up where I left off and I wish you the best in doing what I never did.
As far as non patrol edit permissions, my rule is to make it high enough to prevent new/inactive users from editing without going through Patrol but not stop someone with experience from doing it without going through Patrol. This is why I set it to 10k for normal guides and 20k for special guides I want to protect more then a standard guide.
+
As far as non patrol edit permissions, my rule is to make it high enough to prevent new/inactive users from editing without going through Patrol but not preventing experienced users from editing without approval. This is why I set it to 10k for normal guides and 20k for guides I want to take more precautions with.
I'm guessing it's a C2D system since it had a 7200.12 drive. That drive was released to replace the nightmare 7200.11 (it has a tendency to lock in a BSY state) and typically doesn't show in the BIOS in that condition. It was more effective then the .11 firmware patch, but it still happened; just less often. I've seen some years later that fail to load the SMART data as well; the .11/.12 drives were terrible.
If I had to guess at the failure it probably had a BSY failure rather then a mechanical failure. However, the drives are old enough it's now a plausible theory. Seeing 7200.11/12 is enough to get me to replace it regardless of functionality.
I've thought about doing a teardown of a drive (and have some pictures from a dead 7200.11) but I never did anything with it. I figured someone would pick up where I left off and I wish you the best in doing what I never did.
As far as non patrol edit permissions, my rule is to make it high enough to prevent new/inactive users from editing without going through Patrol but not stop someone with experience from doing it without going through Patrol. This is why I set it to 10k for normal guides and 20k for special guides I want to protect more then a standard guide.
I'm guessing it's a C2D system since it had a 7200.12 drive. That drive was released to replace the nightmare 7200.11 (it has a tendency to lock in a BSY state) and typically doesn't show in the BIOS in that condition. It was more effective then the .11 firmware patch, but it still happened; just less often. I've seen some years later that fail to load the SMART data as well; the .11/.12 drives were terrible.
If I had to guess at the failure it probably had a BSY failure rather then a mechanical failure. However, the drives are old enough it's now a plausible theory. Seeing 7200.11/12 is enough to get me to replace it regardless of functionality.
+
+
I've thought about doing a teardown of a drive (and have some pictures from a dead 7200.11) but I never did anything with it. I figured someone would pick up where I left off and I wish you the best in doing what I never did.
As far as non patrol edit permissions, my rule is to make it high enough to prevent new/inactive users from editing without going through Patrol but not stop someone with experience from doing it without going through Patrol. This is why I set it to 10k for normal guides and 20k for special guides I want to protect more then a standard guide.
I'm guessing it's a C2D system since it had a 7200.12 drive. That drive was released to replace the nightmare 7200.11 (it has a tendency to lock in a BSY state) and typically doesn't show in the BIOS in that condition. It was more effective then the .11 firmware patch, but it still happened; just less often. I've seen some years later that fail to load the SMART data as well; the .11/.12 drives were terrible.
If I had to guess at the failure it probably had a BSY failure rather then a mechanical failure. However, the drives are old enough it's now a plausible theory. Seeing 7200.11/12 is enough to get me to replace it regardless of functionality.
