After uboot update kernel won't boot (2.6.35.7)

Hi I just wanted to upgrade my 2.6.x Kernel to the newer 3.x series.

First I updated uboot as described here without errors and problems

http://forum.doozan.com/read.php?3,6965

I got this output

Marvell>> nand erase 0x0 0x80000
nand erase 0x0 0x80000

NAND erase: device 0 offset 0x0, size 0x80000
Erasing at 0x60000 -- 100% complete.
OK
Marvell>> nand write.e 0x800000 0x0 0x80000
nand write.e 0x800000 0x0 0x80000

NAND write: device 0 offset 0x0, size 0x80000
524288 bytes written: OK

Looks ok with no error.

After a reset, the dockstar boots boot cannot uncompress the kernel....

It says:
Starting kernel ... and then stops....

Can I load the old 2.6.35.7 kernel with the newer uboot?

I also tried to install a rescue but I did not work either.

Maybe I also messed up with the environment....

What can I do to install the dockstar from scratch?

The data on it is not important so a fresh install doesent matter.


Log with usb thumb drive attached:

U-Boot 2011.12 (Feb 12 2012 - 21:33:07)
Seagate FreeAgent DockStar
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot: 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=3"
UBI: MTD device size: 219 MiB
UBI: number of good PEBs: 1750
UBI: number of bad PEBs: 2
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 1729
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
2676840 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
** File not found /boot/uInitrd
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-2.6.35.7-dockstar
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2676776 Bytes = 2.6 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...


Log without usb thumb drive:

U-Boot 2011.12 (Feb 12 2012 - 21:33:07)
Seagate FreeAgent DockStar
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot: 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
** Block device usb 0 not supported

** Invalid boot device **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=3"
UBI: MTD device size: 219 MiB
UBI: number of good PEBs: 1750
UBI: number of bad PEBs: 2
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 1729
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: ....... read_nand_cached: error reading nand off 0xfe0000 size 8192 bytes
read_nand_cached: error reading nand off 0xfe2000 size 8192 bytes
read_nand_cached: error reading nand off 0xfe4000 size 8192 bytes
read_nand_cached: error reading nand off 0xfe6000 size 8192 bytes
read_nand_cached: error reading nand off 0xfe8000 size 8192 bytes
read_nand_cached: error reading nand off 0xfea000 size 8192 bytes
read_nand_cached: error reading nand off 0xfec000 size 8192 bytes
read_nand_cached: error reading nand off 0xfee000 size 8192 bytes
read_nand_cached: error reading nand off 0xff0000 size 8192 bytes
read_nand_cached: error reading nand off 0xff2000 size 8192 bytes
read_nand_cached: error reading nand off 0xff4000 size 8192 bytes
read_nand_cached: error reading nand off 0xff6000 size 8192 bytes
read_nand_cached: error reading nand off 0xff8000 size 8192 bytes
read_nand_cached: error reading nand off 0xffa000 size 8192 bytes
read_nand_cached: error reading nand off 0xffc000 size 8192 bytes
read_nand_cached: error reading nand off 0xffe000 size 8192 bytes
.. done.
read_nand_cached: error reading nand off 0xfdf200 size 8192 bytes
off = 0xfdecac magic 0x1985 type 0xe002 node.totlen = 1738
### JFFS2 load complete: 524288 bytes loaded to 0x800000
## Starting application at 0x00800200 ...

environment vars:

arcNumber=2097
baudrate=115200
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
bootdelay=10
console=ttyS0,115200
ethact=egiga0
ethaddr=xx:xx:xx:xx:xx:8D <- just edited for privacy
filesize=109C59C
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
if_netconsole=ping $serverip
ipaddr=192.168.0.16
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
ncip=192.168.0.1
partition=nand0,2
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
preboot=run if_netconsole start_netconsole
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
serverip=192.168.0.1
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_device=0:1
usb_init=run usb_scan
usb_root=/dev/sda1
usb_rootdelay=10
usb_rootfstype=ext2
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_scan_list=1 2 3 4
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params

Environment size: 2615/131068 bytes

What can I do to solve this problems?

Any help would be appreciated.

Thank you.

regards
starbuck

Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
** File not found /boot/uInitrd

the uInitrd isn't found. That's likely to be a problem.

I've got a ready made rootfs that will run on anything. See the Zyxel thread and after downloading just use the rootfs but not the zyxels uboot
http://forum.doozan.com/read.php?2,7806
My Pogoplug is running that same image. Just copy it onto a USB
Drive and use a usbboot command sequence.

=====================================================

• davy's Github Repo's rescue-dg

Edited 2 time(s). Last edit at 05/13/2012 12:11AM by davygravy.

Hello davygravy,

Thank you for your reply and the support.

I have downloaded your rootfs and copied it over to a ext2 partition on a new usb drive.
I have only one 8GB (ext2) Partition on the stick. Do I need also a swap partition ?
My old system is still on my old stick.

The system is booting and uImage and uInitrdget get loaded.

Loading file "/boot/uImage" from usb device 0:1 (usbda1)
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)

Kernel is loading but after

