USB thumbdrive upon insertion shuts computer down?

I’ve got data, software files, jpegs, music on thumbdrive installation mediaS of different sizes (i.e. 8,16,32,64,128,256 gig sizes.) Some are formated Ext4,fat32,exfat. I’ve noticed on two of them when they are inserted into the usb port on the computer the whole system shuts down. I hit the power button and then everything comes back on after I remove the thumbdrive. What could be causing the thumbdrive to shut down the system when it is inserted? Any idea’s.

Rich;)

I think I remember an old kernel bug that sounds familiar to this. Is the kernel up to date?

Please be more specific. Upon insertion of the USB drive, did the system go through a normal shut down process (with a bunch of console text appearing like usual)? Or did the screen just go black as if the power was cut off? If the system did go through a normal shut down process after you insert the USB drive, then the journal logs may provide clues as to what triggered the shutdown process.

What do you mean? Do you mean to say that the system will only boot if you unplug the usb drive? So if you leave the usb drive plugged in and then press the power button, the system won’t boot? If that’s the case, I strongly suspect a hardware issue.

Also, what do you mean by “everything comes back on”? Do you mean the system go through the normal boot process? Or do you mean the screen just came back on and the system was in the same state as before? Please clarify.

  1. System is running properly
  2. I insert USB thumbdrive into port.
  3. Screen goes black and the system shuts off ( turns off. . . no process is seen on the screen. It just goes black and everythng just turns off.)
  4. I remove the thumbdrive completely. System is still off.
  5. I press the power button and the system turns backs on. . . i.e. screen reappears , wifi reconnects, cpu fan begins spinning and the system is once again operational without a reboot.

I’m using the 6.16.-1 stable kernal. My system uses 32 gig ram and 3700X cpu. (AM4, with latest motherboard bios.)

Rich;)

Just so I’m understading correctly. So when you pressed the power button, it looked like you just wake the system up from sleep or hibernation?

??? Come again? Do you mean kernel 6.6.16-lts? The stable kernel is currently at version 6.7.4

Looks like a power issue, power shortcut in the usb drive?

Try the thumb drive on a different computer, if the result is the same your thumb drive is “kaput”

1 Like

It is unclear whether the power was cut off completely when the drive is plugged in. The OP claimed that when he pressed the power button after pulling out the USB drive, the system didn’t go through a boot process (as it the screen just reappeared as if it woke up from sleep or hibernation).

I would say there is something that is triggering the system to go into hibernation. What does your Xorg log say?

6/16.-1 -lts kernel . . .

It seems like the system goes into hibernation mode. . . . .

Rich . .

I initialized the logs (including xorg) a while ago. I will run the process again and see if it gives me the information I can present to you.

For the record, going into hibernation and “computer shutting down” are two completely different things.

What you can do now is to figure out what triggered the hibernation mode when you insert the USB drive. For that, you need to check the journal logs:

  1. Plug in the problematic USB stick.
  2. Let the system enter hibernation.
  3. Remove USB stick.
  4. Press the power button to exit hibernation.
  5. Run journalctl -b 0 | eos-sendlog and post the resulting url here.

I’m not showing anything in terminal . . . . nothing pops up.

I looked in eos-log-tool.logs and in x.0rg (section) couldn’t see anything unusual I think.

https://0x0.st/HddH.txt

Rich :wink:

That’s to be expected. Because you’ve just piped everything into eos-sendlog.

