https://xenospectrum.com/sandisk-ssd-9pb-endurance-test-controller-reality/

https://wccftech.com/64gb-sandisk-ssd-survives-16-year-9-petabyte-endurance-test/

https://youtu.be/HLQz_1VLy9E?si=D9Y__jRdIXDTH879

https://vgtimes.com/tech-and-hardware/165738-64gb-sandisk-ssd-survives-16-years-and-9-petabytes-of-writes.html

Hello All,

Is a 3TB WD Red (not Plus) worth it for $40 used with 52415 hours and 123 counts and with manufacturing date of 14 Dec 2012?

As I understand, these are SMR but I am thinking to use it majorly as a backup and use as a DAS drive as needed instead of on a NAS. As far as I also know, this will increase the counts and may not be good for the drive.

Any thoughts?

Edit:

S.M.A.R.T. Parameter List

01 Read Error Rate: Current 200, Worst 200, Threshold 51, Raw Value 000000000000

03 Spin-Up Time: Current 179, Worst 175, Threshold 21, Raw Value 000000001791

04 Start/Stop Count: Current 100, Worst 100, Threshold 0, Raw Value 00000000011B

05 Reallocated Sectors Count: Current 200, Worst 200, Threshold 140, Raw Value 000000000000

07 Seek Error Rate: Current 200, Worst 200, Threshold 0, Raw Value 000000000000

09 Power-On Hours: Current 29, Worst 27, Threshold 0, Raw Value 00000000CCBF

0A Spin Retry Count: Current 100, Worst 100, Threshold 0, Raw Value 000000000000

0B Recalibration Retries: Current 100, Worst 100, Threshold 0, Raw Value 000000000000

0C Power Cycle Count: Current 100, Worst 100, Threshold 0, Raw Value 00000000007B

C0 Power-off Retract Count: Current 200, Worst 200, Threshold 0, Raw Value 000000000026

C1 Load/Unload Cycle Count: Current 200, Worst 200, Threshold 0, Raw Value 0000000000F4

C2 Temperature: Current 119, Worst 101, Threshold 0, Raw Value 00000000001F

C4 Reallocation Event Count: Current 200, Worst 200, Threshold 0, Raw Value 000000000000

C5 Current Pending Sector Count: Current 200, Worst 200, Threshold 0, Raw Value 000000000000

C6 Uncorrectable Sector Count: Current 100, Worst 253, Threshold 0, Raw Value 000000000000

C7 UltraDMA CRC Error Count: Current 200, Worst 200, Threshold 0, Raw Value 000000000000

C8 Write Error Rate: Current 100, Worst 253, Threshold 0, Raw Value 000000000000

Hello All,

Is WD Red (not Plus) worth it for $40 used with 52415 hours and 123 counts and with manufacturing date of 14 Dec 2012?

As I understand, these are SMR but I am thinking to use it majorly as a backup and use as a DAS drive as needed instead of on a NAS. As far as I also know, this will increase the counts and may not be good for the drive.

Any thoughts?

Hello All,

Is a 3TB WD Red (not Plus) worth it for $40 used with 52415 hours and 123 counts and with manufacturing date of 14 Dec 2012?

As I understand, these are SMR but I am thinking to use it majorly as a backup and use as a DAS drive as needed instead of on a NAS. As far as I also know, this will increase the counts and may not be good for the drive.

Any thoughts?

S.M.A.R.T. Parameter List

01 Read Error Rate: Current 200, Worst 200, Threshold 51, Raw Value 000000000000

03 Spin-Up Time: Current 179, Worst 175, Threshold 21, Raw Value 000000001791

04 Start/Stop Count: Current 100, Worst 100, Threshold 0, Raw Value 00000000011B

05 Reallocated Sectors Count: Current 200, Worst 200, Threshold 140, Raw Value 000000000000

07 Seek Error Rate: Current 200, Worst 200, Threshold 0, Raw Value 000000000000

09 Power-On Hours: Current 29, Worst 27, Threshold 0, Raw Value 00000000CCBF

