Dennis,
How do I rebuild the initrd? I can do this on my raspberryPI 2
running Fedora 26 if I know the procedure to do it?
In the mean time, I will try to do the modprobe. Would I do this
within the dracut shell when the system aborts?
Stewart
It does not look like the USB controllers module is present, I
have run fedora from a micro SD card in my tests. You could try
"modprobe usb-storage" and try get the USB modules loaded. From
another arm system you should be able to rebuild the initrd with
all the USB modules if needed.
Dennis
Dennis
On 22 August 2017 6:17:13 pm GMT-05:00,
Stewart Samuels <searider74@xxxxxxxxx> wrote:
Here is the output from cat
/proc/modules:
-----------------------------------------------------------------
dracut:/#
dracut:/# cat /proc/modules
hid_logitech_hidpp 24576 0 - Live 0xbf461000
xhci_plat_hcd 16384 0 - Live 0xbf44f000
dwc3 110592 0 - Live 0xbf407000
ulpi 16384 1 dwc3, Live 0xbf3f7000
udc_core 49152 1 dwc3, Live 0xbf3db000
phy_generic 16384 0 - Live 0xbf3c3000
hid_logitech_dj 20480 0 - Live 0xbf3a5000
clk_s2mps11 16384 1 - Live 0xbf39d000
s2mps11 49152 14 - Live 0xbf38d000
rtc_s5m 20480 0 - Live 0xbf383000
dwc3_exynos 16384 0 - Live 0xbf373000
phy_exynos_mipi_video 16384 0 - Live 0xbf36b000
phy_exynos_dp_video 16384 0 - Live 0xbf363000
pl330 28672 0 - Live 0xbf33f000
clk_exynos_audss 16384 0 - Live 0xbf301000
pwm_samsung 16384 0 - Live 0xbf24f000
i2c_exynos5 16384 0 - Live 0xbf247000
i2c_s3c2410 20480 0 - Live 0xbf23d000
dw_mmc_exynos 16384 0 - Live 0xbf235000
dw_mmc_pltfm 16384 1 dw_mmc_exynos, Live 0xbf1ff000
exynosdrm 167936 1 - Live 0xbf1c9000
dw_mmc 36864 2 dw_mmc_exynos,dw_mmc_pltfm, Live 0xbf1ba000
analogix_dp 32768 1 exynosdrm, Live 0xbf1ad000
mmc_core 135168 2 dw_mmc_exynos,dw_mmc, Live 0xbf17f000
ohci_exynos 16384 0 - Live 0xbf176000
phy_exynos_usb2 20480 2 - Live 0xbf16c000
drm_kms_helper 143360 2 exynosdrm,analogix_dp, Live 0xbf13a000
phy_exynos5_usbdrd 16384 4 - Live 0xbf132000
syscopyarea 16384 1 drm_kms_helper, Live 0xbf12b000
sysfillrect 16384 1 drm_kms_helper, Live 0xbf124000
sysimgblt 16384 1 drm_kms_helper, Live 0xbf11d000
ehci_exynos 16384 0 - Live 0xbf114000
fb_sys_fops 16384 1 drm_kms_helper, Live 0xbf10d000
drm 327680 4 exynosdrm,analogix_dp,drm_kms_helper, Live
0xbf0a2000
rtc_s3c 20480 0 - Live 0xbf098000
s5p_sss 16384 0 - Live 0xbf08f000
sunrpc 323584 1 - Live 0xbf022000
scsi_transport_iscsi 86016 1 - Live 0xbf000000
dracut:/#
-----------------------------------------------------------------
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@xxxxxxxxx>
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.
--
Sent from my Android device with K-9 Mail. Please excuse my
brevity.
|
