sata boot working, but not usb

[Robert Moskowitz]

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.

Here is the console capture:

U-Boot SPL 2015.01 (Feb 07 2015 - 22:09:40)
DRAM: 2048 MiB
CPU: 960000000Hz, AXI/AHB/APB: 3/2/2


U-Boot 2015.01 (Feb 07 2015 - 22:09:40) Allwinner Technology

CPU:   Allwinner A20 (SUN7I)
I2C:   ready
DRAM:  2 GiB
MMC:   SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

Reserved 8192kB of RAM for Framebuffer.
HDMI connected.
Setting up a 1024x768 console.
In:    serial
Out:   vga
Err:   vga
SCSI:  SUNXI SCSI INIT
SATA link 0 timeout.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part ccc apst
Net:   dwmac.1c50000
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 4 USB Device(s) found
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
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
** Invalid partition 1 **
** Invalid partition 1 **
** Invalid partition 1 **
** Invalid partition 1 **
** Invalid partition 1 **
** Invalid partition 1 **
** Invalid partition 1 **
** Invalid partition 1 **
scanning bus for devices...
Found 0 device(s).

SCSI device 0:
     Device 0: not available
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 4 USB Device(s) found
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

USB device 0: unknown device
dwmac.1c50000 Waiting for PHY auto negotiation to complete.... done
Speed: 100, full duplex
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
DHCP client bound to address 192.168.96.63 (4004 ms)
*** Warning: no boot file name; using 'C0A8603F.img'
Using dwmac.1c50000 device
TFTP from server 0.0.0.0; our IP address is 192.168.96.63; sending 
through gateway 192.168.96.1

================================

And it goes on from there trying to find a BOOTP image.

Note it did not recognize the USB drive.

[Hans de Goede]

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.
>
>  Here is the console capture:
>
>  U-Boot SPL 2015.01 (Feb 07 2015 - 22:09:40)
>  DRAM: 2048 MiB
>  CPU: 960000000Hz, AXI/AHB/APB: 3/2/2
>
>
>  U-Boot 2015.01 (Feb 07 2015 - 22:09:40) Allwinner Technology
>
>  CPU:   Allwinner A20 (SUN7I)
>  I2C:   ready
>  DRAM:  2 GiB
>  MMC:   SUNXI SD/MMC: 0
>  *** Warning - bad CRC, using default environment
>
>  Reserved 8192kB of RAM for Framebuffer.
>  HDMI connected.
>  Setting up a 1024x768 console.
>  In:    serial
>  Out:   vga
>  Err:   vga
>  SCSI:  SUNXI SCSI INIT
>  SATA link 0 timeout.
>  AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
>  flags: ncq stag pm led clo only pmp pio slum part ccc apst
>  Net:   dwmac.1c50000
>  (Re)start USB...
>  USB0:   USB EHCI 1.00
>  scanning bus 0 for devices... 4 USB Device(s) found
>  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.

Regards,

Habs

[Robert Moskowitz]

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.
> >
> > Here is the console capture:
> >
> > U-Boot SPL 2015.01 (Feb 07 2015 - 22:09:40)
> > DRAM: 2048 MiB
> > CPU: 960000000Hz, AXI/AHB/APB: 3/2/2
> >
> >
> > U-Boot 2015.01 (Feb 07 2015 - 22:09:40) Allwinner Technology
> >
> > CPU:   Allwinner A20 (SUN7I)
> > I2C:   ready
> > DRAM:  2 GiB
> > MMC:   SUNXI SD/MMC: 0
> > *** Warning - bad CRC, using default environment
> >
> > Reserved 8192kB of RAM for Framebuffer.
> > HDMI connected.
> > Setting up a 1024x768 console.
> > In:    serial
> > Out:   vga
> > Err:   vga
> > SCSI:  SUNXI SCSI INIT
> > SATA link 0 timeout.
> > AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
> > flags: ncq stag pm led clo only pmp pio slum part ccc apst
> > Net:   dwmac.1c50000
> > (Re)start USB...
> > USB0:   USB EHCI 1.00
> > scanning bus 0 for devices... 4 USB Device(s) found
> > 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.

U-Boot SPL 2015.01 (Feb 07 2015 - 22:09:40)
DRAM: 2048 MiB
CPU: 960000000Hz, AXI/AHB/APB: 3/2/2


U-Boot 2015.01 (Feb 07 2015 - 22:09:40) Allwinner Technology

CPU:   Allwinner A20 (SUN7I)
I2C:   ready
DRAM:  2 GiB
MMC:   SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