Feb 14 07:25:22 richard-ms7c91 kernel: usb 1-3: new high-speed USB device number 7 using xhci_hcd
Feb 14 07:25:22 richard-ms7c91 kernel: usb 1-3: New USB device found, idVendor=0781, idProduct=5575, bcdDevice= 1.00
Feb 14 07:25:22 richard-ms7c91 kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 14 07:25:22 richard-ms7c91 kernel: usb 1-3: Product: Cruzer Glide
Feb 14 07:25:22 richard-ms7c91 kernel: usb 1-3: Manufacturer: SanDisk
Feb 14 07:25:22 richard-ms7c91 kernel: usb 1-3: SerialNumber: 20054055201D7F024CC8
Feb 14 07:25:22 richard-ms7c91 kernel: usb-storage 1-3:1.0: USB Mass Storage device detected
Feb 14 07:25:22 richard-ms7c91 kernel: scsi host7: usb-storage 1-3:1.0
Feb 14 07:25:22 richard-ms7c91 mtp-probe[7747]: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3"
Feb 14 07:25:22 richard-ms7c91 mtp-probe[7747]: bus: 1, device: 7 was not an MTP device
Feb 14 07:25:22 richard-ms7c91 kernel: usbcore: registered new interface driver uas
Feb 14 07:25:22 richard-ms7c91 mtp-probe[7754]: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3"
Feb 14 07:25:22 richard-ms7c91 mtp-probe[7754]: bus: 1, device: 7 was not an MTP device
Feb 14 07:25:23 richard-ms7c91 kernel: scsi 7:0:0:0: Direct-Access     SanDisk  Cruzer Glide     1.00 PQ: 0 ANSI: 6
Feb 14 07:25:23 richard-ms7c91 kernel: sd 7:0:0:0: Attached scsi generic sg3 type 0
Feb 14 07:25:23 richard-ms7c91 kernel: sd 7:0:0:0: [sdc] 30595072 512-byte logical blocks: (15.7 GB/14.6 GiB)
Feb 14 07:25:23 richard-ms7c91 kernel: sd 7:0:0:0: [sdc] Write Protect is off
Feb 14 07:25:23 richard-ms7c91 kernel: sd 7:0:0:0: [sdc] Mode Sense: 43 00 00 00
Feb 14 07:25:23 richard-ms7c91 kernel: sd 7:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 07:25:23 richard-ms7c91 kernel:  sdc: sdc1 sdc2 sdc3
Feb 14 07:25:23 richard-ms7c91 kernel: sd 7:0:0:0: [sdc] Attached SCSI removable disk
Feb 14 07:25:23 richard-ms7c91 udisksd[1230]: Mounted /dev/sdc1 at /run/media/richardc/68AC-E98F on behalf of uid 1000
Feb 14 07:25:23 richard-ms7c91 kernel: FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Feb 14 07:25:24 richard-ms7c91 udisksd[1230]: Mounted /dev/sdc2 at /run/media/richardc/681A-458D on behalf of uid 1000
Feb 14 07:25:24 richard-ms7c91 kernel: FAT-fs (sdc2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Feb 14 07:25:24 richard-ms7c91 udisksd[1230]: Mounted /dev/sdc3 at /run/media/richardc/66FB-98C7 on behalf of uid 1000
Feb 14 07:25:24 richard-ms7c91 kernel: FAT-fs (sdc3): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Feb 14 07:25:28 richard-ms7c91 kernel: usb 1-3: USB disconnect, device number 7
Feb 14 07:25:28 richard-ms7c91 kernel: device offline error, dev sdc, sector 65 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2
Feb 14 07:25:28 richard-ms7c91 kernel: Buffer I/O error on dev sdc1, logical block 1, lost async page write
Feb 14 07:25:28 richard-ms7c91 udisksd[1230]: Cleaning up mount point /run/media/richardc/68AC-E98F (device 8:33 no longer exists)
Feb 14 07:25:28 richard-ms7c91 udisksd[1230]: Cleaning up mount point /run/media/richardc/681A-458D (device 8:34 no longer exists)
Feb 14 07:25:28 richard-ms7c91 systemd[1]: run-media-richardc-68AC\x2dE98F.mount: Deactivated successfully.
Feb 14 07:25:28 richard-ms7c91 udisksd[1230]: Cleaning up mount point /run/media/richardc/66FB-98C7 (device 8:35 no longer exists)
Feb 14 07:25:28 richard-ms7c91 systemd[1]: run-media-richardc-681A\x2d458D.mount: Deactivated successfully.
Feb 14 07:25:28 richard-ms7c91 systemd[1]: run-media-richardc-66FB\x2d98C7.mount: Deactivated successfully.
Feb 14 07:25:47 richard-ms7c91 kernel: usb 1-3: new high-speed USB device number 8 using xhci_hcd
Feb 14 07:25:47 richard-ms7c91 kernel: usb 1-3: New USB device found, idVendor=0781, idProduct=5575, bcdDevice= 1.00
Feb 14 07:25:47 richard-ms7c91 kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 14 07:25:47 richard-ms7c91 kernel: usb 1-3: Product: Cruzer Glide
Feb 14 07:25:47 richard-ms7c91 kernel: usb 1-3: Manufacturer: SanDisk
Feb 14 07:25:47 richard-ms7c91 kernel: usb 1-3: SerialNumber: 4C530001181029110313
Feb 14 07:25:47 richard-ms7c91 kernel: usb-storage 1-3:1.0: USB Mass Storage device detected
Feb 14 07:25:47 richard-ms7c91 kernel: scsi host7: usb-storage 1-3:1.0
Feb 14 07:25:47 richard-ms7c91 mtp-probe[7829]: checking bus 1, device 8: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3"
Feb 14 07:25:47 richard-ms7c91 mtp-probe[7829]: bus: 1, device: 8 was not an MTP device
Feb 14 07:25:47 richard-ms7c91 mtp-probe[7835]: checking bus 1, device 8: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3"
Feb 14 07:25:47 richard-ms7c91 mtp-probe[7835]: bus: 1, device: 8 was not an MTP device
Feb 14 07:25:48 richard-ms7c91 kernel: scsi 7:0:0:0: Direct-Access     SanDisk  Cruzer Glide     1.00 PQ: 0 ANSI: 6
Feb 14 07:25:48 richard-ms7c91 kernel: sd 7:0:0:0: Attached scsi generic sg3 type 0
Feb 14 07:25:48 richard-ms7c91 kernel: sd 7:0:0:0: [sdc] 30842880 512-byte logical blocks: (15.8 GB/14.7 GiB)
Feb 14 07:25:48 richard-ms7c91 kernel: sd 7:0:0:0: [sdc] Write Protect is off
Feb 14 07:25:48 richard-ms7c91 kernel: sd 7:0:0:0: [sdc] Mode Sense: 43 00 00 00
Feb 14 07:25:48 richard-ms7c91 kernel: sd 7:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 07:25:48 richard-ms7c91 kernel:  sdc: sdc1
Feb 14 07:25:48 richard-ms7c91 kernel: sd 7:0:0:0: [sdc] Attached SCSI removable disk
Feb 14 07:25:48 richard-ms7c91 udisksd[1230]: Mounted /dev/sdc1 at /run/media/richardc/6995-B7AB on behalf of uid 1000
Feb 14 07:25:48 richard-ms7c91 kernel: FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Feb 14 07:25:51 richard-ms7c91 kernel: usb 1-3: USB disconnect, device number 8
Feb 14 07:25:51 richard-ms7c91 kernel: device offline error, dev sdc, sector 2049 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2
Feb 14 07:25:51 richard-ms7c91 kernel: Buffer I/O error on dev sdc1, logical block 1, lost async page write
Feb 14 07:25:51 richard-ms7c91 udisksd[1230]: Cleaning up mount point /run/media/richardc/6995-B7AB (device 8:33 no longer exists)
Feb 14 07:25:52 richard-ms7c91 systemd[1]: run-media-richardc-6995\x2dB7AB.mount: Deactivated successfully.
Feb 14 07:27:28 richard-ms7c91 systemd-logind[781]: Power key pressed short.
Feb 14 07:27:28 richard-ms7c91 systemd-logind[781]: The system will suspend now!

It wasn’t hibernation; it was suspend. Based on these journal entries, it appears that the system detected a power key press shortly after the USB stick was plugged in, which means you pressed the power button after you insert the USB stick, causing the system to go into suspend mode. What made you to press the power button? Did the system become unresponsive right after you insert the USB drive?

Feb 14 07:25:48 richard-ms7c91 kernel: sd 7:0:0:0: [sdc] Attached SCSI removable disk
Feb 14 07:25:48 richard-ms7c91 udisksd[1230]: Mounted /dev/sdc1 at /run/media/richardc/6995-B7AB on behalf of uid 1000
Feb 14 07:25:48 richard-ms7c91 kernel: FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Feb 14 07:25:51 richard-ms7c91 kernel: usb 1-3: USB disconnect, device number 8
Feb 14 07:25:51 richard-ms7c91 kernel: device offline error, dev sdc, sector 2049 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2
Feb 14 07:25:51 richard-ms7c91 kernel: Buffer I/O error on dev sdc1, logical block 1, lost async page write
Feb 14 07:25:51 richard-ms7c91 udisksd[1230]: Cleaning up mount point /run/media/richardc/6995-B7AB (device 8:33 no longer exists)
Feb 14 07:25:52 richard-ms7c91 systemd[1]: run-media-richardc-6995\x2dB7AB.mount: Deactivated successfully.
Feb 14 07:27:28 richard-ms7c91 systemd-logind[781]: Power key pressed short.
Feb 14 07:27:28 richard-ms7c91 systemd-logind[781]: The system will suspend now!

Can you explain these sequence of events? At 07:25, you attached the USB stick. At 07:27, you pressed the power button. Something must have happened in between.

Also, if it isn’t already obvious, there’s something wrong with your USB drive.

After inserting the USB key. . . .system went into hibernation ( os suspend) I assume by what you said. . . . If that’s the case am I to think maybe it will resume out of (hiberation or suspend) on its own if I do nothing? Or will this state this stay for a period of time? I don’t know. . . . what is the sequence of events that take place after this happens?. . I don’t know an am unaware of. . . so I press the power switch thinking this is the only alternative to getting the system to resume it’s activities as it still remains in a (suspect/hiberation state). . . . As to what happens in between I haven’t a clue other than the screen is blanked out and the system appears to have shut down. This is what happens. . . . I did this to show that the problem has repeated itself once again. Pressing the power buttom was to get the system to resume where it left off.

If the usb drive is bad. . . as inferred it will be trash canned. . . .simple enough.

Rich;)

