2.0.4 Fiskarsinjoki bricked my Jolla 1?

Question

2

2.0.4 Fiskarsinjoki bricked my Jolla 1?

asked 2016-10-26 11:30:28 +0200

sturk
71 ●3 ●6 ●6

updated 2016-10-26 14:21:58 +0200

I immediately tried to update the day before yesterday and no I didn't do a backup I rarely do that with any update. But this time my phone just started the optimising process and then died. Now when i try to start it the jolla startup logo shows up and then nothing but darkness..

What happened? How do I fix it? Am I alone whit this problem? I'm no linux pro so I would need a guide for like a three year old. Linux for super dummies so to speak.

Sorry if someone already asked/answered this I did a quick search and didn't find anything.

edit retag flag offensive close delete

Comments

1

Which phone? and it didn't start the actual update process just the optimising bit? Sounds like a filesystem problem, maybe try and get into recovery mode

r0kk3rz ( 2016-10-26 12:03:03 +0200 )edit

I treid an update yesterday, did backup, then started the optimising process, but that one stopped after a while without moving to the next step of the update procedure. Instead the optimise screen occurred again, so I think the optimisation didn't finish properly. I think that there is not enough free space on the internal storage, mine has just 1.3GB free, so maybe this is the reason, but the optimise doesn't tell you this :-( the recommendation in the release notes recommend to assure that there are 3-4GB of free internal storage.

barral ( 2016-10-26 12:20:15 +0200 )edit

@barral

maybe you do free some space:5-6 GB and then do run btrfs balancer manually

then start update

the problem with balancer is if you do not have enough space it will return successfully, but not do any significant optimization

pawel ( 2016-10-26 12:51:45 +0200 )edit

Which phone? and it didn't start the actual update process just the optimising bit? Sounds like a filesystem problem, maybe try and get into recovery mode
r0kk3rz ( 2016-10-26 12:03:03 +0200 )edit
I treid an update yesterday, did backup, then started the optimising process, but that one stopped after a while without moving to the next step of the update procedure. Instead the optimise screen occurred again, so I think the optimisation didn't finish properly. I think that there is not enough free space on the internal storage, mine has just 1.3GB free, so maybe this is the reason, but the optimise doesn't tell you this :-( the recommendation in the release notes recommend to assure that there are 3-4GB of free internal storage.
barral ( 2016-10-26 12:20:15 +0200 )edit
@barral
maybe you do free some space:5-6 GB and then do run btrfs balancer manually
then start update
the problem with balancer is if you do not have enough space it will return successfully, but not do any significant optimization
pawel ( 2016-10-26 12:51:45 +0200 )edit

Answer 1

1

answered 2016-10-27 00:29:54 +0200

Johans
11 ●1

My jolla was also bricked by the recent update !

Optimization needed long time but showed no error
backup failed with a error message (should have warned me)
deleted big files in /home/nemo/
started update: did not try to optimize again.
went in to update screen "Sainfish OS" with a progress bar of around 5% not moving since 5 hours.

Any advice from the Jolla Gurus ? You should seriously think about removing the update as long as there is no save way to overcome this possibly btrfs related problems.

edit flag offensive delete publish link

Comments

my personal opinion: if you do not watch btrfs on jolla 1, you will.sooner.or later.end up like that. now that jolla 1 is history from selling point of view, i would make this issue more.visible. there is a reason for schturmans btrfs patch. imho

pawel ( 2016-10-27 00:49:14 +0200 )edit

If this is the case, isn't is fair to await a warning or better a howto-document from the sailfish release team ? Ordinary users will not check btrfs sanity (on the console and without any hint to do so) before doing an recommended update.

Johans ( 2016-10-27 02:13:12 +0200 )edit

1

Please have a look at the following help articles (which do not require using the command line):

https://jolla.zendesk.com/hc/en-us/articles/203840836-How-to-keep-your-Jolla-in-good-shape https://jolla.zendesk.com/hc/en-us/articles/206354737-Free-up-space-on-your-device https://jolla.zendesk.com/hc/en-us/articles/203837576-Sailfish-Utilities

jovirkku ( 2016-10-27 10:15:33 +0200 )edit

Answer 2

0

answered 2016-10-26 14:27:54 +0200

sturk
71 ●3 ●6 ●6

I don't think I had to little memory left, but anyway I will try recovery mode later. Nice guide! Hope that I can safely save everything thats on it.

edit flag offensive delete publish link

Comments

1

I had basically the same (Jolla 1). I had plenty of free space (data) but I couldn't do any operation on the filesystem (includin rm on files). This was my btrfs info:

/mnt # btrfs fi show
ERROR: unable get label Inappropriate ioctl for device
Label: 'sailfish'  uuid: 86180ca0-d351-4551-b262-22b49e1adf47
        Total devices 1 FS bytes used 8.45GiB
        devid    1 size 13.75GiB used 13.74GiB path /dev/mmcblk0p28
Btrfs v3.16

My phone still booted, but it was so bad that I even couldn't enter in devel-su mode. So I've booted into recovery console, mounted the partition with nocow option, but stil wasn't able to perform any maintenance. Then I tried adding extra space to a volube from the SD card (through loop device). This helped me to do some file cleansing and also btrfs balancing that actually released plenty of space.

Unfortunately something was not OK because after deleting the added volume, unmounting the FS-s and rebooting the device went completely black ... Still I was able to btrfs check --repair and mount @home volume to backup the data, but it didn't helped.

Finally I have resented to a factory reset which luckily worked as expected. I only had to re-install several updates (from 1.1.2.x to 2.0.4.14) which took me about 2h. Luckily I 'tested' the back-up option to Dropbox last month, so I was 'back in game' rather quickly.

All the above based on: https://together.jolla.com/question/30822/root-and-home-disks-full-and-causing-various-problems/

My conclusion - the filesystem was on brink even before I started the Optimizaiton process prior to upgrade. It seems (guessing only) the btrfs balancer shoot himself in a knee by consuming all the metadata space prior to realizing it. Unfortunately something must've gone wrong when I did 'manual' optimization with additional volume; most likely related to the way how added volume was detached from the main one ...

Upside - I have learned a lot about my device ;-). In addition to that I've got the impression that the phone is more responsive now than it was before.

Valentin ( 2016-10-26 16:30:54 +0200 )edit

Answer 3

0

answered 2016-10-28 01:09:14 +0200

Johans
11 ●1

Thanks for answering. but - The Jolla shows a black screen, a progress bar (constant) the sailfish logo and the words SAILFISH OS - when i press the power button, screen blanks and the LED blinks i a kind of bluish purple. When I press power again, i get the update screen as above. - connecting USB to a linux PC gives me

[  663.362021] usb 1-6.1: new high-speed USB device number 5 using ehci-pci
[  663.438448] usb 1-6.1: New USB device found, idVendor=2931, idProduct=0afe
[  663.438459] usb 1-6.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  663.438467] usb 1-6.1: Product: Jolla
[  663.438472] usb 1-6.1: Manufacturer: Jolla
[  663.438478] usb 1-6.1: SerialNumber: DU3CC0xxxx
[  663.480188] usb-storage 1-6.1:1.0: USB Mass Storage device detected
[  663.480508] scsi6 : usb-storage 1-6.1:1.0
[  663.480752] usbcore: registered new interface driver usb-storage
[  663.488366] usbcore: registered new interface driver uas
[  664.485253] scsi 6:0:0:0: Direct-Access     Linux    File-CD Gadget   0000 PQ: 0 ANSI: 2
[  664.485967] sd 6:0:0:0: Attached scsi generic sg4 type 0
[  664.490984] sd 6:0:0:0: [sdd] Attached SCSI removable disk
[  667.809827] usb 1-6.1: USB disconnect, device number 5

edit flag offensive delete publish link

2.0.4 Fiskarsinjoki bricked my Jolla 1?

Comments

3 Answers

Comments

Comments

Question tools

Stats

Related questions

2.0.4 Fiskarsinjoki bricked my Jolla 1?

Comments

3 Answers

Comments

Comments

Question tools

Public thread

Stats

Related questions