Reserved 8192kB of RAM for Framebuffer.
HDMI connected.
Setting up a 1024x768 console.
In:    serial
Out:   vga
Err:   vga
SCSI:  SUNXI SCSI INIT
SATA link 0 timeout.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part ccc apst
Net:   dwmac.1c50000
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 4 USB Device(s) found
USB1:   USB EHCI 1.00
scanning bus 1 for devices... 2 USB Device(s) found
        scanning usb for storage devices... 1 Storage Device(s) found
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
** Invalid partition 1 **
** Invalid partition 1 **
** Invalid partition 1 **
** Invalid partition 1 **
** Invalid partition 1 **
** Invalid partition 1 **
** Invalid partition 1 **
** Invalid partition 1 **
scanning bus for devices...
Found 0 device(s).

SCSI device 0:
     Device 0: not available
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 4 USB Device(s) found
USB1:   USB EHCI 1.00
scanning bus 1 for devices... 2 USB Device(s) found
        scanning usb for storage devices... 1 Storage Device(s) found

USB device 0:
     Device 0: Vendor: HITACHI_ Rev: 00J0 Prod: DK23DA-40
             Type: Hard Disk
             Capacity: 38154.3 MB = 37.2 GB (78140160 x 512)
... is now current device
Scanning usb 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
551 bytes read in 120 ms (3.9 KiB/s)
Ignoring unknown command: ui
Ignoring malformed menu command:  autoboot
Ignoring malformed menu command:  hidden
Ignoring unknown command: totaltimeout
Fedora-Xfce-armhfp-22-20150227 Boot Options.
1:    Fedora-Xfce-armhfp-22-20150227 (4.0.0-0.rc1.git0.1.fc22.armv7hl)
Enter choice: 1:    Fedora-Xfce-armhfp-22-20150227 
(4.0.0-0.rc1.git0.1.fc22.armv7hl)
Retrieving file: /initramfs-4.0.0-0.rc1.git0.1.fc22.armv7hl.img
40284030 bytes read in 1963 ms (19.6 MiB/s)
Retrieving file: /vmlinuz-4.0.0-0.rc1.git0.1.fc22.armv7hl
5636640 bytes read in 480 ms (11.2 MiB/s)
no console=
append: ro root=UUID=77c64937-ac75-40ed-9607-e781e24b4686 
console=ttyS0,115200
Retrieving file: 
/dtb-4.0.0-0.rc1.git0.1.fc22.armv7hl/sun7i-a20-cubietruck.dtb
26296 bytes read in 1521 ms (16.6 KiB/s)
Kernel image @ 0x42000000 [ 0x000000 - 0x560220 ]
## Flattened Device Tree blob at 43000000
    Booting using the fdt blob at 0x43000000
    Loading Ramdisk to 4d995000, end 4fffff7e ... OK
    Loading Device Tree to 4d98b000, end 4d9946b7 ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.0.0-0.rc1.git0.1.fc22.armv7hl 
(mockbuild(a)arm02-builder02.arm.fedoraproject.org) (gcc version 5.0.0 
20150217 (Red Hat 5.0.0-0.15)
(GCC) ) #1 SMP Mon Feb 23 22:31:16 UTC 2015
[    0.000000] CPU: ARMv7 Processor [410fc074] revision 4 (ARMv7), 
cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing 
instructio
n cache
[    0.000000] Machine model: Cubietech Cubietruck
[    0.000000] cma: Reserved 16 MiB at 0xbe800000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: Using PSCI v0.1 Function IDs from DT
[    0.000000] PERCPU: Embedded 12 pages/cpu @ee5d4000 s17920 r8192 
d23040 u4915
2
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  
Total pag
es: 520530
[    0.000000] Kernel command line: ro 
root=UUID=77c64937-ac75-40ed-9607-e781e24
b4686  console=ttyS0,115200
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 
bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 
bytes)
[    0.000000] Memory: 2000776K/2088960K available (7021K kernel code, 
892K rwda
ta, 3328K rodata, 952K init, 829K bss, 71800K reserved, 16384K 
cma-reserved, 129
4336K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)

....

[  OK  ] Started udev Kernel Device Manager.
[    7.054410] audit: type=1130 audit(7.035:9): pid=1 uid=0 
auid=4294967295 ses=
4294967295 subj=kernel msg='unit=systemd-udevd comm="systemd" 
exe="/usr/lib/syst
emd/systemd" hostname=? addr=? terminal=? res=success'
          Starting dracut pre-trigger hook...
[  OK  ] Started dracut pre-trigger hook.
[    7.709413] audit: type=1130 audit(7.690:10): pid=1 uid=0 
auid=4294967295 ses
=4294967295 subj=kernel msg='unit=dracut-pre-trigger comm="systemd" 
exe="/usr/li
b/systemd/systemd" hostname=? addr=? terminal=? res=success'
          Starting udev Coldplug all Devices...
[  OK  ] Started udev Coldplug all Devices.
          Starting dracut initqueue hook...
          Starting Show Plymouth Boot Screen...