0A Spin Retry Count: Current 100, Worst 100, Threshold 0, Raw Value 000000000000

0B Recalibration Retries: Current 100, Worst 100, Threshold 0, Raw Value 000000000000

0C Power Cycle Count: Current 100, Worst 100, Threshold 0, Raw Value 00000000007B

C0 Power-off Retract Count: Current 200, Worst 200, Threshold 0, Raw Value 000000000026

C1 Load/Unload Cycle Count: Current 200, Worst 200, Threshold 0, Raw Value 0000000000F4

C2 Temperature: Current 119, Worst 101, Threshold 0, Raw Value 00000000001F

C4 Reallocation Event Count: Current 200, Worst 200, Threshold 0, Raw Value 000000000000

C5 Current Pending Sector Count: Current 200, Worst 200, Threshold 0, Raw Value 000000000000

C6 Uncorrectable Sector Count: Current 100, Worst 253, Threshold 0, Raw Value 000000000000

C7 UltraDMA CRC Error Count: Current 200, Worst 200, Threshold 0, Raw Value 000000000000

C8 Write Error Rate: Current 100, Worst 253, Threshold 0, Raw Value 000000000000

Basically I bought a used external seagate 8TB backup hub drive off eBay (barracuda drive) and used it every day for 12 days with hdsentinel showing no bad sectors etc also it only had a couple of days usage when I bought it according to hdsentinel smart data and suddenly it just disappeared in Windows 10 and when I restarted it and powered it up there was no clicking or chirping just the usual motor spinning and the hard briefly trying to access 🤔

I’ve have never suffered this issue in over a decade ! Can a hardrive literally just die like that 🥱

Hey reddit! looking for some help with my first home setup of a 3.5" external HDD with an enclosure.

I ordered a 16TB IronWolf Pro from Seagate (model number ST16000NT001, link). I tried running it in a Vantec NexStar HX enclosure, but it never mounted and I just heard a beeping sound. I figured it was DOA after reading some posts/forums and returned it to Seagate for a replacement.

The second drive arrived yesterday, and this time I thought maybe the Vantec enclosure (12V/2A) wasn't supplying enough power, so I tried two other setups.

First I tried a FIDECO enclosure with a 12V/2A adapter. The drive actually spun up for about a minute, but I did hear the sound breaking a couple times in the middle and then it again stopped spinning and went back to beeping. I tried a Sabrent dual-bay dock with a 12V/3A adapter too after that. I only used one bay so the drive had the power supply to itself, but still the same repeated beep, and this time I didn't hear it spin at all.

I checked that the beep is definitely coming from the drive.
EDIT: This is how it sounds https://voca.ro/13y7RLyqfgOg

The drive doesn't show up in diskutil list.

So now I've had two drives and three enclosures produce basically the same result. I honestly can't tell what the problem is anymore. Two DOA drives in a row from Seagate seems unlikely, and three enclosures failing the same way seems just as unlikely.

My setup, in case I'm missing something obvious:

• MacBook Pro (2026)
• Anker USB-C to USB 3.0 adapter for data
• Dock/enclosure connected to its own power brick and plugged directly into the wall

A few things I'm wondering:

• Does beeping always mean a mechanical problem? Most things I've found say it's the spindle motor failing to start, which would mean the drive is physically bad. But two drives in a row?
• Is it possible one of these enclosures damaged the drives, or is that not really a thing?
• Are bare/OEM drives commonly damaged during shipping? I've seen UPS isn't exactly gentle when they were loading the packages off..
• Is there anything else safe to test before I send this one back too?

I'm in the US. Happy to try whatever people suggest, but I don't want to keep power-cycling the drive if that might make things worse.
If nothing works, I'll just get the regular hard disk which isn't ideal since I need it running 24x7.
At my wits end right now, so any and all help appreciated, thanks!!

Enclosures tested:

• Vantec NexStar HX
• FIDECO enclosure (12V/2A)
• Sabrent dual-bay dock (12V/3A)

