I bought a new USB hard disk yesterday and I was copying my files from my DVD archive. I copied around 200 GB when suddenly I found out the disk was no longer readable. The disk was also making some beeping sounds.
Sorry, I don't know if this is related to the kernel but there was another bug (#191644) filed few years ago which was filed against the kernel was closed without any solution. I was using 22.214.171.124-0 when this happened.
A dmesg output is attached.
I panicked and shutdown the system immediately. I then turned the system on again a little later and booted into the latest kernel (126.96.36.199-5) and I started using the drive again without any issues.
So, what really happened? Was this a bug with the kernel or some other problem with the OS? If so, has it been fixed already? Or is this a faulty drive (The drive was purchased less than 24 hours ago)
Created attachment 522099 [details]
Are you still having issues with this drive? I don't see anything that immediately suggests it is a kernel issue. It seems that the drive was offlined and I/O to it stopped.
If you're still seeing things like this happen, you might try adding usbcore.autosuspend=-1 to your kernel command line and see if that helps.
I saw that error just once. I had that error twice on another drive. Why did the drive get offlined like that? I thought it had something to do with the kernel. I guess I was wrong then.
I'll post again if I ever see that happening again. I'll try usbcore.autosuspend=-1 like you suggested.
OK. For now, we'll close this bug out. If you see it again, please reopen.