<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Macos on Philippe-Anselme logs</title>
    <link>https://mtwabp.fr/tags/macos/</link>
    <description>Recent content in Macos on Philippe-Anselme logs</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>© Philippe-Anselme Foury</copyright>
    <lastBuildDate>Mon, 24 Aug 2026 01:03:00 +0000</lastBuildDate>
    <atom:link href="https://mtwabp.fr/tags/macos/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Réparer ses backups Time Machine</title>
      <link>https://mtwabp.fr/posts/2026-08-24_time-machine/</link>
      <pubDate>Mon, 24 Aug 2026 01:03:00 +0000</pubDate>
      <guid>https://mtwabp.fr/posts/2026-08-24_time-machine/</guid>
      <description>&lt;p&gt;Mes sauvegardes Time Machine ne fonctionnent plus depuis quelques jours / semaines. Je dois intervenir.&lt;/p&gt;&#xA;&lt;p&gt;Après quelques recherches sur internet sans grand succès, j&amp;rsquo;ai finalement trouvé ce que je cherchais.&lt;/p&gt;&#xA;&lt;p&gt;Visiblement macos n&amp;rsquo;aime pas quand il y a plusieurs snapshots en stagmation qui n&amp;rsquo;ont pas été transférés. Voici les commandes pour voir les snapshots actuellement sur le système et comment les supprimer. Ensuite il suffit de relancer la procédure de sauvegarde.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to fix my Apple external hard drive</title>
      <link>https://mtwabp.fr/posts/2026-06-24_r%C3%A9parer_time_machine/</link>
      <pubDate>Wed, 24 Jun 2026 06:27:00 +0000</pubDate>
      <guid>https://mtwabp.fr/posts/2026-06-24_r%C3%A9parer_time_machine/</guid>
      <description>&lt;p&gt;After a couple of hard restarts, my external USB hard drive finally showed up as &amp;ldquo;unprepared&amp;rdquo; on my Mac mini. That was when I started to sweat.&lt;/p&gt;&#xA;&lt;p&gt;I knew the hard drive was old and certainly flaky. However, it was not making any strange sounds, so I assumed the problem was not hardware-related. It was more likely an issue with bad sectors being written. This meant several things:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;first, all the data was not lost &lt;em&gt;yet&lt;/em&gt;&lt;/li&gt;&#xA;&lt;li&gt;second, a lot of it could be retrieved with the right tools&lt;/li&gt;&#xA;&lt;li&gt;third, I must not &amp;ldquo;prepare&amp;rdquo; the disk, as that would wipe all its contents.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;I think the hardest part about losing data is not what you actually lose, especially because anything important should already be backed up. It is what you do not know you have lost: the infamous unknown unknown.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