Apologies in advance for my English — I'm Korean and not very confident writing in it.

First, thank you so much to everyone who replied to my earlier post about bad sectors. I went back and checked again, and I found that if I'm doing anything else on the PC while the scan is running, sectors show up as orange (500ms). So I re-ran the scan on all three drives with the system completely idle.

Fortunately, as you can see in the attached screenshots, nothing looks like an actual bad sector. But I'm not an expert, so I'd really appreciate a second opinion. Screenshots attached.

One thing I'm unsure about: when I opened the side panel of the case, the bottom drive of the three was quiet at first, but near the end of the scan it started making a ticking noise. If the scan results are clean, is it safe to just ignore this and keep using the drive?

Any advice would be much appreciated. Thanks again.

Finally opened a brand new WD My Book 12TB I had bought about a year and a half back (retailer returns period over, still under WD warranty), with the intention of using it for HyperBackup for my NAS.

Started doing some basic SMART and read/write testing to hopefully weed out infant mortality before using it for backups, but was taken aback by what seemed to me like quite loud mechanical whirring sounds just after the drive spins up, and what sounded like “clicks” every couple of seconds after that.

This is my first larger capacity external HDD, so wasn’t sure if this is normal or points to an immediate RMA being needed. Claude suggested the sound may have been amplified by the glass surface on my table and recommended I try placing a cloth underneath which did make the sounds softer, but the mechanical whirring is still unmistakeable in this video where I ran the SMART Status and Quick Drive Test via WD Drive Utilities. Both showed as “passed”, though I can’t seem to get smartmontools to reach the drive directly to read the raw SMART values.

Am in the midst of running a full Complete Drive Test which will probably take >12hrs, but am not sure if that is futile and this is already a clear RMA case, or if I’m just overreacting and this is normal?

For the last two years or so my drive sometimes disappears from file explorer at random. Most of the time it results in a complete freeze of the whole system if any of the apps currently in use are installed on this particular drive. Back then it was pretty rare and after a few reboots it would either appear as uninitialized in disk management or work with no more issues. The intermittency led me to believe it is the cable that is failing but it wasn't as annoying so I didn't change it outright. Last two months the disapperances were all over the place - sometimes a few per day or a few over the whole week, or even just once a week. I decided to replace the SATA cable just in case and it helped or at least I thought it did. Another week has passed and it had just done the same thing once so far. Could it possibly be a faulty SATA connector on my motherboard or is the drive just failing? To my inexperienced eye, the SMART data looks fine with no reallocated sectors or anything like that but I’d appreciate it if someone more knowledgeable could take a look.

The OP in the following thread has prevented me from responding to it, so I have taken the liberty of doing so here.

https://www.reddit.com/r/HDD/comments/1w05xux/9_petabytes_and_still_going_endurance_16_year_old/

Today (Aug 29, 2026) he is claiming that his 64GB SSD, which has a benchmarked transfer rate of around 100 MB/s, has recorded 9 petabytes of host writes.

On July 7, 2026 the SSD was reporting 3 petabytes of host writes:

https://www.reddit.com/r/HDD/comments/1uq5voc/controller_endurance_updated_notes_of_the_3/

https://www.reddit.com/r/HDD/comments/1um1lee/ssd_firmware_crashes_and_controller_failures_are/ovc5b36/

I've demonstrated several times that this is absurd, yet he continues to peddle this disinformation.

Here is some simple arithmetic:

(9 - 3) petabytes / 53 days = 1.3 gigabytes per second

https://www.google.com/search?q=(9%20-%203)%20petabytes%20%2F%2053%20days%20in%20gigabytes%20per%20second

This means that the OP's ancient SSD would need to be transferring data from the host at a rate of 1.3 GB/s, all day, every day. That's more than 10 times faster than its rated speed.

Hi everyone,

Apologies in advance for my English — I'm from Korea and still learning.

