[Announce] BackupMenu - OS backup & restore | New version - Jul 9th(v1.1) - Page 57 - maemo.org

Active Topics

The N900 is now 15 years old! (8)
to Nokia N900 by whayong - 13 hrs, 9 mins ago
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 9 hrs ago
more...

Page 57 of 139

Thread Tools

Rob1n	2011-01-28 , 16:59
Posts: 3,617 \| Thanked: 2,412 times \| Joined on Nov 2009 @ Cambridge, UK	#561

Originally Posted by pali

Can you check this?
http://talk.maemo.org/showpost.php?p...&postcount=540

The bootmenu part works fine. I can't create a backup though as it fails to mount the eMMC (this works fine with the standard 0.61-1 though).

Quote & Reply |

	debernardis	2011-01-28 , 17:27
	Posts: 2,142 \| Thanked: 2,054 times \| Joined on Dec 2006 @ Sicily	#562

I can confirm what found by Rob1n, that also my system has /bin/tar symlinked to /usr/bin/gnu/tar, which is a symlink to /opt/maemo/usr/bin/gnu/tar.

All this comes from the tar-gnu package, not from something manually changed.

Now I know why I found my rootfs full of garbage today.

__________________
Ernesto de Bernardis

Quote & Reply |

pali	2011-01-28 , 17:38
Posts: 2,154 \| Thanked: 8,464 times \| Joined on May 2010	#563

I can confirm problem with tar too. I sended mail to RobbieThe1st with this problem.

Quote & Reply |

Tigerite	2011-01-28 , 21:00
Posts: 284 \| Thanked: 320 times \| Joined on May 2010 @ Peterborough, UK	#564

Originally Posted by Tigerite

Yes, I believe that flasher doesn't like the ubinized file when it's compressed with zlib. However nandwrite isn't as fussy and just happily, well, writes the data to the mtd5 block - the reason that flash_eraseall is needed is so that the ubi controller doesn't get in a tizzy and fail to mount the device once attached.

I'll test later (to simulated NAND) if it's possible to use nandwrite with the file created via mkfs.ubifs, i.e. prior to ubinizing, if ubiupdatevol is called first. It probably won't work, but worth a try anyway.

