Re: [smartmontools-support] I'd like to fix read failure issue on Mac OS X

[Kimio M. <xa...@ap...>]

2014/12/19 19:12, Tim Small <tim <at> seoss.co.uk> wrote: 

>> I can do zero-disk for entire my hdd if it required.  Can this fix the
>> issue?
> 
> As this sector isn't user-addressable, then a normal zero-out won't work
> I think.

OK I understand.

> There are two things you could try - both will use hdparm, don't know if
> that's available under OSX, but if it isn't, you can use use the grml
> boot disk which you already have instead.
> 
> First try using hdparm --write-sector on the sector which the drive is
> reporting as in-error.

I have tried it with 2 configuration.

a. Connect hdd using USB bridge.  i.e. I ordinary use this hdd as USB external drive by putting hdd into USB-SATA bridge enclosure.

$ hdparm --yes-i-know-what-i-am-doing --write-sector 976783240 /dev/sdc
/dev/sdc:
re-writing sector 976783240: FAILED: Invalid argument The running kernel lacks CONFIG_IDE_TASK_IOCTL support for this device.

Where 976783240 is the LBA which "smartctl -l selftest" provides.  I have googled "CONFIG_IDE_TASK_IOCTL", but I can't figure out what the word mean.


b. Put the hdd into my mac.  I have a macintosh computer which can replace hdd.

$ hdparm --yes-i-know-what-i-am-doing --write-sector 976783240 /dev/sdc
/dev/sdc:
re-writing sector 976783240: FAILED: Input/output error

I don't know why "Input/output error" occurs...


> https://ata.wiki.kernel.org/index.php/ATA_Secure_Erase
> 
> ... substitute --security-erase-enhanced in "step 3" if hdparm -I shows
> it's supported, as I think this will have the greatest chance of
> overwritting "everything".

With above configuration "b", I have tried to set security password to invoke security erase.  then I got same "Input/output error" error as above.

In fact, even though I have read the wiki you provided, I have tried to security erase with USB connection.  
Then the result was "The running kernel lacks CONFIG_IDE_TASK_IOCTL support for this device" and when I boot my mac normally, I need to initialize the hdd which annoying me.



Am I entered into deep place which normal Mac user never run into?  There is a Mac application which uses smartctl internally.  The application does not warn at all  because this hdd's S.M.A.R.T. status is still OK.  Normal Mac user accepts this and never doubt it.  I also know that "smartctl" which I installed manually reports this hdd's S.M.A.R.T. status is OK.
I am wondering weather I should give up or not...


// Miya