PPV2 boots to alarm only on reboot

[Socaltom]

Brand new fresh install on a Pink V2. When I unplug it, it consistently boots to the pogoplug prompt, then I /sbin/reboot and the alarm system boots up. Only one drive attached.
It's been a while since I did a fresh install. Did I forget something?
Tom

[WarheadsSE]

This is a historical issue about cold boots. You can find many ways to address it.

[Socaltom]

$this->bbcode_second_pass_quote('WarheadsSE', 'T')his is a historical issue about cold boots. You can find many ways to address it.

[WarheadsSE]

Spin up time is even greater on spinning drives.

[grayman4hire]

@socialtom, try the below (cut/paste from my blog).

$this->bbcode_second_pass_quote('', '
')A cold/hard boot (disconnect/reconnect power cord) can behave differently than a warm boot (executing the 'reboot' command via the console). Yes, very strange. I've experienced where if I do a cold boot, the default Pogoplug OS will boot up and not ALARM. However, if I execute a reboot command from within the default Pogoplug OS, ALARM will boot up properly. I've also experienced the opposite, where ALARM will boot up properly from a cold boot, but if I execute a 'reboot' command via the console, ALARM will not boot properly. This all depends on your USB flash/hard drive. Try the following, it may help and typically it shouldn't hurt. I'm using the below bootcmd for two of my Pogoplugs with Western Digital My Passport drives.

#E02 - Only. Fix boot issue with some USB drives
#credit - viewtopic.php?f=18&t=1717&p=9527#p9527
#print default bootcmd value
fw_printenv bootcmd

#default bootcmd
#[root@pogoplug ~]# fw_printenv bootcmd

#bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; #run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; #reset

#update bootcmd value to start, stop and start usb again
#all one line
fw_setenv bootcmd "usb start; usb stop; usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset"

#confirm update
fw_printenv bootcmd

[bodhi]

@Tom,

I concur with WarheadsSE. It seems like a historical issue. To confirm, watch your neconsole/serial console, if you see "USB not ready" after a few tries, then that's it. Usually it's also preceded by a few "Time Out" errors. Mainline U-boot USB driver has 1 second time out, which is too short for certain USB HDDs.

[Socaltom]

$this->bbcode_second_pass_quote('bodhi', '@')Tom,

I concur with WarheadsSE. It seems like a historical issue. To confirm, watch your neconsole/serial console, if you see "USB not ready" after a few tries, then that's it. Usually it's also preceded by a few "Time Out" errors. Mainline U-boot USB driver has 1 second time out, which is too short for certain USB HDDs.