[  OK  ] Reached target System Initialization.
[    8.254546] ehci-platform: EHCI generic platform driver
[    8.269968] platform 1c14000.usb: Driver ehci-platform requests probe 
deferra
l
[    8.284503] ohci-platform: OHCI generic platform driver
[    8.299176] platform 1c1c000.usb: Driver ehci-platform requests probe 
deferra
l
[    8.316354] sunxi-rtc 1c20d00.rtc: rtc core: registered rtc-sunxi as rtc0
[    8.323288] sunxi-rtc 1c20d00.rtc: RTC enabled
[    8.330500] platform cpufreq-dt: Driver cpufreq-dt requests probe 
deferral
[    8.338251] platform 1c14000.usb: Driver ehci-platform requests probe 
deferra
l
[    8.341433] pps_core: LinuxPPS API ver. 1 registered
[    8.341438] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 
Rodolfo Giome
tti <giometti(a)linux.it&gt;
[    8.342797] PTP clock support registered
[    8.368753] platform 1c1c000.usb: Driver ehci-platform requests probe 
deferra
l
[    8.368939] ahci-sunxi 1c18000.sata: controller can't do PMP, turning 
off CAP
_PMP
[    8.368950] ahci-sunxi 1c18000.sata: forcing PORTS_IMPL to 0x1
[    8.369026] ahci-sunxi 1c18000.sata: AHCI 0001.0100 32 slots 1 ports 
3 Gbps 0
x1 impl platform mode
[    8.369038] ahci-sunxi 1c18000.sata: flags: ncq sntf pm led clo only 
pio slum
  part ccc
[    8.407070] platform cpufreq-dt: Driver cpufreq-dt requests probe 
deferral
[    8.411925] scsi host0: ahci-sunxi
[    8.412462] ata1: SATA max UDMA/133 mmio [mem 0x01c18000-0x01c18fff] 
port 0x1
00 irq 30
[    8.425994] sunxi-mmc 1c0f000.mmc: No vqmmc regulator found
[    8.440890] platform 1c14000.usb: Driver ehci-platform requests probe 
deferra
l
[    8.450689] platform 1c1c000.usb: Driver ehci-platform requests probe 
deferra
l
[    8.458498] sunxi-mmc 1c0f000.mmc: Got CD GPIO
[    8.465638] platform cpufreq-dt: Driver cpufreq-dt requests probe 
deferral
[    8.499157] sunxi-mmc 1c0f000.mmc: base:0xf0248000 irq:26
[    8.506908] platform 1c14400.usb: Driver ohci-platform requests probe 
deferra
l
[    8.509635] platform 1c14000.usb: Driver ehci-platform requests probe 
deferra
l
[    8.510170] platform 1c1c000.usb: Driver ehci-platform requests probe 
deferra
l
[    8.510358] platform cpufreq-dt: Driver cpufreq-dt requests probe 
deferral
[    8.546199] axp20x 0-0034: AXP20x variant AXP209 found
[    8.567762] axp20x 0-0034: AXP20X driver loaded
[    8.572381] mmc0: host does not support reading read-only switch, 
assuming wr
ite-enable
[    8.581173] mmc0: new high speed SDHC card at address e624
[    8.582596] stmmaceth 1c50000.ethernet: no regulator found
[    8.582667] stmmaceth 1c50000.ethernet: no reset control found
[    8.582672]  Ring mode enabled
[    8.582678]  No HW DMA feature register supported
[    8.582679]  Normal descriptors
[    8.582681]  TX Checksum insertion supported
[    8.584949] platform 1c14000.usb: Driver ehci-platform requests probe 
deferra
l
[    8.585511] platform 1c1c000.usb: Driver ehci-platform requests probe 
deferra
l
[    8.585704] platform cpufreq-dt: Driver cpufreq-dt requests probe 
deferral
[    8.586161] platform 1c14400.usb: Driver ohci-platform requests probe 
deferra
l
[    8.603978] platform 1c14000.usb: Driver ehci-platform requests probe 
deferra
l
[    8.604557] platform 1c1c000.usb: Driver ehci-platform requests probe 
deferra
l
[    8.604755] platform cpufreq-dt: Driver cpufreq-dt requests probe 
deferral
[    8.605226] platform 1c14400.usb: Driver ohci-platform requests probe 
deferra
l
[    8.614668] platform 1c14000.usb: Driver ehci-platform requests probe 
deferra
l
[    8.615221] platform 1c1c000.usb: Driver ehci-platform requests probe 
deferra
l
[    8.615418] platform cpufreq-dt: Driver cpufreq-dt requests probe 
deferral
[    8.615885] platform 1c14400.usb: Driver ohci-platform requests probe 
deferra
l
[    8.618146] libphy: stmmac: probed
[    8.618156] eth0: PHY ID 001cc915 at 0 IRQ POLL (stmmac-0:00) active
[    8.618161] eth0: PHY ID 001cc915 at 1 IRQ POLL (stmmac-0:01)
[    8.618730] platform 1c14000.usb: Driver ehci-platform requests probe 
deferra
l
[    8.619298] platform 1c1c000.usb: Driver ehci-platform requests probe 
deferra
l
[    8.619478] platform cpufreq-dt: Driver cpufreq-dt requests probe 
deferral
[    8.619930] platform 1c14400.usb: Driver ohci-platform requests probe 
deferra
l
[    8.620618] sunxi-mmc 1c12000.mmc: No vqmmc regulator found
[    8.658917] sunxi-mmc 1c12000.mmc: base:0xf0256000 irq:27
[    8.659698] platform 1c14000.usb: Driver ehci-platform requests probe 
deferra
l
[    8.660263] platform 1c1c000.usb: Driver ehci-platform requests probe 
deferra
l
[    8.660462] platform cpufreq-dt: Driver cpufreq-dt requests probe 
deferral
[    8.660928] platform 1c14400.usb: Driver ohci-platform requests probe 
deferra
l
[    8.664678] platform 1c1c400.usb: Driver ohci-platform requests probe 
deferra
l
[    8.666137] platform 1c14000.usb: Driver ehci-platform requests probe 
deferra
l
[    8.666685] platform 1c1c000.usb: Driver ehci-platform requests probe 
deferra
l
[    8.666878] platform cpufreq-dt: Driver cpufreq-dt requests probe 
deferral
[    8.667343] platform 1c14400.usb: Driver ohci-platform requests probe 
deferra
l
[    8.667793] platform 1c1c400.usb: Driver ohci-platform requests probe 
deferra
l
[    8.669084] platform 1c14000.usb: Driver ehci-platform requests probe 
deferra
l
[    8.669595] platform 1c1c000.usb: Driver ehci-platform requests probe 
deferra
l
[    8.669777] platform cpufreq-dt: Driver cpufreq-dt requests probe 
deferral
[    8.670223] platform 1c14400.usb: Driver ohci-platform requests probe 
deferra
l
[    8.670658] platform 1c1c400.usb: Driver ohci-platform requests probe 
deferra
l
[    8.758931] ata1: SATA link down (SStatus 0 SControl 300)
[    8.887179] Driver 'mmcblk' needs updating - please use bus_type methods
[    8.896770] sunxi-mmc 1c12000.mmc: smc 1 err, cmd 8, RTO !!
          Mounting Configuration File System...
