![]() |
Re: Help needed to do a backup
Quote:
|
Re: Help needed to do a backup
Quote:
just send a private message If someone know where to get It Edit..I see It was removed,Jolla care then |
Re: Help needed to do a backup
It's 2017 now and I'm still using a Jolla 1 phone.
My BTRFS partition got corruption. (One log entry causes the kernel to segfault while trying to replay). I made the mistake of trying the recovery mode without much checking. I ended up with a partition with cleared checksum, that still doesn't mount in-kernel (Still the same replay-log segfault). Luckily, I can recover nearly every file I need from my busted partition (thank you BTRFS's Copy-on-Write !!!) using btrfs tools which will use whichever copy happens to not be busted. Now instead of trying to rebuild a functioning BTRFS partition myself.... (which would be possible at this point but tedious - recovery mode lost the checksums, btrfs tools doesn't save the posix access rights, and I still need to fix the segfault causing log entry. So quite some work until phone is up again) ...I wanted to know if anyone happens to have a useable "factory-@" Image file ? (Jolla Care are slow to answer my Zendesk ticket, and as mentioned above, it's not possible to publish it on web due to copyrighted bit from Qualcomm) |
Re: Help needed to do a backup
Quote:
My laptop's btrfs restore works even better and I got everything I wanted out of the busted partition. I managed to rebuild a new BTRFS partition with both the recovery bits ( 'factory-@', etc. ) and the regular subvolumes ( '@', '@home' ). I replaced mmcblk0p28 and now I've got everything back working, not even needing to do a factory reset. ("Copy-on-Write", bitches ! It works) |
Re: Help needed to do a backup
Argh, I had send in my Jolla for service to Finland.See here.
They actually had to change mainboard because it was completely dead. So I had it back now for three weeks or so,everything set up again, as far as possible since I didn't have a full backup and only an older one from backup function. Last week I found it on my table stuck on boot screen. This time I could get into recovery mode, but... I thought, the option in that menu are actually to be used! Naah, almost everytime I tried something, it disconnected telnet. An everytime I tried again, I made it worse. factory-@ was broke pretty early maybe even form the beginning. Yesterday I finally got around to make my own image file from the remaining pieces, while adding missing pieces from /@ which I thought were part of the original image (mostly translations). It seems, it was not enough to be recovered :( Tar complained about errors while packing and unplacking as well. I am proud to at least make it to the next stage: It went from bootloop to "trying to revover file system" but ends at "please seek service". Could someone help me out with advice or even factory-@? factory-@home seems to be OK. I understand, these parts don't contain personal information as with the other 2 subvolumes. |
Re: Help needed to do a backup
*BUMP*
Sorry to doublepost. I could still use some help here. I already contacted jolla support, but they seem to be busy shipping sailfish X. Where could I get help from? For a start I would at least try to confirm contents of factory-@ just to be sure of it's completeness. |
Re: Help needed to do a backup
I managed to build a new image too. There were some files missing from originial, if I found all that is. I added them from my regular linux machine as there were all public files like /zoneinfo folder and xmls in /application.
But: When I write the new image to mmcblk0p28 everything seems fine, btrfs check gives no errors. After reboot, I get the "trying to recover" followed by "seek service" I mentioned above. When doing another btrfs check, file system is now broken again with lots of csum erros and more. What am I missing? btw: asking on #jollamobile or zendesk seems to not help. Please help somebody!! |
Re: Help needed to do a backup
Quote:
(Same applies for other CoW filesystems like ZFS and log-structured filesystems like UDF and F2FS). The best is to always simply try to get an early version (before the "copy" part of Copy-on-Write). For BTRFS, things that might help : - mounting with "recovery" (will scan back the older copies until it finds the latest usable) (for kernel 4.6 and newer, its now called "usebackuproot") - mounting with "nologreplay" (completely ignore the journal log) - using "btrfs restore -s -x -m -S -i " on an image transfered to a laptop. Quote:
Not that you mount the (perhaps corrupted) partition and untar your files inside ? By check you mean mount and "btrfs scrub start" ? Quote:
If you have some place where I can send you the file (FTP server ? Something else ?) I can send you my recovery partition. I just can't post it publicly, because it contain non-public code (mostly driver and blobs from Qualcomm which make it illegal to post online). |
Re: Help needed to do a backup
Quote:
Quote:
Quote:
By check I mean unmounted btrfs check (without --repair) Quote:
At the moment I try to create btrfs on device and the restore from dd image file. I do not have a publicly writable storage for file transfer. Will see, if I can get a ftp server running temporarily. Appreciate your help! |
Re: Help needed to do a backup
Quote:
Format it with (where <uuid> is the UUID of the old partition, or alternatively, let btrfs generate a new UUID and upgrade your /etc/fstab file) : Code:
mkfs.btrfs -d single -m single -n 4096 -L sailfish -O ^extref,^skinny-metadata -U <uuid> The 3.4.108.20170530.1 kernel onboard of the Jolla 1 is a tiny bit old. As such it doesn't support some feature that later versions of BTRFS have enabled by default. If you generate it on a laptop/desktop your BTRFS will be way too modern. If you generate it on device, the btrfs-tools are a tiny bit more modern too (3.16 instead of 3.4). Details :
More information about features in BTRFS : Code:
> mkfs.btrfs -O list-all Quote:
|
All times are GMT. The time now is 19:42. |
vBulletin® Version 3.8.8