I could recover the data by creating the same paritioning and then re-downloading the kernel in the first partition (one of teh post suggested that the bug actually eats up a sector from the first partition as well....I didn't check and downloading the kernel was pretty easy).
--Vikas On Wed, Aug 20, 2008 at 7:55 PM, Cédric Berger <[EMAIL PROTECTED]>wrote: > Thanks ! > > Anyway my partition table is now crashed thanks to suspend/resume issue. > I go digging in mailing list, I think I saw ways to recover... else > I'll have to start from 0... > > > On Wed, Aug 20, 2008 at 16:05, arne anka <[EMAIL PROTECTED]> wrote: > >> * can I change this table order without losing partition data ? > > > > nope. > > > >> * can I have Extended partition number (mmcblk0p3 now) to be after the > >> logical ones (so that mmcnlk0p2 and mmcblk0p3 refer to the 2 first > >> logical ones, -just the same as in my 512MB card-) ? > > > > nope. the logicla partitions are inside the extended partition -- numbers > > have to be bigger than the number of the extended partition. > > if you like partition number independent identifiers use labels -- either > > when creating the xt2 fs or afterwards with tune2fs, argument -L. > > > > > >> What is "funny" on my ubuntu laptop is that mount points are not > >> always in the same order. I have to be carefull ! > >> (of course I can fix mount points once for all on my pc -and also > >> access rights for ext3-, but when I plug the card in another PC, I > >> have the problem back...) > > > > you probably need to fix the udev script that creates the mount points. > > > > _______________________________________________ > Openmoko community mailing list > firstname.lastname@example.org > http://lists.openmoko.org/mailman/listinfo/community >
_______________________________________________ Openmoko community mailing list email@example.com http://lists.openmoko.org/mailman/listinfo/community