Hello all.
I'm working on making a bootable USB, but booting isn't going well, to
say the least.
It boots when plugged into a computer, but during boot, mounting the
rootfs fails initially, because it takes that long to start up? or
something?
When the emergency shell starts, you can just exit, and it proceeds like
normal because the "missing volume" exists, just too late for timeout, I
guess.
However, boot takes very long to complete, and anything that is reading
from storage will also take long.
Occassionally, dmesg has an output similar to this issue that raspberri
pi has:
https://github.com/raspberrypi/linux/issues/3070
It isn't the same ( mine is gen 2, and this refers to the JMS579 which
is gen 1), but mine otherwise has basically the same output as the
issue, showing:
"
Jul 12 20:39:05 alarmpi kernel: sd 0:0:0:0: [sda] tag#5
uas_eh_abort_handler 0 uas-tag 6 inflight: CMD IN
Jul 12 20:39:05 alarmpi kernel: sd 0:0:0:0: [sda] tag#5 CDB: opcode=0x28
28 00 1b f2 41 d8 00 00 28 00
Jul 12 20:39:05 alarmpi kernel: sd 0:0:0:0: [sda] tag#4
uas_eh_abort_handler 0 uas-tag 5 inflight: CMD IN
Jul 12 20:39:05 alarmpi kernel: sd 0:0:0:0: [sda] tag#4 CDB: opcode=0x28
28 00 1b f2 41 28 00 00 a8 00
Jul 12 20:39:05 alarmpi kernel: scsi host0: uas_eh_device_reset_handler
start
Jul 12 20:39:05 alarmpi kernel: usb 2-1.1: reset SuperSpeed Gen 1 USB
device number 5 using xhci_hcd
Jul 12 20:39:05 alarmpi kernel: scsi host0: uas_eh_device_reset_handler
success
Jul 12 20:39:35 alarmpi systemd-udevd[221]: sda: Worker [295] processing
SEQNUM=2007 is taking a long time
Jul 12 20:39:36 alarmpi kernel: sd 0:0:0:0: [sda] tag#1
uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN
Jul 12 20:39:36 alarmpi kernel: sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x28
28 00 1b f2 44 78 00 00 28 00
Jul 12 20:39:36 alarmpi kernel: sd 0:0:0:0: [sda] tag#0
uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
Jul 12 20:39:36 alarmpi kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28
28 00 1b f2 44 08 00 00 68 00
Jul 12 20:39:36 alarmpi kernel: sd 0:0:0:0: [sda] tag#2
uas_eh_abort_handler 0 uas-tag 3 inflight: CMD IN
Jul 12 20:39:36 alarmpi kernel: sd 0:0:0:0: [sda] tag#2 CDB: opcode=0x28
28 00 1b f2 43 b8 00 00 48 00
Jul 12 20:39:36 alarmpi kernel: scsi host0: uas_eh_device_reset_handler
start
Jul 12 20:39:36 alarmpi kernel: usb 2-1.1: reset SuperSpeed Gen 1 USB
device number 5 using xhci_hcd
Jul 12 20:39:36 alarmpi kernel: scsi host0: uas_eh_device_reset_handler
success
"
The github issue later shows
"
https://www.raspberrypi.org/forums/viewtopic.php?t=245931" which
doesn't work for me, since I am not using it for a pi, though.
Later they also discuss setting something in udev for trim, however I'm
not sure how to add that to a regular system, let alone an ISO file for
a USB...
Anyone have any advice on making this thing run faster/properly?
lsusb calls it a JMicron JM583. It is also the only USB to PCIe on
JMicron's site, if you want to see more details on it:
https://www.jmicron.com/download/index/4
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss
(text/plain)