Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backup location disabled after backup failed on re-formated flash drive #805

Open
An-anonymous-coder opened this issue Nov 28, 2024 · 9 comments
Labels
bug needs info Requires more information from reporter

Comments

@An-anonymous-coder
Copy link

An-anonymous-coder commented Nov 28, 2024

After GrapheneOS updated Seedvault in their latest release, I'm running into an issue. I'm going to give a rough outline of what may have caused it:

  1. Format a new USB drive for Android storage. The name of it is "android", I don't know if there is a way to change this.
  2. Using the old version of Seedvault, create a backup location inside the drive
  3. Backup like normal
  4. Eject the drive
  5. Update Seedvault to the new version
  6. Insert the USB drive
  7. Format the USB drive. This will wipe the Seedvault data and the device will be named "android" still.
  8. Open Seedvault

You will receive a notification "Backup failed: An error occurred while running the backup"

The option to select the backup location is grayed out, even when the USB drive is not plugged in.

Backup scheduling is set to 1 week. Backup status says "Last backup: Never", even though it has been backed up recently.

I essentially have no way to backup to this USB drive now, or anywhere else since I can't change the backup location.

version 15-5.1
versionCode 35050010
Android 15: GrapheneOS 2024112700
@An-anonymous-coder
Copy link
Author

I like to frequently format the USB drive for backup sanity and cleanliness, especially after major updates like this.

@An-anonymous-coder
Copy link
Author

An-anonymous-coder commented Nov 28, 2024

I tried formatting the drive off-device and naming it something other than "android". Same error message, still no way to change backup location.

Should I clear Seedvault's cache and storage?

@grote grote added bug needs info Requires more information from reporter labels Nov 29, 2024
@grote
Copy link
Collaborator

grote commented Nov 29, 2024

Can you reproduce the issue using steps 6 to 8 only? I just want to be sure that the upgrade to the new version is not involved here.

Otherwise, frequently reformatted the backup medium isn't something we really tested so far.

Should I clear Seedvault's cache and storage?

Yes, if there's no data to lose, you can do that, also to get back to a working state to reproduce 6-8 above.

If you can reproduce, and after formatting, backup fails and you can't change storage location, then please export logs from expert settings and post them here. Thanks.

@grote grote changed the title Unable to format new drive for backup Backup location disabled after backup failed on re-formated flash drive Nov 29, 2024
@An-anonymous-coder
Copy link
Author

An-anonymous-coder commented Nov 30, 2024

I cleared cache and storage and I was able to backup as normal.

Repeating steps 6-8 reproduced the bug. I didn't receive an error notification. It says the last backup was (correctly) 5 minutes ago. Here is a revised bug report:

  1. Format a new USB drive for Android storage. The name of it is "android", I don't know if there is a way to change this.
  2. Create a backup location inside the drive
  3. Backup like normal.
    After the backup is finished, you may eject and reinstert the flash drive, if desired. This isn't necessary.
  4. Format the USB drive. This will wipe the Seedvault data and the device will be named "android" still.
  5. Open Seedvault

You will not be able to select a backup location or create a backup.

seedvault-15-5.1-1732926357439.txt

There may be some oddities around the log, if that is the case I will explain why it may have occurred and will try to provide better logs. If there are no oddities, disregard this.

@lxto
Copy link

lxto commented Dec 4, 2024

Same issue on my Pixel7a , GOS Built 2024120200.
Additional advice: I am using 2 different USB-C drives alternating, which worked well in earlier versions. Now only the latest USB-C drive used for backup allows further backups (not greyed out). After plugging in the altenate drive , the backup target is greyed. However when inserting the latest used backup-Drive it is possible to change the backup-target to e.g. "device" or "nextcloud" or "dav-device". I see this behaviour no matter if the backup failed or succeded.

@grote
Copy link
Collaborator

grote commented Dec 4, 2024

After plugging in the altenate drive , the backup target is greyed.

Sounds like there's a bug and it may indeed be the same one as the reformated drive. @t-m-w can you reproduce?

@t-m-w
Copy link
Collaborator

t-m-w commented Dec 4, 2024

Sounds like there's a bug and it may indeed be the same one as the reformated drive. @t-m-w can you reproduce?

Yes. I accidentally tried these steps with 15.5-0 at first, and everything was fine. As soon as I updated to 15.5-1, "Backup location" became grayed out for the first time in testing.

@jkos95
Copy link

jkos95 commented Dec 8, 2024

I am also experiencing this issue. Only the last working flash drive works. I have formatted and tried another but backup location is greyed out.

I have a pixel 6 on Android 15 2024120400.

@jkos95
Copy link

jkos95 commented Dec 13, 2024

I tested after you merge and it is working successfully. At first, the backup location was still greyed out, so I plugged in my original flash drive that was working, and when the backup location lit up, I switched to internal storage. After that I unmounted and plugged in my new one (mSATA to USB enclosure) and I was able to select it and backup no problem.

Edit: I spoke too soon. The backup failed since it did not like using the mSATA drive after a few minutes. I tried a flash drive after formatting my original one and now cannot get anything to un-grey the backup location :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug needs info Requires more information from reporter
Projects
None yet
Development

No branches or pull requests

5 participants