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 ?
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.
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?).
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)
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.
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)
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:
