Hello,
I have a strange issue when running argononed.service on an ARGON EON with a M.2 boot device. As soon as I start the service, the M.2 device (sda) starts to muck around.
Apr 25 23:55:22 eon kernel: sd 0:0:0:0: [sda] tag#8 uas_eh_abort_handler 0 uas-tag 1 inflight: IN
Apr 25 23:55:22 eon kernel: sd 0:0:0:0: [sda] tag#8 CDB: opcode=0x85 85 08 2e 00 00 00 00 00 00 00 00 00 00 00 ec 00
Apr 25 23:55:22 eon kernel: scsi host0: uas_eh_device_reset_handler start
Apr 25 23:55:22 eon kernel: usb 2-2.3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
Apr 25 23:55:22 eon kernel: usb 2-2.3: Enable of device-initiated U1 failed.
Apr 25 23:55:22 eon kernel: usb 2-2.3: Enable of device-initiated U2 failed.
Apr 25 23:55:22 eon kernel: scsi host0: uas_eh_device_reset_handler success
This happens as soon as the daemon is started and stops as soon as its stopped, so it must be related. Leaving the daemon running ends with a failed device and no more root filesystem.
I am running stock Raspberry Pi OS 64bit
Anyone has an idea about that problem?
Thanks a lot in advance.