Loading Kernel Image ... OK
OK

Starting kernel ...

nothing happen also after waiting for a while....

The usb drive led is solid blue and the dockstar led lights solid green. (seems to be ok)

Before this trying to boot the system with my other stick the dockstar led flashed yellow.

The kernel gets not decompressed. Whats wrong here?

I also could not ping the dockstar.

PING 192.168.0.16 (192.168.0.16) 56(84) bytes of data.
From 192.168.0.1 icmp_seq=1 Destination Host Unreachable

(That's clear, kernel not loaded and eth0 is not up and running)

I think there is still another problem. What about the bootcmd?


What could I try next?

bootlog from netconsole:

U-Boot 2011.12 (Feb 12 2012 - 21:33:07)
Seagate FreeAgent DockStar
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot: 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=3"
UBI: MTD device size: 219 MiB
UBI: number of good PEBs: 1750
UBI: number of bad PEBs: 2
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 1729
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
2279256 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
7004538 bytes read
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.3.2
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2279192 Bytes = 2.2 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-3.3.2-kirkwood-dg
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 7004474 Bytes = 6.7 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...


regards
starbuck

Which machine you you have? Which U-Boot did you use to update? Are you sure you put the correct U-Boot on the correct machine ? Dockstar, GoFlex, and Pogoplug U-Boot kwb files are all similar, yet have differences that would cause them to not be interchangeable...

I'm using all of these same U-Boots and have tested them extensively... so I don't think the problem is w/ the U-Boot itself... but rather either an env setting or ... perhaps... wrong bootcmd...

How do you know the kernel isn't decompressing? If the light has gone green, then it is most likely booted, but something else it wrong...

=====================================================

• davy's Github Repo's rescue-dg

I have a seagate dockstar.

According to http://forum.doozan.com/read.php?3,6965

I used

for Dockstar and Pogoplug V1/E01 [wallwart-ish] : dockstar and Pogoplug V1/E01 u-boot replacement filename=uboot.mtd0.kwb-2011.12-L2Cdisabled-davysconfig

Quote
How do you know the kernel isn't decompressing? If the light has gone green, then it is most likely booted, but something else it wrong...

I think after the line Starting kernel ... there should something like decompressing the kernel.

What about the arc number ? arcNumber=2097 Have I set it to 2998?

What about the environment vars? Can you have a look at yours so we can compare it?

Could I use this for rescue? http://forum.doozan.com/read.php?2,1169

There is also a link to the original uboot file. ->uboot-original-mtd0.kwb
What's the correct md5sum of this file?

There are also rescue files

http://jeff.doozan.com/debian/uboot/uboot.environment
http://jeff.doozan.com/debian/rescue/uImage-mtd1.img
http://jeff.doozan.com/debian/rescue/rootfs-mtd2.img

but when I downloaded them they have different md5sums as stated in the post strange....

@davygravy

Success! Your image worked.

Dockstar booted without any errors I think. Dockstar led is solid green. Don't know exactly because I don't have any netconsole output anymore.

I couldn't ping the dockstar with the old address (192.168.0.16). Ah the dockstar must have get a new one via my dhcp from the router.

I quickly did a port scan and found an open ssh port. Bingo! ssh connection to this maschine worked. After a few trial and error shots I found out the root password as well.

Now I am in.

Quote
Linux debian-kirkwood-wide 3.3.2-kirkwood-dg #1 Mon Apr 23 17:09:27 CDT 2012 armv5tel

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun May 13 17:57:15 2012 from 192.168.0.1
root@debian-kirkwood-wide:~#

What should I do next to reinstall my system from scratch?

best regards
starbuck

Great to hear!

=====================================================

• davy's Github Repo's rescue-dg

Ok. Now so my system is running again I can start with a new installation.

How can I install the system completely new to the usb drive from scratch?
I think I can't install it on the usb drive I just booted the system from because it's used by the system, right?

Can I plugin a second usb stick on the second usb port and install the new system there?

After installation can I plug out the stick from which I started my system und boot from the newly installed system?

Will that work?

Or can I install the new system on the first stick also?

regards
starbuck

Starbuck : just to let you know ... another user found a problem w/ the image that was in the tarball. It has been updated.

The problem is with the apt-get infrastructure : /var/lib and some other contents were clobbered. You should re-download the tarball and then you can use that.

And yes, it will run on your machine - just about any Kirkwood machine.

=====================================================

• davy's Github Repo's rescue-dg

@davygravy

Ok. I will try it. Have you updated the first link? What is the md5sum for the file to make sure it is not corrupt?

FYI the 2nd link did not work anymore.

Can I then use the image from usb to install a complete new system on the a usb stick?

Or will I first have to flash a rescue system to the dockstar? See also my questions above?

regards
starbuck

I do not have an md5 sum for it, but I can tell you that since it is a tarball, both tarred and gzipped, it is pretty unlikely that it could be corrupted, unless it won't untar. If it won't untar/gunzip, then it is corrupt. If it does untar&gunzip, then it is OK.

hth, davy

=====================================================

• davy's Github Repo's rescue-dg