El Amir | # 1 | 2008-08-14, 01:01 | Report

I have ( -well had) 2 bootable partitions for my NIT.
Today I updated my flash partition with the latest SSU without problems and when I tried it on the mmc2 partition, I got "update error" -yet i didn't do anything to fix this.

I then tried to update my bootmenu and did so successfully a couple of times yet each time I try to boot from mmc2, the tablet tries but then finally boots into flash without giving a reason ( i don't get the "booting from mmc2 failed, booting from from flash" message)

I think I messed up bad the first time I flashed the bootmenu as I tried to reflash a bootmenu.conf I saved from the pre-SSU period.

I do have a backup of the mmc2 partition but would really appreciate not having to reclone the Os or format the SD.

Any ideas of what I can do? I even tried re-installing bootmenu-installer from penguinbait!

I did search the forum thoroughly, but still haven't encountered anyone with the same problem...
Hope I dont get bashed for this

bunanson | # 2 | 2008-08-14, 01:04 | Report

what did your boot menu show? Does it show any bracket bracket out your choices?

N810 or N800?

bun

El Amir | # 3 | 2008-08-14, 01:13 | Report

N800.
And nope I don't get brackets around my choices.
Here are a couple of pics of what I get:

when Im boot from mmc2:


and the bootmenu itself:


What do you think bun?

beatniks3 | # 4 | 2008-08-14, 01:30 | Report

have you tried to switch around the SD cards and see it you can boot from your cloned OS after that?

El Amir | # 5 | 2008-08-14, 01:33 | Report

Just tried but wont load from the 1st partition and fails from the second. Any more advice ?

El Amir | # 6 | 2008-08-14, 03:20 | Report

I don't think so but just to be sure, do I, at any point, need to mount my partition? read it somewhere on some recent thread and it put me in doubt...

nhanquy | # 7 | 2008-08-14, 03:40 | Report

You should boot device from flash then run fsck on the partition on the SD. After that, try to boot from the mmc again.

#sudo gainroot
#fsck /dev/mmcblk1p2 (for example ! )

El Amir | # 8 | 2008-08-14, 03:52 | Report

Here what i get when I do fsck /dev/mmcblk1p1 and fsck /dev/mmcblk1p2 :

Nokia-N800-23-14:~# fsck /dev/mmcblk1p1
fsck 1.37 (21-Mar-2005)
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
alleged total clusters: 1994972
malloc:Success


Nokia-N800-23-14:~# fsck /dev/mmcblk1p2
fsck 1.37 (21-Mar-2005)
e2fsck 1.37 (21-Mar-2005)
fsck.ext2: No such file or directory while trying to open /dev/mmcblk1p2
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

---> when I do e2fsck /dev/mmcblk0p2 , I get :
e2fsck 1.37 (21-Mar-2005)
/dev/mmcblk0p2: clean, 87563/430272 files, 447017/860160 blocks



even when I reboot it still won't boot from mmc2

---

Last edited by El Amir; 2008-08-14 at 04:02.

nhanquy | # 9 | 2008-08-14, 04:31 | Report

should you do e2fsck -b 8193 /dev/mmcblk1p2 instead?

El Amir | # 10 | 2008-08-14, 04:44 | Report

Indeed, and here's the output of e2fsck -b 8193 /dev/mmcblk1p2:

Nokia-N800-23-14:~# e2fsck -b 8193 /dev/mmcblk1p2

e2fsck 1.37 (21-Mar-2005)
e2fsck: No such file or directory while trying to open /dev/mmcblk1p2
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>



Thats bad news no?