![st4000vn000 crystal diskmark st4000vn000 crystal diskmark](https://i.imgur.com/K2uKi8P.jpg)
- #St4000vn000 crystal diskmark serial
- #St4000vn000 crystal diskmark update
- #St4000vn000 crystal diskmark full
- #St4000vn000 crystal diskmark pro
- #St4000vn000 crystal diskmark verification
Like the other disks I tried, this first generation Seagate is officially supported by my NAS and was used to replace a generic 7200RPM 500GB Samsung hard drive bought in 2011 and which has worked fine but is now full to the brim. After the bad experiences with the other two drives, I thought let me have one more go with an older model Seagate before trying a Western Digital Red which reviews indicate has reliability problems. See my other reviews for more details on these two drives.īack to this Seagate ST2000VN000 then. Both were officially supported by my NAS but neither was suitable the Hitachi arrived faulty and failed to initialise whilst the Seagate, although fast, was noisier than a room full of kids in a crisp eating contest. I first tried a 3TB Hitachi HGST IDK Deskstar NAS drive and then a 2TB Seagate ST2000VN0001 NAS drive. This is a really good fast drive and best of all super quiet. I bought this drive 3 months ago from Appods (fulfilled by Amazon) and it's been used 24/7 in a DLNA wired and wireless streaming NAS environment.
#St4000vn000 crystal diskmark update
So all in all very happy with the drives so I'll update my rating but still critical of the packaging. Hitachi drive although being 7200rpm and having better transfer rates was more expensive and to be honest the extra performance would be wasted in my Microserver as it just streams to the TV's/PC's etc in the house. The Red's seem to have a few issues with the early drives failing and the These are the first Seagate drives I've bought in a long time it was a choice between these, the WD Red 4TB and the Hitachi NAS 4TB. Performance wise the drives are fine, faster than the 2TB WD Greens they replaced with about the same power draw looking at the specs. Uncorrectable Sector Count : This can indicate an issue with the discs themselves of the heads that read them.Įxcept for a few SMART items where the raw info was not correct (manufacturers set up their drives differently so apps can have issues reading the raw data) all the info was fine with almost all zeros. This can be an early sign of issues with a drive.
#St4000vn000 crystal diskmark verification
Reallocated Sectors Count : If the drive finds a error with its read,write or the verification it does it will mark the area and move the data to another area on the drive.Ĭurrent Pending Sector Count : If an area of the drive failed but the next time it was accessed it was okay it's recorded here as it may be unstable and need moving.
#St4000vn000 crystal diskmark pro
Then I ran a full health and error check with HD Tune Pro (downloaded the 15 day free trial version as the freeware version has a 2TB limit on volume size).Īll of the SMART info checked out OK the critical ones to check seem to be:
![st4000vn000 crystal diskmark st4000vn000 crystal diskmark](https://aphnetworks.com/review/seagate-laptop-sshd-st500lm000-500gb/cdm4.png)
![st4000vn000 crystal diskmark st4000vn000 crystal diskmark](https://www.technologyx.com/wp-content/uploads/2013/09/Crystal-DiskMark.png)
Well the drives had survived, ran a full error check on both drives with Seagates own utility ( not very informative as just gives a pass/fail) but Just waiting for a backup to complete on my sever before I can test the drives out and see if they survived. The proper brown cardboard boxes with the plastic end covers/supports or the foam lined boxes we used to get with hard drives ? Two drives in antistatic bags in a box with a bit of crumpled brown paper !! What happened to
#St4000vn000 crystal diskmark serial
I record the wwn numbers and serial of each drive, and a copy of any test notesĨTB wwn-0x5000cca03bac1768 -Failed, 26 -Read errors, non recoverable, drive is unsafe to use.ĨTB wwn-0x5000cca03bd38ca8 -Failed, CheckSum Errors, possible recoverable, drive use is not recommend.Arrived this afternoon, drives look okay which is surprising considering the lack of any kind of protective packaging. If everything passes, drive goes into my good pile, if something fails, I contact the seller, to get a partial refund for the drive or a return label to send it back. Sudo zpool import -d /dev/disk/by-id TESTR001ĥ) ZFS Scrub to check any Read, Write, Checksum errors. Zpool create -f -o ashift=12 -O logbias=throughput -O compress=lz4 -O dedup=off -O atime=off -O xattr=sa TESTR001 /dev/sdxx No one knows why this happens but it does. So I pulled the drive re ran my test with compression on. I would put it back into the pool and errors would appear again. So I pulled and ran my test without compression on.
![st4000vn000 crystal diskmark st4000vn000 crystal diskmark](https://revimg03.kakaku.k-img.com/images/Review/000/301/301514_m.jpg)
I had a drive that would produce checksum errors when it was in a pool. I have a dedicated testing server setup.Ģ) BadBlocks -This is a complete write and read test, will destroy all data on the driveīadblocks -b 4096 -wsv /dev/sdxx > $disk.logģ) Format to ZFS -Yes you want compression on, I have found checksum errors, that having compression off would have missed. Testing can take anywhere from 4-7 days depending on hardware. This is something I developed to stress both new and used drives so that if there are any issues they will apear.