On 03/02/2015 01:32 PM, Hans de Goede wrote:
Hi,
On 02-03-15 14:36, Robert Moskowitz wrote:
>
> On 03/02/2015 03:09 AM, Hans de Goede wrote:
>> Hi,
>>
>> On 01-03-15 02:59, Robert Moskowitz wrote:
>>> When I first was testing the sata boot, I did not have the sata
>>> drive connected properly, and I watched the system also try to scan
>>> usb. So I thought, that maybe usb boot was also enabled. I powered
>>> down and did the sata test successfully.
>>>
>>> So this evening I put the partitions on an IDE drive connected via
>>> a USB adapter. The drive is rated at .5A, and works fine on my
>>> notebook. I plugged it into my Cubietruck and as you will see
>>> below, the partitions were found. The USB adapter was plugged into
>>> the top USB port, and a USB hub that has the keyboard and mouse
>>> were plugged into the lower USB port. I have a USB IDE enclosure
>>> that provides 1A (one of those with 2 USB male plugs, I can put the
>>> second into a USB powersupply) if you think the failure was power
>>> related. I really don't so won't try that test unless asked.
>>> Bottom line
>>> is those of us with a SATA port have sata boot. Those without will
>>> have to at least keep the /boot partition on the SD card to point
>>> to the USB drive.
>>>
>>> USB1: USB EHCI 1.00
>>> scanning bus 1 for devices... 1 USB Device(s) found
>>> scanning usb for storage devices... 0 Storage Device(s) found
>>
>> Note how u-boot says that it is not seeing any usb storage devices...
>>
>> My first hunch is that the drive is simply not getting enough power,
>> try with a usb "stick" type device, that should work.
>
> I put it in a powered USB/IDE enclousure and it started the boot, but
> then failed. I am including the beginning and ending of the serial
> console, which is 30K long, so I am not posting it to this list. If
> anyone wants the whole console capture, tell me where to send it.
>
> [ 214.026523] audit: type=1131 audit(214.005:13): pid=1 uid=0
> auid=4294967295 s
> es=4294967295 subj=kernel msg='unit=plymouth-start comm="systemd"
> exe="/usr/lib/
> systemd/systemd" hostname=? addr=? terminal=? res=success'
> Warning: /dev/disk/by-uuid/77c64937-ac75-40ed-9607-e781e24b4686 does
> not exist
>
> Generating "/run/initramfs/rdsosreport.txt"
>
>
> Entering emergency mode. Exit the shell to continue.
> Type "journalctl" to view system logs.
> You might want to save "/run/initramfs/rdsosreport.txt" to a USB
> stick or /boot
> after mounting them and attach it to a bug report.
>
>
> dracut:/#
>
> =================================
>
> I have also saved /run/initramfs/rdsosreport.txt if you want to see
> that.
>
>
>
This looks to me like your ramdisk / initrd does not contain the
necessary usb modules.
So what are the necessary usb modules and how do I get them? This USB
drive was built from:
Fedora-Xfce-armhfp-22-20150227-sda.raw.xz
The IDE drive was built using the installer script, slightly modified so
that it does not get uboot written to it. I am using a generic IDE USB
enclousure.
If I should use a newer build or a different device (within reason), I
will do the testing.