maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Alternatives (https://talk.maemo.org/forumdisplay.php?f=36)
-   -   Introducing ubiboot N9 (multiboot OS loader) (https://talk.maemo.org/showthread.php?t=89345)

fejd 2013-12-27 10:12

Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:

Originally Posted by juiceme (Post 1400939)
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

Should I repartition it? I'd have to say I've never done that but there's a thread on the topic here that looks helpful:
http://talk.maemo.org/showthread.php?t=91914

fejd 2013-12-27 16:22

Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:

Originally Posted by juiceme (Post 1400939)
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:

~ # df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 3.9G 1.8G 1.9G 49% /
devtmpfs 10.0M 252.0K 9.8M 2% /dev
tmpfs 4.0M 88.0K 3.9M 2% /tmp
tmpfs 512.0K 160.0K 352.0K 31% /var/run
none 10.0M 252.0K 9.8M 2% /dev
tmpfs 64.0M 436.0K 63.6M 1% /dev/shm
/dev/mmcblk0p3 2.0G 1.1G 790.6M 59% /home
/dev/mmcblk0p1 49.8G 14.5G 35.3G 29% /home/user/MyDocs
aegisfs 3.9G 1.8G 1.9G 49% /var/run/applauncherd
aegisfs 3.9G 1.8G 1.9G 49% /home/user/.odnp-fpcd/private
aegisfs 3.9G 1.8G 1.9G 49% /home/user/.odnp/private
aegisfs 3.9G 1.8G 1.9G 49% /home/user/.positioningd/private
aegisfs 3.9G 1.8G 1.9G 49% /home/user/private
aegisfs 3.9G 1.8G 1.9G 49% /var/cache/timed/aegis
aegisfs 3.9G 1.8G 1.9G 49% /home/user/.slpgwd/layer
aegisfs 3.9G 1.8G 1.9G 49% /home/user/.mms/private
aegisfs 3.9G 1.8G 1.9G 49% /home/user/.facebook/private
aegisfs 3.9G 1.8G 1.9G 49% /home/user/.signon/private
aegisfs 3.9G 1.8G 1.9G 49% /etc/ssl/certs
/dev/mapper/signonfs 6.8M 41.0K 6.4M 1% /home/user/.signon/signonfs-mnt

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

Should I repartition it? I'd have to say I've never done that but there's a thread on the topic here that looks helpful:
http://talk.maemo.org/showthread.php?t=91914

Garp 2013-12-28 07:44

Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:

Originally Posted by juiceme (Post 1393855)
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?

juiceme 2013-12-28 10:24

Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:

Originally Posted by Garp (Post 1401363)
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 :D

Usually people just are impatient with that, and do a reflash, as that will always fix it.

Garp 2013-12-28 16:46

Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:

Originally Posted by juiceme (Post 1401403)
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 :D

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?:(

juiceme 2013-12-28 18:17

Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:

Originally Posted by Garp (Post 1401554)
OK thanks reflash back to closed mode -- no-preserve?:(

Just take backups before you do that and you'll be okay.

Garp 2013-12-28 18:32

Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:

Originally Posted by juiceme (Post 1401583)
Just take backups before you do that and you'll be okay.

Ups back-up in Ubiboot how: Still reserved empty screen for Farfary's Backupmenu?

juiceme 2013-12-28 22:17

Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:

Originally Posted by Garp (Post 1401589)
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.

Garp 2013-12-29 05:57

Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:

Originally Posted by juiceme (Post 1401655)
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?

juiceme 2013-12-29 11:12

Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:

Originally Posted by Garp (Post 1401722)
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 :D:D

So, if you have a device in a broken/faulty state, you do not want to use the second type of backup.


All times are GMT. The time now is 16:55.

vBulletin® Version 3.8.8