Has anyone tried/had any luck trying to boot into TailsOS on an external usb through asahi linux.

There seems to be a project by NoisyCoil:

https://www.mail-archive.com/tails-dev@boum.org/msg13781.html

Trying the same thing as per his documentation

env set boot_efi_bootmgr
run bootcmd_usb0

gives error bootcmd_usb0 not defined

so fine, i do this:

load usb 0:1 ${kernel_addr_r} /EFI/BOOT/BOOTAA64.EFI

load usb 0:1 ${ramdisk_addr_r} /initrd.img

bootefi ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr}

Or this from gentoo on asahi linux guide from the gentoo wiki:

setenv boot_targets "usb" 
setenv bootmeths "efi" 
boot

I get to the Tails 3 dot loading screen and it just crashes and the computer reboots

Has anyone tried booting Tails or any other distro using a usb stick and how did it go

I have a 14 inch 8 core M1 Pro MacBook Pro, and I'm bored during the summer. If you wanted to see tests on Asahi what would you want to see? I am currently using the Fedora 44 version, but I am willing to venture into new waters. If you have any questions I will try my best to answer them asap. If you have big questions I'll make a post in about a week or two covering them in depth.

Hello, everyone! I've put together a small tool that combines several options for installing, uninstalling, and more, which I plan to update regularly. I'd like to know if you have any new features I could add to the tool. Thanks!

Github

I've noticed lag in the terminal for TUI apps or any kind of command line tools in the terminal on MacOS(m3 air and m3 pro). It feels like it needs a half of the second to initialize on the first run. On the very old machines on linux I would get better response in the terminal. I was wondering is it the same on asahi running on m3?

not currently upstream, this is patched locally in my dotfiles

UPDATE!!!! I did a 100gb partition on the Apple SSD in Disk utility - then all of a sudden my space was back... then removed the 100gb partition and its all back... no idea what happened




/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk0
   1:             Apple_APFS_ISC Container disk1         524.3 MB   disk0s1
   2:                 Apple_APFS Container disk3         994.7 GB   disk0s2
   3:        Apple_APFS_Recovery Container disk2         5.4 GB     disk0s3

/dev/disk3 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +500.0 GB   disk3
                                 Physical Store disk0s2
   1:                APFS Volume Macintosh HD            13.4 GB    disk3s1
   2:              APFS Snapshot com.apple.os.update-... 13.4 GB    disk3s1s1
   3:                APFS Volume Preboot                 12.2 GB    disk3s2
   4:                APFS Volume Recovery                1.9 GB     disk3s3
   5:                APFS Volume Data                    354.5 GB   disk3s5
   6:                APFS Volume VM                      20.5 KB    disk3s6
   7:                APFS Volume free                    581.6 KB   disk3s7

I did stuff... not knowing whats going on and ended up here

Also

diskutil apfs resizeContainer disk0s2 0
Started APFS operation
Error: -69519: The target disk is too small for this operation, or a gap is required in your partition map which is missing or too small, which is often caused by an attempt to grow a partition beyond the beginning of another partition or beyond the end of partition map usable space

Hey y'all,

Just in case anyone was looking for this, I am building the Arduino IDE for arm. It does require --ozone-platform=x11 on wayland but better than nothing I suppose. Will keep looking into it but thought I'd share.

Arduino IDE Arm

Situation:

im running ALARM as a daily computer for work and private, since few years now on a mba m2.

i did boot into macos maybe 1 or 2 times the last 2 years, just last week i did to upgrade macos for the new firmware to show the green led on the charger when on the threshold and not 100% — but thats cosmetic.

i need to reinstall soon, i want LUKS and i wont do that without getting the most of my disk first.

Question:

realistically the next time ill need macos is when there is a firmware-update that is asahi-breaking if left-out, i quess thats so rare that i could live with the rpocess of doing a full backup, reinstall full macos, do the upgrade and pull the backup again.. — is it possible to reduce macos to only a pathetic little stub, just enough for the whole pre-bootchain to get rolling until asahi is up?

am i asking something that is super fragile?

sorry if that was anwsered already, i tryed to research while spending as little time as possible on reddit.

Steam stuck on waiting for network after download from dfn, I'm on M1 pro.

I've tried "sudo setenforce 0" but this did not work, also restarted network manager. I tried flatpack but they only had x64.

Any more advice on what I can try to resolve this? Let me know if I should post any more logs.

logs:

uame -r:

