Re: My external disks no longer mont
Hi,
Thanks for your reply. After reboot, the problem is fixed. Frankly it is
strange as I had already rebooted, I just have one kernel release, but
well... it works.
Thanks for your help
Regards
Jean-Philippe MENGUAL
Le 28/06/2019 à 11:21, Reco a écrit :
> Hi.
>
> On Fri, Jun 28, 2019 at 11:09:37AM +0200, Jean-Philippe MENGUAL wrote:
>>
>> Here is what I get now when I plug in a USB stick or disk:
>> https://paste.debian.net/1089600/
>>
>> I think it is a bug, as I use Sid. Where should I report? Kernel? udev? systemd?
>
> A relevant part of dmesg follows:
>
> 2.168328] usb 2-1.2: new high-speed USB device number 9 using ehci-pci
> [218062.284596] usb 2-1.2: New USB device found, idVendor=1bcf, idProduct=0c31, bcdDevice= 1.0f
> [218062.284602] usb 2-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
> [218062.284606] usb 2-1.2: Product: USB to Serial-ATA bridge
> [218062.284609] usb 2-1.2: Manufacturer: Sunplus Innovation Technology.
> [218062.284611] usb 2-1.2: SerialNumber: FAFFFFF0FFF0FFFD0F919597
> [218062.363885] usb_storage: disagrees about version of symbol __dynamic_dev_dbg
> [218062.363888] usb_storage: Unknown symbol __dynamic_dev_dbg (err -22)
> [218062.363908] usb_storage: disagrees about version of symbol wake_up_process
>
>
> The most likely reason of that is the version mismatch between the
> current kernel and a kernel module.
> A typical Debian kernel package contains both the kernel and a modules
> built at the same time, so this should be impossible.
>
> One of the way to achieve this is to update the kernel, refrain from
> rebooting and trying to load a kernel module.
> Another one is to break a bootloader forcing it to load an older kernel.
>
> In short - a reboot can fix it, and if it does not - fix your
> bootloader.
>
> Reco
>
Reply to: