On 1/15/24 13:44, Felix Miata wrote:
gene heskett composed on 2024-01-15 08:39 (UTC-0500):└─md2 9:2 0 3G 0 raid10 sdh 8:112 0 1.9T 0 disk └─sdh1 8:113 0 1.9T 0 part <<< the one I'm fooling with sdi 8:128 0 1.9T 0 disk └─sdi1 8:129 0 1.9T 0 part <<< sdj 8:144 0 1.9T 0 disk └─sdj1 8:145 0 1.9T 0 part <<< sdk 8:160 0 1.9T 0 disk └─sdk1 8:161 0 1.9T 0 part <<< sdl 8:176 0 1.9T 0 disk └─sdl1 8:177 0 1.9T 0 part <<< sr0 11:0 1 1024M 0 romIs there a smart card reader in coyote? They can cause what looks like phantom drives. If not, I have no idea what those 5 <<< devices might be assigned to, other than their sizes. :( I suspect it could be some kind of bug, possibly in SATA expansion card firmware. There was a buggy Bookworm kernel recently causing I/O problems. What kernel are you running? 6.1.0-17 is current. Bug was sometime after 6.1.0-13. I have a card reader that produces sd[cdef]: # lsscsi [2:0:0:0] disk ATA ST1000NM0011 SN02 /dev/sda [3:0:0:0] disk ATA ST1000DM003-1CH1 CC49 /dev/sdb [4:0:0:0] cd/dvd ASUS DRW-24B1ST j 1.11 /dev/sr0 [6:0:0:0] disk Generic USB SD Reader 1.00 /dev/sdc [6:0:0:1] disk Generic USB CF Reader 1.01 /dev/sdd [6:0:0:2] disk Generic USB SM Reader 1.02 /dev/sde [6:0:0:3] disk Generic USB MS Reader 1.03 /dev/sdf # So, when I insert a generic USB stick, it gets /dev/sdg. :p
I have one, plugged into usb, but nothing is plugged into it ATM, an ONN from wallies. no problems here but it can mess with armbian booting on a bannapi-m5. Got a bunch of those. Nothing that ob this box that looks like the last 4 above. I look at dmesg tp see what it is before I mount it.
Thank you Felix. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
