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.
After digging around in the python code, the problem seems to be the call to hddtemp inside argonsysinfo.py. Once it starts to call /usr/sbin/hddtemp -n sata:/dev/sda the problem starts.
root@eon:/home/pi# /usr/sbin/hddtemp -n sata:/dev/sda
/dev/sda: Invalid argument
Apr 26 00:21:45 eon kernel: sd 0:0:0:0: [sda] tag#4 uas_eh_abort_handler 0 uas-tag 1 inflight: IN
Apr 26 00:21:45 eon kernel: sd 0:0:0:0: [sda] tag#4 CDB: opcode=0x85 85 08 2e 00 00 00 00 00 00 00 00 00 00 00 ec 00
Apr 26 00:21:45 eon kernel: scsi host0: uas_eh_device_reset_handler start
Apr 26 00:21:45 eon kernel: usb 2-2.3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
Apr 26 00:21:45 eon kernel: usb 2-2.3: Enable of device-initiated U1 failed.
Apr 26 00:21:45 eon kernel: usb 2-2.3: Enable of device-initiated U2 failed.
Apr 26 00:21:45 eon kernel: scsi host0: uas_eh_device_reset_handler success
Any ideas here? Is it probably related to my M.2 adapter?
I have yet to actually get the script to work in Ubuntu 21.10. It installs (I think). On a check there’s no service running and from what I’m reading in the threads I’m actually afraid to try to kick it off.
Any updates would be greatly appreciated.
CDB opcode 85 is a pass through request, looks like the device connected does not like the command being passed through to it.
Since hddtemp -n seems to be generating the issue, I suspect that the M.2 device does not support SMART… hence the command being sent to the device to get the SMART data is failing.
You could load up smartmon and see if you can get any SMART data from the device.
I’m using a ZEXMTE M.2 NVME USB 3.1 USB adapter in my EON with a 500 GB NVME drive as my boot drive.
When I run the hddtemp command against that device (mine is mounted as /dev/sdc) I get the Invalid Argument message but I don’t get the rest of the errors you are seeing.
According to The S.M.A.R.T. control in OMV6, it can’t figure out what to do with it.
With my adapter, it is running a JMicron chipset, which may be the issue, but it is functional otherwise.