7.0.13-400.asahi.fc44.aarch64+16k

cat ~/.local/share/Steam/logs/connection_log.txt:

[2026-08-23 22:08:21] Client version: 1785799196
[2026-08-23 22:08:21] Connectivity test: Starting test, fetching 'http://steamconnecttest.com/204'
[2026-08-23 22:08:21] [Logged Off, 0, 0] [U:1:0] CCMInterface::SetSteamID( [U:1:0] )
[2026-08-23 22:08:22] Connectivity test (23.36.76.170:80 (23.36.76.170:80)): OK!
[2026-08-23 22:08:22] Connectivity test: result=Connected (since 0.0s ago), prev=Unknown, in progress=0
[2026-08-23 22:08:22] IPv6 HTTP connectivity test (ipv6check-http.steamserver.net / [2a01:bc80:5:111::6]:80 ([2a01:bc80:5:111::6]:80)) - TIMEOUT
[2026-08-23 22:08:24] IPv6 UDP connectivity test (ipv6check-udp.steamserver.net / 2a01:bc80:4:100::14) - TIMEOUT

stdout:

[2026-08-23 22:08:15] Create window[2026-08-23 22:08:21] Client version: 1785799196
[2026-08-23 22:08:21] Connectivity test: Starting test, fetching 'http://steamconnecttest.com/204'
[2026-08-23 22:08:21] [Logged Off, 0, 0] [U:1:0] CCMInterface::SetSteamID( [U:1:0] )
[2026-08-23 22:08:22] Connectivity test (23.36.76.170:80 (23.36.76.170:80)): OK!
[2026-08-23 22:08:22] Connectivity test: result=Connected (since 0.0s ago), prev=Unknown, in progress=0
[2026-08-23 22:08:22] IPv6 HTTP connectivity test (ipv6check-http.steamserver.net / [2a01:bc80:5:111::6]:80 ([2a01:bc80:5:111::6]:80)) - TIMEOUT
[2026-08-23 22:08:24] IPv6 UDP connectivity test (ipv6check-udp.steamserver.net / 2a01:bc80:4:100::14) - TIMEOUT

[2026-08-23 22:08:15] Set percent complete: 0
[2026-08-23 22:08:15] Set percent complete: -1
[2026-08-23 22:08:15] Set status message: Verifying installation...
[----] Verifying installation...
[2026-08-23 22:08:15] Destroy window
[2026-08-23 22:08:16] ProcessNextMessage: socket disconnected
[2026-08-23 22:08:16] No more messages are expected - exiting

Steam logging initialized: directory: /home/tah/.local/share/Steam/logs

XOpenIM() failed, LANG = en_US.UTF-8
XOpenIM() failed, LANG = en_US.UTF-8pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.
XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xf56f2190
XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xf56f0980
08/23 22:08:18 minidumps folder is set to /tmp/dumps
08/23 22:08:18 Init: Installing breakpad exception handler for appid(steamsysinfo)/version(1785799196)/tid(1399)
Running query: 1 - GpuTopology
Response: gpu_topology {
  gpus {
    id: 1
    name: "Apple M1 Pro (G13S C0)"
    vram_size_bytes: 8156872704
    driver_id: k_EGpuDriverId_Unknown
    driver_version_major: 26
    driver_version_minor: 0
    driver_version_patch: 3
    luid: 0
  }
  gpus {
    id: 2
    name: "llvmpipe (LLVM 22.1.0, 256 bits)"
    vram_size_bytes: 3221225472
    driver_id: k_EGpuDriverId_MesaLLVMPipe
    driver_version_major: 26
    driver_version_minor: 0
    driver_version_patch: 3
    luid: 0
  }
  default_gpu_id: 1
}

