USB Stick with UASP support; uas.ko missing
Posted: 12 Sep 2015, 19:42
Short:
Porteus 3.1 does not boot from USB devices with UASP support since the needed driver "uas.ko" is missing at boot time. It is contained in "000-kernel.xzm", that is 'too late for booting'.
How can this be fixed? I want to use the performance of USB UASP
For details on UAS / UASP: https://en.wikipedia.org/wiki/USB_Attached_SCSI
Long:
Downloaded a freshly build Porteus 3.1 - 32bit ISO with LXQt.
Copied to a FAT32 partition on a Sandisk SSD in an external USB 3.0 enclosure with USB UASP support.
USB SSD is detected by BIOS as USB HDD.
a) Booting from USB device with UASP support
When trying to boot from this USB SDD / FAT32 partition it hangs with 'no porteus data found'.
Entering debug shell:
"blkid" lists all other SATA and USB devices, but not the enclosure.
"dmesg" only contains logs from other USB devices.
b) Booting from other USB 2.0 device with (old) bulk protocol
Boot the same files from an older USB Key / FAT32 partition and enter debug shell:
"blkid" lists all other SATA and USB devices, but not the enclosure.
"dmesg" only lists logs from other USB devices.
Exiting debug shell and continue booting.
As soon as the system loads the .xzm-modules with "/lib/modules/../uas.ko" the uas.ko-kernel module is loaded, the USB devices is registered and the USB SSD in the enclosure can be accessed.
Examing in the "000-kernel.xzm": uas.ko ist supplied as a kernel-module in this package-file. But in order to boot from an USB device with UASP, this module has either to be compiled into the kernel or supplied via initrd.
Perhaps the error report has the same reason: It also happened with a new USB 3.0 stick:
viewtopic.php?f=81&t=4574
Since USB SSDs are more advertised this time, this problem will be encountered by other people, too.
Thanks in advance,
ping69
Porteus 3.1 does not boot from USB devices with UASP support since the needed driver "uas.ko" is missing at boot time. It is contained in "000-kernel.xzm", that is 'too late for booting'.
How can this be fixed? I want to use the performance of USB UASP
For details on UAS / UASP: https://en.wikipedia.org/wiki/USB_Attached_SCSI
Long:
Downloaded a freshly build Porteus 3.1 - 32bit ISO with LXQt.
Copied to a FAT32 partition on a Sandisk SSD in an external USB 3.0 enclosure with USB UASP support.
USB SSD is detected by BIOS as USB HDD.
a) Booting from USB device with UASP support
When trying to boot from this USB SDD / FAT32 partition it hangs with 'no porteus data found'.
Entering debug shell:
"blkid" lists all other SATA and USB devices, but not the enclosure.
"dmesg" only contains logs from other USB devices.
b) Booting from other USB 2.0 device with (old) bulk protocol
Boot the same files from an older USB Key / FAT32 partition and enter debug shell:
"blkid" lists all other SATA and USB devices, but not the enclosure.
"dmesg" only lists logs from other USB devices.
Exiting debug shell and continue booting.
As soon as the system loads the .xzm-modules with "/lib/modules/../uas.ko" the uas.ko-kernel module is loaded, the USB devices is registered and the USB SSD in the enclosure can be accessed.
Examing in the "000-kernel.xzm": uas.ko ist supplied as a kernel-module in this package-file. But in order to boot from an USB device with UASP, this module has either to be compiled into the kernel or supplied via initrd.
Perhaps the error report has the same reason: It also happened with a new USB 3.0 stick:
viewtopic.php?f=81&t=4574
Since USB SSDs are more advertised this time, this problem will be encountered by other people, too.
Thanks in advance,
ping69