After Upgrade to Wheezy reboot problem

Hi,

I made an upgrade from Debian Squeeze to Wheezy. After apt-get upgrade the reboot was fine. Then I made apt-get dist-upgrade and now I'm unable to reboot.

Here is the output on netconsole

First with the direct installed kernel

U-Boot 2010.09 (Oct 23 2010 - 11:49:22)
Marvell-Dockstar/Pogoplug by Jeff Doozan
Hit any key to stop autoboot:  9 ^C
root@polo:/home/niels# nc -klu 6666
 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: fixable bit-flip detected at PEB 179
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=3"
UBI: MTD device size:            219 MiB
UBI: number of good PEBs:        1752
UBI: number of bad PEBs:         0
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:             1731
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)
1607752 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
7233592 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   kernel 3.2.0-4-kirkwood
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1607688 Bytes = 1.5 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   ramdisk 3.2.0-4-kirkwood
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7233528 Bytes = 6.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Then I take vmlinuz.bak and initrd.img.old and make rename them to vmlinuz initrd.old. Futhermore I take the bak-Files from /boot/uImage and /boot/uInitrd. With no success.

After that I copied the old /boot/uImage and /boot/uInitrd to the stick (I took them from a backup).
This ends to

U-Boot 2010.09 (Oct 23 2010 - 11:49:22)
Marvell-Dockstar/Pogoplug by Jeff Doozan
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: fixable bit-flip detected at PEB 179
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=3"
UBI: MTD device size:            219 MiB
UBI: number of good PEBs:        1752
UBI: number of bad PEBs:         0
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:             1731
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)
1431936 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
4738738 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.32-5-kirkwood
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1431872 Bytes = 1.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-2.6.32-5-kirkwood
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4738674 Bytes = 4.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Using an old-stick with the backup the output is the following:

OLD_Output
U-Boot 2010.09 (Oct 23 2010 - 11:49:22)
Marvell-Dockstar/Pogoplug by Jeff Doozan
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: fixable bit-flip detected at PEB 179
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=3"
UBI: MTD device size:            219 MiB
UBI: number of good PEBs:        1752
UBI: number of bad PEBs:         0
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:             1731
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)
1431936 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
4738738 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.32-5-kirkwood
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1431872 Bytes = 1.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-2.6.32-5-kirkwood
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4738674 Bytes = 4.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

I can't see the difference. Can someone give me a hint how to analyze this problem?

In /var/log I can't find any information. All files are old.



Edited 1 time(s). Last edit at 09/10/2013 05:27AM by dockstar.

Looks like its booting to me. Maybe it's not getting an ip. Try removing the /etc/udev/rules.d/70-persistent-net.rules.

I uncommenting everything in /etc/udev/rules.d/70-persistent-net.rules, but no success.

Furthermore I tried to add some log in /etc/init.d/bootlogs with
case "$1" in
start|"")
echo "Hallo Welt " > /root/test
do_start
;;

But no log found.

I take my running system and followed http://forum.doozan.com/read.php?2,9522,9713.
First enter to /etc/initramfs-tools/modules

netconsole=6666@192.168.0.2/eth0,6666@192.168.0.39/

192.168.0.2 =dockstar
192.168.0.39=myPC

modprobe netconsole works fine.

Then I create

 update-initramfs -c -b ~/rescue -k  2.6.32-5-kirkwoo
 mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-3.2.28 -d ~/rescue/initrd.img-2.6.32-5-kirkwood ~/rescue/uInitrd

and copied both files to my new usb-stick. Unfortunatly no more infos on netconsole.

One more interesting thing: After about 3 minutes I'm able to make a ping to the dockstar. SSH get Connection refused.
I stopped all firewalls.

icmp_seq=186 Destination Host Unreachable
icmp_req=187 ttl=64 time=1998 ms

ssh seems to be on the host. Still no output which shows that the dockstar is really booting - Frustrating.

dockstar Wrote:
-------------------------------------------------------
> I uncommenting everything in
> /etc/udev/rules.d/70-persistent-net.rules, but no
> success.
>

The suggestion was to remove the file, not uncomment lines in it.

Sorry for don't follow the suggestion directly. I tried it with the self made ramdisk, nothing changed. This time the 145 ping get an response (The oldstick with normal startup req 15 after Kernel is booting). SSH still not work. However it shows that the server is booting, because it's recreate the file.
I switch then to the kernel 3.2 from Debian Wheezy and remove the file again. However then the ping has no success. The file 70-persistent-net.rule wasn't recreated :-(

What I'm still not understand, why I don't see any file-output from /etc/init.d/bootlogs. And I created a cronjob which run every 5 Minutes, without success too.

Can the file /etc/network/interfaces makes the trouble?

auto lo eth0
iface lo inet loopback
iface eth0 inet static
        address 192.168.0.2
        netmask 255.255.255.0
        network 192.168.0.0
        broadcast 192.168.0.255
        gateway 192.168.0.10
        dns-nameservers 192.168.0.10
        dns-search fritz.box
  up /etc/local_init_scripts/getDate.sh

