Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
No entry sign on boot
- Thread starter mcmul
- Start date
- Sort by reaction score
Luckily, the bloody drive still works. I put the SSD into the enclosure and mounted it fine on Windows and Mac. Oddly, Windows reported a corrupted drive and Mac just read it fine. Very weird but copied off my XCode data nonetheless. I am going to reformat the drive and see if Disk Utility reports any disk errors. I am more confused than before.
I think it'll be the 13" retina with 8GB and 256GB SSD
Luckily, the bloody drive still works. I put the SSD into the enclosure and mounted it fine on Windows and Mac. Oddly, Windows reported a corrupted drive and Mac just read it fine. Very weird but copied off my XCode data nonetheless. I am going to reformat the drive and see if Disk Utility reports any disk errors. I am more confused than before.
I think it'll be the 13" retina with 8GB and 256GB SSD
Even if it works, I would never trust that drive again.
The problem that has occurred once, could occur again. If you win at Russian Roulette would you reload and have another go?
Good metaphor; bad assignment of it.
Of course, you're assuming that the drive is indeed at fault here and I'm not sure it is. Unlike the metaphor where there are (excuse my ignorance of guns; I'm English
) six "slots for a bullet" and only one bullet "in one slot" (queue American laughter), you will eventually lose because there is a one in six chance. However there is no such chance with the drive because it hasn't proven to be at fault. Couldn't one argue that OS X is the culprit for mismanaging the drive, or some app edited something it shouldn't have been? Unless someone with an in-depth knowledge of SSDs could attribute the following course of events to some type of SSD issue: the failure of the Mac to find the start-up disk, the failure of Disk Utility to "verify" the disk, the successful reading/writing of the drive in an enclosure by another system and finally the successful reformat of the disk.
Last edited:
Good metaphor; bad assignment of it.
Of course, you're assuming that the drive is indeed at fault here and I'm not sure it is. Unlike the metaphor where there are (excuse my ignorance of guns; I'm English
Unless someone with an in-depth knowledge of SSDs could attribute the following course of events to some type of SSD issue: the failure of the Mac to find the start-up disk, the failure of Disk Utility to "verify" the disk, the successful reading/writing of the drive in an enclosure by another system and finally the successful reformat of the disk.
Many machines fail before they are proven to be at fault.Reality is reality whether humans know the reality or not. On the basis of what has gone before I would not trust that drive with data that has any value whatsoever as there are plenty of drives that have not exhibited such issues (the first two failures you quote). The two successful indicators are just that, they aren't an exhaustive set of tests. While extended testing can give confidence in a drive (HDD or SSD, or indeed any other component), the wise will give further weight to errors, which are generally a positive indicator of failure at some level.
Again, your assertion that because the drive "hasn't been proven to be faulty" there "is no such possibility" is logical fallacy.
So is laying blame (in this case, the hardware) without any reason.
I agree that "[one should] give further weight to errors" but attributing these errors to the drive on the basis that "there are plenty of drives that have not exhibited such issues" (which is conjecture) isn't enough. How many people have encountered drive issues, done something e.g. format, and encountered no further issues?
The failures are reason enough for me - and I am not "attributing errors to the drive because other drives haven't exhibited such issues" (which is a complete logical error in any case). I am attributing the errors to the drive that you say have occurred and I am saying that those errors are enough evidence to not trust that drive to be fault-free.
Wait for absolute proof if you must, by the time you get it you may be in big trouble.
Dear Mr "E" - congrats on the blagging of a new rMP
I had EXACTLY this scenario last october, when my Crucial M4 SSD took a nose
dive and refused to boot under any circumstances.
It WOULD however allow itself to be seen in an external enclosure, thus allowing
me to rescue all my data - though I had a backup TM volume anyway.
With the M4 it was a "known" issue that after 4000 hrs use the "header" information
would possibly fail and the disk would have boot problems - something that I missed in
my research.
I have been using an EVO840 750gb since and have had no issues.
The M4 has been reformatted BUT I just didn't trust it as a boot volume and it was also
a bit too small... 256gb.
It is being used as an "audio recording / scratch drive" at the moment and doing well.
I would try getting a replacement from Samsung if I were you and I wouldn't completely
trust that drive as a boot volume anymore, just my opinion
Regards,
Martin.
I had EXACTLY this scenario last october, when my Crucial M4 SSD took a nose
dive and refused to boot under any circumstances.
It WOULD however allow itself to be seen in an external enclosure, thus allowing
me to rescue all my data - though I had a backup TM volume anyway.
With the M4 it was a "known" issue that after 4000 hrs use the "header" information
would possibly fail and the disk would have boot problems - something that I missed in
my research.
I have been using an EVO840 750gb since and have had no issues.
The M4 has been reformatted BUT I just didn't trust it as a boot volume and it was also
a bit too small... 256gb.
It is being used as an "audio recording / scratch drive" at the moment and doing well.
I would try getting a replacement from Samsung if I were you and I wouldn't completely
trust that drive as a boot volume anymore, just my opinion
Regards,
Martin.
If my car starts misfiring on the highway, and I trace it down to a coil pack which mysteriously after tinkering starts to work again, do I not replace it? Keep it as a storage drive sure! However, I seem to believe something is up then.
Thanks for the insight, Martin. I have requested an exchange with Samsung and just waiting for the DHL chaps to arrange collection. Meanwhile, I bought the Samsung Evo 256GB to go in the main drive slot. Then, whatever Samsung decide about the drive (knackered, new one; fine, same one), I will put that into the DVD slot for general scratch data/dropbox.
----------
Thanks for your thoughts
I will update with whatever Samsung say
Thanks for the insight, Martin. I have requested an exchange with Samsung and just waiting for the DHL chaps to arrange collection. Meanwhile, I bought the Samsung Evo 256GB to go in the main drive slot. Then, whatever Samsung decide about the drive (knackered, new one; fine, same one), I will put that into the DVD slot for general scratch data/dropbox.
----------
Thanks for your thoughts
I will update with whatever Samsung say
I look forward to hearing of their response, especially with a failure like this.
Delta did say "seem to", so its not like he made some scientific claim.
I will agree with him though. Just from anecdotal reports here from forum members it does seem like when an SSD dies it goes from working perfectly to full stop dead in an instant. No funny noises or error messages like hard drives.
lol :d
----------
Pretty understandable, HDDs read from a magnetic coating on the platters, that recorded signal can degrade in an analogue fashion, i.e. become weaker due to failing coating, weak write current etc etc, all of which contributes to the possibility of error-before-complete-failure.
SSD on the other hand is flash memory so failures of the logic gates are more binary, i.e. completely ok or utterly nadged without much in between.
I should have just asked this question in here:
But it has to be on Windows. My new SSD (purchased, not the potential warranty replacement) has arrived and I need to image it tonight. I would rather download it now rather than tonight via Internet Recovery.
Does anybody know any [OS X Mavericks] direct download locations, preferably from Apple? I can't use torrents.
But it has to be on Windows. My new SSD (purchased, not the potential warranty replacement) has arrived and I need to image it tonight. I would rather download it now rather than tonight via Internet Recovery.
Last edited:
I don't think these failures have anything to do with NAND failure. I think it is the controller that is failing.
Nope... no legal way to get it outside Internet recovery or on a Mac through the App Store.
Hm, I don't rate this Internet Recovery.
1. Fitted the new Samsung 840 Evo.
2. Booted into Internet Recovery.
3. Partitioned the drive.
4. Started the OS install, selected disk, agreed and accepted everything.
5. Downloaded the components, installed and then rebooted.
6. Shows the attachment.
Seriously, wtf?
Edit 1: I will note that this has happened twice now. The first time I decided to google the issue and seen people mentioning the Startup disk and it not being selected which makes sense. I then booted into IR again, opened Select Startup Disk and it wasn't there. Since then I have just reinstalled and the same thing has happened. Can someone help me out before I hit the single malt; HARD.
1. Fitted the new Samsung 840 Evo.
2. Booted into Internet Recovery.
3. Partitioned the drive.
4. Started the OS install, selected disk, agreed and accepted everything.
5. Downloaded the components, installed and then rebooted.
6. Shows the attachment.
Seriously, wtf?
Edit 1: I will note that this has happened twice now. The first time I decided to google the issue and seen people mentioning the Startup disk and it not being selected which makes sense. I then booted into IR again, opened Select Startup Disk and it wasn't there. Since then I have just reinstalled and the same thing has happened. Can someone help me out before I hit the single malt; HARD.
Attachments
Please see the attachments. Note that it I checked this before the second install and it, eventually, repaired and verified fine. Do you think this could be the Mac rather than SSD?
Attachments
It may be the Logic Board SATA controller or potentially a degrading cable...