| --- Day changed Thu Nov 21 2013 | ||
| -!- b2h [~user@180.245.180.142] has quit [Quit: Leaving] | 02:00 | |
| Wnt | Super! Got Sailfish SDK image running on my N9 | 03:34 |
|---|---|---|
| Wnt | But I somehow managed to break my harmattan root partition | 03:35 |
| Wnt | and running "fsck.ext4 -y /dev/mmcblk0p2" in Ubiboot says "fsck.ext4: Bad magic number in super-block while trying to open /dev/mmcblk0p2" | 03:36 |
| Wnt | I suspect that the moslo partition resizing messed it up. And that propably was caused by me having some old nitroid related partitions | 03:40 |
| Wnt | Is there something I can do to rescue my harmattan root filesystem or should I just reflash everything? This is my current partition table: http://upload.egarden.fi/N9_partition_table.txt | 03:43 |
| -!- user__ [~user@120.168.1.53] has joined #ubiboot | 08:17 | |
| -!- user__ [~user@120.168.1.53] has quit [Client Quit] | 08:19 | |
| @juiceme | Wnt, good morning | 08:47 |
| @juiceme | Do you have backups from your Harmattan partition? | 08:47 |
| @juiceme | If so, then just reflash and restore from backups. If not, how badly is it messed up, can you access it at all? | 08:48 |
| Wnt | juiceme: cannot access it fsck doesn't understand that there would be any filesystem on the partition. | 13:19 |
| Wnt | I suspect that the partition table was messed up by the moslo partition resizing thing | 13:20 |
| Wnt | Is there some default start and end blocks that the harmattan root filesystem partition would normally have on all devices? | 13:21 |
| Wnt | I could try to change the partitions to match those | 13:23 |
| Wnt | but I do have backup of my MyDocs filesystem and just made a backup with the N9's builtin backup software so I could reflash without losing any data | 13:24 |
| Wnt | I would only need to install all software again | 13:25 |
| @juiceme | wnt, just a minute I'll check from my device | 13:44 |
| @juiceme | the partitions on my device are currently like this; | 13:45 |
| @juiceme | ~ # /sbin/sfdisk -l | 13:45 |
| @juiceme | Disk /dev/mmcblk0: 1957120 cylinders, 4 heads, 16 sectors/track | 13:45 |
| @juiceme | Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0 | 13:45 |
| @juiceme | Device Boot Start End #cyls #blocks Id System | 13:45 |
| @juiceme | /dev/mmcblk0p1 16 1632511 1632496 52239872 c W95 FAT32 (LBA) | 13:45 |
| @juiceme | end: (c,h,s) expected (1023,3,16) found (1023,63,32) | 13:45 |
| @juiceme | /dev/mmcblk0p2 1760512 1891583 131072 4194304 83 Linux | 13:45 |
| @juiceme | /dev/mmcblk0p3 1891584 1957119 65536 2097152 83 Linux | 13:45 |
| @juiceme | /dev/mmcblk0p4 1632512 1760511 128000 4096000 83 Linux | 13:45 |
| @juiceme | start: (c,h,s) expected (1023,3,16) found (1023,63,32) | 13:45 |
| @juiceme | end: (c,h,s) expected (1023,3,16) found (1023,63,32) | 13:45 |
| @juiceme | You can try to manually fix your device to resemble that. (it's a 64G device btw, just a minute I'll fetcg the 16G version...) | 13:47 |
| Wnt | I have a 64G device also | 13:50 |
| Wnt | that's at least something I can try before reflashing | 13:50 |
| Wnt | I guess there migh also be some tools that could scan the whole block device for filesystem information | 13:51 |
| @juiceme | here's the info | 13:51 |
| @juiceme | RM696-21-3:~# sfdisk -l | 13:51 |
| @juiceme | Disk /dev/mmcblk0: 485120 cylinders, 4 heads, 16 sectors/track | 13:51 |
| @juiceme | Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0 | 13:51 |
| @juiceme | Device Boot Start End #cyls #blocks Id System | 13:51 |
| @juiceme | /dev/mmcblk0p1 16 288511 288496 9231872 c W95 FAT32 (LBA) | 13:51 |
| @juiceme | /dev/mmcblk0p2 288512 419583 131072 4194304 83 Linux | 13:51 |
| @juiceme | /dev/mmcblk0p3 419584 485119 65536 2097152 83 Linux | 13:51 |
| @juiceme | /dev/mmcblk0p4 0 - 0 0 0 Empty | 13:51 |
| @juiceme | ah | 13:51 |
| @juiceme | was too quick to paste it :) | 13:52 |
| @juiceme | I am only aware of tools for checking a particular filesystem on a device but there certainly is no reason why whole device could not be checked. | 13:53 |
| Wnt | Used testdisk on my laptop while ubiboot exported the whole block device via usb and testdisk was able to determine the correct partition table | 15:27 |
| Wnt | Now might be a good time to make a backup of the rootfs :) | 15:36 |
| -!- Basstard` [~sturgeon@c-5eeaaa55-74736162.cust.telenor.se] has joined #ubiboot | 21:15 | |
Generated by irclog2html.py 2.12.1 by Marius Gedminas - find it at mg.pov.lt!