Solution wollik Posted February 15, 2021 Solution Posted February 15, 2021 Armbianmonitor: http://ix.io/2Pyl Hi Linux Admins, I have a wrong device in the /dev direcrory and can't delete it. Here is what I get when I do a: ls -la /dev/ttyUSB* pi@armbian_test: ls -la /dev/ttyUSB* crw-rw---- 1 root dialout 188, 0 Feb 15 20:47 /dev/ttyUSB0 -rw-r--r-- 1 root root 1 Feb 15 20:48 /dev/ttyUSB1 You see that the device ttyUSB1 is not character device and has no major device number assigned. Also the device belongs not to the dialout group. The causing USB_2_Serial Stick is disconnected and the device entry is still there. Trying to remove this devis is also not working. pi@armbian_test: sudo rm /dev/ttyUSB1 pi@armbian_test: ls -la /dev/ttyUSB* crw-rw---- 1 root dialout 188, 0 Feb 15 20:47 /dev/ttyUSB0 -rw-r--r-- 1 root root 1 Feb 15 20:48 /dev/ttyUSB1 pi@armbian_test: Pleas can somone help me to fix this wrong device ? Regards wollik
Werner Posted February 15, 2021 Posted February 15, 2021 Your issue report is invalid for one or multiple reasons (non-exhaustive enumeration): it has been stated at the wrong place it lacks fundamental requested data it could have been easily solved by a quick search and/or reading documentation unsupported userspace/image/SBC Since you refused to use the bug reporting form carefully and follow the information there as you have been asked for we have no intention to further investigate. Please add missing information if applicable. https://www.armbian.com/bugs
wollik Posted February 15, 2021 Author Posted February 15, 2021 Hi Werner, I don't know what is missing so I put some additional informations. I'm using a A20 SBC so I put it here, please can you move it to the right forum section ? I don't think this is a bug, I just want help how I can get rid of this wrong device. Regards wollik
wollik Posted March 3, 2021 Author Posted March 3, 2021 Hi All, this was caused by a hardware problem during the detection of the second USB-device. The system tried to create the node, but becaus of the hw failure it created a regular file. If someone tried to delete this file, the system recreated this wrong regular file again, what can be seen on the new I-Nodenumber. This situation persists even after a reboot without the failing USB-Stick! Here is my solution how I fixed this: I rebooted without any USB-device, and then reconnected each USB-2-Serial stick again each after the other. Regards wollik
Recommended Posts