e2fsck takes more than 2 minutes ⇒ time out ⇒ breaks activation

• wb:2fe427e53715b2ba625077f567bc70e: success
• wb:76e5cbf93278a41eeba36105e386b1a6: failure

Logs

Jul 23 05:32:46 amnesia tpsd[6483]: INFO:service.py:360: Unlocking Persistent Storage...
Jul 23 05:32:52 amnesia udisksd[4435]: Unlocked device /dev/sda2 as /dev/dm-0
[…]
Jul 23 05:32:52 amnesia tpsd[6483]: INFO:device.py:763: [6783-Unlock] Executing command e2fsck -f -p /dev/dm-0
Jul 23 05:32:57 amnesia tpsd[7127]: TailsData: Inode 120088616 extent tree (at level 1) could be narrower.  IGNORED.
Jul 23 05:32:57 amnesia tpsd[7127]: TailsData: Inode 120090109 extent tree (at level 1) could be narrower.  IGNORED.
Jul 23 05:32:58 amnesia tpsd[7127]: TailsData: Inode 120095998 extent tree (at level 1) could be narrower.  IGNORED.
Jul 23 05:33:05 amnesia tpsd[7127]: TailsData: Inode 121014994 extent tree (at level 1) could be narrower.  IGNORED.
Jul 23 05:33:22 amnesia tpsd[7127]: TailsData: Inode 121634912 extent tree (at level 2) could be narrower.  IGNORED.
Jul 23 05:33:26 amnesia tpsd[7127]: TailsData: Inode 121634913 extent tree (at level 2) could be narrower.  IGNORED.
Jul 23 05:33:28 amnesia tpsd[7127]: TailsData: Inode 121634914 extent tree (at level 2) could be narrower.  IGNORED.
Jul 23 05:33:34 amnesia tpsd[7127]: TailsData: Inode 121634915 extent tree (at level 2) could be narrower.  IGNORED.
Jul 23 05:33:38 amnesia tpsd[7127]: TailsData: Inode 121634916 extent tree (at level 2) could be narrower.  IGNORED.
Jul 23 05:33:40 amnesia tpsd[7127]: TailsData: Inode 121634917 extent tree (at level 2) could be narrower.  IGNORED.
Jul 23 05:34:14 amnesia tpsd[7127]: TailsData: Inode 121634918 extent tree (at level 2) could be narrower.  IGNORED.
Jul 23 05:34:18 amnesia tpsd[7127]: TailsData: Inode 121634919 extent tree (at level 2) could be narrower.  IGNORED.
Jul 23 05:34:28 amnesia tpsd[7127]: TailsData: Inode 121634920 extent tree (at level 2) could be narrower.  IGNORED.
Jul 23 05:34:33 amnesia tpsd[7127]: TailsData: Inode 121634921 extent tree (at level 2) could be narrower.  IGNORED.
Jul 23 05:34:34 amnesia tpsd[7127]: TailsData: Inode 121634922 extent tree (at level 2) could be narrower.  IGNORED.
Jul 23 05:34:40 amnesia tpsd[7127]: TailsData: Inode 121634923 extent tree (at level 2) could be narrower.  IGNORED.
Jul 23 05:34:44 amnesia tpsd[7127]: TailsData: Inode 121634924 extent tree (at level 2) could be narrower.  IGNORED.
Jul 23 05:34:47 amnesia tails-greeter.desktop[6468]: [ERROR] persistent_storage.py:131 do_unlock_storage: Error unlocking Persistent Storage: g-io-error-quark: Timeout was reached (24)

Analysis

It seems this 120 seconds timeout is the culprit:

        self.service_proxy.call_sync(
            method_name="Unlock",
            parameters=GLib.Variant("(s)", (passphrase,)),
            flags=Gio.DBusCallFlags.NONE,
            # In some cases, the default timeout of 25 seconds was not
            # enough, so we use a timeout of 120 seconds instead.
            timeout_msec=120000,
        )

Original report

Tails fails to load the stored user settings from the Persistent Storage- Welcome Screen - external ADATA Disk 4TB.

Copied from the tails-dev:

(23/07/24 08:03:36) toptin: Good morning everybody, the problem isn't solved. It seems the timeout and the time it takes to activate the disk are just only seconds apart. So, when it takes just 1 or 2 seconds longer the Welcome Screen times out. I send two WhisperReports the first (Tails fails to load the stored user settings from the Persistent Storage- Welcome Screen - Tails 6.5 - ADATA Disk A) and the second (Tails fails to load the stored user settings from the Persistent Storage- Welcome Screen - Tails 6.5 - ADATA Disk B). The first one failed; the second one succeeds. Disk B is a clone of Disk A. If you search for toptin@ you should find them. They belong together, I send them for comparison purposes. I realize that not many people use such external disks, but nevertheless it shouldn't matter. BTW, I have a hard time to understand as to why the front-end needs to have a timeout setting. When I developed a frond-end that starts/managed background processes, I set the front-end up in such a way that it waits and the back-end to spew log messages etc. However, maybe someone could explain it to me or point me a document etc. Regards.

(23/07/24 08:24:33) toptin: Search result for "persisten" in the first WhisperReport: Line 5238: Jul 23 05:34:47 amnesia tails-greeter.desktop[6468]: [ERROR] persistent_storage.py:131 do_unlock_storage: Error unlocking Persistent Storage: g-io-error-quark: Timeout was reached (24)