Just because you were lucky and something that could be a very realistic possibility didn't affect you before, doesn't mean that it wouldn't at some pony or that essentially ignoring it because you've been lucky is somehow a rational excuse.
Apple Seeds Sixth Beta of macOS High Sierra 10.13.3 to Developers and Public Beta Testers [Updated]
- Thread starter MacRumors
- Start date
- Sort by reaction score
MacHiavelli
macrumors 65816
Does CMD R on a cold boot give the same error?
It is beta software, it specifically says do not run it on a production machine. You agreed to the terms and conditions when enrolling in the beta program.
https://beta.apple.com/sp/betaprogram/faq
"Install the beta software only on non-production devices that are not business critical. We strongly recommend installing on a secondary system or device, or on a secondary partition on your Mac."
TVreporter
macrumors 68020
Not this bata, the last approved update that was issued bricked it. I don’t know how to fix it
[doublepost=1516450329][/doublepost]
I never installed bata??? It’s the last update that did this ... are you suggesting I ended up with a bata version because I am not enrolled in any program.
You are commenting in the thread for beta software release, hence everyone assumes you are running a beta version of the operating system on a production machine, which is why you are not getting any sympathy.
Have you tried any of the following:
SMC reset: https://support.apple.com/en-gb/HT201295
NVRAM reset: https://support.apple.com/en-gb/HT204063
try to start in Safe mode: https://support.apple.com/en-gb/HT201262
Disconnect all external devices such as hard drives, DVD drives, card readers, even USB keyboard and mouse and then try to start the machine. this test is to eliminate the possibility of a faulty device preventing the computer from booting.
Use another mac to install a fresh copy of Sierra onto an external USB hard drive. Connect this hard drive to your Mac press and hold OPTION key during boot to bring up the start up manager https://support.apple.com/en-gb/HT202796, then boot from the USB disk and use disk utility to try to repair your internal disk.
squirrelist
macrumors regular
Yes, six versions of the same BETA are beyond ridiculous. It's like they have no clue what they're doing as far as fixes, let alone thinking about improvements.
Six betas is pretty typical for Apple. And not just recently. If you Google "mac os x sixth beta" you'll see many news articles of beta sixes over the years. Even betas eight (10.6.7), and nine (10.9.3 which was in beta for two months compared to this beta lasting only about six weeks so far). I'm not saying your conclusion is wrong, but the number of betas has little to do with it.
chrfr
macrumors G5
If you don't want to reboot your computer every week, don't install the betas. Seems pretty simple to me.
As others have said, this number of betas is, and has been, common for OS X/macOS for many years, even back when Steve Jobs was still alive and in charge.
It appears to me that one of your system storage devices ("hard drive" or SSD) has a problem. When that is serious enough, all bets are off.
The reason I am giving this opinion is because the terminal is showing fsck_hfs ("fsck" for short) running at the top of the screen shot. That normally would only run when there are problems on the hard drive or storage device. Sometimes fsck can fix things up; other time if the hard drive is actually failing, you will not be able to recover. In such a case it has nothing to do with MacOS, or betas, but rather hardware failure. Unless in the odd case that they have introduced bugs into the fsck process.
I am responding only because nobody has chimed in so far, and am judging only at a high level, without detailed knowledge of the specific messages in your screen shot, but rather general knowledge that fsck is running.
Someone with more expertise with fsck can shed more light.
KingOfStuff
macrumors regular
I reminisce about the days of my Mac Pro not being re-booted for 6 months.
Or when there were not 6 versions of the same beta. What are they? Monkeys throwing paint at a wall?
Why doesn't Apple realize it's lost not only its edge, but also its biggest marketing thing about why Macs are/were better.
I cringe every time I see this image. It usually means screwing with my MAIL server settings and bad news.
Hey Timmy! My Mac was SET UP with the FIRST High Sierra release. How many times do you want to screw it up?
Another note: Command-B still lights up in "Format" when you click on it, but it still only works half the time when writing a message. I've been reporting this since Sierra, but apparently no one takes it seriously. I cannot think of any reason why this would affect me and not other since I've tried different keyboards and clearly Command-B works here.
Whole Heartedly agree with you.
BaltimoreMediaBlog
Suspended
You obviously missed my point. Six versions of the SAME beta did not used to be common. You released a new beta number, not screwed up versions of the same one over and over and over.
The appearance of releasing the same beta over and over and over is simply that you do not know what the hell you are doing! And that's what I'm starting to wonder.
This beta is the same as the previous one which is the same as the one before it and so forth? Based on what?
BaltimoreMediaBlog
Suspended
Apparently you were not born in the days of Leopard and Snow Leopard. There simply were NOT SIX of THE SAME BETA! It simply did not take 6 tries to get it right back then. And to add insult to injury, they ignore the reports I send in, so that boggles my mind as to actually WHAT they are really fixing.
A 10.13.4 might give me some confidence, but it looks like they are stuck in this rabbit hole for quite some time.
Sounds like basically a misunderstanding of the beta process that is attempted to be hidden with strawman, ad hominem, and other similar type of arguments.Apparently you were not born in the days of Leopard and Snow Leopard. There simply were NOT SIX of THE SAME BETA! It simply did not take 6 tries to get it right back then. And to add insult to injury, they ignore the reports I send in, so that boggles my mind as to actually WHAT they are really fixing.
A 10.13.4 might give me some confidence, but it looks like they are stuck in this rabbit hole for quite some time.
BaltimoreMediaBlog
Suspended
Simply further confirmation of the observation I made.No, you obviously are too young to remember how the beta process was.
chrfr
macrumors G5
No, you utterly misunderstand how the beta process works. Perhaps beta builds were not always publicly available, but Apple certainly has not ever just written up one or two versions of a system update and released it.No, you obviously are too young to remember how the beta process was.
squirrelist
macrumors regular
I'm not sure what you mean. Are you saying that these past six betas are identical and that they haven't made any modifications from one beta to the next? Or that they haven't addressed the bug reports that you filed?
What I'm saying is that OS X Snow Leopard 10.6.7 went through a two and a half month beta process with eight beta releases. That's probably the most in OS X history, but there are many other point releases that went through a beta process that hit a beta 6 and a beta 7.
I sure hope that with this "update" that they fix the issue with the FUSION DRIVES for people like me who have one of the earlier models of that particular model style. They said originally that they would include Fusion Drives in a future update and I have yet to see it. So I hope they follow through as promised.
I might be late but have a question? Is macOS High Sierra fusion drive friendly yet? I remember when it first came out it wasn’t and there was a rumor that they might work on it
Apple today seeded the sixth beta of an upcoming macOS High Sierra 10.13.3 update to developers, just a few days after seeding the fifth beta and more than a month after releasing macOS High Sierra 10.13.2, the second major update to the macOS High Sierra operating system.
The new macOS High Sierra 10.13.3 beta can be downloaded from the Apple Developer Center or through the Software Update mechanism in the Mac App Store with the proper profile installed.
It's not yet clear what improvements the macOS High Sierra 10.13.3 update will bring, but it's likely to include bug fixes and performance improvements for issues that weren't addressed in macOS High Sierra 10.13.2.
It does offer additional fixes for the Spectre and Meltdown vulnerabilities that were discovered and publicized in early January and fixed initially in macOS High Sierra 10.13.2.
The update also fixes a bug that allows the App Store menu in the System Preferences to be unlocked with any password.
The previous macOS High Sierra 10.13.2 update focused solely on security fixes and performance improvements, with no new features introduced, and a supplemental update introduced a fix for the Spectre vulnerability.
Update: Apple appears to have temporarily pulled the macOS High Sierra 10.13.3 update, and it is no longer available for download from the developer site.
Update 2: The macOS High Sierra 10.13.3 update is once again available to download.
Article Link: Apple Seeds Sixth Beta of macOS High Sierra 10.13.3 to Developers and Public Beta Testers [Updated]
loby
macrumors 68000
Yes, I was dumb and made that error and when working on HS beta 1 on my production machine it ruined my FCPX project. Had to go back to Sierra and rebuild my project over again.
The Friar
macrumors member
Why the hell would Apple release 6 beta's that are all the same? It just isn't making any sense at all.
The changes may not all be directly noticeable but i bet there are changes in every beta.
squirrelist
macrumors regular
High Sierra has always worked with Fusion Drives. It's APFS that doesn't work with Fusion Drives yet. So if you have a Fusion Drive and you upgrade to High Sierra your Fusion Drive will just be left using HFS+, which is fine.
chrfr
macrumors G5
Of course the betas are different. The supposition that all 6 are the same is ridiculous.
LarryJoe33
macrumors 68030
I do not understand the people whining about betas, reboots, bugs, etc. when they choose to be in the beta program. Then they bitch about Apple to no end with every release. Christ, just use the official release and be like the general public.