![]() |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
~ # /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 |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
~ # 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 |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
|
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
Usually people just are impatient with that, and do a reflash, as that will always fix it. |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
|
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
|
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
|
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
|
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
|
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
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