Welcome! Log In Create A New Profile

Advanced

Kernel loads, but cant connect

Posted by menno 
Forum List Message List New Topic
menno
Kernel loads, but cant connect
October 27, 2010 01:42PM
I followed the instructions at http://jeff.doozan.com/debian/ but cant connect to my Dockstar.

I've used the netconsole to check, and my device seems to start the debian kernel ok. But I cant ssh into it or ping it.

Without the USB stick, it defaults back into the pogoplug linux, which allows me to ping and ssh into it.

I've mounted the USB stick from that and had a look, but cant see any of the /var/log files being updated. Is there anywhere else I can look to see what is happening after the kernel boot?

The netconsole log is as follows:

Quote

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: attached mtd1 to ubi0
UBI: MTD device name: "mtd=3"
UBI: MTD device size: 219 MiB
UBI: number of good PEBs: 1751
UBI: number of bad PEBs: 1
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: 1730
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)
1432032 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
4735332 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: 1431968 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: 4735268 Bytes = 4.5 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...


Cheers,
Menno
Reply Quote
Jeff
Re: Kernel loads, but cant connect
October 27, 2010 01:54PM
Your Dockstar may have a different IP address after installing Debian. Check your DHCP logs.

-- Jeff
Reply Quote
menno
Re: Kernel loads, but cant connect
October 27, 2010 01:58PM
Hi Jeff,

I checked that, and cant find anything in my dd-wrt router DHCP logs. Nmap also didnt find anything.

I also tried editing the /etc/network/interfaces file to use a static ip, but without any success.
Reply Quote
menno
Re: Kernel loads, but cant connect
October 27, 2010 07:58PM
I managed to get my dockstar loading the kernel by using a different USB stick. The other two USB sticks I tried both failed to show up on the network, although both said "Starting kernel ..." on the netconsole.

So not sure why that is happening.
Reply Quote
Jeff
Re: Kernel loads, but cant connect
October 27, 2010 08:08PM
Did you have multiple devices plugged in when you tried to boot? Sometimes the kernel will detect USB devices that uBoot doesn't and the sda/b/c enumeration gets messed up.

If you even get a serial cable connected, I'd be curious to see what the bootlog looks like with your bad drives.

-- Jeff
Reply Quote
menno
Re: Kernel loads, but cant connect
October 28, 2010 04:11AM
Jeff Wrote:
-------------------------------------------------------
> Did you have multiple devices plugged in when you
> tried to boot? Sometimes the kernel will detect
> USB devices that uBoot doesn't and the sda/b/c
> enumeration gets messed up.

No I always have only the usb stick connected. I'm still trying to boot from one of the failing USB sticks as the working one is only a 512MB stick.

I did get some errors when trying to reinstall:

Quote

W: Failure trying to run: chroot /tmp/debian dpkg --force-depends --install /var/cache/apt/archives/base-files_5.9_armel.deb /var/cache/apt/archives/base-passwd_3.5.22_armel.deb
debootstrap failed.
See /tmp/debian/debootstrap/debootstrap.log for more information.

The debootstrap.log contained a Segmentation fault:

Quote

Unpacking base-passwd (from .../base-passwd_3.5.22_armel.deb) ...
dpkg: base-passwd: dependency problems, but configuring anyway as you requested:
base-passwd depends on libc6 (>= 2.4); however:
Package libc6 is not installed.
Setting up base-passwd (3.5.22) ...
dpkg: base-files: dependency problems, but configuring anyway as you requested:
base-files depends on awk; however:
Package awk is not installed.
Setting up base-files (5.9) ...
Segmentation fault
dpkg: error processing base-files (--install):
subprocess installed post-installation script returned error exit status 139
Errors were encountered while processing:

Have reformatted the stick, and will try again.

Cheers,
Menno
Reply Quote
menno
Re: Kernel loads, but cant connect
October 29, 2010 09:47AM
Hi Jeff,

Just to update you, but in the end I discovered the cause of this error was two failing USB sticks. Bad blocks would appear over time. I'm guessing the translation layer of the flash device which can move the physical block mappings explains the fact that sometimes the sticks were ok and sometimes not.

Cheapo unbranded USB sticks so anyone else having this problem, I recommend you test the blocks on your disk.
Reply Quote
Newer Topic Older Topic
Author:

Your Email:


Subject:
Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: