Notices

Just go ahead and, as root, "rm /etc/bootmenu.d/BackupMenu.item".
It'll have the same overall effect.

And, version 0.54-1 has been uploaded.
You can either get it from my site on the first panel, or through extras-devel.

This version:
1. fixes "error mounting rootfs" error the -second- time you try to backup, or do a restore right after a backup.
2. "x - exit" has been changed to "q - quit" on the main menu at the behest of ilius on the IRC.
3. A glitch preventing you from saving your Optfs to the SD card has been fixed(well, actually, all that was fixed was you seeing the button you needed to press - actually backing up would have worked fine).

I have done it but cannot see anything is deleted. I still have "backupmenu" but with no capitals.

Installed the last one 0.54-1 and booted with keyboard open boot menu show 2 item "Flash" and "power off when charger is not connected" and then screen go blank what ever I choose. UP and down work but excuse me which button is CENTER ?

As a newbie I think I wait until moore info is available.

That means it's not installed correctly. Go reinstall the current version.

apt-get remove backupmenu --purge
apt-get install backupmenu

Edit: After trying that, if it doesn't fix it, let me know.

Hello Robbie,

for the n-th time, the simple act of macking a backup with your latest version has messed up irreparably my optfs. And, while trying to restore, I had uncountable "stale nfs handle" errors. The restored optfs was also messed up, of course.

Luckily I had a backup made with your version 0.32 on Nov 1st, so I haven't lost too much.

Is the code to umount the optfs/rootfs after backup still there, as per your answer to the first time I reported this problem?

This seems to me quite a showstopper

I don't know what you are running into. I have it unmounting all filesystems before shutdown, after backup or restore, and with this latest version it -will- give you an error if it can't unmount.

The best thing I can think of is that you have a corrupt, or semi-corrupt optfs filesystem - You seem to be the only person with this problem.

What I would like you to try is:
1. install the latest version.
2. run FSCK mode. What error(if any) does it display.

Also, if you could give me a complete run down of any and all errors you encounter, and the screens you encounter them on, I'll do my best to fix anything I can from my end.

Edit:
I'm off for now, but can anyone try out SSH mode and USB terminal mode? I can ping my n900, but ssh doesn't seem to want to work about half the time, and I can't login with my root pass.
Same with terminal. I don't know if this is a glitch, or just me not knowing how to deal with these things.

Robbie, though my opt filesystem after the last backup was left in an inconsistent state, after reinstalling the Nov 1st images through your version 0.32, I could subsequently restore the today's backup tar files, both for rootfs and optfs, with the older version (0.50-something) I had in the Nov 1st backup.

Sorry if this seems confusing: basically the issue is that even if backupmenu damaged the opt filesystem, today's backups were still good, but they couldn't be restored in the borked optfs until it was reset through the img reinstall.

Weird, isn't it? This means that something very nasty happens *after* tarring.

Now, how do you think I can determine what the h[a|e]ck appens when making a backup, that destroys my fs? After I have a new backup set made both with 0.32 and with the latest version, I could play kamikaze again to see where is the bug!

EDIT:
I could make a backup with ver 0.54 without any apparent damage to the filesystem so far. This time I waited for at least 30 seconds when backup was done before I pushed q to quit. Might be that?

OK, I've taken the plunge and upgraded from the old 0.32, but before I did I checked to make sure usb networking and SSH working.

With this v0.54-1 I'm getting the same as you, ping works but when I try to ssh in I get connection refused. Message from backupmenu states that ssh was started and even gives a pid.

I had this issue too (stale nfs handles in optfs) back in late september and there was no way in restoring anything useful. I defintely was not backup-menu's fault as I didn't run it the day the fs broke. I could do a backup afterwards using plain tar command as root and tar was complaining about these broken files as they could not be read but the backup finished. Therefore you should have a close look at your (tar-)backup as it might be it's not complete!
In the end what you did was: overwriting the whole partition using the image-backup (all fs-errors are eliminated) and then overwriting those files that tar could read and save when using the tar-backup. All files not read are therefore as old as your image-backup.
As my optfs was completely messed up I lost a lot of data which was not backed up by hildon-backup. Handling with the images I backed up was also no option as the latest one was way too old.

Hm, I'll take a look at ssh again - maby it's dying, missing files or something.

Also, for those with problems - I'd -really- like to see What FSCK mode says on your damaged partitions.
I have a feeling, though, that it wont be able to actually fix it.

When my own optfs goes haywire, I -have- had luck:
1. starting up backupmenu
2. connecting a linux pc/livecd-based system to my n900
3. run "w" mode. The Optfs will be visible over usb.
4. run "sudo fsck -y /dev/partition" on that partition(partitions/disks will be listed with "sudo fdisk -l").