Also try changing the whitelist in
/lib/udev/rules.d/xx-persistent-net-generator.rules

# device name whitelist
KERNEL!="eth*|ath*|wlan*[0-9]|msh*|ra*|sta*|ctc*|lcs*|hsi*", \
					GOTO="persistent_net_generator_end"

to

# device name whitelist
KERNEL!="Eth*|ath*|Wlan*[0-9]|msh*|ra*|sta*|ctc*|lcs*|hsi*", \
					GOTO="persistent_net_generator_end"

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I tried it with this in /lib/udev/rules.d/75-persistent-net-generator.rules using the new kernel.

# device name whitelist
KERNEL!="Eth*|ath*|wlan*[0-9]|msh*|ra*|sta*|ctc*|lcs*|hsi*", \
                                        GOTO="persistent_net_generator_end"

Again no success to connect the server and again
/etc/udev/rules.d/70-persistent-net.rules will not created if I delete it before booting. :-(

Did you ever find out what was causing this because I am having exactly the same problem.

I have been running Squeeze on my DockStar for a couple of years. I should have left well alone but I foolishly decided to upgrade and I appear to be having the same problem you did. I have had similar problems booting in the past and deleting the udev file did the trick then but now it isn't.

[Edit]
After further investigation, it appears my problem is different as I'm fairly sure my DockStar is not booting at all. I have posted separately.



Edited 1 time(s). Last edit at 10/18/2013 11:41AM by lotus49.

No I stopped completly the upgrade and run the old version. Still a little bit frustrated. I'm thinking to buy a device with graphic interface like rasperry pi, but at the moment I fouces on

I'm having exaclty the same frustrations, I have some RaspPi devices around, but still these devices have their limits.
I visited a local PC parts distributor yesterday and saw Gigabyte is selling Intel Celeron barebones (BRIX) with the footprint of a 3.5" floppy (but thicker off cource). You can install a full blown Linux distro on this, have the gcc environment on it an compile stuff from sources. It's more expensive, but saves a lot of time (in my case anyway). I'm nearly at the end of my patience, ready to throw the dockstar & Co devices in the bin. I allready spent 2 days "reviving" the dockstar. In theory it's nice, but it needs to work O.O.B. or you spend more time on the forums then on the actual project ( my project is controlling my home KNX Domotics system).
When I was experimenting with openwrt on asus and linksys devices I never had these kind of issues, I never even bricked a single router. Now I have 1 device "unable to boot" and others where I'm unable to get a fresh Squeeze install (see my fresh post of today).

My advise: If you have a working Squeeze, don't upgrade unless you actually backupped the USB stick (what I luckily did).

pdecle Wrote:

>
> My advise: If you have a working Squeeze, don't
> upgrade unless you actually backupped the USB
> stick (what I luckily did).

Sadly that wouldn't have helped me. Whatever has happened in my case affected the DockStar itself not the disk on which Debian is installed. When I swapped the disks around on my two DockStars, the same DockStar failed to boot and the other still worked fine.

Looking back at the opening post, The poster has this uboot installed

Quote
uboot
U-Boot 2010.09 (Oct 23 2010 - 11:49:22)
Marvell-Dockstar/Pogoplug by Jeff Doozan

I don't think the installed uboot can boot the 3.2 kenel. See this thread:
http://forum.doozan.com/read.php?3,6965

Uboot needs to be update to the lastest version



Edited 1 time(s). Last edit at 10/20/2013 05:07PM by laprjns.

I fear you are right.
OK so I must do the following steps
1. Check that my netconsole or serial console connection is working correctly, just in case.
2. fw_printenv |sort > uboot_env
3. cd /tmp
wget http://projects.doozan.com/uboot/install_uboot_mtd0.sh
chmod +x install_uboot_mtd0.sh
./install_uboot_mtd0.sh
4. Before reboot, make sure you check that you have your original values... a few of the values might have to be restored.
fw_printenv |sort > uboot_env.after
diff uboot_env uboot_env.after
Take changes and restore via fw_setenv <var> <value> the oldvalues for the relevant settings (I guess everything except arcNumber?)
5. reboot

Is it correct or must I read the whole threads?

Thanks for check it, it's not so easy for an non native English speaker who isn't familar with firmware to understand the whole things.
Niels

No, you don;t have to read the complete thread, looks like you've got the correct instructions.

IIRC, when you run the script install_uboot_mtd0.sh, it will ask you whether you want to keep the current uBoot envs or restore to the default version, you should say No (I think it is the default answer).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thanks!!! Now it works. The boot-process seems to be a bit slower and there are still some error-message, but the server starts :-)

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: fixable bit-flip detected at PEB 179
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=3"
UBI: MTD device size:            219 MiB
UBI: number of good PEBs:        1752
UBI: number of bad PEBs:         0
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:             1731
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)
1607752 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
7233592 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   kernel 3.2.0-4-kirkwood
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1607688 Bytes = 1.5 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   ramdisk 3.2.0-4-kirkwood
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7233528 Bytes = 6.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...