Solved Problem with the HDD disk Hitachi HDS724040ALE640.

Yes. and make sure to tell him that you torrent 900,000 GB per day on it, and you are not happy it only lasted one month. Give him a heads up that you will be returning the replacement too, for another replacement, as a common courtesy to him. Keep doing this again and again and you can get used hard drives free from him for life. Make a sh script to automatically fill out all the claim forms, and them send them to him 100 at a time. You will save a lot of time doing this.
 
I told the seller that I would wait a week, if the situation persists, I would send it back. So far it is working normally. Shame to throw away a good drive. At this point, I recommend pills and rest.

001.jpg
 
Please read SMART attributes when disk runs with WindowsOS.
Use shareware aida64 (site aida64.com)

If SMART 'Current pending sectors' happens non-zero value then I advice you to return the disk to the seller.
 
I can't do this because, the drive is stuck with double sided tape to an anti-vibration pad I found in the basement:). The S.M.A.R.T. could have been throwing errors, from the errors that were there, and duplicating them. I don't know. It works. Besides, I don't have time to sit on it anymore. On this week. This case did not have a slot for a 3.5" drive I gave this in place of the floppy drive. The noise was unbearable.

.IMG_20220530_175758_043[1].jpg
 
The refurbished/tested hdd drives from a brick and mortar store have had more longevity than some brand new sdd drives. As of up to now. A used hdd drive had data that was more easily recoverable when it failed. This has happened during a power surge to the house. Files were damaged, but it was largely accessible. I've had a brand new ssd fail, when it wasn't even a year old. I couldn't access the filesystem at all.

There's some cases where a used harddisk can be used.

I found sdd drives best for basic /, /var and /usr directories. Maybe swap too. If these files get damaged, just reinstall or replace the files. hdd doesn't perform as well (as fast or efficiently) for these directories.

Used hdd drives may be good for storage, but not for important storage, where it's not backed up. I would suggest not to use the drive you described for important storage. It could be ok, but with the problems described, that's risky. There also may be some bias that it shows problems or is difficult to work around, and trying to overlook them. Even if it's perfectly good, don't take the chance with any important data. Maybe used hdd drives would be ok for music, non-personal videos, and games meant for wine which can be reinstalled. Like something that can be copied from an optical disk.

A lot of about how I use the drives with each other is my opinion, but some method of using drives needs to be used.


Another thing, aside from the harddisks, is about the cables. The ones with the snap on connections can easily damage the pins/connectors on a harddisk. Also, when the ends have metal parts, a piece can flop and cause a shortage on other nonrelated hardware. I've tried being careful and slow with this, and as much care as I took, when I got it off, I let it go, and it flopped and damaged something. I was careful, but not careful enough to turn off the power on my pc, as it's known as being plug and play.
 
StephanieJones said:
# 1 Short offline Completed without error 00% 47539 -
Click to expand...
Something weird is going on with SMART. Up top it says 808 POH and down low it says 47539 Lifetime Hours
I would believe the higher number. That is 5+ years. Exactly when an enterprise ditches drives. End of warranty.

StephanieJones said:
I'm beginning to think that for torrents some SAS drives would be most suitable.
Click to expand...
Enterprise drives should have the same resilience whether SATA or SAS version.
Nothing magical about the interface. They use common guts.
Look at backblaze for guidance.

Backblaze Hard Drive Stats

Hard Drive test data from the Backblaze data center. Backblaze is affordable, easy-to-use cloud storage.
www.backblaze.com
 
It may be bad. Everyone says the stats aren't good.

Also, if it's making loud noise, that happens before they fail. If there's tape on something in a hard to reach place, it's better to take it off to make the adjustment, as inconvenient as it may be. When it makes noise or gives errors, data on that disk may not survive a reboot, or that disk could fail by itself within a day.

They have mounting trays/rails for securing it, when the computer doesn't have a small enough drive bay. 5.25" to 3.5" mounting trays are common. The one that's less common, or doesn't mount as well is the one to the smaller 2.5". Movements from vibrating may cause wear and tear and shorten the life of a drive.
 
Phishfry said:
Something weird is going on with SMART. Up top it says 808 POH and down low it says 47539 Lifetime Hours
I would believe the higher number. That is 5+ years. Exactly when an enterprise ditches drives. End of warranty.
Click to expand...

