FS#78213 - [linux] 6.2.11-arch1-1 doesn't recognize my usb3 external disk WD1Tb

Attached to Project: Arch Linux
Opened by Oscar (archlinuxforever) - Sunday, 16 April 2023, 12:20 GMT
Last edited by Toolybird (Toolybird) - Thursday, 20 April 2023, 21:18 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

https://bugzilla.kernel.org says: "If you did not compile your own kernel from scratch, you are probably in the wrong place. Please use the following links to report a bug to your distribution instead:", so I clicked on Arch and this is the web page where I must report the issue.

I have 3 disks on my PC and one usb3 external disk for backups.

Today I made full system upgrade on my previous Arch Linux disk and I have an issue. The first boot, as usual, recognized my external usb3 disk, but after full system upgrade reported an error:

[ TIME ] Timed out waiting for device /dev/disk/by-uuid/********-****-****-****-************.
[DEPEND] Dependency failed for /run/media/user/WD1Tb.

Arch Linux 6.2.11-arch1-1 (tty1)

disk1Tb login:

Led stays without blink (usually blinks), I unplugged it and plugged it again several times, but it continued without recognize it

The usual folder where was mounted disappear (/run/media/user/WD1Tb). I created folder and mounted disk (without error), but folder was empty.

$ sudo mount /run/media/user/WD1Tb/

So, I reboot my PC with an script. When the command sync was executed, the kernel hanged.

I let my PC for about 4 hours and didn't reboot, so I reboot with ALT+SysRq R+E+I+S+U+B.

I attached log files.


Additional info:
* package version(s)

Arch Linux 6.2.11-arch1-1

* config and/or log files etc.

I attached them.

* link to upstream bug report, if any

N/A

Steps to reproduce:

I made full system upgrade today and after reboot, the kernel don't recognize my external usb3 disk WD1Tb.

I boot on my Debian and Arch Linux disk4Tb and they recognize my usb3 external disk, so the disk is ok.
This task depends upon

Closed by  Toolybird (Toolybird)
Thursday, 20 April 2023, 21:18 GMT
Reason for closing:  Not a bug
Additional comments about closing:  See comments
Comment by Oscar (archlinuxforever) - Sunday, 16 April 2023, 12:26 GMT
I attached log files and picture from monitor before reboot with ALT+SysReq+R+E+I+S+U+B.

If you need more information, logs, etc. don't hesitate to ask me.
   202304160631.ps_aux.log.xz (3.9 KiB)
   202304160628.error_boot.log.xz (0.2 KiB)
   202304160635.screen_hanged.lo... (1.8 KiB)
   202304160653.ps_aux.log.xz (3.9 KiB)
   202304160733.journalctl_this_... (29.9 KiB)
   202304160753.ps_aux.log.xz (4.6 KiB)
   202304160733.journalctl_last_... (25 KiB)
   IMG2_20230416_115841.jpg (1.56 MiB)
   202304161404.lshw.log.xz (0.3 KiB)
   Last_full_system_upgrade.txt.... (6.2 KiB)
Comment by Oscar (archlinuxforever) - Sunday, 16 April 2023, 12:29 GMT
I forgot to set Category, Severity and Architecture. I can't change them. Architecture is x86_64, Category is Kernel and Severity is High.
Comment by Toolybird (Toolybird) - Sunday, 16 April 2023, 21:59 GMT
This kind of thing is more suited to our dedicated support channels (forum/IRC/mailing lists/Reddit/etc). Instead of just dumping a whole pile of logfiles, your first steps should be to apply some effort in troubleshooting it yourself. There is no indication of an Arch packaging bug here. If you think it's the kernel, have you tried downgrading the kernel pkg? If an earlier kernel works then it's a kernel regression and you can follow the usual advice [1]. I see you are you using apparmor and other lsm stuff. I also see in your journal a hung kernel task related to a USB hub, so I'd start your troubleshooting there.

[1] https://wiki.archlinux.org/title/Kernel#Debugging_regressions
Comment by Oscar (archlinuxforever) - Thursday, 20 April 2023, 18:47 GMT
Sorry, I though that was a clear kernel bug because previous kernel worked and after full system upgrade it didn't work.

It is my fault that I didn't reboot the kernel to try if was a temporary issue. Today I switch on my PC and it didn't report any issue, so I booted five times without any issue.

You can close this task.

Loading...