Problem popping on accessing pluged in hardware

[mylo]

Hi all,


since (may be longer) time but now clear, I experience a problem on plugging hardware.
Problem appeared now, when I wanted to dd to a sdcard for one of my raspis. Impossible, so first guess: my card reader is defect or corrupted. So I lent one from a neighbour, same problem.


I tried all blkid and mod checks, mods ok, but no sd* showed up.


I remember, that a week ago I attachad a hd from a tv receiver by ide>sata connector to grab my records from that. But the disk was not recognized nor showed up in no kind.


So usb or sata no dev recognition on these hardwares.


I can deliver all infos, fear a hw problem. Any ideas what to check on top? My inst is from 2013, currently upgraded over generations of forks.


Thanks for hints before solving by a big migration/setup.

[Geier0815]

First try should be to boot from a live-DVD or stick. Will it work then it's a problem with your installation, if it's not working it seems to be a hardware problem.
This would be my first step to resolv such an error.

[mylo]

thanks for downing my horizon, so that I can see this very logical stepping forward to ex-/include areas of root cause. I will try and report. Thanks!

[mylo]

hallo Geier0815,


I fooded the dvd drive with a Mint Cinnamon 64 bit, prioritised bios to booting dvd.


1 By just letting run/boot up, it stalled in the showup of the green M logo, nothing more happens after that.


2 Starting up by the [forgot the name] light mode, Mint's booting trial shows up errors by errors. I monitored the very hard hard fight on CLI feedbacks, how Mint tried to boot up, reducing requirements after requirements, to getting the bloody fucking job done. Unfortunately ending successlessly.


Question:

Is this already a hint onto a HW failure?
[by the way, why board forces font size reduction?]

What can I test/try on top?

