Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Constant backups are essential when using a computer without user-serviceable storage. That or mounting another [network] drive and doing all your work from that instead of internal storage. Otherwise you'll be without your data for hours if not days/weeks whenever something inevitably goes wrong (not even with the storage itself) and you can't simply pull the drive to continue working on another computer.


M1 won't boot without internal storage.

The point of the parent comment was not about saving data from the drive, but that the devices are landfill material once they hit tbw limits on their drives, even if they were otherwise in good condition.


Sure it will. Just checked, found a bunch of articles with 5 step instructions where one of the steps is hold the power button down.


> The M1 boot process requires a working SSD to boot macOS. The SSD contains a Signed System Volume that is cryptographically sealed by Apple. No seal, no bootable System.

> So if the internal drive on your M1 Mac fails completely, even an external bootable drive won't boot. Yep, your Mac is bricked.

https://www.zdnet.com/article/how-bad-is-the-m1-macs-ssd-fai...


Well you'll not hit TBW limits if you're using another drive anyway.


Unless you have configured your Macbook to not use Swap, it will constantly write to the built-in drive when memory pressure is high enough.


> Constant backups are essential when using a computer without user-serviceable storage.

Constant backups are a necessity even if your computer has RAID-6 storage built on enterprise-grade storage.

Your office can catch fire. You can be hit by ransomware. Multiple devices in the array can fail in rapid sequence (happened to me once). Your computer can get stolen (happened to me, twice).

Have an offsite backup always on hand.


Or just not caring about any data you have locally.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: