Pogo won't respond to ping or ssh (waited about hr)

[amanpatel]

My pogo (alarm'd) did not respond to ping or ssh after a reboot. I did do a pacman upgrade of the system about few days ago.

My suspicion was fsck was running and therefore had to wait a while before it would come back up. However waiting for an hour did not help (also the hdd activity light was not blinking at all).

I removed the hard drive and put it in a linux machine, I fsck'ed it and it repaired several hundred orphaned inodes.

Here is the end part of my dmesg: (i'm concerned where it detects the ethernet address as "00:30:e0:00:00:00").

Any other ideas on what could be wrong?

$this->bbcode_second_pass_code('', '
[ 2.840000] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 2.850000] usb 1-1: Product: USB2.0 Hub
[ 2.850000] usb 1-1: configuration #1 chosen from 1 choice
[ 2.860000] hub 1-1:1.0: USB hub found
[ 2.870000] hub 1-1:1.0: 4 ports detected
[ 3.150000] usb 1-1.2: new high speed USB device using oxnas-ehci and address 3
[ 3.260000] usb 1-1.2: New USB device found, idVendor=04fc, idProduct=0c25
[ 3.270000] usb 1-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 3.270000] usb 1-1.2: Product: USB to Serial-ATA bridge
[ 3.280000] usb 1-1.2: Manufacturer: Sunplus Technology Co.,Ltd.
[ 3.280000] usb 1-1.2: SerialNumber: FFFFFBA0FF00000000000F17EFF02F
[ 3.290000] usb 1-1.2: configuration #1 chosen from 1 choice
[ 3.300000] scsi2 : SCSI emulation for USB Mass Storage devices
[ 3.310000] usb-storage: device found at 3
[ 3.310000] usb-storage: waiting for device to settle before scanning
[ 8.310000] scsi 2:0:0:0: Direct-Access TOSHIBA MK1059GSM PQ: 0 ANSI: 2
[ 8.320000] usb-storage: device scan complete
[ 8.320000] sd 2:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 8.330000] sd 2:0:0:0: [sda] Write Protect is off
[ 8.340000] sd 2:0:0:0: [sda] Mode Sense: 38 00 00 00
[ 8.340000] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 8.350000] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 8.350000] sda: sda1
[ 8.700000] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 8.700000] sd 2:0:0:0: [sda] Attached SCSI disk
[ 8.800000] kjournald starting. Commit interval 5 seconds
[ 8.800000] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
[ 8.800000] EXT3 FS on sda1, internal journal
[ 8.800000] EXT3-fs: recovery complete.
[ 8.800000] EXT3-fs: mounted filesystem with writeback data mode.
[ 8.800000] VFS: Mounted root (ext3 filesystem) on device 8:1.
[ 8.800000] Freeing init memory: 124K
[ 12.480000] Probing for Synopsis GMAC, unit 0
[ 12.490000] eth0: Tuning GMAC 0 RGMII timings
[ 12.490000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
[ 12.500000] eth0: GMAC ver = 53, vendor ver = 18 at 0xed400000, IRQ 40
[ 12.510000] eth0: Found PHY at address 3, type 0x001cc914 -> 10/100/1000
[ 12.510000] eth0: Ethernet addr: 00:30:e0:00:00:00
[ 12.520000] probe() eth0: Leon x2 clock
[ 12.770000] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
[ 12.780000] EXT3 FS on sda1, internal journal
')

[Philoo]

let's trust that the external power for the sata drive is enough. I'd next check the whole boot process with the serial cable, you'll need to open the pogo to connect the pins.
you could also, from a different computer:
- install current rootfs on a spare usb flash drive
- remove your 1TB drive from the pogo
- boot from the spare flash drive
- re-insert the 1TB
- chroot to it
- try to figure out what's wrong from there.

I would not worry too much about the mac address shown in dmesg, this is the default sent to the kernel by uboot, it is updated to the "actual" value further in the startup process (I *think* gmac does it, based on /usr/mac_address file if memory serves).

[kuleszdl]

I am currently experiencing the same problem with a self-built debian rootfs. On a working setup it should look like the following. First comes the message you have posted with the fake mac:

$this->bbcode_second_pass_code('', '
[ 12.800000] eth0: Tuning GMAC 0 RGMII timings
[ 12.810000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
[ 12.840000] eth0: GMAC ver = 53, vendor ver = 18 at 0xed400000, IRQ 40
[ 12.850000] eth0: Found PHY at address 3, type 0x001cc914 -> 10/100/1000
[ 12.850000] eth0: Ethernet addr: 00:30:e0:00:00:00
[ 12.860000] probe() eth0: Leon x2 clock
')

But then, followed by something like this:

$this->bbcode_second_pass_code('', '
[ 16.110000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
[ 16.120000] CoPro offload is active on eth0
[ 16.120000] Alloc'ing ARM descs 8192 bytes
[ 16.130000] Alloc'ing CoPro parameters 36 bytes
[ 16.130000] gmac gmac.0: firmware: requesting gmac_copro_firmware
[ 16.150000] CoPro: Programming start address as 0xd000e000
[ 16.260000] eth0: Resetting GMAC
[ 16.260000] eth0: GMAC reset complete
[ 16.270000] eth0: Setting Rx flow control thresholds for LAN port
[ 16.830000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
[ 17.330000] eth0: link down
[ 19.290000] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 19.330000] eth0: link up, 100Mbps, full-duplex, using pause, lpa 0x45E1
[ 19.330000] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 29.540000] eth0: no IPv6 routers present
')

In my case, ifconfig shows the correctly changed address on the working setup. In the broken setup, I don't get the second listing at all, the log ends with "Turning off blinking LED."