Device recovery, stuck on "create a snapshot"

Question

2

Device recovery, stuck on "create a snapshot"

asked 2014-12-20 19:13:47 +0200

joakknut

146 ●4 ●6 ●10

updated 2015-01-15 10:31:07 +0200

Hello,

After experiencing some trouble with phone (no messages, no jolla store access, cant access system setting etc) I decided to reset my phone to factory settings.

I managed to get in recovery mode and followed the instructions for 1.0.8.21 as described here; https://jolla.zendesk.com/hc/en-us/articles/202208763#2.

Now I've been patiently waiting for about 30 minutes, but I'm stuck at "Create a snapshot of '/mnt/factory-@' in '/mnt/@'"

Here is the whole terminal output so far:

-----------------------------
     Jolla Recovery v0.2.7      
-----------------------------
Welcome to the recovery tool!
The available options are:
1) Reset device to factory state
2) Reboot device
3) Bootloader unlock [Current state: locked]
4) Shell
5) Try btrfs recovery if your device is in bootloop
6) Exit
Type the number of the desired action and press [Enter]: 
1

ALL DATA WILL BE ERASED! Clears everything from the device and reverts the 
software back to factory state. This means LOSING EVERYTHING you have added to 
the device (e.g. updates, apps, accounts, contacts, photos and other media). 
Are you really SURE? [y/N] y[CLEANUP] Starting cleanup!
[CLEANUP] Umounting top volume...
[CLEANUP] Umounting /mnt
[CLEANUP] Deleting /mnt
[CLEANUP] Cleanup done.
Mounting /dev/mmcblk0p28 on /mnt
sh: unlock: unknown operand
[OK] No lockcode has been set. Proceeding...
sh: unlock: unknown operand
sh: shell: unknown operand
[OK] Factory snapshots found.
Resetting procedure started!
Backing up current root and home subvolumes. If the backup fails, the old data will be deleted to let the recovery process continue.
[Done]
Restoring factory subvolumes...
Create a snapshot of '/mnt/factory-@' in '/mnt/@'

Do anyone know how long this is supposed to take?

UPDATE: Soooo, it seems I've made things worse. After 2-3 hours and nothing happening in the terminal, I pulled the plug, took the battery out and in again, and turned on my phone. Now I'm stuck on the Jolla logo.

UPDATE 2: I contacted Jolla Care about 2 weeks ago. After a bit back and fourth, trying different things all with the same result, they advised me to send it in for repair. Let's hope they can fix it! I'm already sick of the S3 I've been using..

edit retag flag offensive close delete

Comments

1

Do you have any idea how you got into that mess? You didn't happen to check if you were possibly affected by the problem of btrfs filling up? (https://together.jolla.com/question/30822/root-and-home-disks-full-and-causing-various-problems/)

Jolly-Jo ( 2015-01-15 12:40:04 +0200 )edit

I have not checked it, no. But looking at the symptoms in the link you provided it seems highly likely. The phone started to act weird (UI freeze, no sms/mail, core apps crashing, accounts got logged out, could not reset trough UI etc.) after I deleted most of my apps from Jolla Store, Openrepos and Google Play (long hold, press "x").

From what I can remember I had plenty of free space before deleting my apps. And the files I managed to recover from the phone trough shell (photos, contacts etc) only took about 0.5-1 gigabyte.

joakknut ( 2015-01-15 13:05:00 +0200 )edit

Do you have any idea how you got into that mess? You didn't happen to check if you were possibly affected by the problem of btrfs filling up? (https://together.jolla.com/question/30822/root-and-home-disks-full-and-causing-various-problems/)
Jolly-Jo ( 2015-01-15 12:40:04 +0200 )edit
I have not checked it, no. But looking at the symptoms in the link you provided it seems highly likely. The phone started to act weird (UI freeze, no sms/mail, core apps crashing, accounts got logged out, could not reset trough UI etc.) after I deleted most of my apps from Jolla Store, Openrepos and Google Play (long hold, press "x").
From what I can remember I had plenty of free space before deleting my apps. And the files I managed to recover from the phone trough shell (photos, contacts etc) only took about 0.5-1 gigabyte.
joakknut ( 2015-01-15 13:05:00 +0200 )edit