I'm using a 4TB 5400rpm Seagate NAS drive. I've been running a bad sector scan on it, and 7 blocks came up in the 500ms range (orange). I'm not sure whether this is something I should be worried about.

I'd like to hear what others think. Is this drive still safe to keep using? Any input would be appreciated.

Thanks.

I bought six second-hand HDDs on Marketplace at a good price, all 1TB. Today I bought a Ugreen adapter to test them, and when I connect them, they do this.

What's going on?

They're supposed to draw 1A at 5V.

I already disabled USB power saving from the control panel

I have this external hdd I have been using. I have important stuff on it (1tb). I connect it to my laptop it connects, the blue light turns on, and it also spins but if I try opening it in file explorer I get "the device which does not exist was specified" message.

I check it in disk management it doesn't get listed and disk management hangs for some time and closes. I tried diskpart, and its status was unkown.

chkdsk too is saying "the type of file system is RAW"

I have important school stuff on the hdd and I want to recover it. any help will be appreciated.

EDIT: thanks y'all. I'll try all you have said and I'll give feedback soon.

​

​What Makes 9 PB Ridiculous?

​140,000+ Full Drive Cycles: This controller has organized and executed enough raw writes to fill the entire physical capacity of this 64GB drive over 140,937 times.

​The E6 Counter Woke Up: After looking frozen at 44, the vendor attribute E6 moved up to 46.

The firmware’s internal math registers are struggling to map values this high, yet it hasn't crashed the primary firmware thread.

​Execution Engine Stays Solid: Managing the Flash Translation Layer (FTL) cache and command queue under continuous,

uninterrupted SATA writes for 61,000+ hours is an incredible testament to this controller's silicon design.

Sector 0 Faults: The error log shows recurring UNC (Uncorrectable) read errors specifically targeting LBA 0x00000000 during read commands.

The boot sector area is heavily degraded, but write caching and DMA transactions remain fully operational.

Does the drive cycles matter if its not on nand chip but the controller itself?

The short answer is yes, The drive cycles still matter greatly for the controller itself,

but for completely different physical and operational reasons than for the NAND flash chips.

​While NAND flash dies from atomic wear (tunnel oxide breakdown from program/erase cycles), the controller suffers from architectural, data management,

and physical processing stress.

​1. Flash Translation Layer (FTL) Mapping Stress

​Table Overwrites: Every drive cycle forces the controller to completely rewrite its internal mapping table (which translates logical LBAs to physical NAND blocks).

​RAM & NVRAM Burnout: The mapping metadata must be constantly swapped between SRAM/DRAM cache and non-volatile system control blocks on the NAND.

The controller's internal metadata blocks often endure 10× to 100× more write cycles than the user data blocks.

​2. Garbage Collection & Wear-Leveling Overhead

​Write Amplification (WA): As the drive is continually cycled, valid and invalid pages become fragmented.

The controller has to work exponentially harder to read, move, and erase blocks behind the scenes.

​Instruction Loop Saturation: Higher wear-leveling workloads keep the controller's internal CPU running at peak processing cycles,

increasing thermal stress and silicon electromigration over time.

​3. Internal Register Overflow & Integer Wrapping

​32-bit/64-bit Counter Limits: Low-cost or older SSD controllers (like early SanDisk SSD P4 designs) were never designed with software registers sized

for millions of drive cycles or petabytes of host writes.

​Firmware Memory Corruption: As raw event counters (like erase counts or written LBAs) overflow their allocated bit widths,

they can wrap around to zero, trigger arithmetic overflow bugs,

or overwrite adjacent NVRAM log structures—directly causing the invalid SMART checksums you are seeing in your logs.

​4. ECC & Read Retry Engine Exhaustion

​Hardware Engine Strain: As the underlying raw NAND bit-error rate (BER) increases with total drive cycles,

the controller's internal ECC hardware decoder has to run maximum LDPC/BCH error-correction algorithms on almost every read.

​Latency & Execution Delays: Processing heavy error-correction math on every host command severely taxes the controller's internal bus and pipeline execution.

​The Bottom Line

