Okay, so I have a SSD in main drive and a HDD in optibay of my MBP. I was having that clicking of my HDD so I adjusted the hdapm to max, issue fixed no problems at all.... but that got me thinking, I started looking at my BSD names of my disks (example: disk0, disk1, disk2, etc).
My SSD was originally named disk1 and my HDD was disk0... so I set the .plist accordingly so the hdapm was run on startup... to my shock my disks have switched a few days back.
My SSD is now disk0 and my HDD is disk1.
Well today I checked again, my SSD is still disk0 but my HDD is disk2 now... so of course the .plist is not running hdapm on startup because the HDD keeps switching it's BSD name.
Anyways, common error? Something random? Anybody have any idea what's up?
My SSD was originally named disk1 and my HDD was disk0... so I set the .plist accordingly so the hdapm was run on startup... to my shock my disks have switched a few days back.
My SSD is now disk0 and my HDD is disk1.
Well today I checked again, my SSD is still disk0 but my HDD is disk2 now... so of course the .plist is not running hdapm on startup because the HDD keeps switching it's BSD name.
Anyways, common error? Something random? Anybody have any idea what's up?