• 15 Posts
  • 505 Comments
Joined 2 years ago
cake
Cake day: July 20th, 2023

help-circle






  • Funny enough, that was the last model I had to do that to, a 9000 series. We had several, but they are dying off steadily to print head failure errors. Reminds me of the Whack-a-Mole scandal.

    I would 100% buy a used enterprise printer if I could get a proper deal on it, but that is because I have been a certified HP printer tech and have fixed hundreds of printers. If you count receipt printers and other brands of office printer, I have probably touched over a thousand for anything from rebuilds to jams. There was a year when I rebuilt 10-20 printers a week as part of a schedule.

    Anyhow, what I’m getting at isn’t that they are better built or anything like that. There just happens to be enough third party vendors that you never have to pay them a cent to keep a printer running. Someone else already paid them the 2-6k for the printer, and it’s e-waste if it goes into the dump. I can ship of Thesius it indefinitely, even if I have to buy parts from God knows where.








  • True, but it’s not clear to me that both drives are exhibiting the behavior and it sounds more like a copy between two drives. I wouldn’t rule it out and do think it is a possibility, but in my professional experience drives fail much more frequently than controllers.

    It makes sense to me to test the drives individually, in another system preferably, using smart long test, which is non-destructive. Next test other drives in this system. If there are errors, try changing out the SATA cables, too. If you can shuffle the data off the drives, do so and then try running them through a secure erase in another system. A bad drive should fail the same way in another system.

    My other thought for probably not being the controller is that 4TB is a very long time for a sustained transfer to fail on a flakey component. Also, there are no reports of other errors.