Cold booting into archlinux

Ask questions about Arch Linux ARM. Please search before making a new topic.

Cold booting into archlinux

Postby mores » Fri Aug 26, 2011 1:47 pm

There seems to be a common issue that a cold boot ( toggle power ) will boot into factory OS while a warm boot ( reboot ) will start archlinux just fine.

I have seen many different attempts to fix it:
- change bootcmd
- change usb_rootdelay
- try a different flash drive
- try a different port
- use a smaller working flash just for kernel
- in factoryOS check /etc/init.d/rcS
$this->bbcode_second_pass_code('', '
checkusb=`grep sda /proc/partitions`
if [ -n "$checkusb" ]; then
/sbin/reboot
fi
')

Has a consensus been reached on the correct way to fix the issue ?
Has a consensus been reached on what the real issue is ?

Have enough people had this problem that it deserves to get put on the FAQ ?
mores
 
Posts: 5
Joined: Fri Aug 26, 2011 1:31 pm

Re: Cold booting into archlinux

Postby slycat » Fri Aug 26, 2011 5:27 pm

Generally the problem stemmed from the amount of time it took to power on the drive that holds the rootfs. Or if other drives or devices are plugged in and seen first (thus loaded as /dev/sda) then the plug won't boot at all. My old drive would power on slower than the connection to my USB printer, so I would have to disconnect the printer first while in the reboot process and then reconnect/start CUPS/start Samba. Since changing drives I've had no issues. Changing the rootdelay was the solution of choice for a while (still is?). According to the devs for the pogos the best port is right above the ethernet port. Should all else fail having the drive connected to the internal sata (for pro only, if I'm not mistaken) is a sure thing. The code you posted could work, but if the timing of the power-up-state is just right, your plug will reboot forever :(

Which hardware/plug are you using that is causing issues?
Pogoplug Pro w/ Wireless User -> decomm.
Cubox-i4pro User
4TB eSATA HDD (8g/3700+ Sw/Storage)
Kodi / Transmission / Minidlna / Samba / Batch-audio-conversions / Lighttpd
------------------------------
Rollback Machine - Thanks to impatt
slycat
 
Posts: 169
Joined: Wed Feb 09, 2011 3:07 am
Location: Miami, FL

Re: Cold booting into archlinux

Postby mores » Fri Aug 26, 2011 7:12 pm

I am using a POGO-E02.
The only usb device currently plugged in is a brand new Toshiba 4GB TransMemory U2K USB Flash Drive.
It is plugged into the usb port directly above the ethernet port.

So far I have changed usb_rootdelay from 10 to 15.

My next step will try to increas usb_rootdelay to 20, if that does not work I will be configuring a netconsole so I will be able to see more detail.
mores
 
Posts: 5
Joined: Fri Aug 26, 2011 1:31 pm

Re: Cold booting into archlinux

Postby mores » Sat Aug 27, 2011 12:18 am

Increasing usb_rootdelay to 20 did not help. Here are the cold boot logs:
$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... Device NOT ready
Request Sense returned 00 00 00
1 Storage Device(s) found
** Bad partition 1 **
Device NOT ready
Request Sense returned 00 00 00
** Can't read from device 0 **

** Unable to use usb 0:1 for fatload **
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: 726
UBI: number of bad PEBs: 2
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: 715
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'!
** Bad partition 1 **
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Bad partition 1 **
** Bad partition 1 **
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.
### JFFS2 load complete: 524288 bytes loaded to 0x800000
## Starting application at 0x00800200 ...


')
mores
 
Posts: 5
Joined: Fri Aug 26, 2011 1:31 pm

Re: Cold booting into archlinux

Postby mores » Sat Aug 27, 2011 12:23 am

And here are the warm boot logs ( reboot )

$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... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
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: 726
UBI: number of bad PEBs: 2
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: 715
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'!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
2624664 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
** File not found /boot/uInitrd
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-2.6.39-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2624600 Bytes = 2.5 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

')
mores
 
Posts: 5
Joined: Fri Aug 26, 2011 1:31 pm

Re: Cold booting into archlinux

Postby mores » Sun Aug 28, 2011 11:34 am

My solution was to use a different flash drive.

warm boots only:
[ 6.507271] scsi 0:0:0:0: Direct-Access TOSHIBA TransMemory PMAP PQ: 0 ANSI: 0 CCS


cold and warm boot:
[ 6.914148] scsi 0:0:0:0: Direct-Access SanDisk Cruzer Blade 8.02 PQ: 0 ANSI: 0 CCS
mores
 
Posts: 5
Joined: Fri Aug 26, 2011 1:31 pm


Return to User Questions

Who is online

Users browsing this forum: No registered users and 2 guests