cat /proc/partitions in dracut returns no output other than the dracut prompt.  An ls -l command shows listing output:  See the following:

---------------------------------------------------------------------
dracut:/# pwd
/
dracut:/# cat /proc/partitions
dracut:/# ls -l
total 12
lrwxrwxrwx   1 root root    7 Jun 22 13:42 bin -> usr/bin
drwxr-xr-x  13 root root 3900 Jun 27 21:45 dev
-rw-r--r--   1 root root  508 Jun 27 21:45 dracut-state.sh
-rw-r--r--   1 root root    2 Jun 22 13:42 early_cpio
drwxr-xr-x  11 root root    0 Jun 27 21:48 etc
lrwxrwxrwx   1 root root   23 Jun 22 13:42 init -> usr/lib/systemd/systemd
drwxr-xr-x   3 root root    0 Jun 22 13:42 kernel
lrwxrwxrwx   1 root root    7 Jun 22 13:42 lib -> usr/lib
dr-xr-xr-x 125 root root    0 Jan  1  1970 proc
drwxr-xr-x   2 root root    0 Jun 22 13:42 root
drwxr-xr-x  11 root root  260 Jun 27 21:45 run
lrwxrwxrwx   1 root root    8 Jun 22 13:42 sbin -> usr/sbin
-rwxr-xr-x   1 root root 3113 Jun 22 13:41 shutdown
dr-xr-xr-x  12 root root    0 Jan  1  1970 sys
drwxr-xr-x   2 root root    0 Jun 22 13:42 sysroot
drwxr-xr-x   2 root root    0 Jun 22 13:42 tmp
drwxr-xr-x   6 root root    0 Jun 22 13:42 usr
drwxr-xr-x   4 root root    0 Jun 27 21:45 var
dracut:/#


---------------------------------------------------------------------

On 08/22/2017 04:06 PM, dennis@ausil.us wrote:
What is the output of "cat /proc/partitions" next step would be making sure the right modules for the block storage are loaded.

Dennis

On 22 August 2017 6:03:52 pm GMT-05:00, Stewart Samuels <searider74@gmail.com> wrote:
Dennis,

I let the system try to boot and gave it more time with the dracut 
messages.  It dumps me into the dracut login via emergency mode looking 
for the root partition it seems.  It cannot find the system drive via 
the UUID that I showed in my last email is the UUID for the root 
partition.  See the output on my serial console now.  What do you suggest?

Stewart


. . . [ 221.513878] dracut-initqueue[484]: Warning: dracut-initqueue timeout - starting timeout scripts [ 222.098261] dracut-initqueue[484]: Warning: dracut-initqueue timeout - starting timeout scripts [ 222.681174] dracut-initqueue[484]: Warning: dracut-initqueue timeout - starting timeout scripts [ 222.683247] dracut-initqueue[484]: Warning: Could not boot. [ 224.157646] dracut-initqueue[484]: Warning: /dev/disk/by-uuid/11cf09b5-43b2-4588-969d-550b4e2af055 does not exist Starting Setup Virtual Console... [ OK 224.359135] audit: type=1130 audit(1498600128.720:15): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit' m] Started Setup Virtual Console[ 224.384023] audit: type=1131 audit(1498600128.720:16): pid=1 uid=0 auid=4294967295 ses=429496' . Starting Dracut Emergency Shell... [ 224.501053] audit: type=1131 audit(1498600128.862:17): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=plymo' Warning: /dev/disk/by-uuid/11cf09b5-43b2-4588-969d-550b4e2af055 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:/#
On 08/22/2017 03:46 PM, Stewart Samuels wrote:
Dennis, I have confirmed the UUID is still 11cf09b5-43b2-4588-969d-550b4e2af05. See output from my Ubuntu login that follows. Our root partition here shows up as /dev/sda4. Stewart
Ubuntu 16.04.2 LTS odroid ttySAC2 odroid login: Password: Login incorrect odroid login: odroid Password: Welcome to Ubuntu 16.04.2 LTS (GNU/Linux 4.9.27-35 armv7l) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support: https://ubuntu.com/advantage 131 packages can be updated. 1 update is a security update. The programs included with the Ubuntu system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. odroid@odroid:~$ blkid /dev/mmcblk1p1: SEC_TYPE="msdos" LABEL="boot" UUID="52AA-6867" TYPE="vfat" PARTUUID="3cedfd53-01" /dev/mmcblk1p2: LABEL="rootfs" UUID="e139ce78-9841-40fe-8823-96a304a09859" TYPE="ext4" PARTUUID="3cedfd53-02" /dev/sda1: UUID="1E1E-EBA6" TYPE="vfat" PARTUUID="3cedfd53-01" /dev/sda2: LABEL="_boot" UUID="9bef0c7b-ced7-453b-bb4f-5072d3810d44" TYPE="ext4" PARTUUID="3cedfd53-02" /dev/sda3: UUID="8753dccc-b774-4213-82fc-6941ced77673" TYPE="swap" PARTUUID="3cedfd53-03" /dev/sda4: LABEL="_root" UUID="11cf09b5-43b2-4588-969d-550b4e2af055" TYPE="ext4" PARTUUID="3cedfd53-04" odroid@odroid:~$
On 08/22/2017 03:18 PM, Dennis Gilmore wrote:
El mar, 22-08-2017 a las 15:14 -0700, Stewart Samuels escribió:
Hello Dennis, The parameter you provided me below was incorrect (spelling error). I used cpuidle.off=1 and the system now boot much further, but eventually goes into a:
dracut-initqueue[493]: Warning: dracut-initqueue timeout - starting timeout scripts
loop and never completes the boot process. Any other suggestions? See the output from the serial port that follows:
sorry for the typo I meant cpuidle.off=1 can you confirm that the uuid of the root filesystem is still 11cf09b5-43b2-4588-969d-550b4e2af055 and has not ben changed? Dennis

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.