Strange issue with Windows 10 and HGST Ultrastar DC HC510 | HUH721010ALN600 (0F27607) | 10TB 7200 RPM 4Kn

[lepa71]

Hi all.
I bought 2 drives to try as a backup drive with enclosure for my windows 2016 server essentials. One is MDD - HGST Ultrastar DC HC510 | HUH721010ALN600 (0F27607) | 10TB 7200 RPM 4Kn and another is HGST Ultrastar He8 Helium (HUH728080ALE601) 8TB. I believe 8TB drive is not 4kn.

The thing is. This 10TB drive is usable in windows explorer on windows 10 laptop. I can read and write into it. This drive is a 10TB 4kn connected to a laptop with W10 via enclosure. Disk sentinel can't recognize it but when I connect this to my Windows server 2016 then DIsk Sentinel works fine and can see all smart info from the drive. I think it is my windows 10 is the potential problem.

Any idea if the 4kn drive has issues with windows 10? I was trying to do a writing test for 10TB drive as both drives are refurbs.
Thanks

 

[Moopere]

Win10 shouldn't have any problems with a 4Kn hdd. However, using it in a USB enclosure might introduce who-knows-what variables depending on the SATA->USB interface.

Are you also connecting the disk to Windows server 2016 via the USB enclosure ... or directly into a backplane?

 

[CyklonDX]

so sas disks won't always be visible through your normal sata/usb controllers. SAS disk most often require SAS controller. Not sata one.
*(some sata controllers will allow you to plug in sas disks, but 99% of them won't.)

 

[Moopere]

@CyklonDX: I looked up the part numbers provided and they are both SATA disks.

The OP says that the 10TB disk can be seen by Win10 and read/write, so on face value all should be good. The fact that Disk Sentinel can't see the drive when its connected to an external enclosure makes me think its a DS problem - perhaps not recogised internally (to DS) ... but this must be because of some translation confusion with the SATA-USB interface in the external enclosure as DS apparently works fine when the same drive is connected to Windows Server 2016 ... I'm assuming now that the disk is being connected to Server 2016 directly, via backplane or other method.

 

[CyklonDX]

~my bad.

In such case - the 4kn partition blocks could potentially also be not recognized by some older devices (In past it was hit/miss with controllers with 4kn). Not sure if all versions of win10 have support for 4kn either - i know they've been cutting home/student editions quite aggressively.

 

[i386]

4Kn (not 512e!) support was added in windows 8/server 2012.
I don't have 4kn hdds, but husmm ssds that I formated back and forth and they worked in windows 10 and 11 (and the server version) without problems.
From what I read over the years the sata <-> usb controllers/adapters/enclosures can't handle 4kn devices and will cause problems