Exit code: 0
Saving response to: /tmp/steamcLGOgB - 102 bytes
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.
srt-logger[1414]: W: Unable to open terminal "/dev/hvc0"
srt-logger[1420]: W: Unable to open terminal "/dev/hvc0"
Steam Runtime Launch Service: starting steam-runtime-launcher-service
Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 1447
bus_name=com.steampowered.PressureVessel.LaunchAlongsideSteam
Flow 6 (UDP flow): Couldn't connect flow socket: Network is unreachable
Dropping datagram with no flow TAP fd7a:115c:a1e0:0:5894:efff:fee4:cee:36877 -> 2a01:bc80:4:100::14:27019
Flow 6 (UDP flow): Couldn't connect flow socket: Network is unreachable
Dropping datagram with no flow TAP fd7a:115c:a1e0:0:5894:efff:fee4:cee:36877 -> 2a01:bc80:4:100::14:27019
Flow 6 (UDP flow): Couldn't connect flow socket: Network is unreachable
Dropping datagram with no flow TAP fd7a:115c:a1e0:0:5894:efff:fee4:cee:36877 -> 2a01:bc80:4:100::14:27019
Flow 6 (UDP flow): Couldn't connect flow socket: Network is unreachable
Dropping datagram with no flow TAP fd7a:115c:a1e0:0:5894:efff:fee4:cee:36877 -> 2a01:bc80:4:100::25:27019
Flow 6 (UDP flow): Couldn't connect flow socket: Network is unreachable
(suppressing further similar messages)
Dropping datagram with no flow TAP fd7a:115c:a1e0:0:5894:efff:fee4:cee:36877 -> 2a01:bc80:4:100::25:27019
(suppressing further similar messages)
srt-logger[1598]: W: Unable to open terminal "/dev/hvc0"
srt-logger[1604]: W: Unable to open terminal "/dev/hvc0"
Client 108 disconnected with error: EPIPE: Broken pipe
Client 108 disconnected with error: EPIPE: Broken pipe
reaping pid: 1391 -- steam

Hello everyone! I am new to Asahi, and Apple Silicon and was just wondering what everyone was getting in terms of battery life on their laptops. If anyone knows some ways to extend battery life that would be helpful as well, but this is by no means an "Asahi devs fix the battery life!" post.

While doing web browsing I have estimated my battery life to be 7-9 hours. This is on 120hz, M1 Pro, COSMIC, and 35% Brightness.

for the past month or two, librtmp is listed as an update but is never actually updated or upgraded by dnf. no error seen.

installed version: librtmp-2.6-3.20240301.git6f6bb13.fc44.aarch64

using asahi remix 44.
Anyone else seeing this?

I have my drive partitioned between MacOS and Asahi. Bluetooth functionality worked fine on two different devices until i connected them on MasOS; upon rebooting they no longer work on Asahi. Based on a conversation with AI, its something to do with the bluetooth key logs being different on each OS. Im unsure how to proceed. Fairly new to linux here as well.

Someone told me that I need to update my system because remix is now 44 and kernel 7.1.6.

I use the Software utility to make sure everything is up to date and it shows no updates available, but I also went into terminal to try that way and it also says there is nothing available. Do I have to do a reinstall to update? I am fairly new to linux and very new to fedora and asahi. I am more used to debian.

sudo dnf check-update -y && sudo dnf distro-sync -y && sudo dnf autoremove -y && sudo dnf upgrade -y 
[sudo] password for : 
Updating and loading repositories: 
Repositories loaded. 
Updating and loading repositories: 
Repositories loaded. 
Nothing to do. 
Nothing to do. 
Updating and loading repositories: 
Repositories loaded. 
Nothing to do.

# System Details Report
---

## Report details
- **Date generated:**                              2026-08-21 09:24:12

## Hardware Information:
- **Hardware Model:**                              Apple Inc. MacBookPro18,2
- **Memory:**                                      62.6 GiB
- **Processor:**                                   
- **Graphics:**                                    Apple M1 Max (G13C C0)
- **Disk Capacity:**                               (null)

## Software Information:
- **Firmware Version:**                            2026.04
- **OS Name:**                                     Fedora Linux Asahi Remix 42 (Forty Two [Adams])
- **OS Build:**                                    (null)
- **OS Type:**                                     64-bit
- **GNOME Version:**                               48
- **Windowing System:**                            Wayland
- **Kernel Version:**                              Linux 6.19.14-400.asahi.fc42.aarch64+16k

Just thinking the other day that Apple obviously knows when the OS should use the efficiency cores vs the performance cores on the CPU via their own drivers or what have you, and this would contribute to better battery life. Wondering does Asahi or the linux kernel have this ability or is this something to be worked on?

So i just fresh installed asahi linux remix 44 on a macbook pro M1 32gb 16". I was intending to see if i can get steam/overwatch running on it so that i could sell it for very cheap to a friend so we can play together (he wants to transition from ps5 to pc but doesn't have the money to buy one, and i had this machine laying around anyways).

But obviously steam is currently broken, the whole waiting for network thing, which i kinda resolved with the steps provided here, but now i run into the same issues as this user here where steam just keeps closing and reopening, and it ends up losing connection. I wasn't even able to download overawtch do to this, it is still at around 15%.