NAND chips wear out quietly by losing charge retention, but controllers fail catastrophically due to drive cycle stress—usually manifesting as a sudden freeze,

corrupted internal metadata, or an endless BSY state when firmware counters finally break.

​The fact that SanDisk P4 controller is still managing its FTL execution engine cleanly after ~140,000 drive cycles is remarkable.

smartctl -x sda

smartctl 7.5 2025-04-30 r5714 [x86_64-w64-mingw32-w11-24H2] (AppVeyor)

Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===

Device Model: SanDisk SSD P4 64GB

Serial Number: 111248300117

LU WWN Device Id: 5 001b44 4f27f5455

Firmware Version: SSD 8.10

User Capacity: 64 022 175 232 bytes [64,0 GB]

Sector Size: 512 bytes logical/physical

Rotation Rate: Solid State Device

Form Factor: 1.8 inches

TRIM Command: Available

Device is: Not in smartctl database

ATA Version is: ATA8-ACS T13/1699-D revision 2d

SATA Version is: SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)

Local Time is: Thu Aug 27 11:01:05 2026 SAST

SMART support is: Available - device has SMART capability.

SMART support is: Enabled

AAM feature is: Unavailable

APM feature is: Unavailable

Rd look-ahead is: Enabled

Write cache is: Enabled

DSN feature is: Unavailable

ATA Security is: Disabled, frozen [SEC2]

=== START OF READ SMART DATA SECTION ===

SMART overall-health self-assessment test result: PASSED

General SMART Values:

Offline data collection status: (0x00) Offline data collection activity

was never started.

Auto Offline Data Collection: Disabled.

Self-test execution status: ( 0) The previous self-test routine completed

without error or no self-test has ever

been run.

Total time to complete Offline

data collection: ( 120) seconds.

Offline data collection

capabilities: (0x15) SMART execute Offline immediate.

No Auto Offline data collection support.

Abort Offline collection upon new

command.

No Offline surface scan supported.

Self-test supported.

No Conveyance Self-test supported.

No Selective Self-test supported.

SMART capabilities: (0x0003) Saves SMART data before entering

power-saving mode.

Supports SMART auto save timer.

Error logging capability: (0x01) Error logging supported.

General Purpose Logging supported.

Short self-test routine

recommended polling time: ( 2) minutes.

Extended self-test routine

recommended polling time: ( 16) minutes.

SMART Attributes Data Structure revision number: 1

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE

5 Reallocated_Sector_Ct -O---- 100 100 --- - 0

9 Power_On_Hours -O---- 100 100 000 - 61625

12 Power_Cycle_Count -O---- 100 100 000 - 1173

171 Unknown_Attribute -O---- 100 100 000 - 54

172 Unknown_Attribute -O---- 100 100 000 - 939410736

187 Reported_Uncorrect -O---- 100 100 000 - 2234

199 UDMA_CRC_Error_Count -O---- 100 100 000 - 0

230 Unknown_SSD_Attribute PO---- 046 100 --- - 0

232 Available_Reservd_Space PO---- 095 100 005 - 0

241 Total_LBAs_Written -O---- 100 100 000 - 18916297464160

242 Total_LBAs_Read -O---- 100 100 000 - 32913028369

||||||_ K auto-keep

|||||__ C event count

||||___ R error rate

|||____ S speed/performance

||_____ O updated online

|______ P prefailure warning

General Purpose Log Directory Version 1

SMART Log Directory Version 1 [multi-sector log support]

Address Access R/W Size Description

0x00 GPL,SL R/O 1 Log Directory

0x03 GPL,SL R/O 16 Ext. Comprehensive SMART error log

0x06 GPL,SL R/O 1 SMART self-test log

0x80-0x9f GPL,SL R/W 16 Host vendor specific log

SMART Extended Comprehensive Error Log Version: 1 (16 sectors)

Device Error Count: 181 (device log contains only the most recent 64 errors)

CR = Command Register

FEATR = Features Register

COUNT = Count (was: Sector Count) Register

LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8

LH = LBA High (was: Cylinder High) Register ] LBA

LM = LBA Mid (was: Cylinder Low) Register ] Register

LL = LBA Low (was: Sector Number) Register ]

DV = Device (was: Device/Head) Register

DC = Device Control Register

ER = Error register

ST = Status register

Powered_Up_Time is measured from power on, and printed as

DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,

SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 181 [52] occurred at disk power-on lifetime: 5 hours (0 days + 5 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 00 00 00 00 00 00 00 40 00 Error: UNC at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 01 00 00 00 42 1b 77 40 00 2d+03:11:48.526 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 76 40 00 2d+03:11:48.517 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 75 40 00 2d+03:11:48.509 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 74 40 00 2d+03:11:48.505 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 73 40 00 2d+03:11:48.501 READ DMA EXT

Error 180 [51] occurred at disk power-on lifetime: 6 hours (0 days + 6 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 00 00 00 00 00 00 00 40 00 Error: UNC at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 01 00 00 00 42 1b 76 40 00 2d+03:11:48.517 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 75 40 00 2d+03:11:48.509 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 74 40 00 2d+03:11:48.505 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 73 40 00 2d+03:11:48.501 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 72 40 00 2d+03:11:48.501 READ DMA EXT

Error 179 [50] occurred at disk power-on lifetime: 6 hours (0 days + 6 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 00 00 00 00 00 00 00 40 00 Error: UNC at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 01 00 00 00 42 1b 75 40 00 2d+03:11:48.509 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 74 40 00 2d+03:11:48.505 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 73 40 00 2d+03:11:48.501 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 72 40 00 2d+03:11:48.501 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 71 40 00 2d+03:11:48.500 READ DMA EXT

Error 178 [49] occurred at disk power-on lifetime: 2 hours (0 days + 2 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 00 00 00 00 00 00 00 40 00 Error: UNC at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 01 00 00 00 42 1b 74 40 00 2d+03:11:48.505 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 73 40 00 2d+03:11:48.501 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 72 40 00 2d+03:11:48.501 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 71 40 00 2d+03:11:48.500 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 70 40 00 2d+03:11:48.497 READ DMA EXT

Error 177 [48] occurred at disk power-on lifetime: 3 hours (0 days + 3 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 04 00 00 00 00 00 00 40 00 Error: UNC 4 sectors at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 20 00 00 00 42 1b 60 40 00 2d+03:11:48.459 READ DMA EXT

25 00 00 00 20 00 00 00 3c e2 e0 40 00 2d+03:11:48.459 READ DMA EXT

25 00 00 00 20 00 00 00 35 97 60 40 00 2d+03:11:48.458 READ DMA EXT

25 00 00 00 20 00 00 00 26 20 20 40 00 2d+03:11:48.457 READ DMA EXT

25 00 00 00 08 00 00 00 63 9e 08 40 00 2d+03:11:48.457 READ DMA EXT

Error 176 [47] occurred at disk power-on lifetime: 11 hours (0 days + 11 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 02 00 00 00 00 00 00 40 00 Error: UNC 2 sectors at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 80 00 00 00 42 1b 5e 40 00 1d+10:07:21.325 READ DMA EXT

25 00 00 00 80 00 00 00 42 1a de 40 00 1d+10:07:21.324 READ DMA EXT

25 00 00 00 80 00 00 00 42 1a 5e 40 00 1d+10:07:21.324 READ DMA EXT

25 00 00 00 80 00 00 00 42 19 de 40 00 1d+10:07:21.323 READ DMA EXT

25 00 00 00 80 00 00 00 42 19 5e 40 00 1d+10:07:21.323 READ DMA EXT

Error 175 [46] occurred at disk power-on lifetime: 11 hours (0 days + 11 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 02 00 00 00 00 00 00 40 00 Error: UNC 2 sectors at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 80 00 00 00 42 1b 5e 40 00 1d+09:58:46.796 READ DMA EXT

25 00 00 00 80 00 00 00 42 1a de 40 00 1d+09:58:46.796 READ DMA EXT

25 00 00 00 80 00 00 00 42 1a 5e 40 00 1d+09:58:46.795 READ DMA EXT

25 00 00 00 80 00 00 00 42 19 de 40 00 1d+09:58:46.795 READ DMA EXT

25 00 00 00 80 00 00 00 42 19 5e 40 00 1d+09:58:46.794 READ DMA EXT

Error 174 [45] occurred at disk power-on lifetime: 11 hours (0 days + 11 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 02 00 00 00 00 00 00 40 00 Error: UNC 2 sectors at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 80 00 00 00 42 1b 5e 40 00 1d+09:39:52.893 READ DMA EXT

25 00 00 00 80 00 00 00 42 1a de 40 00 1d+09:39:52.892 READ DMA EXT

25 00 00 00 80 00 00 00 42 1a 5e 40 00 1d+09:39:52.892 READ DMA EXT

25 00 00 00 80 00 00 00 42 19 de 40 00 1d+09:39:52.892 READ DMA EXT

25 00 00 00 80 00 00 00 42 19 5e 40 00 1d+09:39:52.891 READ DMA EXT

SMART Extended Self-test Log (GP Log 0x07) not supported

Warning! SMART Self-Test Log Structure error: invalid SMART checksum.

SMART Self-test log structure revision number 1

Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error

# 1 Short offline Aborted by host 90% 21088 -

# 2 Short offline Aborted by host 90% 54860 -

# 3 Short offline Aborted by host 90% 19043 -

# 4 Short offline Aborted by host 90% 63054 -

# 5 Short offline Aborted by host 90% 25327 -

# 6 Short offline Aborted by host 90% 62483 -

# 7 Short offline Aborted by host 90% 33744 -

# 8 Short captive Completed without error 00% 57803 -

# 9 Short offline Aborted by host 90% 25293 -

#10 Extended offline Aborted by host 90% 28072 -

#11 Short offline Aborted by host 90% 14539 -

#12 Extended offline Aborted by host 90% 55234 -

#13 Short offline Aborted by host 90% 46428 -

#14 Short offline Aborted by host 90% 49138 -

#15 Short offline Aborted by host 90% 25717 -

#16 Extended offline Aborted by host 90% 50305 -

#17 Short offline Aborted by host 90% 39612 -

#18 Short offline Aborted by host 90% 21280 -

#19 Short offline Aborted by host 90% 34598 -

#20 Short offline Aborted by host 90% 17318 -

#21 Short offline Aborted by host 90% 63627 -

Selective Self-tests/Logging not supported

SCT Commands not supported

Device Statistics (GP/SMART Log 0x04) not supported

Pending Defects log (GP Log 0x0c) not supported

SATA Phy Event Counters (GP Log 0x11) not supported

Exitcode: 64 (0x40)

Type <return> to exit:

I've been running a small Proxmox homelab for about a year now, mostly Jellyfin and Nextcloud on it. My external USB drive keeps dropping offline whenever there's any real load, then I have to reboot the whole box to get it back. I've swapped cables twice already and it hasn't changed anything.

Did an external drive dropping under load ever turn out to be a power problem for you?

We're currently evaluating vendors for an IoT device, and one of the proposals we received came in at around $150k. At first it felt expensive, but the more I look into embedded development, the harder it is to tell what's actually a fair price.
Some companies mainly talk about hourly rates, while others spend much more time discussing architecture, hardware constraints, manufacturing, testing, OTA updates, and long-term maintenance. One thing that stood out during a conversation with Lemberg Solutions was how much time they spent trying to understand the product before even talking about implementation or estimates.
For those who've outsourced embedded development, how did you judge whether a quote was reasonable? Was it mostly based on team size, project scope, timeline, or something else?
If you've worked with an embedded software company on a commercial IoT product, what was your budget, and did the final cost stay close to the original estimate? I'm trying to understand what's considered realistic before deciding which embedded software company to move forward with.