Well, you know what? It only blinkin' well went and worked! So, that's another option now - which again, creates no dmesg entries and results in a seemingly working partition (certainly one that's mountable and has all the files, at any rate). This would need ubirmvol, ubimkvol and ubiupdatevol - but crucially only 256MiB of space (less, actually) rather than double that for the pre-ubinized and then ubinized image. It should also save on NAND flash as there's no need for flash_eraseall or even nandwrite (though I imagine ubiupdatevol is calling something similar to nandwrite behind the scenes). The script to restore the pre-ubinized image would be:

Code:

ubirmvol /dev/ubi0 -N rootfs
ubimkvol /dev/ubi0 -N rootfs -S 1986
ubiupdatevol /dev/ubi0_0 /home/user/MyDocs/systemBackups/rootfs.ubi.img

..but BackupMenu would, in this instance, need to add the date and time to the image. However there'd be no need for the ubinize.cfg file, nor ubidetach/attach as the ubi commands would require rootfs to be attached to ubi control anyway. Also none of ubirm/mk/updatevol require any additional libraries!

Oh and I've got the gnu tools installed, so very glad I didn't try the latest version yet..

Last edited by Tigerite; 2011-01-28 at 21:02.

Quote & Reply |

RobbieThe1st	2011-01-29 , 00:14
Posts: 842 \| Thanked: 1,197 times \| Joined on May 2010	#565

Erm... Before we get carried away, I want to know if the solution you are proposing makes files that can be flashed by Nokia's PC-based flasher. If it can't, I see no reason to bother - That's the main reason to go with this(Being able to flash back a good rootfs when things fail).

As for the tar bit, I didn't understand whatthe heck pali ment until last night - I kept thinking he was talking about the ode used to create/restore images...
I made that change last night, to /usr/share/backupmenu/tar, and you'll get it when I compile it.

The odd thing I'm still not sure about is -when- 'tar' actually becomes a symlink to /opt/ - I have gnu-tools installed, and it didn't do it for me.

Oh and one more thing: I've seen several people talk about getting bootmenu's menu working... But -I- can't. I've done the exact same thing as you guys have, but bootmenu's menu fails to appear. I troubleshooted it back to text2screen in /bootmenu.sh not running; I just get "Can't determine screen resolution." when I redirect stderr to a logfile. But -why-?

__________________
My projects: BackupMenu - OS Backup & restore | Video: Flashing your n900(LiveCD)
My devices: N770 + 8GB SD card soldered internally, N900 with 8GB SD card + Custom OC(125-950 typically).
OC freqs: 0:22,90 125:22,90 250:28,180 500:30,360 550:32,400 600:34,430 700:39,430 750:41,430 805:45,430 850:47,500 900:50,500 950:54,500 1000:58,500 1100:67,520 1150:71,520

Quote & Reply |

Tigerite	2011-01-29 , 07:48
Posts: 284 \| Thanked: 320 times \| Joined on May 2010 @ Peterborough, UK	#566

Well, only the lzo-compressed, ubinized version would be flashable. However, there are two benefits to using ubiupdatevol with the pre-ubinized version (or flash_eraseall/nandwrite if you prefer, as this would work with flashable images also), rather than the tarred file: namely, the backup would take up less space in MyDocs, which is good if you want to have several; and it gives back space on the rootfs partition (in my tests, the space before was 56MiB and afterwards 83MiB - a difference of slightly more than 10% of the total amount available).

Quote & Reply |

	ndi	2011-01-29 , 11:31
	Posts: 2,050 \| Thanked: 1,425 times \| Joined on Dec 2009 @ Bucharest	#567

Is there no way to "fix" the tar approach so it would compress well?

Since the PC version is better compressed I assume that it's the ubifs driver that does it. And I assume nobody rewrote compression algos, it's likely a setting so that performance and size can be traded.

Can't this be fixed? Either by setting compression to max if setting or using a compiled driver if it's a const?

__________________
N900 dead and Nokia no longer replaces them. Thanks for all the fish.

Keep the forums clean: use "Thanks" button instead of the thank you post.

Quote & Reply |

	debernardis	2011-01-29 , 12:10
	Posts: 2,142 \| Thanked: 2,054 times \| Joined on Dec 2006 @ Sicily	#568

Originally Posted by Tigerite

Well, only the lzo-compressed, ubinized version would be flashable. However, there are two benefits to using ubiupdatevol with the pre-ubinized version (or flash_eraseall/nandwrite if you prefer, as this would work with flashable images also), rather than the tarred file: namely, the backup would take up less space in MyDocs, which is good if you want to have several; and it gives back space on the rootfs partition (in my tests, the space before was 56MiB and afterwards 83MiB - a difference of slightly more than 10% of the total amount available).

Unfortunately, not even the lzo-compressed image is working, at least in my hands. I've used the same procedure as above, with lzo instead of zlib; but after flashing, my n900 isn't bootable.

Robbiethe1st, how did you craft the flashable_rootfs_v0.56-1-20101109.img that is on your site? Did you use mkfs.ubifs or another method?

EDIT: again, flashing the flashable_rootfs_v0.56-1-20101109.img isn't enough to start backupmenu and restore from sd. I have to reflash stock firmware, then flashable_rootfs_v0.56-1-20101109.img, then restore with backupmenu.

EDIT2: might be I need to everything on-device? Might be mtd-utils from ubuntu 10.10 gives different results from the maemo5 one?

__________________
Ernesto de Bernardis

Last edited by debernardis; 2011-01-29 at 12:20.

Quote & Reply |

	Tiboric	2011-01-29 , 16:05
	Posts: 433 \| Thanked: 312 times \| Joined on Nov 2009 @ U.K	#569

I'm still not getting this working since 0.6-. the boot menu pops up and then i just have a choice of internal boot or reboot and two blank entry's in-between.
any ideas anyone?
P.s I love this app it has to be one of my favourites saved me more than once. lol