• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About jwells

  • Rank
  1. According to Microsoft bulletin: https://support.microsoft.com/en-us/kb/2510009 HDD's with 512b logical emulation over 4k physical sector (aka AF 512e) is not supported on Windows 10. How can that possibly be? The great majority of current generation large capacity HDD's are 512e. The only others are 512n (512b logical/physical) which is legacy old and seems to be limited to drives 4TB and under, and AF 4Kn (3096 logical/physical) which is fairly new and largely found only on enterprise drives. What the deal?
  2. Looking at buying a Samsung 850 Pro and a 960 pro. What advanced format scheme is used: 512e (logical 512b translated to 4k) or 4kN (native 4k)?
  3. Great answer. Appreciate it. I know helium hdd's haven't been around all that long, but is their reliability/longevity on par, worse or better than non-helium, all other factors constant? It seems that the possibility of a leak would just be one more mechanical thing that can go wrong. Sorry, I just realized this was posted to an ssd forum, should have posted to hdd forum. Is it possible to move to the correct forum?
  4. So, helium results in lower noise and lower weight? How so?
  5. Western Digital is coming out with a Red Pro 7200 8TB soon. I've looked at the stats here: http://www.wdc.com/wdproducts/library/SpecSheet/ENG/2879-800022.pdf If find it interesting that the idle noise on this beast is 20 dBA. Idle noise on all other 7200 Red Pro and Blacks are in a narrow range of 29-31 dBA, irrespective of size. The weight on the new 8TB is 1.43 lbs, vs. 1.56 lbs for the 6TB, 5TB, 4TB and 3TB Red Pro's. What could possibly account for these disparities, especially the much lower noise, other than a misprint?
  6. My current desktop PC at home currently has an all HDD setup, with O/S and Apps on one HDD and data files on another. I want to build a new PC and this time around I want to use solid state storage for O/S, Apps, and smaller data files. I will also get a big 6TB HDD for video files, movies and the like. The two choices I'm considering are: 1) get a large 2TB SSD, partition it, and put O/S and Apps on one partition and smaller data files on another partition, or 2) get two 1TB SSD's, and put O/S and Apps on one and smaller data files on the other. I need a fairly large O/S drive as I have multiple operating systems and copies each. The main consideration is this: would getting two SSD drives provide for perceptively snappier system response compared to putting everything on the same drive? It certainly helps to divide the work when using HDD's so that file opening doesn't bog down the system and vice versa. But I don't know if the same holds true in the world of solid state. Any input would be very helpful. BTW, the SSD's would be Samsung EVO or PRO SATA III in 2.5" form factor.
  7. I've always understood that, all other things equal, a large hard drive is slower than a small hard drive because the former has more space to seek. Is this true? Some comments on this forum and elsewhere, especially regarding the Hitachi 1TB drive, seem to suggest otherwise. What's the truth?
  8. Thanks much for all your responses. But I don't see how partitions are necessarily separate contiguous blocks of space. Imagine a one partition hard drive with files spread all over the place (beginning, middle and end). If you use Disk Director to create a new partition, it does so very quickly, implying that it is not consolidating files to create additional contiguous free space. On another matter, is the Raptor worth getting for an OS drive, i.e., will the system seem more responsive than if I used a 150GB 7200 Samsung Spinpoint T? Or will I simply be able to impress my friends with great benchmarks? Short of SCSI, any better suggestion for the OS drive?
  9. If I have a new 100GB hard drive and partition it into four 25GB partitions, and then install an OS on each partition, will the files for each OS be laid out in a physically discrete manner, as if you divided a pie into four slices. Or will the files for any one OS be spread out all over the hard drive but somehow identified as belonging to a particular partition. That is to say, is a partition a physically continguous space? If physically contiguous, then how does a partition program, like Disk Director, add a new partition if the existing partition is the entire hard drive and the existing files are spread out all over the place (beginning, middle and end of the disk). It seems that the program would have to first consolidate all the existing files into one section to make room for a new parititon. Yet, I don't believe this is what Disk Director does. The reason I ask is that I'm trying to decide between a 75GB or 150 GB raptor for my operating system drive. It will have XP, Vista and Ubuntu, and perhaps a copy of each. My understanding is that smaller HDD's find data faster because there is less physical space to search. However, if you have smallish parititions, does that mean seeks for any one partiular OS be limited to one smallish area on the hard drive, or will it still have to search the entire HDD. All comments would be welcome. Thanks.