[  OK  ] Mounted Configuration File System.
[    8.914764] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[[    8.930136] mmcblk0: mmc0:e624 SS08G 7.40 GiB
[    8.934984] audit_printk_skb: 3 callbacks suppressed
[    8.940066] audit: type=1130 audit(8.915:12): pid=1 uid=0 
auid=4294967295 ses
=4294967295 subj=kernel msg='unit=plymouth-start comm="systemd" 
exe="/usr/lib/sy
stemd/systemd" hostname=? addr=? terminal=? res=success'
[    8.940818]  mmcblk0:
[    8.942460] platform 1c14000.usb: Driver ehci-platform requests probe 
deferra
l
[    8.943011] platform 1c1c000.usb: Driver ehci-platform requests probe 
deferra
l
[    8.943209] platform cpufreq-dt: Driver cpufreq-dt requests probe 
deferral
[    8.943682] platform 1c14400.usb: Driver ohci-platform requests probe 
deferra
l
[    8.944508] platform 1c1c400.usb: Driver ohci-platform requests probe 
deferra
l
[    8.958223] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    8.963316] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    8.966145] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    8.982037] mmc1: new high speed SDIO card at address 0001
   OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Reached target Paths.
[  OK  ] Reached target Basic System.
[  213.813678] dracut-initqueue[352]: Warning: Could not boot.
          Mounting Configuration File System...
[  OK  ] Mounted Configuration File System.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Reached target Paths.
[  OK  ] Reached target Basic System.
[  213.813678] dracut-initqueue[352]: Warning: Could not boot.
[  213.858837] dracut-initqueue[352]: Warning: 
/dev/disk/by-uuid/77c64937-ac75-4
0ed-9607-e781e24b4686 does not exist
          Starting Dracut Emergency Shell...
