The ubiboot image is very large; about 12M in compressed form, true, that is because it includes the root filesystem of the repair mode in the kernel image.
However I have not ever seen that it would be too big to be flashed to the kernel MTD partition.
Would it be possible that your kernel partition is smaller than on other devices? I believe that even on MTD there is some flash filesystem that removes damaged flash blocks from use, maybe your kernel partition has been reduced in size?
Could be, I suspect the flash is damaged, it kind of makes sense now with the issues I've had previously with lost data and settings. Here's the output from sfdisk:
~ # /sbin/sfdisk -l
Disk /dev/mmcblk0: 1957120 cylinders, 4 heads, 16 sectors/track
Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/mmcblk0p1 16 1632511 1632496 52239872 c W95 FAT32 (LBA)
end: (c,h,s) expected (1023,3,16) found (1023,63,32)
/dev/mmcblk0p2 1760512 1891583 131072 4194304 83 Linux
/dev/mmcblk0p3 1891584 1957119 65536 2097152 83 Linux
/dev/mmcblk0p4 1632512 1760511 128000 4096000 83 Linux
start: (c,h,s) expected (1023,3,16) found (1023,63,32)
end: (c,h,s) expected (1023,3,16) found (1023,63,32)
Disk /dev/dm-0: 0 cylinders, 0 heads, 0 sectors/track
sfdisk: ERROR: sector 0 does not have an msdos signature
/dev/dm-0: unrecognized partition table type
No partitions found
The ubiboot image is very large; about 12M in compressed form, true, that is because it includes the root filesystem of the repair mode in the kernel image.
However I have not ever seen that it would be too big to be flashed to the kernel MTD partition.
Would it be possible that your kernel partition is smaller than on other devices? I believe that even on MTD there is some flash filesystem that removes damaged flash blocks from use, maybe your kernel partition has been reduced in size?
Could be, I suspect the flash is damaged, it kind of makes sense now with the issues I've had previously with lost data and settings. How do I see the size of the kernel MTD partition? df shows me:
Did you try what I suggested?
I believe the problem is not kernel, and not ubiboot, I believe you have problem in your Harmattan OS of the second device.
Just flash it with L2-fixed kernel, and try how it works without ubiboot.
Your ubiboot setup will not disappear, everything will be just as it was when you flash it again with ubiboot kernel.
By the way forgot, is there anything to do with the problem in Harmattan OS in second device?
By the way forgot, is there anything to do with the problem in Harmattan OS in second device?
Probably yes, the N9 device is pretty forgiving in that respect, it can usually be fixed without reflash just by replacing/fixing the thing that's broken in the first place... however to know what exactly to fix is more difficult
Usually people just are impatient with that, and do a reflash, as that will always fix it.
Probably yes, the N9 device is pretty forgiving in that respect, it can usually be fixed without reflash just by replacing/fixing the thing that's broken in the first place... however to know what exactly to fix is more difficult
Usually people just are impatient with that, and do a reflash, as that will always fix it.
OK thanks reflash back to closed mode -- no-preserve?
Ups back-up in Ubiboot how: Still reserved empty screen for Farfary's Backupmenu?
Well no, I meant just the regular Harmattan backups, and be sure to transfer the backup archive to your PC. And also back up all your stuff on MyDocs if you'd want to wipe the device.
Well no, I meant just the regular Harmattan backups, and be sure to transfer the backup archive to your PC. And also back up all your stuff on MyDocs if you'd want to wipe the device.
Regular Harmattan backups? To me it's the one in settings and farfary's Backupmenu and last one can't be used with Ubiboot?
Regular Harmattan backups? To me it's the one in settings and farfary's Backupmenu and last one can't be used with Ubiboot?
Well, there are basically 2 kinds of backups you can take off Harmattan.
The first type is the normal backup via the "settings -> backup" menu. This creates backup of your settings, messages, notes, whatever application data you have (or most of it) and the result is a new subdirectoty under MyDocs/.backups/ which contains 7 zipfiles and a metadata file.
This backup does not contain your applications, so to reinstall those you need to either reload from store or save the DEB's when you install applications.
The second type of backup is the type taken with BackupMenu or ubiboot maintanance console, which is a snapshot of the filesystem state at the moment it was taken.
This type saves the state exactly as it is, which is a problem if your state is not correct (like on your N9), as if you restore this kind of backup to your device after a reflash, you will get the device back in the (broken/faulty) state it was before
So, if you have a device in a broken/faulty state, you do not want to use the second type of backup.
