First of all, thanks to Bodhi and others for such a wonderful, cool project. I have been loading the rootfs image with the 3.16 kernel on a few pogoplugs and dockstars and I am amazed how well they work.
For my latest project, I am placing two Dockstars inside an old NSS4000 case (1U Rackmount box). The motherboard was shot and I am just replacing the guts with two Dockstars.
In any case, I have a Dockstar with a USB stick in it and it boots up just fine. After I add one or two more SATA drives that uBoot cannot read (not formatted ext2) uBoot gives up and says "Error: Can't get Kernel Image"
It then resets and goes into a continual boot-loop.
It is almost as if the extra drive(s) that it cannot read are confusing it.
If I leave the SATA drives powered off until the exact point that I see the linux Kernel get read off of the USB stick and then flip the power switch... Everything comes up just fine.
I am under the impression that uBoot scans all drives installed on the usb bus and looks for a partition with the rootfs label. Is there a way to exclude certain drives from the search? (I am thinking that this might fix it).
Below is the output on the console. (I have a console attached to the serial port) As you can see, the rootfs label is found, but it does not load the kernel from the ext2 or ext3 partition (I have tried both).
Side Note: In case anybody is interested, two dockstars and 4 USB/SATA adapters fit just fine inside an empty case from an NSS4000.
For my latest project, I am placing two Dockstars inside an old NSS4000 case (1U Rackmount box). The motherboard was shot and I am just replacing the guts with two Dockstars.
In any case, I have a Dockstar with a USB stick in it and it boots up just fine. After I add one or two more SATA drives that uBoot cannot read (not formatted ext2) uBoot gives up and says "Error: Can't get Kernel Image"
It then resets and goes into a continual boot-loop.
It is almost as if the extra drive(s) that it cannot read are confusing it.
If I leave the SATA drives powered off until the exact point that I see the linux Kernel get read off of the USB stick and then flip the power switch... Everything comes up just fine.
I am under the impression that uBoot scans all drives installed on the usb bus and looks for a partition with the rootfs label. Is there a way to exclude certain drives from the search? (I am thinking that this might fix it).
Below is the output on the console. (I have a console attached to the serial port) As you can see, the rootfs label is found, but it does not load the kernel from the ext2 or ext3 partition (I have tried both).
Side Note: In case anybody is interested, two dockstars and 4 USB/SATA adapters fit just fine inside an empty case from an NSS4000.
scanning usb for storage devices... 3 Storage Device(s) found Unknown command 'mmc' - try 'help' Unknown command 'ide' - try 'help' Partition Map for USB device 0 -- Partition Type: EFI Part Start LBA End LBA Name Attributes Type GUID Partition GUID 1 0x00000800 0xe8e087ff "RAID" attrs: 0x0000000000000000 type: a19d880f-05fc-4d3b-a006-743f0f84911e guid: 660d0beb-df2d-43b3-b64d-d295d70ce387 Partition Map for USB device 1 -- Partition Type: EFI Part Start LBA End LBA Name Attributes Type GUID Partition GUID 1 0x00000800 0xe8e087ff "RAID" attrs: 0x0000000000000000 type: a19d880f-05fc-4d3b-a006-743f0f84911e guid: b538bdca-54c1-4ef3-9b84-ea42646c392f Partition Map for USB device 2 -- Partition Type: EFI Part Start LBA End LBA Name Attributes Type GUID Partition GUID 1 0x00000800 0x00e887ff "rootfs" attrs: 0x0000000000000000 type: 0fc63daf-8483-4772-8e79-3d69d8477de4 guid: 34226768-1ec1-4f97-8168-c6af0e19547d loading envs from usb 0 ... Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** Unknown command 'mmc' - try 'help' Unknown command 'ide' - try 'help' (Re)start USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 5 USB Device(s) found scanning usb for storage devices... 3 Storage Device(s) found Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** Wrong Image Format for bootm command ERROR: can't get kernel image! Unknown command 'mmc' - try 'help' ** Bad device mmc 0 ** ** Bad device mmc 0 ** Wrong Image Format for bootm command ERROR: can't get kernel image! Unknown command 'ide' - try 'help' ** Bad device ide 0 ** ** Bad device ide 0 ** Wrong Image Format for bootm command ERROR: can't get kernel image! resetting ...