I don't think the "lifetime hours" are actually how long the drive has been used. Pretty sure that's a simulated calculated value. You want to look at power on hours for how long the drive has been in use.
 
I just looked up the technical specifications of your Hitachi HDS724040ALE640 drive.

There's virtually nothing published for "Reliability". Missing are:
  • Error rate (non-recoverable bits read)
  • MTBF
  • Annualized Failure Rate
Instead, we see a footnote reading "Intended for low duty cycle, non mission-critical applications in PC, gaming and external storage environments, which may vary from application to application."

Using this drive for heavy torrents is ill-advised.
 
It works and I think it will work. It handles small files poorly. It works better with large files.
Heats up a bit.

Code: 
root@Router:~ # smartctl -A /dev/ada1 | grep -i temperature
194 Temperature_Celsius     0x0002   113   113   000    Old_age   Always       -       53 (Min/Max 21/61)
root@Router:~ #
1.jpg
 
In case anyone was curious, the drive still works. And processed 109TB of data.

Code: 
root@router:~ # smartctl -a /dev/ada1
smartctl 7.3 2022-02-28 r5338 [FreeBSD 13.1-RELEASE-p6 amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Hitachi/HGST Deskstar 7K4000
Device Model:     Hitachi HDS724040ALE640
Serial Number:    PK1331PAH34G9S
LU WWN Device Id: 5 000cca 22bcf855d
Firmware Version: MJAOA3B0
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database 7.3/5319
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed May 31 21:56:11 2023 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x84) Offline data collection activity
                                        was suspended by an interrupting command from host.
                                        Auto Offline Data Collection: Enabled.
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:                (   24) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        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:        (   1) minutes.
Extended self-test routine
recommended polling time:        ( 569) minutes.
SCT capabilities:              (0x003d) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   095   095   016    Pre-fail  Always       -       131081
  2 Throughput_Performance  0x0005   136   136   054    Pre-fail  Offline      -       80
  3 Spin_Up_Time            0x0007   126   126   024    Pre-fail  Always       -       622 (Average 600)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       180
  5 Reallocated_Sector_Ct   0x0033   065   065   005    Pre-fail  Always       -       728
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   117   117   020    Pre-fail  Offline      -       36
  9 Power_On_Hours          0x0012   099   099   000    Old_age   Always       -       9352
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       179
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       317
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       317
194 Temperature_Celsius     0x0002   142   142   000    Old_age   Always       -       42 (Min/Max 19/61)
196 Reallocated_Event_Count 0x0032   001   001   000    Old_age   Always       -       3182
197 Current_Pending_Sector  0x0022   081   081   000    Old_age   Always       -       536
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 413 (device log contains only the most recent five errors)
        CR = Command Register [HEX]
        FR = Features Register [HEX]
        SC = Sector Count Register [HEX]
        SN = Sector Number Register [HEX]
        CL = Cylinder Low Register [HEX]
        CH = Cylinder High Register [HEX]
        DH = Device/Head Register [HEX]
        DC = Device Command Register [HEX]
        ER = Error register [HEX]
        ST = Status register [HEX]
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 413 occurred at disk power-on lifetime: 3200 hours (133 days + 8 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 08 60 7a 48 08  Error: UNC at LBA = 0x08487a60 = 138967648

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 40 80 28 7a 48 40 00   3d+07:46:07.583  READ FPDMA QUEUED
  60 40 78 a8 e2 95 40 00   3d+07:46:07.583  READ FPDMA QUEUED
  60 40 70 68 e2 95 40 00   3d+07:46:07.575  READ FPDMA QUEUED
  60 40 68 e8 04 79 40 00   3d+07:46:07.575  READ FPDMA QUEUED
  60 40 60 a8 04 79 40 00   3d+07:46:07.575  READ FPDMA QUEUED

Error 412 occurred at disk power-on lifetime: 3197 hours (133 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 40 e8 1a e7 06  Error: WP at LBA = 0x06e71ae8 = 115809000

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 90 a8 00 00 40 00   3d+05:01:15.658  WRITE FPDMA QUEUED
  61 40 88 68 9e 00 40 00   3d+05:01:15.658  WRITE FPDMA QUEUED
  61 40 80 28 9e 00 40 00   3d+05:01:15.658  WRITE FPDMA QUEUED
  61 40 78 e8 9d 00 40 00   3d+05:01:15.657  WRITE FPDMA QUEUED
  61 40 70 68 c9 03 40 00   3d+05:01:13.659  WRITE FPDMA QUEUED

Error 411 occurred at disk power-on lifetime: 3147 hours (131 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  10 51 40 e8 24 59 00  Error: IDNF at LBA = 0x005924e8 = 5842152

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 40 b8 e8 24 59 40 00   1d+03:13:41.540  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   1d+03:13:41.540  READ LOG EXT
  60 40 a8 e8 24 59 40 00   1d+03:13:24.260  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   1d+03:13:24.259  READ LOG EXT
  60 40 98 e8 24 59 40 00   1d+03:13:06.340  READ FPDMA QUEUED

Error 410 occurred at disk power-on lifetime: 3147 hours (131 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  10 51 40 e8 24 59 00  Error: IDNF at LBA = 0x005924e8 = 5842152

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 40 a8 e8 24 59 40 00   1d+03:13:24.260  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   1d+03:13:24.259  READ LOG EXT
  60 40 98 e8 24 59 40 00   1d+03:13:06.340  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   1d+03:13:06.339  READ LOG EXT
  61 10 88 e8 e3 56 40 00   1d+03:12:56.750  WRITE FPDMA QUEUED

Error 409 occurred at disk power-on lifetime: 3147 hours (131 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  10 51 38 f0 24 59 00  Error: IDNF at LBA = 0x005924f0 = 5842160

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 40 98 e8 24 59 40 00   1d+03:13:06.340  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   1d+03:13:06.339  READ LOG EXT
  61 10 88 e8 e3 56 40 00   1d+03:12:56.750  WRITE FPDMA QUEUED
  61 40 80 68 b3 d8 40 00   1d+03:12:52.753  WRITE FPDMA QUEUED
  61 40 78 68 c9 03 40 00   1d+03:12:52.753  WRITE FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     47539         -
# 2  Short offline       Completed without error       00%        57         -
# 3  Extended offline    Interrupted (host reset)      90%        10         -
# 4  Short offline       Completed without error       00%         9         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
 
Just a note. There is a venthole on top of spinners that should not be covered up.
It is important to let the drive breathe right.
With temperatures it contracts and expands and the vent is essential to reliable operation.
I see at day 133 she burped again.
 
I did another long test. But no change.
Code: 
#smartctl -t long /dev/ada1
.

Data as of 2023.05.31 shows:
Code: 
 9 Power_On_Hours          0x0012   099   099   000    Old_age   Always       -       9352
Data as of 2022.05.30 shows:
Code: 
 9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       821
Today 2023.06.01:
Code: 
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
   9 Power_On_Hours          0x0012   099   099   000    Old_age   Always       -       9370

9352h-821h = 8531h
8531h/24h = 355,458(3) day's of working.

Which maybe correct - But where does it start counting from? Since creating the partition table?

Data as of 2023.05.31 shows:
Code: 
 5 Reallocated_Sector_Ct   0x0033   065   065   005    Pre-fail  Always       -       728
Data as of 2022.05.30 shows:
Code: 
5 Reallocated_Sector_Ct   0x0033   089   089   005    Pre-fail  Always       -       322
However, the first SMART before cleaning MHDD showed
Code: 
5 Reallocated_Sector_Ct   0x0033   001   001   005    Pre-fail  Always   FAILING_NOW 213

With the caveat that the SMART of the day 2022.05.30 was dumped after the UFS partition was created. I just forgot.
So it increases. It's not 0 but it's not bad.

The router consumes 30-40Watts, I checked the consumption meter. Together with Operator Router 70Watt.

It is sad that if this motherboard fails, I will not be able to repair HDD drives using MHDD, because I will not plug it in the IDE drive in CHS mode.
When I have time, I will print a pocket on the disk to keep it cooler. :)
 
Power_On_Hours are just that - total power on hours for the hard drive, independent of what you've done with it (reformatted, completely wiped and changed OS, etc.) Even leaving it completely idle without formatting it but still powered on would increase the Power_On_Hours.

I would avoid storing anything of value (irreplacable) on a drive with rising relocated sector counts.
 
The warranty seal is from the local computer service, and since there were 800 hours at the beginning, I conclude that someone was messing with the controller.
 
You must log in or register to reply here.
Back
Top