Thanks for any help, preferring a reinstall instead of a costly HW migration (procurement...

Thanks for any help! btw: how to disbale automatic font size reduction in this board?

[mylo]

Hi all,


a new burned Mint dvd ran up fine. On live dvd the usb stick did also not show up. So, I conclude according to Geier0815's root cause localization strategy's first step, the problem is in my inst.


I would like to use may 8 year old inst as long as possible. So are there any hints on how to detect the area of failure further?


Thanks in advance!

[gnasch]

Hi,
don't know if this helps:
open a konsole window, type journalctl -f.
output when pushing in a usb stick:

Feb 13 14:47:59 Nh364Mz kernel: usb 6-2: new high-speed USB device number 2 using ehci-pci
Feb 13 14:48:00 Nh364Mz kernel: usb 6-2: New USB device found, idVendor=058f, idProduct=6387, bcdDevice= 1.05
Feb 13 14:48:00 Nh364Mz kernel: usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 13 14:48:00 Nh364Mz kernel: usb 6-2: Product: Mass Storage
Feb 13 14:48:00 Nh364Mz kernel: usb 6-2: Manufacturer: Generic
Feb 13 14:48:00 Nh364Mz kernel: usb 6-2: SerialNumber: D1B6A22A
Feb 13 14:48:00 Nh364Mz mtp-probe[139483]: checking bus 6, device 2: "/sys/devices/pci0000:00/0000:00:1d.7/usb6/6-2"
Feb 13 14:48:00 Nh364Mz mtp-probe[139483]: bus: 6, device: 2 was not an MTP device
Feb 13 14:48:00 Nh364Mz kernel: usb-storage 6-2:1.0: USB Mass Storage device detected
Feb 13 14:48:00 Nh364Mz kernel: scsi host5: usb-storage 6-2:1.0
Feb 13 14:48:00 Nh364Mz kernel: usbcore: registered new interface driver usb-storage
Feb 13 14:48:00 Nh364Mz kernel: usbcore: registered new interface driver uas
Feb 13 14:48:00 Nh364Mz mtp-probe[139521]: checking bus 6, device 2: "/sys/devices/pci0000:00/0000:00:1d.7/usb6/6-2"
Feb 13 14:48:00 Nh364Mz mtp-probe[139521]: bus: 6, device: 2 was not an MTP device
Feb 13 14:48:01 Nh364Mz kernel: scsi 5:0:0:0: Direct-Access     Generic  Flash Disk       8.07 PQ: 0 ANSI: 4
Feb 13 14:48:01 Nh364Mz kernel: scsi 5:0:0:0: Attached scsi generic sg0 type 0
Feb 13 14:48:01 Nh364Mz kernel: sd 5:0:0:0: [sdb] 16384000 512-byte logical blocks: (8.39 GB/7.81 GiB)
Feb 13 14:48:01 Nh364Mz kernel: sd 5:0:0:0: [sdb] Write Protect is off
Feb 13 14:48:01 Nh364Mz kernel: sd 5:0:0:0: [sdb] Mode Sense: 23 00 00 00
Feb 13 14:48:01 Nh364Mz kernel: sd 5:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Feb 13 14:48:01 Nh364Mz kernel:  sdb: sdb1 sdb2
Feb 13 14:48:01 Nh364Mz kernel: sd 5:0:0:0: [sdb] Attached SCSI removable disk
Feb 13 14:48:02 Nh364Mz dbus-daemon[845]: [system] Activating service name='org.kde.kded.smart' requested by ':1.51' (uid=1026 pid=1672 comm="/usr/bin/kded5 ") (using servicehelper)


when pulling out the stick:


Feb 13 14:48:12 Nh364Mz kernel: usb 6-2: USB disconnect, device number 2

[dibl]

So are there any hints on how to detect the area of failure further?

To discover whether there is a hardware problem on your system, you need to try at least one more USB hotplug device. I don't think it has to be a thumb drive -- it could be a mouse or a printer or a cell phone cable. If it detects and connects another device, then the problem is not your system hardware. It might be your thumb drive hardware, or it might be a system software setting. Try gnasch's method and look for errors.  Good luck!

[mylo]

Thanks gnasch and dibl, I will do so [size=78%][/size]and report further.[size=78%][/size]

Right now I was experimenting:
I unplugged the card reader on the front panel (offfering various sizes) from the motherboard.


AFTER THAt NOW:


I can plug USB sticks and they pop-up ordinarily.
I can plug SD cards via an adapter with USB plug -> no detection!


Strange, will come back with more results!

[mylo]

So listing ob usb stick plug unplug

Code Select Expand

cat 2.txt | grep usb
Feb 14 15:41:42 tuap kernel: usb 1-4: new high-speed USB device number 12 using xhci_hcd
Feb 14 15:41:42 tuap kernel: usb 1-4: New USB device found, idVendor=1f75, idProduct=0917, bcdDevice= 0.01
Feb 14 15:41:42 tuap kernel: usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 14 15:41:42 tuap kernel: usb 1-4: Product: Intenso Ultra Line
Feb 14 15:41:42 tuap kernel: usb 1-4: Manufacturer: Innostor Technology
Feb 14 15:41:42 tuap kernel: usb 1-4: SerialNumber: 14110400005124
Feb 14 15:41:42 tuap kernel: usb-storage 1-4:1.0: USB Mass Storage device detected
Feb 14 15:41:42 tuap kernel: scsi host7: usb-storage 1-4:1.0
Feb 14 15:41:42 tuap mtp-probe[203740]: checking bus 1, device 12: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4"
Feb 14 15:41:42 tuap mtp-probe[203754]: checking bus 1, device 12: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4"
Feb 14 15:41:44 tuap usbmount[203812]: /dev/sde1 does not contain a filesystem or disklabel
Feb 14 15:41:44 tuap systemd-udevd[203757]: sde1: Process '/usr/share/usbmount/usbmount add' failed with exit code 1.
Feb 14 15:41:49 tuap usbmount[203909]: executing command: mount -tvfat -osync,noexec,nodev,noatime,nodiratime,gid=users,dmask=0007,fmask=0117 /dev/sde2 /media/usb0
Feb 14 15:41:49 tuap usbmount[203920]: executing command: run-parts /etc/usbmount/mount.d
Feb 14 15:41:51 tuap kernel: usb 1-4: USB disconnect, device number 12
Feb 14 15:41:59 tuap systemd-udevd[203737]: sde3: Process '/usr/share/usbmount/usbmount add' failed with exit code 2.
Feb 14 15:41:59 tuap usbmount[204940]: executing command: umount -l /media/usb0
Feb 14 15:41:59 tuap usbmount[204943]: executing command: run-parts /etc/usbmount/umount.d

and on sd card:

Code Select Expand

cat 3.txt | grep usb
mylo@tuap:~$

so nothing (tested 3 sd cards).

[gnasch]

this may be a very stupid question 
I have tried to reproduce this with my micro sd card, and found that it depends a lot
on the holder, how you set the micro into the holder, which side up and down,
if you try to center it or push it left or right a little.

The computer will lack *any* response in the logs only
when there is no contact or no micro sd in the holder.

so - are you "holding it wrong" (Apple ref)?
do you have another holder to try?

best, gnasch

[mylo]

there are no stupid questions, i also thought about.
My neighbour from whom I lent the card holder, will check it in parallel.
I checked carefully for the right orientation, will report soon.
Thanks for that question!

[mylo]

neighbours test positive, so a defect! Thanks to all and will finally report on result.
regards