Answer 1

0

answered 2014-12-22 14:46:04 +0200

Riddicule
13 ●2 ●2 ●7

same here stuck withe the same problem

edit flag offensive delete publish link

Answer 2

0

answered 2015-02-24 23:13:51 +0200

Vistaus

96 ●4 ●5 ●10

Same problem here :(

edit flag offensive delete publish link

Comments

Check the link jolly-jo provided above. And try btrfs balancing.

J4ZZ ( 2015-02-25 22:33:06 +0200 )edit

Btrfs reports there's no space when issuing the command to check that, but there are no rec* files or folders... The balance command given there errors out.

Vistaus ( 2015-02-25 22:34:53 +0200 )edit

Have you read and tried the Measures to free up raw space

Deleting big files helps freeing up space both in under visible filesystem and in the area of allocated space. However it does not shrink the allocated space automatically. When you run out of space it is recommended to delete several gigabytes of data to make sure that the filesystem has enough space to "breathe".

The method to free up space reserved by unused or sparsely used blockgroups is called 'balancing'. It resembles filesystem 'defrag' operation, but instead of just speeding up the filesystem by regrouping splintered files, balance also frees up space. Classic filesystems do not suffer from space usage problems to the extent of btrfs.

Balance operation can consume more space than what you have available. If you do not free up enough space in existing blockgroups manually, you may run out of space during the balancing operation depicted below.

plus

If you are unable to delete files, your problem may be that you are in a chicken-egg situation of running out of metadata space. You can free up metadata space in already used block group by overwriting the data in files you do not need.

echo > /path/to/yourfile

After this you can try normal deleting again.

J4ZZ ( 2015-02-26 01:40:52 +0200 )edit

I'm sorry, I'm not sure what you mean by that last part. The balancing errors out so I cannot use the balance command to free up space and that last part is not understandable for me. I've already come quite far using the guides, but I'm not a techie so I need a little bit more of an explanation if you don't mind.

Vistaus ( 2015-02-26 03:05:16 +0200 )edit

No problem. Your balancing doesn't work, because there is no more free space for the program to do its magic. Therefore you need to delete some files from your home (/home/nemo/) directory until balancing works again. The above 'echo' command is basically a workaround, when deleting files normally (via FileBrowser) isn't possible anymore, if that is your case. If not go on and backup/delete more files from your user directory /home/nemo/ eg, videos, downloads, pictures etc. and then try the balancing command again.

If you are in the situation that you can't delete anything on your phone anymore. Try overwriting huge files using the echo commmand above. (for example, if I would have a huge *.mp4 in my Videos folder) (I would) open terminal and simply enter:

echo > /home/nemo/Videos/BigBugBunny.mp4

And then try again to delete files...

J4ZZ ( 2015-02-26 16:49:04 +0200 )edit

Answer 3

0

answered 2015-02-27 04:02:17 +0200

Vistaus

96 ●4 ●5 ●10

I tried to mount the nemo folder using mount -o remount,rw subvolid=0 /dev/mmcblk0p28 /mnt/ and that seemed to work but no matter if I use rm or echo, it constantly complains that the file system is read-only :/

And balancing still errors out:

/ # btrfs balance start -dusage=0 / ERROR: error during balancing '/' - Inappropriate ioctl for device There may be more info in syslog - try dmesg | tail / #

edit flag offensive delete publish link

Device recovery, stuck on "create a snapshot"

Comments

3 Answers

Comments

Question tools

Stats

Related questions

Device recovery, stuck on "create a snapshot"

Comments

3 Answers

Comments

Question tools

Public thread

Stats

Related questions