Problem rebooting into ALARM

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

Re: Problem rebooting into ALARM

Postby LavaChild » Thu Apr 19, 2012 2:27 pm

bootdelay was initially set to 3. I just tried changing it to 10 and did not see any difference. :(
LavaChild
 
Posts: 46
Joined: Wed Mar 21, 2012 12:39 pm

Re: Problem rebooting into ALARM

Postby LavaChild » Thu Apr 19, 2012 3:47 pm

I have set up netconsole. This is with everything stock, following the ALARM installation guide for the PogoPlug and with all UBoot environment variables set as default.

$this->bbcode_second_pass_code('', '
U-Boot 2010.09 (Oct 23 2010 - 11:51:16)
Marvell-PinkPogo 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... 0 Storage Device(s) found
** Block device usb 0 not supported

** Invalid boot device **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000008000000 : "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: 91 MiB
UBI: number of good PEBs: 727
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: 716
UBI: total number of reserved PEBs: 11
UBI: number of PEBs reserved for bad PEB handling: 7
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: ....... read_nand_cached: error reading nand off 0x13b2a00 s
ize 8192 bytes
. done.
read_nand_cached: error reading nand off 0x13b1600 size 8192 bytes
off = 0x13b128c magic 0x1985 type 0xe002 node.totlen = 2431
### JFFS2 load complete: 524288 bytes loaded to 0x800000
## Starting application at 0x00800200 ...
')

Does this help?

Note, too, that the only device connected is the HDD. This is connected to the top-rear USB port. All others are not connected to anything.

Note two, this is with ALARM installed to /dev/sda1 (10G) and another blank ext2 partition /dev/sda2 using the remaining. I only did this because the drive is 100G and I read the ALARM partition must be <32G. I am not sure if this is relevant or not... I'm really quite out of my depth now! Just trying to hold on with the hope of fixing this! :)
LavaChild
 
Posts: 46
Joined: Wed Mar 21, 2012 12:39 pm

Re: Problem rebooting into ALARM

Postby WarheadsSE » Thu Apr 19, 2012 4:55 pm

There is your problem. "0 devices". The time between usb power being applied, and the HDD responding is too short. Hence why I didn't suggest bootdelay/rootdelay
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Problem rebooting into ALARM

Postby LavaChild » Thu Apr 19, 2012 5:03 pm

Why would this only be a problem on reboot but not on a cold boot? Is there any fix for this?

Thank you.
LavaChild
 
Posts: 46
Joined: Wed Mar 21, 2012 12:39 pm

Re: Problem rebooting into ALARM

Postby LavaChild » Fri Apr 20, 2012 5:29 am

Anybody, please? Now we've identified the problem I'm keen to find a solution! :)
LavaChild
 
Posts: 46
Joined: Wed Mar 21, 2012 12:39 pm

Re: Problem rebooting into ALARM

Postby WarheadsSE » Fri Apr 20, 2012 12:34 pm

let me make an analogy:
Which is easier: waking a man from a full nights sleep, or 10 minutes into sleeping after being awake for a day?

The drive may be cycling down, and get the notice to cycle up, thus not responding fast enough.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Problem rebooting into ALARM

Postby LavaChild » Fri Apr 20, 2012 12:48 pm

Okay, I appreciate why the behaviour may differ between a coldboot and reboot. Are you aware of any fix to this problem?
LavaChild
 
Posts: 46
Joined: Wed Mar 21, 2012 12:39 pm

Re: Problem rebooting into ALARM

Postby WarheadsSE » Fri Apr 20, 2012 1:19 pm

Attempt doubling the usb reset command
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Problem rebooting into ALARM

Postby LavaChild » Fri Apr 20, 2012 1:31 pm

I'm not sure I understand - 'usb reset command'?

Are you referring to the adding 'usb start; usb stop' to the start of 'bootcmd'? If so, I've tried this and it is did not work. I have also tried increasing 'usb_rootdelay' from 10 to 15 (and, separately, 30) and that did not work. Neither did increasing 'bootdelay' from 3 to 10. (Note all of these were changed one at a time only).

Is the 'usb reset command' a different UBoot variable? Thank you!
LavaChild
 
Posts: 46
Joined: Wed Mar 21, 2012 12:39 pm

Re: Problem rebooting into ALARM

Postby WarheadsSE » Fri Apr 20, 2012 3:01 pm

Interrupt uboot.

`help usb`
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

PreviousNext

Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 15 guests