Reply
Thread Tools
Posts: 344 | Thanked: 1,345 times | Joined on Aug 2012 @ Paris, FR
#1
Hi guys. I'm have a N9 that appeared to have commited suicide: all data from /home just mysteriously dissapeared. I wonder what happened. Did anyone of you expected this issue, and (better) did anyone of you recovered from it ?
__________________
Developer of Friends Facebook client, patchmanager, Phonebot
Blogger at Jollafr and random thoughts on my personnal blog
Support my work
 
Posts: 344 | Thanked: 1,345 times | Joined on Aug 2012 @ Paris, FR
#2
Alright, at least for MyDocs, I brought it back by plugging it as a Mass storage and unplugging it + rebooting. But for /home, it is still missing. Investigating.
__________________
Developer of Friends Facebook client, patchmanager, Phonebot
Blogger at Jollafr and random thoughts on my personnal blog
Support my work
 
Posts: 344 | Thanked: 1,345 times | Joined on Aug 2012 @ Paris, FR
#3
Right: looks like /home is corrupted. Now do anyone know how to run a fsck on /home ...
__________________
Developer of Friends Facebook client, patchmanager, Phonebot
Blogger at Jollafr and random thoughts on my personnal blog
Support my work
 
Posts: 138 | Thanked: 144 times | Joined on Oct 2012 @ Devon, England
#4
The relevant fsck is /sbin/e2fsck, and the device mounted to /home is /dev/mmcblk0p3.

Hope that's some help, at least.
 
peterleinchen's Avatar
Posts: 4,117 | Thanked: 8,901 times | Joined on Aug 2010 @ Ruhrgebiet, Germany
#5
You cannot fsck a mounted fs. And you cannot umount /home.
So probably do (from heart, so please cross check):
dd if=/dev/mmcblk0p3 of=/home/user/MyDocs/p3.img
fsck /home/user/MyDocs/p3.img

If some error pop up, you may correct them on the img file. But to correct them on device you would need to bring it back to /dev/mmcblk0p3. I am unsure if
dd of=/dev/mmcblk0p3 if=/home/user/MyDocs/p3.img
would work..
Maybe better try that with a Linux system and all partitions mounted to that PC (e.g. via ubiboot. Or are there other rescue systems?).
__________________
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!

Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257

editsignature, http://talk.maemo.org/profile.php?do=editsignature
 

The Following User Says Thank You to peterleinchen For This Useful Post:
Community Council | Posts: 4,920 | Thanked: 12,867 times | Joined on May 2012 @ Southerrn Finland
#6
Did you check that your home is actually mounted?
Happened to me once that, well it was my own fault really as I messed up some boot related things, and /dev/mmcblk0p3 (/home) was not mounted.
What happens then, when the device boots it will create a new /home for you on your root device, and copy the skeleton files to it from /etc.
It will look like your device had been wiped clean, but the old stuff stil exists there on /dev/mmcblk0p3

As for rescuing the device, there are at least 3 differnt rescue kernels but ubiboot is the easiest to use and most versatile.
Just load up ubiboot kernel without flashing it, and telnet to the device & run fsck on filesystems.
(or fsck them on USB mount if you have linux)
 

The Following 2 Users Say Thank You to juiceme For This Useful Post:
Posts: 344 | Thanked: 1,345 times | Joined on Aug 2012 @ Paris, FR
#7
Originally Posted by juiceme View Post
Did you check that your home is actually mounted?
Happened to me once that, well it was my own fault really as I messed up some boot related things, and /dev/mmcblk0p3 (/home) was not mounted.
What happens then, when the device boots it will create a new /home for you on your root device, and copy the skeleton files to it from /etc.
It will look like your device had been wiped clean, but the old stuff stil exists there on /dev/mmcblk0p3
Don't think so: in /home, lost+found if full of stuff, running a e2fsck on /dev/mmcblk0p3 gives me tons of errors.

Originally Posted by juiceme View Post
As for rescuing the device, there are at least 3 differnt rescue kernels but ubiboot is the easiest to use and most versatile.
Just load up ubiboot kernel without flashing it, and telnet to the device & run fsck on filesystems.
(or fsck them on USB mount if you have linux)
Great, that's exactly what I was searching for !
__________________
Developer of Friends Facebook client, patchmanager, Phonebot
Blogger at Jollafr and random thoughts on my personnal blog
Support my work
 
Posts: 58 | Thanked: 10 times | Joined on Dec 2011
#8
Originally Posted by juiceme View Post
Just load up ubiboot kernel without flashing it, and telnet to the device & run fsck on filesystems.
(or fsck them on USB mount if you have linux)
Sorry for this silly question but can you tell me the procedure to load the kernel without flashing it.
 

The Following User Says Thank You to bvaibhav For This Useful Post:
Community Council | Posts: 4,920 | Thanked: 12,867 times | Joined on May 2012 @ Southerrn Finland
#9
Originally Posted by bvaibhav View Post
Sorry for this silly question but can you tell me the procedure to load the kernel without flashing it.
When you load up a kernel without flashing, start like you would start flashing, (meaning, device switched off). You do not need to specify the emmc or --flash-only parameters on the command line, just enter the kernel name:

"sudo flasher -k <name_of_kernel> -n <name_of_initramfs_if_desided> -l -b"
 
Reply


 
Forum Jump


All times are GMT. The time now is 10:51.