It's possible format the internal memory from ubuntu gparted? - Page 2 - maemo.org

Active Topics

Porting apps to Leste (32)
to Maemo 7 / Leste by Arno_11 - 3 days, 12 hrs ago
[ANNOUNCE] CSSU-thumb thread - stable Thumb2 on N900 (2,264)
to Maemo 5 / Fremantle by panjgoori - 5 days, 6 hrs ago
Full linux distros on Sailfish OS (254)
to SailfishOS by qoh - 6 days, 4 hrs ago
more...

Page 2 of 2

< Prev

Thread Tools

	sub7	2011-01-20 , 15:47
	Posts: 69 \| Thanked: 10 times \| Joined on Sep 2010 @ Spain	#11

Seems something related with the superblock
http://ska0.wordpress.com/2007/04/05...oque-corrupto/

an screenshot of my internal memory phone.

any idea¿?

Last edited by sub7; 2011-01-20 at 15:49.

Quote & Reply |

J4ZZ	2011-01-20 , 21:46
Posts: 539 \| Thanked: 518 times \| Joined on May 2010 @ nanaurbusiness	#12

I repartitioned my internal memory, too using Ubuntu and gparted.

Maybe you should just backup /dev/sdb2 (its the /home partition) and /dev/sdb1 (MyDocs) just in case and then wipe the whole table.

Code:

dd if=/dev/sdbX of=/path/to/image/on/computer

I recreated everything from scratch, resized /home/user from 2 GB to 5 GB, made two extra partitions for nitroid and meego to play with and increased my swap partition by a few megs.

Finally restored /home

Code:

dd if=/path/to/image of=/dev/sdbX

And btw. there is no reason not to use the unallocated space, seen in your screenshot.

FYI: That's how I get into R&D mode Solution #6

Greetz,

..::J4ZZ::..

Quote & Reply |

retsaw	2011-01-20 , 21:56
Posts: 701 \| Thanked: 585 times \| Joined on Sep 2010 @ London, England	#13

Originally Posted by sub7

well i try this but gparted dont repair nothing but and if i do fsck to test, give one error.
Code:
sudo e2fsck -n /dev/sdb1
the error sorry it's on spanish, i got this on ubuntu
Code:
e2fsck 1.41.12 (17-May-2010)
e2fsck: Superbloque es inválido, intentando los bloques de respaldo...
e2fsck: Bad magic number in super-block mientras se intentaba abrir /dev/sdb1

El superbloque podría no ser leido o no describe un sistema de ficheros ext2 correcto.
Si el dispositivo es válido y en verdad contiene un sistema de ficheros ext2 (y no uno 
de intercambio, ufs o algo más), entonces el superbloque está corrompido
y podría intentarse ejecutar el e2fsck con un superbloque alternativo:
   e2fsck -b 8193 <dispositivo>
EDIT: it seems i only got this error when i do e2fsck on fat32 partitions, because i try to do it on the sdcard where i have nitdroid and i get the same.

That's because e2fsck is for ext2/ext3/ext4 partitions. You want to use dosfsck for FAT partitions. Or you could try the generic fsck, which should work out which fsck program is needed for the filesystem you want to check.