You can tell if uboot supports ext2 and if you have it plugged into the right port or which usb device name it is by running the ext2load 0:0 type of command from the uboot prompt. The syntax is in the help page for writing a new kernel. The ls command should return a directory listing of the boot partition if the device is correct. You may need to change the number to get the right one.
----- Reply message -----
From: "Robert Moskowitz" <rgm@xxxxxxxxxxxxxxx>
To: "Scott Sullivan" <scott@xxxxxx>, <arm@xxxxxxxxxxxxxxxxxxxxxxx>
Subject: [fedora-arm] Bad image/instructions? - Re: Problems with a pogoplug v02
Date: Thu, Apr 18, 2013 2:49 pm
Per:
fedoraproject.org/wiki/Architectures/ARM/F18/GuruPlug
I just downloaded the image again from:
http://dl.fedoraproject.org/pub/fedora-secondary/releases/18/Images/arm/Fedora-18-kirkwood-arm.img.xz
This time I took a 4Gb usb drive I got from MicroCenter that still had a
FAT partition. On my F18 notebook as root, I ran:
xzcat Fedora-18-kirkwood-arm.img.xz > /dev/sdc1
I removed the drive, put it in a different usb port, and my notebook
(which is running gnome on f18) would not open it in Nautilus. I kind
of assumed that this was suppose to be a readable partition. So I
brought up Disk Manager, and it showed the drive still having a MSDOS
FAT partition with unknown content. My previous attempt was with a 8Gb
usb drive that had a ext3 partition, and now still has that partition
with unknown content. Note below that the pogoplug boot things it is
seeing an ext2 partition on the drive.
So what now? Is the image bad? Is that the wrong command on F18 (note
that the nc options on http://forum.doozan.com/read.php?3,14,14 are
wrong for F18)? Is the image totally non-workable on the plug and I
should instead use the f17 image at:
http://fedoraproject.org/wiki/Architectures/ARM/Kirkwood#Writing_the_Image
?
Help?
On 04/18/2013 10:51 AM, Robert Moskowitz wrote:
> Bad USB drive, I built it with xzcat on a F18 notebook. See below
>
> On 04/17/2013 10:24 PM, Scott Sullivan wrote:
>> On 04/17/2013 09:11 PM, Robert Moskowitz wrote:
>>> Any advise on what to do next? I really think it has to do with which
>>> usb port I am using.
>>>
>>>
>>
>> So I do recall from back when the Pogoplug was new there were many
>> folks having issues with some USB drive just not being recognized
>> during uboot.
>>
>> Since it looks you got the new uboot installed, I would now try using
>> a netconsole to see if you can get any extra information about why
>> it's booting into the Pogoplug linux.
>>
>> http://forum.doozan.com/read.php?3,14,14
>>
>> This thread mentions the dockstar, which is just the same basic
>> hardware in a different configuration. Same principle applies.
>>
> U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
> Pogoplug E02
> arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
> GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
> 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)
> Failed to mount ext2 filesystem...
> ** Bad ext2 partition or disk - usb 0:1 **
> 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: 728
> UBI: number of bad PEBs: 0
> 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: 717
> 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 "uImage" from usb device 0:1 (usbda1)
> Failed to mount ext2 filesystem...
> ** Bad ext2 partition or disk - usb 0:1 **
> ** Block device usb 1 not supported
> ** Block device usb 2 not supported
> ** Block device usb 3 not supported
> Loading file "uImage" from usb device 0:1 (usbda1)
> Failed to mount ext2 filesystem...
> ** Bad ext2 partition or disk - usb 0:1 **
> Loading file "uInitrd" from usb device 0:1 (usbda1)
> Failed to mount ext2 filesystem...
> ** Bad ext2 partition or disk - usb 0: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 ...
>
>
> _______________________________________________
> arm mailing list
> arm@xxxxxxxxxxxxxxxxxxxxxxx
> https://admin.fedoraproject.org/mailman/listinfo/arm
_______________________________________________
arm mailing list
arm@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/arm
_______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