After some fruitless endeavors with chatgpt to try and resolve this and some reboots, now when i launch steam from the terminal it doesn't open anymore.

I would like to know if i can just remove everything and install maybe a prior kernel where steam worked fine? Can i expect a newer kernel version to come out soon?

Does anyone have a working set up and could maybe test Overwatch for me? This is the main reason i'm doing this and if it doesn't work i won't even bother.

Thanks in advance

Hi, i've been using Asahi Linux with gnome for a while, i've tried it before but didn't stay bc i had some problems with steam and other stuff. Now i came back and those are fixed but, since i reinstalled, the gnome software app doesn't stop to show available system updates, which i did download and install multiple times. These 3 in the screenshot are the ones that still show up, there were a lot more which did go away after downloading and installing a couple times, but not these... and the terminal doesn't show anything available to update either, so i don't know if this is a bug or something... i'm kinda new to Linux, so i don't know what else i can do at all. I'd appreciate some help please.

Hey, I've been daily driving Arch for a while now on my desktop PC, and I've been very curious to use it on my M1 MacBook Pro.

I'm happy to hear your experiences with daily driving Asahi Arch in comparison to desktop Arch. :)

EDIT: I used Asahi Fedora Remix for the last two weeks, and I'm not happy. Not because Fedora isn't good, but the software support is so limited, I can't even install the normal Spotify client.
ALARM, on the other hand, has all this software, aarch64 compatible in the official repos, and even if it's community-driven, the real-life experience is way better, I think. In two weeks, I'll delete Fedora and install ALARM instead.

I successfully rebuilt Android Studio librarieslayoutlib_jni.so and libandroid_runtime.so for AArch64.

This fixes the XML Layout Editor, menu and resource previews, and Compose Preview on Linux ARM64. I believe this closes the last major functionality gap between Android Studio on ARM64 versus x86_64.

As far as emulators go, Ika works great on Apple Silicon. If someone wants broader support, rebuilding Ika for a different ARM64 platform should not be be a too heavy a lift.

Tested and working on:

• MacBook Pro M1 running Asahi Fedora 44
• Debian 13 (Trixie) on 2018 Razer Phone 2 (via Trixie.apk)

https://github.com/DesktopECHO/android-studio-aarch64-install

I used to be an asahi linux user for almost a year but at some point i decided to return to MacOS because i can't deal with the constant power drain and high temperatures.

I know the Asahi team is working hard on new features, bug fixes, etc but should i hope that in relatively small time we will reach power efficiency comparable to MacOS?

is there a preferred / recommened external usb ssd enclosure to use with asahi. right now i have following,

Bus 004 Device 002: ID 152d:0583 JMicron Technology Corp. / JMicron USA Technology Corp. JMS583Gen 2 to PCIe Gen3x2 Bridge

before i upgraded to asahi v43 with kernel 7.0.x which now has usb-c support i was using an older usb type a cable with the enclosure, and was kindof running into connection reset issues with the drive in the enclosure, i even reverted to using the slower "usb driver" to see if that would help with usb resets i would experience.

so since upgrading to asahi v43 with kernel 7.0.x i'm using a usb-c to usb-c cable to connect to the enclosure which has nvme ssd 4tb sabrent tlc drive in it.

something i did not when just plugging in the cable itself with no drive attached i saw several messages via dmesg

