This is a little weird.
I have an ancient Mac Pro 4.1 on OSX 10.11.6. Recently there have been a number of 'refurbished' 6Tb hard disks on the market.
I bought a particular model and found that it mounts and works fine on power-up, but does not mount on restart. This issue only occurs when this model (HGST HUH728060ALE600) is installed internally. It works fine as an external drive on the USB bus (albeit a lot slower).
A different drive, same brand, same size, but different model (HGST HUS726060ALA640) works fine internally and externally.
The main difference between the specifications of these two is the one that works has a 64Mb cache and the one that doesn't mount on restart has a 128Mb cache.
My first thought was I had a bad drive. I returned it and several weeks later I got a second drive from a different retailer - and it does the same thing.
Anybody else seen anything like this?
Anybody know why?
My guess is it's a firmware bug on that particular model drive - but that's a guess with only negative evidence. I know it isn't the size and I know the drive works - I don't have a way to review the firmware. Is there an error log somewhere that would show something?
I have an ancient Mac Pro 4.1 on OSX 10.11.6. Recently there have been a number of 'refurbished' 6Tb hard disks on the market.
I bought a particular model and found that it mounts and works fine on power-up, but does not mount on restart. This issue only occurs when this model (HGST HUH728060ALE600) is installed internally. It works fine as an external drive on the USB bus (albeit a lot slower).
A different drive, same brand, same size, but different model (HGST HUS726060ALA640) works fine internally and externally.
The main difference between the specifications of these two is the one that works has a 64Mb cache and the one that doesn't mount on restart has a 128Mb cache.
My first thought was I had a bad drive. I returned it and several weeks later I got a second drive from a different retailer - and it does the same thing.
Anybody else seen anything like this?
Anybody know why?
My guess is it's a firmware bug on that particular model drive - but that's a guess with only negative evidence. I know it isn't the size and I know the drive works - I don't have a way to review the firmware. Is there an error log somewhere that would show something?
Last edited: