[SOLVED] Help! My DockStar Squeeze don't boot anymore.

Did apt-get update, apt-get upgrade this morning. Everything seems to be OK except the LED is off after system is completed loaded and running.
Did "fw_setenv arcNumber 2998" and reboot....
System is no longer able to restart, telnet or ssh to it are not responsive.
Anyway to undo the fw_setenv?
Thank you in advance.

EDIT: reinstall uboot fixed the problem.



Edited 3 time(s). Last edit at 08/06/2012 08:25PM by funtoy1001.

After I re-installed uboot, I am able to reboot it and the LED turns green after it completed its boot process. Why would it not able to boot when I arcNumber to 2998? Was I supposed to something after "apt-get update" and "apt-get upgrade"?
Thanks.

I use arcNumber=2097 for my dockstar.

Although if you try to use a number that your kernel doesn't support it may not work.

When I do a fw_printenv now, I got 2298 for arcNumber.

@funtoy,

As optim said, your kernel probably does not have LED supports. arcNumber 2998 for Dockstar requires a kernel with LED supports. What is the output of
uname -a

and the content of your apt source list ?

-bodhi

uname -a
Linux xxxx 2.6.32-5-kirkwood #1 Sun May 6 16:57:51 UTC 2012 armv5tel GNU/Linux

cat /etc/apt/sources.list


deb http://ftp.us.debian.org/debian squeeze main contrib non-free
deb http://security.debian.org/ squeeze/updates main contrib non-free

I saw you're booting OK now with 2998?. The last unsuccessful reboot could have been something to do with the network udev rules after you've done apt-get upgrade (I am guessing). If you're curious, you could mount the stick on a different box and look at the log files or the udev rules to see if it was reset or messed up.

bodhi Wrote:
-------------------------------------------------------
> I saw you're booting OK now with 2998?. The last
> unsuccessful reboot could have been something to
> do with the network udev rules after you've done
> apt-get upgrade (I am guessing). If you're
> curious, you could mount the stick on a different
> box and look at the log files or the udev rules to
> see if it was reset or messed up.


No, I have not tried again with 2998. After it failed to boot, I reinstalled uBoot and it is working again. After it booted, I did a fw_printeenv and see the arcNumber is set to 2298.
Thanks.

That's really strange! the Dockstar is 2998. I'm wondering whether you have somehow inadvertenly flashed an incorrect UBoot?

I reflashed it by following the instruction at http://projects.doozan.com/uboot/

I guess I am really messed it up. Was trying to put rescue system v2 (http://forum.doozan.com/read.php?4,3896) on and didn't work. After power cycle, it will boot my USB stick but I can't SSH into it if I unplug all the USB device. I have the following from net console...

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: 10  9  8  7  6  5  4  3  2  1  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:        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'!
** 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:    done.
find_inode failed for name=uboot-original-mtd0.kwb
load: Failed to find inode
### JFFS2 LOAD ERROR<0> for uboot-original-mtd0.kwb!
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS:    done.
find_inode failed for name=uboot-original-mtd0.kwb
load: Failed to find inode
### JFFS2 LOAD ERROR<0> for uboot-original-mtd0.kwb!
resetting ...

Looks like it is caused by not able to update mtd2.

 ubiformat /dev/mtd2 -s 512 -f rootfs-mtd2.img -y
ubiformat: mtd2 (nand), size 33554432 bytes (32.0 MiB), 256 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 255 -- 100 % complete
ubiformat: 13 eraseblocks have valid erase counter, mean value is 0
ubiformat: 243 eraseblocks are supposedly empty
ubiformat: warning!: only 13 of 256 eraseblocks have valid erase counter
ubiformat: erase counter 0 will be used for all eraseblocks
ubiformat: note, arbitrary erase counter value may be specified using -e option
ubiformat: use erase counter 0 for all eraseblocks
ubiformat: flashing eraseblock 86 -- 39 % complete  libmtd: error!: cannot write 131072 bytes to mtd2 (eraseblock 86, offset 0)
        error 12 (Cannot allocate memory)

ubiformat: error!: cannot write eraseblock 86
           error 12 (Cannot allocate memory)

Edited 1 time(s). Last edit at 07/31/2012 07:30PM by funtoy1001.

While I can ssh into the unit, it does not have net access.



Edited 1 time(s). Last edit at 08/01/2012 12:44PM by funtoy1001.

Bump...

Anyway to check why it doesn't have web access? I can SSH in but it took several second before I see the password prompt.

If I delete /etc/resolv.conf and restart the network, no password prompt delay when I ssh in but still no net access.



Edited 1 time(s). Last edit at 08/04/2012 08:21PM by funtoy1001.

This is very typical of a DNS issue. The Dockstar is trying to do a reverse lookup for recording the login attempt, but the nameserver for whatever reason is not responding. So, everything pauses until the DNS subsystem times out.

1. Are you using a dynamic or static IP assignment?

2. What is the output of "ifconfig -a"?

3. What is the output of "netstat -rn"?

4. What is the contents of "/etc/network/interfaces"?

restamp Wrote:
-------------------------------------------------------
> This is very typical of a DNS issue. The Dockstar
> is trying to do a reverse lookup for recording the
> login attempt, but the nameserver for whatever
> reason is not responding. So, everything pauses
> until the DNS subsystem times out.
>
> 1. Are you using a dynamic or static IP
> assignment?
Static

>
> 2. What is the output of "ifconfig -a"?
eth0 Link encap:Ethernet HWaddr 02:50:43:xx:xx:xx
inet addr:192.168.1.11 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::50:43ff:fe24:ca80/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:89 errors:0 dropped:0 overruns:0 frame:0
TX packets:240 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:11254 (10.9 KiB) TX bytes:25334 (24.7 KiB)
Interrupt:11

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:57 errors:0 dropped:0 overruns:0 frame:0
TX packets:57 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3796 (3.7 KiB) TX bytes:3796 (3.7 KiB)

tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.8.0.1 P-t-P:10.8.0.2 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
> 3. What is the output of "netstat -rn"?
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
10.8.0.2 0.0.0.0 255.255.255.255 UH 0 0 0 tun0
10.8.0.0 10.8.0.2 255.255.255.0 UG 0 0 0 tun0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0

>
> 4. What is the contents of
> "/etc/network/interfaces"?
auto lo eth0
iface lo inet loopback
iface eth0 inet static
address 192.168.1.11
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1

Hmm, I don't see any obvious problems so far.

When you say you have no web access, do you mean no IP access outside your local LAN or no access to a DNS server?

What is the results of a "traceroute 8.8.8.8"?
("apt-get install traceroute" if you need to.)

Also, do you currently have an /etc/resolv.conf, and if so, what is in it?



Edited 1 time(s). Last edit at 08/05/2012 01:33AM by restamp.

restamp Wrote:
-------------------------------------------------------
> Hmm, I don't see any obvious problems so far.
>
> When you say you have no web access, do you mean
> no IP access outside your local LAN or no access
> to a DNS server?
I can not do ping to anywhere. For example, the result of ping 8.8.8.8 is
--- 8.8.8.8 ping statistics ---
22 packets transmitted, 0 received, 100% packet loss, time 21002ms


>
> What is the results of a "traceroute 8.8.8.8"?
> ("apt-get install traceroute" if you need to.)
Can not do apt-get because of no net access.
Err http://ftp.us.debian.org/debian/ squeeze/main traceroute armel 1:2.0.15-1
Could not resolve 'ftp.us.debian.org'
Failed to fetch http://ftp.us.debian.org/debian/pool/main/t/traceroute/traceroute_2.0.15-1_armel.deb Could not resolve 'ftp.us.debian.org'
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?


>
> Also, do you currently have an /etc/resolv.conf,
> and if so, what is in it?

nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 208.94.147.150
nameserver 209.94.147.151
nameserver 192.168.1.1

As I mentioned before. If I delete this file and reboot, I have no delay getting the password prompt when I do a ssh but it still has no net access. I also tried to edit the file down to just the 192.168.1.1 entry but it didn't make any difference.
Thanks.

I'm running out of ideas.

192.168.1.1 is the IP address of your router, which is connected to the internet, right?

And, your Dockstar is on the same LAN as the router?

Can you ping the router?

Now the dockstar has internet access. For some reason the router was trying to assign the same IP address to another device. Can the MAC address of the Dockstar be changed because I erased MTD1 & MTD2?

I guess what I need to do now is to restore MTD1 & MTD 2.



Edited 2 time(s). Last edit at 08/05/2012 07:06PM by funtoy1001.

Glad you got the issue resolved. I was about to suggest rebooting your router.

The MAC address is set as part of the uBoot's environment. Changing MTD1 & MTD2 shouldn't affect it.

Was the MAC address the same as on the underside of the Dockstar or something different?

restamp Wrote:
-------------------------------------------------------
> Glad you got the issue resolved. I was about to
> suggest rebooting your router.
>
> The MAC address is set as part of the uBoot's
> environment. Changing MTD1 & MTD2 shouldn't
> affect it.
>
> Was the MAC address the same as on the underside
> of the Dockstar or something different?
No, the MAC is totally different from the one on the underside of the unit. The current MAC address is 02:50:... which I never seen before.


EDIT: use fw_setenv to reset the MAC address back to the one on the bottom of the unit and installed rescue v2 on MTD2.



Edited 1 time(s). Last edit at 08/06/2012 08:27PM by funtoy1001.