[Nexus One Android Development] Bierfreund:
General Recover Problem?

I have installed the latest RA-nexus-v1.7.0.1 recovery Image on my N1.

ROM Image is MoDaCo r19 (based on froyo FRF72). SD cars is not partitioned and formated in FAT32

Yesterday i wanted to test some alternate status bars and created a new nandroid backup before i started to test. Backup completed successfully (like the 2 backups i already did some days before).

During my tests I destroyed my image and my N1 did not boot any longer (it hung in the bootscreen). So I had to recover a nandroid backup for the first time.

I booted into recovery selected "Nand restore", afterwards i selected the folder "HT05********" on my sdcard (so sdcard should be mounted) and subfolder "BCDS-20100629-****" for the recent backup.

Unfortunately i got the follwing error message:

Error : run 'nandroid-mobile.sh restore' via adb!

OK, i thought, just try to do what it tells me to. I tried to recover with adb:

>adb devices
List of devices attached
HT05******** recovery

>adb shell
/ # nandroid-mobile.sh restore
nandroid-mobile.sh restore

nandroid-mobile v2.2.1

Using G1 keyboard, enter a directory name substring and then <CR>
to find matches or just <CR> to accept default:

Using string to search for matching backup directories

error: unable to mount /sdcard, aborting

Hm, doesn't work either. I tried to figure out why with my limited unix skills:

/# cd /sdcard
cd /sdcard
/sdcard # ls
ls
/sdcard # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nodev,noatime,nodiratime)

OK, /sdcard is not mounted as you can see above. But it should, as you see below:

/sdcard # cat /etc/fstab
cat /etc/fstab
/dev/block/mtdblock3 /system yaffs2 rw
/dev/block/mtdblock4 /cache yaffs2 rw
/dev/block/mtdblock5 /data yaffs2 rw
/dev/block/mmcblk0p1 /sdcard vfat rw
/dev/block/mmcblk0p2 /sd-ext auto rw

Mounting it manually does not work either:

/sdcard # mount /sdcard
mount /sdcard
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: No such file or directory

There is no /dev/block/mmcblk0p1 device like it is specified it /etc/fstab:

/sdcard # ls /dev/block
ls /dev/block
loop0 loop3 loop6 mtdblock0 mtdblock3
loop1 loop4 loop7 mtdblock1 mtdblock4
loop2 loop5 mmcblk0 mtdblock2 mtdblock5

Strange, because in the recovery menu on the phone the folders were visible.

I selected "Flash zip from sdcard" in the menu on the phone, and i could see all *.zip files on my sdcard.

By selecting "Flash zip from sdcard" the sdcard seems to be mounted correctly, because after selecting "Flash zip from sdcard" everythings seems fine:

mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nodev,noatime,nodiratime)
/dev/block/mmcblk0 on /sdcard type vfat (rw,nodev,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/sdcard # cd /sdcard
cd /sdcard
/sdcard # ls
ls
<...>
nandroid
<...>

And now manual restore works:

/sdcard # nandroid-mobile.sh restore
nandroid-mobile.sh restore

nandroid-mobile v2.2.1

Using G1 keyboard, enter a directory name substring and then <CR>
to find matches or just <CR> to accept default:

Using string to search for matching backup directories

Looking for the latest backup, will display other choices!

Default backup is the latest: /sdcard/nandroid/HT05********/BCDS-20100629-2023
Other available backups are:

/sdcard/nandroid/HT05BP800542/BCDS-20100626-1428
/sdcard/nandroid/HT05BP800542/BCDS-20100629-1113

Using G1 keyboard, enter a unique name substring to change it and <CR>
or just <CR> to accept:

Is it just me, or is this a general problem?