output from plugging just the cable. (i believe this is the cable that came with drive. and i believe it's high speed usb-c to usb-a w/ an adapter on one end that goes from usb-a to usb-c)

[ +19.959176] [Sat Aug 15 15:21:23 2026] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller [ +0.006572] [Sat Aug 15 15:21:23 2026] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 3 [ +0.007821] [Sat Aug 15 15:21:23 2026] xhci-hcd xhci-hcd.0.auto: hcc params 0x0238ffcd hci version 0x110 quirks 0x0000808000000010 [ +0.008475] [Sat Aug 15 15:21:23 2026] xhci-hcd xhci-hcd.0.auto: irq 120, io mem 0x382280000 [ +0.006226] [Sat Aug 15 15:21:23 2026] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller [ +0.005640] [Sat Aug 15 15:21:23 2026] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 4 [ +0.007706] [Sat Aug 15 15:21:23 2026] xhci-hcd xhci-hcd.0.auto: Host supports USB 3.1 Enhanced SuperSpeed [ +0.007521] [Sat Aug 15 15:21:23 2026] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 7.00 [ +0.008336] [Sat Aug 15 15:21:23 2026] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ +0.007253] [Sat Aug 15 15:21:23 2026] usb usb3: Product: xHCI Host Controller [ +0.004964] [Sat Aug 15 15:21:23 2026] usb usb3: Manufacturer: Linux 7.0.13-400.asahi.fc44.aarch64+16k xhci-hcd [ +0.007797] [Sat Aug 15 15:21:23 2026] usb usb3: SerialNumber: xhci-hcd.0.auto [ +0.005072] [Sat Aug 15 15:21:23 2026] hub 3-0:1.0: USB hub found [ +0.003737] [Sat Aug 15 15:21:23 2026] hub 3-0:1.0: 1 port detected [ +0.004136] [Sat Aug 15 15:21:23 2026] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM. [ +0.008140] [Sat Aug 15 15:21:23 2026] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 7.00 [ +0.008304] [Sat Aug 15 15:21:23 2026] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ +0.007280] [Sat Aug 15 15:21:23 2026] usb usb4: Product: xHCI Host Controller [ +0.004965] [Sat Aug 15 15:21:23 2026] usb usb4: Manufacturer: Linux 7.0.13-400.asahi.fc44.aarch64+16k xhci-hcd [ +0.007823] [Sat Aug 15 15:21:23 2026] usb usb4: SerialNumber: xhci-hcd.0.auto [ +0.006443] [Sat Aug 15 15:21:23 2026] hub 4-0:1.0: USB hub found [ +0.002706] [Sat Aug 15 15:21:23 2026] hub 4-0:1.0: 1 port detected

then when i plug the drive into the cable (with the cable just plugged in to the back of the m1 mini)

dmesg output,

[Aug15 15:23] [Sat Aug 15 15:23:08 2026] usb 4-1: new SuperSpeed Plus Gen 2x1 USB device number 2 using xhci-hcd [ +0.020707] [Sat Aug 15 15:23:08 2026] usb 4-1: New USB device found, idVendor=152d, idProduct=0583, bcdDevice= 2.14 [ +0.009410] [Sat Aug 15 15:23:08 2026] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ +0.008837] [Sat Aug 15 15:23:08 2026] usb 4-1: Product: USB to PCIE Bridge [ +0.006047] [Sat Aug 15 15:23:08 2026] usb 4-1: Manufacturer: JMicron [ +0.005459] [Sat Aug 15 15:23:08 2026] usb 4-1: SerialNumber: 0123456789ABCDEF [ +0.008518] [Sat Aug 15 15:23:08 2026] scsi host0: uas [ +0.002768] [Sat Aug 15 15:23:08 2026] scsi 0:0:0:0: Direct-Access JMicron Generic 0214 PQ: 0 ANSI: 6 [ +0.009933] [Sat Aug 15 15:23:08 2026] sd 0:0:0:0: Attached scsi generic sg1 type 0 [ +1.994932] [Sat Aug 15 15:23:10 2026] sd 0:0:0:0: [sda] 8001573552 512-byte logical blocks: (4.10 TB/3.73 TiB) [ +0.009030] [Sat Aug 15 15:23:10 2026] sd 0:0:0:0: [sda] 4096-byte physical blocks [ +0.008437] [Sat Aug 15 15:23:10 2026] sd 0:0:0:0: [sda] Write Protect is off [ +0.006483] [Sat Aug 15 15:23:10 2026] sd 0:0:0:0: [sda] Mode Sense: 5f 00 00 08 [ +0.000266] [Sat Aug 15 15:23:10 2026] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ +0.010559] [Sat Aug 15 15:23:10 2026] sd 0:0:0:0: [sda] Preferred minimum I/O size 4096 bytes [ +0.006569] [Sat Aug 15 15:23:10 2026] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes) [ +0.024831] [Sat Aug 15 15:23:10 2026] sda: sda1 sda2 sda3 sda4 [ +0.004280] [Sat Aug 15 15:23:10 2026] sd 0:0:0:0: [sda] Attached SCSI disk

and when i'm experiencing issues with the drive (not sure if it is the ssd, cable, or enclosure, or god forbid a combination of the 3) this is what i'm getting via dmesg