[  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.

[Hans de Goede]

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.
> >>
> >> Here is the console capture:
> >>
> >> U-Boot SPL 2015.01 (Feb 07 2015 - 22:09:40)
> >> DRAM: 2048 MiB
> >> CPU: 960000000Hz, AXI/AHB/APB: 3/2/2
> >>
> >>
> >> U-Boot 2015.01 (Feb 07 2015 - 22:09:40) Allwinner Technology
> >>
> >> CPU:   Allwinner A20 (SUN7I)
> >> I2C:   ready
> >> DRAM:  2 GiB
> >> MMC:   SUNXI SD/MMC: 0
> >> *** Warning - bad CRC, using default environment
> >>
> >> Reserved 8192kB of RAM for Framebuffer.
> >> HDMI connected.
> >> Setting up a 1024x768 console.
> >> In:    serial
> >> Out:   vga
> >> Err:   vga
> >> SCSI:  SUNXI SCSI INIT
> >> SATA link 0 timeout.
> >> AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
> >> flags: ncq stag pm led clo only pmp pio slum part ccc apst
> >> Net:   dwmac.1c50000
> >> (Re)start USB...
> >> USB0:   USB EHCI 1.00
> >> scanning bus 0 for devices... 4 USB Device(s) found
> >> 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.
>
>  U-Boot SPL 2015.01 (Feb 07 2015 - 22:09:40)
>  DRAM: 2048 MiB
>  CPU: 960000000Hz, AXI/AHB/APB: 3/2/2
>
>
>  U-Boot 2015.01 (Feb 07 2015 - 22:09:40) Allwinner Technology
>
>  CPU:   Allwinner A20 (SUN7I)
>  I2C:   ready
>  DRAM:  2 GiB
>  MMC:   SUNXI SD/MMC: 0
>  *** Warning - bad CRC, using default environment
>
>  Reserved 8192kB of RAM for Framebuffer.
>  HDMI connected.
>  Setting up a 1024x768 console.
>  In:    serial
>  Out:   vga
>  Err:   vga
>  SCSI:  SUNXI SCSI INIT
>  SATA link 0 timeout.
>  AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
>  flags: ncq stag pm led clo only pmp pio slum part ccc apst
>  Net:   dwmac.1c50000
>  (Re)start USB...
>  USB0:   USB EHCI 1.00
>  scanning bus 0 for devices... 4 USB Device(s) found
>  USB1:   USB EHCI 1.00
>  scanning bus 1 for devices... 2 USB Device(s) found
>          scanning usb for storage devices... 1 Storage Device(s) found
>  Hit any key to stop autoboot:  0
>  switch to partitions #0, OK
>  mmc0 is current device
>  Scanning mmc 0:1...
>  ** Invalid partition 1 **
>  ** Invalid partition 1 **
>  ** Invalid partition 1 **
>  ** Invalid partition 1 **
>  ** Invalid partition 1 **
>  ** Invalid partition 1 **
>  ** Invalid partition 1 **
>  ** Invalid partition 1 **
>  scanning bus for devices...
>  Found 0 device(s).
>
>  SCSI device 0:
>       Device 0: not available
>  (Re)start USB...
>  USB0:   USB EHCI 1.00
>  scanning bus 0 for devices... 4 USB Device(s) found
>  USB1:   USB EHCI 1.00
>  scanning bus 1 for devices... 2 USB Device(s) found
>          scanning usb for storage devices... 1 Storage Device(s) found
>
>  USB device 0:
>       Device 0: Vendor: HITACHI_ Rev: 00J0 Prod: DK23DA-40
>               Type: Hard Disk
>               Capacity: 38154.3 MB = 37.2 GB (78140160 x 512)
>  ... is now current device
>  Scanning usb 0:1...
>  Found /extlinux/extlinux.conf
>  Retrieving file: /extlinux/extlinux.conf
>  551 bytes read in 120 ms (3.9 KiB/s)
>  Ignoring unknown command: ui
>  Ignoring malformed menu command:  autoboot
>  Ignoring malformed menu command:  hidden
>  Ignoring unknown command: totaltimeout
>  Fedora-Xfce-armhfp-22-20150227 Boot Options.
>  1:    Fedora-Xfce-armhfp-22-20150227 (4.0.0-0.rc1.git0.1.fc22.armv7hl)
>  Enter choice: 1:    Fedora-Xfce-armhfp-22-20150227 (4.0.0-0.rc1.git0.1.fc22.armv7hl)
>  Retrieving file: /initramfs-4.0.0-0.rc1.git0.1.fc22.armv7hl.img
>  40284030 bytes read in 1963 ms (19.6 MiB/s)
>  Retrieving file: /vmlinuz-4.0.0-0.rc1.git0.1.fc22.armv7hl
>  5636640 bytes read in 480 ms (11.2 MiB/s)
>  no console=
>  append: ro root=UUID=77c64937-ac75-40ed-9607-e781e24b4686 console=ttyS0,115200
>  Retrieving file: /dtb-4.0.0-0.rc1.git0.1.fc22.armv7hl/sun7i-a20-cubietruck.dtb
>  26296 bytes read in 1521 ms (16.6 KiB/s)
>  Kernel image @ 0x42000000 [ 0x000000 - 0x560220 ]
>  ## Flattened Device Tree blob at 43000000
>      Booting using the fdt blob at 0x43000000
>      Loading Ramdisk to 4d995000, end 4fffff7e ... OK
>      Loading Device Tree to 4d98b000, end 4d9946b7 ... OK
>
>  Starting kernel ...
>
>  [    0.000000] Booting Linux on physical CPU 0x0
>  [    0.000000] Initializing cgroup subsys cpuset
>  [    0.000000] Initializing cgroup subsys cpu
>  [    0.000000] Initializing cgroup subsys cpuacct
>  [    0.000000] Linux version 4.0.0-0.rc1.git0.1.fc22.armv7hl
> (mockbuild(a)arm02-builder02.arm.fedoraproject.org) (gcc version 5.0.0 20150217 (Red Hat
> 5.0.0-0.15)
>  (GCC) ) #1 SMP Mon Feb 23 22:31:16 UTC 2015
>  [    0.000000] CPU: ARMv7 Processor [410fc074] revision 4 (ARMv7), cr=10c5387d
>  [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instructio
>  n cache
>  [    0.000000] Machine model: Cubietech Cubietruck
>  [    0.000000] cma: Reserved 16 MiB at 0xbe800000
>  [    0.000000] Memory policy: Data cache writealloc
>  [    0.000000] psci: probing for conduit method from DT.
>  [    0.000000] psci: Using PSCI v0.1 Function IDs from DT
>  [    0.000000] PERCPU: Embedded 12 pages/cpu @ee5d4000 s17920 r8192 d23040 u4915
>  2
>  [    0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pag
>  es: 520530
>  [    0.000000] Kernel command line: ro root=UUID=77c64937-ac75-40ed-9607-e781e24
>  b4686  console=ttyS0,115200
>  [    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
>  [    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
>  [    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
>  [    0.000000] Memory: 2000776K/2088960K available (7021K kernel code, 892K rwda
>  ta, 3328K rodata, 952K init, 829K bss, 71800K reserved, 16384K cma-reserved, 129
>  4336K highmem)
>  [    0.000000] Virtual kernel memory layout:
>  [    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
>
>  ....
>
>  [  OK  ] Started udev Kernel Device Manager.
>  [    7.054410] audit: type=1130 audit(7.035:9): pid=1 uid=0 auid=4294967295 ses=
>  4294967295 subj=kernel msg='unit=systemd-udevd comm="systemd"
> exe="/usr/lib/syst
>  emd/systemd" hostname=? addr=? terminal=? res=success'
>            Starting dracut pre-trigger hook...
>  [  OK  ] Started dracut pre-trigger hook.
>  [    7.709413] audit: type=1130 audit(7.690:10): pid=1 uid=0 auid=4294967295 ses
>  =4294967295 subj=kernel msg='unit=dracut-pre-trigger comm="systemd"
> exe="/usr/li
>  b/systemd/systemd" hostname=? addr=? terminal=? res=success'
>            Starting udev Coldplug all Devices...
>  [  OK  ] Started udev Coldplug all Devices.
>            Starting dracut initqueue hook...
>            Starting Show Plymouth Boot Screen...
>  [  OK  ] Reached target System Initialization.
>  [    8.254546] ehci-platform: EHCI generic platform driver
>  [    8.269968] platform 1c14000.usb: Driver ehci-platform requests probe deferra
>  l
>  [    8.284503] ohci-platform: OHCI generic platform driver
>  [    8.299176] platform 1c1c000.usb: Driver ehci-platform requests probe deferra
>  l
>  [    8.316354] sunxi-rtc 1c20d00.rtc: rtc core: registered rtc-sunxi as rtc0
>  [    8.323288] sunxi-rtc 1c20d00.rtc: RTC enabled
>  [    8.330500] platform cpufreq-dt: Driver cpufreq-dt requests probe deferral
>  [    8.338251] platform 1c14000.usb: Driver ehci-platform requests probe deferra
>  l
>  [    8.341433] pps_core: LinuxPPS API ver. 1 registered
>  [    8.341438] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giome
>  tti <giometti(a)linux.it&gt;
>  [    8.342797] PTP clock support registered
>  [    8.368753] platform 1c1c000.usb: Driver ehci-platform requests probe deferra
>  l
>  [    8.368939] ahci-sunxi 1c18000.sata: controller can't do PMP, turning off CAP
>  _PMP
>  [    8.368950] ahci-sunxi 1c18000.sata: forcing PORTS_IMPL to 0x1
>  [    8.369026] ahci-sunxi 1c18000.sata: AHCI 0001.0100 32 slots 1 ports 3 Gbps 0
>  x1 impl platform mode
>  [    8.369038] ahci-sunxi 1c18000.sata: flags: ncq sntf pm led clo only pio slum
>    part ccc
>  [    8.407070] platform cpufreq-dt: Driver cpufreq-dt requests probe deferral
>  [    8.411925] scsi host0: ahci-sunxi
>  [    8.412462] ata1: SATA max UDMA/133 mmio [mem 0x01c18000-0x01c18fff] port 0x1
>  00 irq 30
>  [    8.425994] sunxi-mmc 1c0f000.mmc: No vqmmc regulator found
>  [    8.440890] platform 1c14000.usb: Driver ehci-platform requests probe deferra
>  l
>  [    8.450689] platform 1c1c000.usb: Driver ehci-platform requests probe deferra
>  l
>  [    8.458498] sunxi-mmc 1c0f000.mmc: Got CD GPIO
>  [    8.465638] platform cpufreq-dt: Driver cpufreq-dt requests probe deferral
>  [    8.499157] sunxi-mmc 1c0f000.mmc: base:0xf0248000 irq:26
>  [    8.506908] platform 1c14400.usb: Driver ohci-platform requests probe deferra
>  l
>  [    8.509635] platform 1c14000.usb: Driver ehci-platform requests probe deferra
>  l
>  [    8.510170] platform 1c1c000.usb: Driver ehci-platform requests probe deferra
>  l
>  [    8.510358] platform cpufreq-dt: Driver cpufreq-dt requests probe deferral
>  [    8.546199] axp20x 0-0034: AXP20x variant AXP209 found
>  [    8.567762] axp20x 0-0034: AXP20X driver loaded
>  [    8.572381] mmc0: host does not support reading read-only switch, assuming wr
>  ite-enable
>  [    8.581173] mmc0: new high speed SDHC card at address e624
>  [    8.582596] stmmaceth 1c50000.ethernet: no regulator found
>  [    8.582667] stmmaceth 1c50000.ethernet: no reset control found
>  [    8.582672]  Ring mode enabled
>  [    8.582678]  No HW DMA feature register supported
>  [    8.582679]  Normal descriptors
>  [    8.582681]  TX Checksum insertion supported
>  [    8.584949] platform 1c14000.usb: Driver ehci-platform requests probe deferra
>  l
>  [    8.585511] platform 1c1c000.usb: Driver ehci-platform requests probe deferra
>  l
>  [    8.585704] platform cpufreq-dt: Driver cpufreq-dt requests probe deferral
>  [    8.586161] platform 1c14400.usb: Driver ohci-platform requests probe deferra
>  l
>  [    8.603978] platform 1c14000.usb: Driver ehci-platform requests probe deferra
>  l
>  [    8.604557] platform 1c1c000.usb: Driver ehci-platform requests probe deferra
>  l
>  [    8.604755] platform cpufreq-dt: Driver cpufreq-dt requests probe deferral
>  [    8.605226] platform 1c14400.usb: Driver ohci-platform requests probe deferra
>  l
>  [    8.614668] platform 1c14000.usb: Driver ehci-platform requests probe deferra
>  l
>  [    8.615221] platform 1c1c000.usb: Driver ehci-platform requests probe deferra
>  l
>  [    8.615418] platform cpufreq-dt: Driver cpufreq-dt requests probe deferral
>  [    8.615885] platform 1c14400.usb: Driver ohci-platform requests probe deferra
>  l
>  [    8.618146] libphy: stmmac: probed
>  [    8.618156] eth0: PHY ID 001cc915 at 0 IRQ POLL (stmmac-0:00) active
>  [    8.618161] eth0: PHY ID 001cc915 at 1 IRQ POLL (stmmac-0:01)
>  [    8.618730] platform 1c14000.usb: Driver ehci-platform requests probe deferra
>  l
>  [    8.619298] platform 1c1c000.usb: Driver ehci-platform requests probe deferra
>  l
>  [    8.619478] platform cpufreq-dt: Driver cpufreq-dt requests probe deferral
>  [    8.619930] platform 1c14400.usb: Driver ohci-platform requests probe deferra
>  l
>  [    8.620618] sunxi-mmc 1c12000.mmc: No vqmmc regulator found
>  [    8.658917] sunxi-mmc 1c12000.mmc: base:0xf0256000 irq:27
>  [    8.659698] platform 1c14000.usb: Driver ehci-platform requests probe deferra
>  l
>  [    8.660263] platform 1c1c000.usb: Driver ehci-platform requests probe deferra
>  l
>  [    8.660462] platform cpufreq-dt: Driver cpufreq-dt requests probe deferral
>  [    8.660928] platform 1c14400.usb: Driver ohci-platform requests probe deferra
>  l
>  [    8.664678] platform 1c1c400.usb: Driver ohci-platform requests probe deferra
>  l
>  [    8.666137] platform 1c14000.usb: Driver ehci-platform requests probe deferra
>  l
>  [    8.666685] platform 1c1c000.usb: Driver ehci-platform requests probe deferra
>  l
>  [    8.666878] platform cpufreq-dt: Driver cpufreq-dt requests probe deferral
>  [    8.667343] platform 1c14400.usb: Driver ohci-platform requests probe deferra
>  l
>  [    8.667793] platform 1c1c400.usb: Driver ohci-platform requests probe deferra
>  l
>  [    8.669084] platform 1c14000.usb: Driver ehci-platform requests probe deferra
>  l
>  [    8.669595] platform 1c1c000.usb: Driver ehci-platform requests probe deferra
>  l
>  [    8.669777] platform cpufreq-dt: Driver cpufreq-dt requests probe deferral
>  [    8.670223] platform 1c14400.usb: Driver ohci-platform requests probe deferra
>  l
>  [    8.670658] platform 1c1c400.usb: Driver ohci-platform requests probe deferra
>  l
>  [    8.758931] ata1: SATA link down (SStatus 0 SControl 300)
>  [    8.887179] Driver 'mmcblk' needs updating - please use bus_type methods
>  [    8.896770] sunxi-mmc 1c12000.mmc: smc 1 err, cmd 8, RTO !!
>            Mounting Configuration File System...
>  [  OK  ] Mounted Configuration File System.
>  [    8.914764] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
>  [[    8.930136] mmcblk0: mmc0:e624 SS08G 7.40 GiB
>  [    8.934984] audit_printk_skb: 3 callbacks suppressed
>  [    8.940066] audit: type=1130 audit(8.915:12): pid=1 uid=0 auid=4294967295 ses
>  =4294967295 subj=kernel msg='unit=plymouth-start comm="systemd"
> exe="/usr/lib/sy
>  stemd/systemd" hostname=? addr=? terminal=? res=success'
>  [    8.940818]  mmcblk0:
>  [    8.942460] platform 1c14000.usb: Driver ehci-platform requests probe deferra
>  l
>  [    8.943011] platform 1c1c000.usb: Driver ehci-platform requests probe deferra
>  l
>  [    8.943209] platform cpufreq-dt: Driver cpufreq-dt requests probe deferral
>  [    8.943682] platform 1c14400.usb: Driver ohci-platform requests probe deferra
>  l
>  [    8.944508] platform 1c1c400.usb: Driver ohci-platform requests probe deferra
>  l
>  [    8.958223] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
>  [    8.963316] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
>  [    8.966145] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
>  [    8.982037] mmc1: new high speed SDIO card at address 0001
>     OK  ] Started Show Plymouth Boot Screen.
>  [  OK  ] Reached target Paths.
>  [  OK  ] Reached target Basic System.
>  [  213.813678] dracut-initqueue[352]: Warning: Could not boot.
>            Mounting Configuration File System...
>  [  OK  ] Mounted Configuration File System.
>  [  OK  ] Started Show Plymouth Boot Screen.
>  [  OK  ] Reached target Paths.
>  [  OK  ] Reached target Basic System.
>  [  213.813678] dracut-initqueue[352]: Warning: Could not boot.
>  [  213.858837] dracut-initqueue[352]: Warning: /dev/disk/by-uuid/77c64937-ac75-4
>  0ed-9607-e781e24b4686 does not exist
>            Starting Dracut Emergency Shell...
>  [  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.

Regards,

Hans

[Robert Moskowitz]

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.

[Robert Moskowitz]

On 03/02/2015 01:56 PM, Robert Moskowitz wrote:
>  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. 
Oh, the system is still up in its dracut prompt.  If there is anything I 
should look for at this time.

[Hans de Goede]

Hi,

On 02-03-15 19:56, Robert Moskowitz wrote:
>  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: 
you need ehci_platform and ohci_platform and phy_sun4i_usb and their deps. They are
already
on your system, you need to regenerate the initrd with them included.

Regards,

Hans

[Robert Moskowitz]

On 03/03/2015 02:04 AM, Hans de Goede wrote:
>  Hi,
>
>  On 02-03-15 19:56, Robert Moskowitz wrote:
> >
> > 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:
>
>  you need ehci_platform and ohci_platform and phy_sun4i_usb and their 
>  deps. They are already
>  on your system, you need to regenerate the initrd with them included. 
It seems this is a working senario for many boards, particularly once 
you get uboot to work in NAND.  Running off an SD card is fine, for a 
simple platform, but if Fedora-arm is going for the new 
desktop/notebook, better media than SD is needed, IMHO.  So, 
particularly with those boards that have USB 3.0, booting from a usb 
connected HDD/SSD seem to be a desired thing.

Thus I hope that a future build will have these as part of initrd, or 
there will be a simple way to add them.

thanks for all the support.