search

kasbert / OS-X-SAT-SMART-Driver

Max OS X kernel driver for providing access to external drive SMART data
578 stars 74 forks source link

FW harddisks want mount with 0.9 #29

Open macuserguru opened 9 years ago

macuserguru commented 9 years ago

First I use SATSMARTDriver-0.9 from here and from http://binaryfruit.com/download/mac/satsmartdriver/SATSMARTDriver-0.9.zip too With SATSMARTDriver-0.9 LaCie d2 Quadra v2 1TB on FW400 don’t mount. The FW HDs are not seen in Macs Disk Utility application too!

Second I use SATSMARTDriver-0.8 from http://binaryfruit.com/download/mac/satsmartdriver/SATSMARTDriver-0.8.zip With SATSMARTDriver-0.8 LaCie d2 Quadra v2 1TB on FW400 mount! The FW HDs are seen in Macs Disk Utility application too!

Another bug: If my WD 2TB My Passport 2TB are mounted. With SATSMARTDriver-0.9 the SMART values from WD 2TB My Passport 2TB are not seen, no connection over USB2 available. With SATSMARTDriver-0.8 the SMART values from WD 2TB My Passport 2TB seen, connection over USB2 available - works well. This I test with Mavericks 10.9.5 on MBP late 2008

Whats the difference between SATSMARTDriver-0.8 and SATSMARTDriver-0.9 ?

kasbert commented 9 years ago

I'm sorry to hear that 0.9 does not work for you. Version 0.9 first probes for JMicron chip and then tries SAT16 mode and SAT12 mode as the last resort. Version 0.8 basically used SAT12 mode, since SAT16 was broken. It is possible that JMicron probe or SAT16 mode causes problems.

I changed the probe order to sat12,sat16,jmicron. Please try the version 0.10-Debug to see if did any change.

macuserguru commented 9 years ago

Now I tested 0,10-Debug on my MacMini (Snow Leopard 10.6.8) - it works well. All connected and reported SMART values good - tested with DriveDxReport: LaCie d2Quadra v2 with Hitachi Deskstar 7K1000.B - on FireWire400 WD 2TB My Passport Ultra - on USB2 Seagate 2TB (Backup Plus 'blue') - on USB2 iomega eGo 500GB with SAMSUNG SpinPoint M7 - on USB2 Seagate Desktop HDD.15, 4TB (3.5") - on USB2 Seagate-750GB in Sharkoon Quickstore Portable case - on USB2

Don't read SMART over 2.5" case - Icy Box IB-231 Series

kasbert if you give me your email address I could send you my complete DriveDxReports and a pice from the kernel log with debugging informations.

macuserguru commented 9 years ago

with Mavericks 10.9.5 I will test them if 0.10-Debug runs stable = no other post problems with.

kasbert commented 9 years ago

Please send email to OS-X-SAT-SMART-Driver@dungeon.fi

kasbert commented 9 years ago

Please try a new SATSMARTDriver-0.10-Debug version. Firewire "LaCie d2Quadra" should report something else than "'Unknown 0000:0000'"

I guess "Icy Box IB-231" does not support SAT, so I blacklisted it.

macuserguru commented 9 years ago

Thanks - I will test them next days.

macuserguru commented 9 years ago

SATSMARTDriver-0.10-Debug or SATSMARTDriver-0.8 kext don't run in Yosemite - bad signature.

killerovsky commented 9 years ago

Unsigned driver package installer don't run in Yosemite (if package was downloaded from internet), kext itself is working in Yosemite.

killerovsky commented 9 years ago

Removing of "quarantine" extended attribute should help. Try to type following command: xattr -d com.apple.quarantine /PATH/TO/DRIVER_PACKAGE

macuserguru commented 9 years ago

I would test this later. Now runs a data restore from TM backup.

kasbert commented 9 years ago

Seems that Yosemite blocks unsigned kernel extensions. However, there is a list of exceptions to that rule (inside one Apple kext). I have no idea how SATSmartDriver got into that list, but versions 0.8 and 0.9 are there and they will work with Yosemite.

alvarnell commented 9 years ago

On Sun, Nov 09, 2014 at 10:56 PM, Jarkko Sonninen wrote:

Seems that Yosemite blocks unsigned kernel extensions. However, there is a list of exceptions to that rule (inside one Apple kext). I have no idea how SATSmartDriver got into that list, but versions 0.8 and 0.9 are there and they will work with Yosemite.

Might be due to their inclusion in SMART Utility and DriveDX?

I can file a report with Apple concerning 0.10 if you think that is necessary at this point.

Have you considered signing them?

-Al-

Al Varnell Mountain View, CA

kasbert commented 9 years ago

I guess signing would need an Apple developer license, which costs $99. Even though I might afford that, I don't want to spend money for a hobby project.

There are issues with some enclosures hanging on boot/connect and I think I should do something for them (either blacklist or fix). I was hoping that the enclosure info could be configured by modifying Info.plist, but the signing prevents that. Normal solution would be using a userspace daemon to set the configuration, but that won't work at the boot time.