Urgent.News

What's breaking now, across thousands of outlets.

Tech

Used enterprise SSDs & SAS drives: what to check before buying

Enterprise storage is one of the best places to buy used. Enterprise SSDs and SAS drives are built for 24/7 duty cycles, have far higher endurance than consumer parts, and depreciate hard once a data center refreshes its fleet. But "enterprise" and "used" both cut both ways - you need to know what you're actually buying. Here's a practical checklist before you drop money on a drive from an…

When purchasing used enterprise SSDs and SAS drives, it is essential to conduct thorough checks before making a purchase. Enterprise drives are built for continuous operation and have higher endurance than consumer-grade drives. They are optimized for sustained IOPS, power-loss protection, and long-term durability. However, these drives have been used heavily in data centers and may have logged thousands of power-on hours.

Before buying, verify the drive's compatibility with your system, including the SAS-capable HBA or backplane, and confirm the drive type (U.2, M.2, or AIC NVMe). Check the drive's SMART data and power-on hours using commands like smartctl -a or nvme smart-log. Look for key metrics such as Power_On_Hours, Reallocated_Sector_Ct, Grown_Defect_List, Percentage_Used, Media_Wearout_Indicator, and Uncorrectable_Error_Cnt.

Be cautious of any non-zero, growing counts or high percentage usage, as these can indicate potential issues. Remember that a high wear percentage does not necessarily mean the drive is unusable, but it does indicate that the drive has been heavily used. Before deploying the drive, run a badblocks or nvme device-self-test to ensure its reliability.

When buying, prefer resellers who test and reset drives, and match drives in sets carefully to avoid correlated failures. Lastly, consider purchasing SAS drives for bulk or cold storage pools, as they often offer the best value for the price.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

How an Unpinned Base Image Tag Let V8 Size Its Heap Off the Host, Not the Pod

14:47 UTC, Tuesday. Pods in the checkout-api deployment start OOMKilling in a loop, three or four at a time, in the middle of an ordinary afternoon. Traffic is flat. No deploy went out today.

  • Unpinned base image tag caused V8 to size heap off host
  • Dockerfile used floating tag FROM node:18-alpine
  • Pinning base image prevents OOMKilling and memory misinterpretation

How to verify emails at signup without blocking real users (Node.js)

Most signup forms validate an email with a regex and call it done. That catches bob@@gmail but happily accepts jane@compnay.com , test@mailinator.com and ceo@a-domain-that-accepts-everything.com .

  • Verify email addresses during signup to ensure deliverability and sender reputation.
  • Use ListCheckup API in Node.js to check email validity without blocking real users.
  • Store verification flags in user records for future newsletter targeting.

More from Friday 23 October →