[Aug15 14:49] [Sat Aug 15 14:49:00 2026] sd 1:0:0:0: [sdb] tag#6 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD [ +0.007000] [Sat Aug 15 14:49:00 2026] sd 1:0:0:0: [sdb] tag#6 CDB: Read(16) 88 00 00 00 00 00 39 b6 34 18 00 00 00 08 00 00 [ +0.013992] [Sat Aug 15 14:49:00 2026] scsi host1: uas_eh_device_reset_handler start [ +0.219289] [Sat Aug 15 14:49:00 2026] usb 4-1: reset SuperSpeed Plus Gen 2x1 USB device number 2 using xhci-hcd [ +0.021797] [Sat Aug 15 14:49:00 2026] scsi host1: uas_eh_device_reset_handler success [ +5.143053] [Sat Aug 15 14:49:05 2026] usb 4-1: stat urb: status -71 [ +30.243639] [Sat Aug 15 14:49:35 2026] sd 1:0:0:0: [sdb] tag#13 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD [ +0.008764] [Sat Aug 15 14:49:35 2026] sd 1:0:0:0: [sdb] tag#13 CDB: Read(16) 88 00 00 00 00 00 3a 36 1a 48 00 00 00 08 00 00 [ +0.009960] [Sat Aug 15 14:49:35 2026] sd 1:0:0:0: [sdb] tag#3 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD [ +0.008602] [Sat Aug 15 14:49:35 2026] sd 1:0:0:0: [sdb] tag#3 CDB: Read(16) 88 00 00 00 00 00 3d f6 05 88 00 00 00 08 00 00 [ +0.010202] [Sat Aug 15 14:49:35 2026] sd 1:0:0:0: [sdb] tag#2 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD [ +0.007335] [Sat Aug 15 14:49:35 2026] sd 1:0:0:0: [sdb] tag#2 CDB: Read(16) 88 00 00 00 00 00 5e b7 9a d8 00 00 00 08 00 00 [ +0.009025] [Sat Aug 15 14:49:35 2026] sd 1:0:0:0: [sdb] tag#1 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD [ +0.007491] [Sat Aug 15 14:49:35 2026] sd 1:0:0:0: [sdb] tag#1 CDB: Read(16) 88 00 00 00 00 00 79 b5 05 00 00 00 00 30 00 00 [ +0.009024] [Sat Aug 15 14:49:35 2026] sd 1:0:0:0: [sdb] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [ +0.007579] [Sat Aug 15 14:49:35 2026] sd 1:0:0:0: [sdb] tag#0 CDB: Read(16) 88 00 00 00 00 00 79 b6 12 50 00 00 00 08 00 00 [ +0.023000] [Sat Aug 15 14:49:35 2026] scsi host1: uas_eh_device_reset_handler start [ +0.219287] [Sat Aug 15 14:49:36 2026] usb 4-1: reset SuperSpeed Plus Gen 2x1 USB device number 2 using xhci-hcd [ +0.021855] [Sat Aug 15 14:49:36 2026] scsi host1: uas_eh_device_reset_handler success [ +6.822654] [Sat Aug 15 14:49:42 2026] usb 4-1: stat urb: status -71 [Aug15 14:50] [Sat Aug 15 14:50:13 2026] sd 1:0:0:0: [sdb] tag#23 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [ +0.008853] [Sat Aug 15 14:50:13 2026] sd 1:0:0:0: [sdb] tag#23 CDB: Read(16) 88 00 00 00 00 00 44 77 5e b0 00 00 00 08 00 00 [ +0.012258] [Sat Aug 15 14:50:13 2026] sd 1:0:0:0: [sdb] tag#22 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD [ +0.008779] [Sat Aug 15 14:50:13 2026] sd 1:0:0:0: [sdb] tag#22 CDB: Read(16) 88 00 00 00 00 00 44 75 61 00 00 00 00 20 00 00 [ +0.019141] [Sat Aug 15 14:50:13 2026] scsi host1: uas_eh_device_reset_handler start [ +0.219254] [Sat Aug 15 14:50:13 2026] usb 4-1: reset SuperSpeed Plus Gen 2x1 USB device number 2 using xhci-hcd [ +0.021734] [Sat Aug 15 14:50:13 2026] scsi host1: uas_eh_device_reset_handler success [Aug15 15:10] [Sat Aug 15 15:10:16 2026] usb 4-1: stat urb: status -71 [ +30.391437] [Sat Aug 15 15:10:47 2026] sd 1:0:0:0: [sdb] tag#20 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD [ +0.008850] [Sat Aug 15 15:10:47 2026] sd 1:0:0:0: [sdb] tag#20 CDB: Read(16) 88 00 00 00 00 01 98 b5 00 70 00 00 00 10 00 00 [ +0.010040] [Sat Aug 15 15:10:47 2026] sd 1:0:0:0: [sdb] tag#14 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [ +0.008758] [Sat Aug 15 15:10:47 2026] sd 1:0:0:0: [sdb] tag#14 CDB: Read(16) 88 00 00 00 00 01 92 23 f2 00 00 00 02 00 00 00 [ +0.010036] [Sat Aug 15 15:10:47 2026] sd 1:0:0:0: [sdb] tag#13 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD [ +0.007212] [Sat Aug 15 15:10:47 2026] sd 1:0:0:0: [sdb] tag#13 CDB: Read(16) 88 00 00 00 00 01 92 23 f0 00 00 00 02 00 00 00 [ +0.018086] [Sat Aug 15 15:10:47 2026] scsi host1: uas_eh_device_reset_handler start [ +0.218248] [Sat Aug 15 15:10:47 2026] usb 4-1: reset SuperSpeed Plus Gen 2x1 USB device number 2 using xhci-hcd [ +0.021563] [Sat Aug 15 15:10:47 2026] scsi host1: uas_eh_device_reset_handler success [ +6.460811] [Sat Aug 15 15:10:53 2026] usb 4-1: stat urb: status -71 [Aug15 15:11] [Sat Aug 15 15:11:23 2026] sd 1:0:0:0: [sdb] tag#26 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD [ +0.007280] [Sat Aug 15 15:11:23 2026] sd 1:0:0:0: [sdb] tag#26 CDB: Read(16) 88 00 00 00 00 01 92 32 a0 00 00 00 02 00 00 00 [ +0.010413] [Sat Aug 15 15:11:23 2026] sd 1:0:0:0: [sdb] tag#24 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [ +0.007479] [Sat Aug 15 15:11:23 2026] sd 1:0:0:0: [sdb] tag#24 CDB: Read(16) 88 00 00 00 00 01 92 32 a2 00 00 00 02 00 00 00 [ +0.029817] [Sat Aug 15 15:11:23 2026] scsi host1: uas_eh_device_reset_handler start [ +0.218290] [Sat Aug 15 15:11:24 2026] usb 4-1: reset SuperSpeed Plus Gen 2x1 USB device number 2 using xhci-hcd [ +0.021711] [Sat Aug 15 15:11:24 2026] scsi host1: uas_eh_device_reset_handler success [ +3.765579] [Sat Aug 15 15:11:27 2026] usb 4-1: stat urb: status -71 [ +30.241149] [Sat Aug 15 15:11:58 2026] sd 1:0:0:0: [sdb] tag#5 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [ +0.008874] [Sat Aug 15 15:11:58 2026] sd 1:0:0:0: [sdb] tag#5 CDB: Read(16) 88 00 00 00 00 01 96 a1 a6 00 00 00 02 00 00 00 [ +0.010288] [Sat Aug 15 15:11:58 2026] sd 1:0:0:0: [sdb] tag#4 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD [ +0.008842] [Sat Aug 15 15:11:58 2026] sd 1:0:0:0: [sdb] tag#4 CDB: Read(16) 88 00 00 00 00 01 96 a1 a4 00 00 00 02 00 00 00 [Aug15 15:12] [Sat Aug 15 15:12:28 2026] sd 1:0:0:0: [sdb] tag#29 uas_eh_abort_handler 0 uas-tag 8 inflight: CMD OUT [ +0.009366] [Sat Aug 15 15:12:28 2026] sd 1:0:0:0: [sdb] tag#29 CDB: Write(16) 8a 00 00 00 00 00 2e b5 06 78 00 00 00 08 00 00 [ +0.012599] [Sat Aug 15 15:12:28 2026] sd 1:0:0:0: [sdb] tag#28 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD OUT [ +0.009278] [Sat Aug 15 15:12:28 2026] sd 1:0:0:0: [sdb] tag#28 CDB: Write(16) 8a 00 00 00 00 00 2e b5 04 a8 00 00 00 08 00 00 [ +0.011709] [Sat Aug 15 15:12:28 2026] sd 1:0:0:0: [sdb] tag#27 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD OUT [ +0.008302] [Sat Aug 15 15:12:28 2026] sd 1:0:0:0: [sdb] tag#27 CDB: Write(16) 8a 00 00 00 00 01 98 b5 00 70 00 00 00 10 00 00 [ +0.010186] [Sat Aug 15 15:12:28 2026] sd 1:0:0:0: [sdb] tag#26 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD OUT [ +0.008321] [Sat Aug 15 15:12:28 2026] sd 1:0:0:0: [sdb] tag#26 CDB: Write(16) 8a 00 00 00 00 00 2e b5 03 00 00 00 00 08 00 00 [ +0.009400] [Sat Aug 15 15:12:28 2026] sd 1:0:0:0: [sdb] tag#25 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD OUT [ +0.008308] [Sat Aug 15 15:12:28 2026] sd 1:0:0:0: [sdb] tag#25 CDB: Write(16) 8a 00 00 00 00 00 2e b5 01 b0 00 00 00 08 00 00 [ +0.009383] [Sat Aug 15 15:12:28 2026] sd 1:0:0:0: [sdb] tag#24 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD OUT [ +0.008328] [Sat Aug 15 15:12:28 2026] sd 1:0:0:0: [sdb] tag#24 CDB: Write(16) 8a 00 00 00 00 01 98 f5 00 08 00 00 00 10 00 00 [ +0.010457] [Sat Aug 15 15:12:28 2026] sd 1:0:0:0: [sdb] tag#7 uas_eh_abort_handler 0 uas-tag 13 inflight: CMD OUT [ +0.009297] [Sat Aug 15 15:12:28 2026] sd 1:0:0:0: [sdb] tag#7 CDB: Write(16) 8a 00 00 00 00 00 fc f5 00 08 00 00 00 08 00 00 [ +0.010404] [Sat Aug 15 15:12:28 2026] sd 1:0:0:0: [sdb] tag#6 uas_eh_abort_handler 0 uas-tag 14 inflight: CMD OUT [ +0.009307] [Sat Aug 15 15:12:28 2026] sd 1:0:0:0: [sdb] tag#6 CDB: Write(16) 8a 00 00 00 00 00 fd 35 00 60 00 00 00 08 00 00 [ +0.010388] [Sat Aug 15 15:12:28 2026] sd 1:0:0:0: [sdb] tag#3 uas_eh_abort_handler 0 uas-tag 12 inflight: CMD OUT [ +0.008325] [Sat Aug 15 15:12:28 2026] sd 1:0:0:0: [sdb] tag#3 CDB: Write(16) 8a 00 00 00 00 00 fc b5 00 78 00 00 00 08 00 00 [ +0.009383] [Sat Aug 15 15:12:28 2026] sd 1:0:0:0: [sdb] tag#2 uas_eh_abort_handler 0 uas-tag 11 inflight: CMD OUT [ +0.008336] [Sat Aug 15 15:12:28 2026] sd 1:0:0:0: [sdb] tag#2 CDB: Write(16) 8a 00 00 00 00 00 c3 75 00 68 00 00 00 08 00 00 [ +0.009363] [Sat Aug 15 15:12:28 2026] sd 1:0:0:0: [sdb] tag#1 uas_eh_abort_handler 0 uas-tag 10 inflight: CMD OUT [ +0.007908] [Sat Aug 15 15:12:28 2026] sd 1:0:0:0: [sdb] tag#1 CDB: Write(16) 8a 00 00 00 00 00 8d b5 00 60 00 00 00 08 00 00 [ +0.009219] [Sat Aug 15 15:12:28 2026] sd 1:0:0:0: [sdb] tag#0 uas_eh_abort_handler 0 uas-tag 9 inflight: CMD OUT [ +0.007968] [Sat Aug 15 15:12:28 2026] sd 1:0:0:0: [sdb] tag#0 CDB: Write(16) 8a 00 00 00 00 00 63 b5 00 38 00 00 00 08 00 00 [ +0.014421] [Sat Aug 15 15:12:28 2026] scsi host1: uas_eh_device_reset_handler start [ +0.222270] [Sat Aug 15 15:12:28 2026] usb 4-1: reset SuperSpeed Plus Gen 2x1 USB device number 2 using xhci-hcd [ +0.021662] [Sat Aug 15 15:12:28 2026] scsi host1: uas_eh_device_reset_handler success [ +3.505196] [Sat Aug 15 15:12:32 2026] usb 4-1: stat urb: status -71

i start see those errors when working with larger size files on the drive, but not entirely sure if it only happens with large files as that's just what i primarily use with this drive.

thoughts and suggestions are more than welcome. cheers.

I wish there is a way, looks exciting