![]() Then even the new MBP 16, using the same SSD, did crash as well many times during the restore. I had to reapeat the backup creation for about 6-8 times, 'cos the old MBP did creash / panic and reboot a lot of times during the backup creation (always with a IOSCSI error, so disk related). I did try to migrate MBP 2018 to 2019 using time machine on this new Sabrent SSD. So I've bought a Sabrent 2TB (Rocket with TLC chips, pretty fast on paper). ![]() ![]() I was using an external NVMe SSD 1TB from Samsung (970 EVO): never had a problem. The "old" one was a 6-core (16GB), with "inflated batteries" (incredible for such a premium machine, but. I've just migrated to a new 8-core i9 (32GB). Sabrent NVMe SSD :: Catalina panics and reboots with these SSDs. See below:Īs it stands, I believe this to be a compatibility issue with the OWC Aura Pro X2 SSD and MacOS Mojave, however I can't find anything to confirm this explicitly. Unfortunately, when loading the 'Marvell' utility my drive does not show-nor does anything-under the 'Device' group. Teh details of which, are available here: Having completed research on this issue I uncovered OWC's firmware update component, which I thought/hoped would be my saving grace, based on other comments in the aforementioned thread. MacOS's native diagnostic utility presented me with a 'VDH002' error-"There may be an issue with a storage device." I've attempted resetting SMC-both to no avail. I've attempted to restart PRAM on multiple occasions This is a new issue since the installation of the new SSD, which was built with the fresh installation of MacOS Mojave and a Time Machine restoration of data. MacOS Mojave compatibility with OWC Aura Pro X2 SSD Referring to an earlier thread-here: -I'm experiencing an issue following the installation of an OWC Aura Pro X2 SSD into my MacBook Air running MacOS Mojave 10.14.5.Īfter a period of inactivity/sleep my MacBook Air will restart itself-sometimes twice before properly booting back up-following any keystroke, rather than simply waking from sleep. Read 1 entries from Error Information Log failed: GetLogPage failed: system=0x38, sub=0x0, code=745 SMART overall-health self-assessment test result: PASSED St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat Optional Admin Commands (0x0004): Frmw_DL I've seen that it only can handle 300 and 400 times its capacity if refer to online information (like. Where my mackbook pro from 2017 which undergo the same intensity of work has only 136TB for 8%.ĭoes it mean that it my m1 SSD is at the end of its life? How is it possible that it can be such short (not even a year) ? After 292 days of work, it looks like it already has 134,28 TB of Data units written and it is already at 5% of prefailed reallocation (data from disk sensei). Hello, I start to worry about the SSD of my mac mini m1 16/512.
0 Comments
Leave a Reply. |