That's exactly what happened to me. Do you have someone higher up looking into it? I was told by Seagate that Newegg is one of their trusted sellers this should not happen. Seagate assured me they will get back to me. Whether that happens is still a mystery.
5 year manufacturer warranty listed on the sales page doesn't equal OEM
That would normally be fine if it were Server Part Deals, who is familiar with drives and honors their own in-house warranty. Newegg won't return a drive after their return period. This drive is sold and shipped by Newegg and is sold with 5 year manufacturer warranty. Not as an OEM drive. There's no excuse for it.
I noticed my X20 Seagate from Newegg was missing 7 months from it's warranty when registered on the Seagate website. This is a common issue, and Seagate usually corrects the warranty expiration date without issue.
However, after supplying the info on this new Exos X20 "Shipped and sold by Newegg",Seagate support informed me that my drive is OEM and doesn't have a Seagate warranty.
I'm already 18+ hours into a full parity sync on this drive - but definitley am concerned about having no warranty on what is supposed to be a brand new HDD.
What would you do in this situation?
For Seagate Exos users, do you adjust your drive's head parking values, or leave at default?
I used to disable EPC and PowerBalance on my Seagate drives and observed the same behavior. After awhile of using Seachest to disable these functions, I decided to re-enable them.
Mostly because I see no need to have the head hovering over my media at all times. I have no reason to save power, but I made this decision based upon how uncommmon it actually is to disable EPC and PB. Aside from a half dozen tech articles and various online posts.
In order for the drive to even get close to the amount of cycles they are rated for, you'd have to be witnessing some extremely aggressive head parking. (Based on 600k cycles) To give you an idea my drives park about 25 times daily on avg. (I have 3 min S.M.A.R.T. check intervals)
In my opinion and apparently every drive manufactuerer's default setting it's a good idea to leave defauly settings in place unless you have a really good reason. Even coming from a 24/7 always on, never spin-down datahoarder like myself I favor the "protections" of having the head safely placed away from the media over disabling EPC and PB. But to each is own.
I've heard a few horror stories of LSI HBA's causing some serious data corruption. Most of these cases were due to insuffiencient airflow. When it comes to data integrity I wonder if LSI HBA's in IT mode have more or less ability to detect errors or increase/decrease the risk of data corruption?
I was wondering what your approach is to using available SATA ports for your array.
I have six MB SATA ports and eight SATA available via HBA (9211-8i)
Do you recommend populating all available motherboard SATA ports first, then using an HBA for the rest of the array? Is it better to have all of the data disks if possible on the HBA first as a priority?
Do you guys recommend keeping many disks as possible on the same controller? (i.e. populating HBA first)
I'm looking to add some large Enterprise HDD's to my array and was wondering if a Long Smart Test would be sufficient before putting the drive into service?
I use Windows/Snapraid and have/use HDD Sentinel and also could run Read and/or write tests.
I'm curious what others testing methods are after a drive is shipped to them before putting it into service?
I'm looking to add some large Enterprise HDD's to my array and was wondering if a Long Smart Test would be sufficient before putting the drive into service?
I use Windows/Snapraid and have/use HDD Sentinel and also could run Read and/or write tests.
I'm curious what others testing methods are after a drive is shipped to them before putting it into service?
A Snapraid user has six data disks and two levels of parity.
If a second data drive dies during the "snapraid fix" operation for the first failed drive, will the fix for the first failed drive continue without issue?
If the fix for the first drive completes without issue should the user then perform another "snapraid fix" operation for the second failed drive?
Or should the first fix operation be cancelled and a fix operation started for both drives at the same time? ex: "snapraid -d d1 -d d2 -l fix.log fix"?
Similarly, if one of the two parity drives fails during a sync operation, will the second parity drive allow the operation to complete successfully without any interaction from the user?
The flash storage business is being spun off as an independent company.
