Is a "read error" normal during auto-root?

[Volknochi]

So, without there being any solution to my previous thread on huge battery drain, I just decided to restore the phone and reroot it. After some problems, I managed to get it rooted fine. At least, I think.

During the last leg of it, I noticed a string of errors (as shown below). Is this normal? Did it root fine?

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

E:\Applications\fresh-pre-kitchen-0.2>
E:\Applications\fresh-pre-kitchen-0.2>.\adb\adb-windows kill-server

E:\Applications\fresh-pre-kitchen-0.2>.\adb\adb-windows start-server
adb server is out of date.  killing...
* daemon started successfully *

E:\Applications\fresh-pre-kitchen-0.2>.\adb\adb-windows shell
# /data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
/data/local/asroot2 /system/bin/sh
 [+] Using newer pipe_inode_info layout
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Opening: /proc/770/fd/3
SUCCESS: Enjoy the shell.
# # cat /system/bin/sh > /system/bin/su
cat /system/bin/sh > /system/bin/su
# chmod 4755 /system/bin/su
chmod 4755 /system/bin/su
# flash_image recovery /sdcard/recovery-RA-heroc-v1.2.3.img
flash_image recovery /sdcard/recovery-RA-heroc-v1.2.3.img
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
mtd: read error at 0x00060000 (Out of memory)
mtd: read error at 0x00080000 (Out of memory)
mtd: read error at 0x000a0000 (Out of memory)
mtd: read error at 0x000c0000 (Out of memory)
mtd: read error at 0x000e0000 (Out of memory)
# reboot recovery
reboot recovery

E:\Applications\fresh-pre-kitchen-0.2>.\adb\adb-windows kill-server

E:\Applications\fresh-pre-kitchen-0.2>