what happens if you press the space bar on the keyboard a few times when it goes into suspend? While the USB in Question is still plugged in?

Oh! Rich! I got that about ~2 years ago …
It was my power supply :upside_down_face:

Is yours OK ? voltages and everything …

tool source (if needed) :

edit: I hope it is software related :pray:, but if you can see a bulged or leaking capacitor inside the power supply then, it might be it … just hoping it’s not :wink:

How it looks like:

1 Like

The only thing that happens when doing this is the darkened LED screen lights up with indications that power is still on and monitor with it’s default settings are shown on the screen. The monitor shows that the video card hasn’t yet interacted with the monitor also and it is searching for a display to show.

Rich;)

Pwr supply is fine. . . .it’s was a brand new 750 watt. (The whole system is less than 6 months old. ) Built from scratch. . . i.e. (all new components).

Rich;)

1 Like

This has happened on two USB thumb drives. . . .a 16 gig and 64 gig SanDisks. 64-gig Sandisk is USB 3.0 compatible.
They are relatively old. . . but articles I have read recently have suggested newer ones are failing because of cheap components inside. . . .(I believe this was in a Tom’s hardware) article. It didn’t state any particular brand that was failing. . . if I remember correctly.

Rich;)

Did you test both on the same USB port? If yes, what happens if you insert them into another port? Are you using the USB ports at the front of your case or are you using the ones directly located at the mainboard I/O. Your system not turning on at all with the USB thumb drive inserted, not even for a short amount of time, makes me suspect a hardware issue, not a software one. As it is happening on multiple USB thumb drives it makes it highly unlikely that the USB drives themselves are the problem. So it could either be a faulty port (inconvenient but I guess you can live with it), or it’s something else that could be more problematic.