Can't boot my pink plug

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

Can't boot my pink plug

Postby ryborg » Thu Jun 09, 2011 2:41 am

I was a happy (and productive) Arch Linux ARM user until late last night when we lost our power. Today I just can't get the USB drive to boot. It was working just fine. It is formatted ext2. I have tried all of the fw_setenv commands including the bootcmd string to help boot with USB drives.
Unsure of a dirty unmount, I also scanned and repaired with ex2fsck. I have no problem mounting the drive and accessing the files. I just can't boot from the USB drive! Also tried reinstall uboot, and even recopying the Arch Linux ARM linux tar to the usb drive again. Just about the only thing I haven't tried is backup, reformat, redo everything.

Here is my dmesg:
$this->bbcode_second_pass_code('', '[ 0.980000] o Driver INFO statistics enabled
[ 0.980000] o Proc tool API enabled
[ 0.990000] o Rx descripors: q0=128
[ 0.990000] o Tx descripors: q0=532
[ 0.990000] o Loading network interface(s):
[ 1.000000] o eth0, ifindex = 1, GbE port = 0
[ 1.010000] o eth1, ifindex = 2, GbE port = 1
[ 1.010000]
[ 1.010000] mvFpRuleDb (cf8c2000): 2048 entries, 8192 bytes
[ 1.020000] Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
[ 1.030000] Copyright (c) 1999-2006 Intel Corporation.
[ 1.030000] e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
[ 1.040000] e100: Copyright(c) 1999-2006 Intel Corporation
[ 1.040000]
[ 1.040000] Warning Sata is Powered Off
[ 1.050000] NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
[ 1.060000] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)
[ 1.070000] Scanning device for bad blocks
[ 1.120000] Bad eraseblock 949 at 0x076a0000
[ 1.120000] Using static partition definition
[ 1.130000] Creating 4 MTD partitions on "nand_mtd":
[ 1.130000] 0x00000000-0x00100000 : "u-boot"
[ 1.140000] 0x00100000-0x00500000 : "uImage"
[ 1.140000] 0x00500000-0x02500000 : "root"
[ 1.150000] 0x02500000-0x08000000 : "data"
[ 1.150000] ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
[ 1.160000] ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
[ 1.200000] ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
[ 1.220000] ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[ 1.220000] usb usb1: configuration #1 chosen from 1 choice
[ 1.230000] hub 1-0:1.0: USB hub found
[ 1.230000] hub 1-0:1.0: 1 port detected
[ 1.350000] ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
[ 1.350000] USB Universal Host Controller Interface driver v3.0
[ 1.630000] usb 1-1: new high speed USB device using ehci_marvell and address 2
[ 1.780000] usb 1-1: configuration #1 chosen from 1 choice
[ 1.780000] hub 1-1:1.0: USB hub found
[ 1.790000] hub 1-1:1.0: 4 ports detected
[ 2.140000] usb 1-1.1: new high speed USB device using ehci_marvell and address 3
[ 2.310000] usb 1-1.1: configuration #1 chosen from 1 choice
[ 2.310000] usbcore: registered new interface driver usblp
[ 2.320000] drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
[ 2.330000] Initializing USB Mass Storage driver...
[ 2.330000] scsi0 : SCSI emulation for USB Mass Storage devices
[ 2.340000] usbcore: registered new interface driver usb-storage
[ 2.340000] USB Mass Storage support registered.
[ 2.350000] usb-storage: device found at 3
[ 2.350000] usb-storage: waiting for device to settle before scanning
[ 2.350000] mice: PS/2 mouse device common for all mice
[ 2.350000] i2c /dev entries driver
[ 2.360000] Linux telephony interface: v1.00
[ 2.360000] md: linear personality registered for level -1
[ 2.370000] md: raid0 personality registered for level 0
[ 2.370000] md: raid1 personality registered for level 1
[ 2.550000] raid6: int32x1 97 MB/s
[ 2.720000] raid6: int32x2 114 MB/s
[ 2.890000] raid6: int32x4 122 MB/s
[ 3.060000] raid6: int32x8 110 MB/s
[ 3.060000] raid6: using algorithm int32x4 (122 MB/s)
[ 3.060000] md: raid6 personality registered for level 6
[ 3.070000] md: raid5 personality registered for level 5
[ 3.070000] md: raid4 personality registered for level 4
[ 3.080000] raid5: measuring checksumming speed
[ 3.130000] arm4regs : 1084.000 MB/sec
[ 3.180000] 8regs : 754.800 MB/sec
[ 3.230000] 32regs : 899.600 MB/sec
[ 3.230000] raid5: using function: arm4regs (1084.000 MB/sec)
[ 3.240000] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
[ 3.240000] dm_crypt using the OCF package.
[ 3.250000] sdhci: Secure Digital Host Controller Interface driver
[ 3.250000] sdhci: Copyright(c) Pierre Ossman
[ 3.260000] usbcore: registered new interface driver usbhid
[ 3.260000] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
[ 3.270000] TCP cubic registered
[ 3.270000] NET: Registered protocol family 1
[ 3.280000] NET: Registered protocol family 17
[ 3.280000] md: Autodetecting RAID arrays.
[ 3.290000] md: autorun ...
[ 3.290000] md: ... autorun DONE.
[ 4.880000] Empty flash at 0x009ac208 ends at 0x009ac800
[ 8.400000] VFS: Mounted root (jffs2 filesystem) readonly.
[ 8.400000] Freeing init memory: 120K
[ 8.420000] scsi 0:0:0:0: Direct-Access Fantom Extemal HDD ML6O PQ: 0 ANSI: 5
[ 8.460000] sd 0:0:0:0: [sda] 3907029168 512-byte hardware sectors (2000399 MB)
[ 8.480000] sd 0:0:0:0: [sda] Write Protect is off
[ 8.480000] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[ 8.480000] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 8.510000] sd 0:0:0:0: [sda] 3907029168 512-byte hardware sectors (2000399 MB)
[ 8.530000] sd 0:0:0:0: [sda] Write Protect is off
[ 8.530000] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[ 8.530000] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 8.540000] sda:<5>eth0: link down
[ 10.590000] eth0: started
[ 12.490000] eth0: link up, full duplex, speed 100 Mbps
[ 17.920000] sda1
[ 17.930000] sd 0:0:0:0: [sda] Attached SCSI disk
[ 17.930000] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 17.940000] usb-storage: device scan complete
')

ANY help would be appreciated
ryborg
 
Posts: 1
Joined: Thu Jun 09, 2011 2:36 am

Re: Can't boot my pink plug

Postby kmihelich » Thu Jun 09, 2011 3:44 am

It appears to be mounting NAND as root:
$this->bbcode_second_pass_quote('', '[') 8.400000] VFS: Mounted root (jffs2 filesystem) readonly.


Serial or netconsole output of the bootloader would be helpful in diagnosing the issue. In general, a format/re-extract typically works fine when a fsck doesn't fix issues. You might also try a different drive.. when things can't be explained, 99% of the time it's the flash drive failing. All problems disappear using a USB hard drive.
Arch Linux ARM exists and continues to grow through community support, please donate today!
kmihelich
Developer
 
Posts: 1133
Joined: Tue Jul 20, 2010 6:55 am
Location: aka leming #archlinuxarm


Return to User Questions

Who is online

Users browsing this forum: No registered users and 10 guests