Kernel 6.12 makes external USB3 drive disappear. #6755
Comments
|
Please post the full output of Weirdness: on 6.12 the Asmedia chipset doesn't report a serial number string, but both WD drives do on both 6.6 and 6.12. |
|
Sure! Here ya go :) 6.12 dmesg |
|
Interesting bit by comparison, can't set config#1, error -110 below: 6.6 6.12 |
That's bad. This is before the usb-storage has bound to the disk's interface, so it's in the very early device setup. This is going to be a fun regression to diagnose. Does the device behave any differently if you hotplug it after booting? |
|
On 6.12, if I unplug it from the USB3 hub, and replug it back in, I can see the device pop up in OMV. But it's completely unusable there. It populates the device list but is uneditable. So, soooomething is happening. But not fully. I can't quite remember where in the interface this happens and I'm not home right now to test it. Can try later, or if you have another command I should run pre-post hotswap I'd be glad to paste it here :) And thanks so much! |
|
The fact that the device "appears" but is inaccessible suggests that it failed further along. Run |
|
Well, what was reproducible 100% of the time, time after time, for the whole day, is now not. Maddening. The drive appears in both 6.6 and 6.12. I'll keep an eye on it. Next time it does it, if it does it, I'll open up this issue. Thanks for your time thus far |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
Upgrading to Kernel 6.12 kills one of my external USB3 EXT4 drives.
I get a Kernel message: kernel: /dev/disk/by-uuid/e0875765-bbc0-458e-b40a-f4d91b5fcbb1: Can't lookup blockdev
The drive doesn't show up in OMV7 or with blkid
Downgrading to 6.6 fixes the issue completely. I downgraded using sudo
rpi-update 8bd0d75837d6a99138c7cbbc24888601b220405aFine to live here for a while, but eventually one must keep up to date for security patches etc.
While I'm the furthest thing from an Advanced user, since this kernel is now master, I was hoping anyone here could help shed light on how I might solve this, and what additional logs I could share to illuminate the problem.
System is: RaspiOS Lite, Latest and fully updated. OMV7 running on top. Raspi 5 4gb. Working brilliantly since Raspi5 release. This is not a migrated system. Fresh install and set up. Drive in Question is a transcend StoreJet (ST2000LM003 HN-M201RAD), about a decade old. But in perfect working condition.
My other drives, two WD MyBook External USB3's work great no matter the kernel version. Just the transcend is saying no to whatever commits happened between 6.6 and 6.12.
Thanks!
Steps to reproduce the behaviour
Downgrade to 6.6 - Drive appears, works, read and writable and is fully performant as expected.
sudo rpi-update 8bd0d75837d6a99138c7cbbc24888601b220405aUpgrade to 6.12 - Drive disappears completely
sudo rpi-updateDowngrade to 6.6 - Drive is back
sudo rpi-update 8bd0d75837d6a99138c7cbbc24888601b220405aDevice (s)
Raspberry Pi 5
System
Raspberry Pi reference 2024-07-04
2025/03/27 00:16:44
Copyright (c) 2012 Broadcom
version 897f94ed (release) (embedded)
Working:
Linux raspberrypi 6.6.77-v8-16k+ #1851 SMP PREEMPT Thu Feb 13 13:02:57 GMT 2025 aarch64 GNU/Linux
and issue on:
Linux raspberrypi 6.12.21-v8-16k+ #1868 SMP PREEMPT Mon Mar 31 17:10:57 BST 2025 aarch64 GNU/Linux
Logs
lsusb -v for Linux raspberrypi 6.6.77-v8-16k+ #1851 SMP PREEMPT Thu Feb 13 13:02:57 GMT 2025 aarch64 GNU/Linux
lsusb -v for Linux raspberrypi 6.12.21-v8-16k+ #1868 SMP PREEMPT Mon Mar 31 17:10:57 BST 2025 aarch64 GNU/Linux
Additional context
No response
The text was updated successfully, but these errors were encountered: