Pogoplug V4 won't restart after power-off

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

Pogoplug V4 won't restart after power-off

Postby skywiselh » Tue May 27, 2014 11:02 pm

So I have a rather frustrating issue with my Pogoplug Mobile. I have a working, fine installation of Archlinux on my Kingston 8GB flash drive and the unit boots fine from the device, I can reboot; no problem until I try to power the unit off - after which it won't restart, no matter what. I do have a serial interface on my device, but it hasn't been much help. To revive the unit, all I have to do is run a quick fsck -f on the flash drive and it will boot again. I suspect something is strange with the shutdown script, but i find it weird that reboot works just fine. Any suggestions appreciated.

Here is the serial output from 'shutdown -h now', power-off and power-on. The USB drive was not touched:
$this->bbcode_second_pass_code('', '
[ OK ] Reached target Shutdown.
[ 83.652575] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[ 83.678835] systemd-journald[82]: Received SIGTERM from PID 1 (systemd-shutdow).
[ 85.366716] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[ 85.390530] systemd-shutdown[1]: Unmounting file systems.
[ 85.396924] systemd-shutdown[1]: Unmounting /dev/mqueue.
[ 85.417891] systemd-shutdown[1]: Unmounting /sys/kernel/debug.
[ 85.540798] systemd-shutdown[1]: All filesystems unmounted.
[ 85.546414] systemd-shutdown[1]: Deactivating swaps.
[ 85.551758] systemd-shutdown[1]: All swaps deactivated.
[ 85.557022] systemd-shutdown[1]: Detaching loop devices.
[ 85.572676] systemd-shutdown[1]: All loop devices detached.
[ 85.578604] systemd-shutdown[1]: Detaching DM devices.
[ 85.584279] systemd-shutdown[1]: All DM devices detached.
[ 85.589778] systemd-shutdown[1]: Storage is finalized.
[ 85.601529] systemd-shutdown[1]: Successfully changed into root pivot.
[ 85.608219] systemd-shutdown[1]: Returning to initrd...
Sending SIGTERM to remaining processes...
Sending SIGKILL to remaining processes...
Unmounting file [ 85.654160] cgroup: option changes via remount are deprecated (pid=1 comm=shutdown)
systems.
Unmounting /oldroot/sys/fs/cgroup/perf_event.
[ 85.687956] cgroup: option changes via remount are deprecated (pid=1 comm=shutdown)
Unmounting /oldroot/sys/fs/cgroup/bfqio.
[ 85.727948] cgroup: option changes via remount are deprecated (pid=1 comm=shutdown)
Unmounting /oldroot/sys/fs/cgroup/blkio.
[ 85.767933] cgroup: option changes via remount are deprecated (pid=1 comm=shutdown)
Unmounting /oldroot/sys/fs/cgroup/net_cls.
[ 85.807932] cgroup: option changes via remount are deprecated (pid=1 comm=shutdown)
Unmounting /oldroot/sys/fs/cgroup/freezer.
[ 85.847927] cgroup: option changes via remount are deprecated (pid=1 comm=shutdown)
Unmounting /oldroot/sys/fs/cgroup/devices.
[ 85.887951] cgroup: option changes via remount are deprecated (pid=1 comm=shutdown)
Unmounting /oldroot/sys/fs/cgroup/cpu,cpuacct.
[ 85.927965] cgroup: option changes via remount are deprecated (pid=1 comm=shutdown)
Unmounting /oldroot/sys/fs/cgroup/cpuset.
[ 85.968100] cgroup: option changes via remount are deprecated (pid=1 comm=shutdown)
[ 85.975726] cgroup: option or name mismatch, new: 0x0 "", old: 0x4 "systemd"
Unmounting /oldroot/sys/fs/cgroup/systemd.
Unmounting /oldroot/sys/fs/cgroup.
Unmounting /oldroot/run.
Unmounting /oldroot/dev/pts.
Unmounting /oldroot/dev/shm.
Unmounting /oldroot/sys/kernel/security.
Unmounting /oldroot/sys.
Unmounting /oldroot/proc.
Unmounting /oldroot/dev.
Unmounting /oldroot.
All filesystems unmounted.
Deactivating swaps.
All swaps deact[ 86.402180] reboot: System halted
ivated.
Detachi

U-Boot 1.1.4 (Oct 1 2011 - 12:21:35) Cloud Engines 1.1.2 (3.4.27) PHYADDR=0

U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006918B4

Soc: 88F6192 A1 (DDR2)
CPU running @ 800Mhz L2 running @ 400Mhz
SysClock = 200Mhz , TClock = 166Mhz

DRAM CAS Latency = 3 tRP = 3 tRAS = 8 tRCD=3
DRAM CS[0] base 0x00000000 size 128MB
DRAM Total size 128MB 16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:128 MB
Flash: 0 kB

CPU : Marvell Feroceon (Rev 1)
CLOUD ENGINES BOARD: PPV4A1

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0 [PRIME]
Hit any key to stop autoboot: 0
Unknown command 'usb' - try 'help'

NAND read: device 0 offset 0x100000, size 0x73d0c
474380 bytes read: OK
## Starting application at 0x00800000 ...


U-Boot 1.1.4 (Jan 13 2012 - 22:33:21) Arch Linux ARM (PPV4 r1) PHYADDR=0

U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CFD60

Soc: 88F6192 A1 (DDR2)
CPU running @ 800Mhz L2 running @ 400Mhz
SysClock = 200Mhz , TClock = 166Mhz

DRAM CAS Latency = 3 tRP = 3 tRAS = 8 tRCD=3
DRAM CS[0] base 0x00000000 size 128MB
DRAM Total size 128MB 16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:128 MB
Flash: 0 kB

CPU : Marvell Feroceon (Rev 1)
CLOUD ENGINES BOARD: PPV4A1

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0 [PRIME]
Hit any key to stop autoboot: 0
(Re)start USB...
USB: scanning bus for devices... 2 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
T Device NOT ready
Request Sense returned 00 00 00
1 Storage Device(s) found

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found

Device NOT ready
Request Sense returned 00 00 00
** Can't read from device 0 **

** Unable to use usb 0:1 for fatls **

IDE device 0 not available
** Bad partition 1 **
ALARM>>
')
To fix all I have to do is this, which doesn't really seem to do anything:
$this->bbcode_second_pass_code('', '
root@raspbx:~# fsck /dev/sda1 -f
fsck from util-linux 2.20.1
e2fsck 1.42.5 (29-Jul-2012)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda1: 49500/480496 files (2.4% non-contiguous), 286343/1919644 blocks
root@raspbx:~#
')
Last edited by WarheadsSE on Wed May 28, 2014 1:23 pm, edited 1 time in total.
Reason: Use code tags.
skywiselh
 
Posts: 10
Joined: Tue May 06, 2014 1:00 am

Re: Pogoplug V4 won't restart after power-off

Postby grayman4hire » Wed May 28, 2014 12:46 am

Any difference if you used the "poweroff" command instead of "shutdown -h now"?

Also, is the partition formatted at ext2 or ext3. I believe you want to use ext3.
grayman4hire
 
Posts: 350
Joined: Sat Sep 29, 2012 12:03 am
Location: SF, CA


Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 11 guests