started resilvering with the new hdd via “replace” command in the GUI.
The first 10% of resilvering went quite ok in terms of duration. The remaining time shown in the gui was between 2 and 10 hours. But now I am sort of stuck at 11%. The number is still increasing but extremely slow. the remaining time now says 9 days.
Does anybody what’s going on here? Does that means that the newly bought HDD is already corrupt?
Shall I simply wait or shutdown the server to avoid another faulty hdd? The server itself is not business critical. I just don’t wanna lose data. (even tough, I do have backups of course :-))
Unfortunately this Server is on a remote site. I went there this morning, started the resilvering and since I looked good, left the site.
Additional information:
I am running TrueNAS-13.3-U1.1 Core
the degraded Pool consists of 6x 8TB Ironwolf HDDs.
The Pool is 3x vdev mirror with 2 hdd each.
The faulty drive was in fact the newest HDD - ST8000VN004
All other drives are ST80000VN0022
I replaced the N004 with a N0022. So now every HDD of this Pool is ST80000VN0022.
I just realized that the rotation speed is listed as 5400rpm which can’t be right.
it doesn’t seem right since I intentionally bought a 7200rpm hdd from this Amazon seller.
"Seagate IronWolf, NAS interne Festplatte 8TB, 3.5 Zoll, 7200 u/min, 256 MB
Cache, SATA 6GB/s, silber, bulk, inkl. 3 Jahre Rescue Service, Modellnr.:
ST8000VN0022"
Seems like I need to sort this out with the seller.
I know that ironwolf 8TB is also available with 5400rpm but then the model number should be different. like ST8000VN002.
I couldn’t find any drive with 5400rpm and model number ST8000VN0022 online.
Regarding the resilvering it seems, that the remaining time counter is somehow a litte off.
Right now it still shows 4 days and 11 hours but is at 85% already. Meaning we’re at 23h since the resilvering start which is not as bad as it seems yesterday
Edit:
The model number and rpm mismatch puzzles me. Am I wrong or could this hdd be fake?
For what it is worth, I have heard people say that these modern rpm numbers are mood anyway.
Apparently WD lied about these numbers in the past. A 5400 rpm drive seems green, while a 7200 rpm seems fast and power hungry.
So I would not read too much into these rpm numbers.
Also Seagate does not specify any numbers on the N0022 data sheet and only says:
“Low-RPM spindle speed” whatever that means.
What I find more interesting, is that you have no warranty left.
Sorry for being noise, but since you posted your serial number, I checked it.
Warranty Expired 14. Oktober 2019.
Which is very odd, since you drive was produced in 2022?!
no worries. thanks for checking.
I saw this as well when checking the seagate waranty. Afterwards I checked all my other ST8000VN0022 serial numbers and all of them have the same waranty expiration date.
As you said, production date and waranty date doesn’t make sense.
Futhermore if you check the QR code there are more discrepancies.
if I submit this number anyway, it says this is supposed to be a 16GB Drive
However, I can’t really tell if this is really an indication of fake hdds or just a crapy implementation of this entire serial number validation process by seagate.
smartctl -x /dev/da4 give me some runtime information:
Device Statistics (GP Log 0x04)
Page Offset Size Value Flags Description
0x01 ===== = = === == General Statistics (rev 1) ==
0x01 0x008 4 1 --- Lifetime Power-On Resets
0x01 0x010 4 28 --- Power-on Hours
0x01 0x018 6 3192274332 --- Logical Sectors Written
0x01 0x020 6 4436736 --- Number of Write Commands
0x01 0x028 6 291388 --- Logical Sectors Read
0x01 0x030 6 12743 --- Number of Read Commands
0x01 0x038 6 - --- Date and Time TimeStamp
0x03 ===== = = === == Rotating Media Statistics (rev 1) ==
0x03 0x008 4 28 --- Spindle Motor Power-on Hours
0x03 0x010 4 28 --- Head Flying Hours
0x03 0x018 4 2 --- Head Load Events
0x03 0x020 4 0 --- Number of Reallocated Logical Sectors
0x03 0x028 4 0 --- Read Recovery Attempts
0x03 0x030 4 0 --- Number of Mechanical Start Failures
0x03 0x038 4 0 --- Number of Realloc. Candidate Logical Sectors
0x03 0x040 4 2 --- Number of High Priority Unload Events
0x04 ===== = = === == General Errors Statistics (rev 1) ==
0x04 0x008 4 0 --- Number of Reported Uncorrectable Errors
0x04 0x010 4 0 --- Resets Between Cmd Acceptance and Completion
0x05 ===== = = === == Temperature Statistics (rev 1) ==
0x05 0x008 1 33 --- Current Temperature
0x05 0x010 1 - --- Average Short Term Temperature
0x05 0x018 1 - --- Average Long Term Temperature
0x05 0x020 1 34 --- Highest Temperature
0x05 0x028 1 24 --- Lowest Temperature
0x05 0x030 1 - --- Highest Average Short Term Temperature
0x05 0x038 1 - --- Lowest Average Short Term Temperature
0x05 0x040 1 - --- Highest Average Long Term Temperature
0x05 0x048 1 - --- Lowest Average Long Term Temperature
0x05 0x050 4 0 --- Time in Over-Temperature
0x05 0x058 1 60 --- Specified Maximum Operating Temperature
0x05 0x060 4 0 --- Time in Under-Temperature
0x05 0x068 1 0 --- Specified Minimum Operating Temperature
0x06 ===== = = === == Transport Statistics (rev 1) ==
0x06 0x008 4 3 --- Number of Hardware Resets
0x06 0x010 4 1 --- Number of ASR Events
0x06 0x018 4 0 --- Number of Interface CRC Errors
|||_ C monitored condition met
||__ D supports DSN
|___ N normalized value
28h seems very reasonable and if that number is correct, that’s the time when I first activated this HDD.
I hope you file a complaint with Amazon. With that said, the Amazon seller may also have been cheated, they may have been in good faith as well.
Good luck and I would have all those drives replaced. they could have over 50,000 hours on them and you would not know. Also report to Seagate, include the serial numbers. I’m certain they know who purchased cases of drives that would have those serial numbers in them. Not that they will tell you but it is part of the fight.
just to get it right. do you mean the 28h power-on-hours could be faked?
The other drives I mentioned are bascially old drives running in my NAS for many years already and bought by different sellers at different times.
Therefore I didnt care about the warranty date so much, because this would be a strance coincidence, don’t you think so?
If the drive dates do not line up, for any drive, then you should question the validity of the drive. It is one thing to purchased a “Refurbished” drive, then you know the drive was previously used and have a specific warranty for that refurbished drive, and those hours would have been reset as well, but you would know why.
Contact the Amazon seller, ask a few questions, provide facts like the label manufacturing date, the warranty date, your purchase date, the RPM discrepancy, and every other thing that does not add up.
As said before, the RPM of the drive is not a major factor for most people, rotational latency in a NAS is not a major factor. It is all those discrepancies that are the issue. And this is just my opinion, I think the hours value was reset. Do some investigating and hopefully all will turn out well.
Nope. They could show you a photo but are they actually shipping that specific drive? Find a reputable place to purchase from. I like NewEgg as they have a wonderful return policy, and that means a sell by them, not a 3rd party, so be attentive. Since the problems seem to have been mainly around Seagate drives, maybe choose a different manufacturer. And remember, Seagate has a lot of companies, HGST for example. Maybe a Western Digital drive? Pay attention also to CMR.
HGST is now a subsidiary of WD (WD Gold are rebranded HGST Ultrastar).
As for Seagate, to be honest, the issue seems to be with some resellers rather with the manufacturer.
Supposedly China Crypto Farms making the drives look like new and selling off massive amount of drives because the easy data has been mined. Well that was a story I read a few days ago.
finally I was able to drive to my remote location in order to swop the Ironwolf hdd we’ve been talking about here by a new one I bought from another shop.
First observation was, that the resilvering process took less than 4 hours with the new drive. The “scam” drive took more than 24 hours.
Afterwards I plugged the “scam” drive to my laptop via a usb bridge - unfortunately I don’t have any other option with direct sata connections. The smartmontools apparently don’t like usb bridges, so I couldn’t use the FARM command but I read that the seagate seatools could read these values as well.
So I installed seatools and here are the drive details given by this tool via the usb bridge.
The values don’t make much sense to me besides the fact that they look suspicious. e.g. the power-on-hours. This is something like a trillion years of runtime. Or do I read in a wrong way?
