Incessant bad block requests

Bug #153344 reported by Hans van Dok
2
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I just upgraded from Feisty (kernel 2.6.20-16-386) to Gutsy (kernel 2.6.22-14-386). When I try to boot that new kernel, everything seems to be going okay for a while. I get the regular Ubuntu + percentage bar, but after a while the screen drops to console and it keeps printing

[ xxx.xxxxxx] sd 4:0:0:0 [sdb] Bad block number requested

When I go back to the previous kernel this doesn't happen.

Can anyone help?

Revision history for this message
Hans van Dok (dok) wrote :

Addition: today I had to reboot and accidentally ran the new kernel. This time it seemed to boot up okay. But after a while I noticed the external USB drives didn't appear and they weren't around as dev/sdX either.
I turned them off and on. They still wouldn't come on, and one of them was making a scratchy sound. When I checked out dmesg, I saw that the "Bad block number requested" messages kept spewing there, but now for one of those drives!

...
[ 7599.985688] sd 9:0:0:0: [sdd] Bad block number requested
[ 7599.986058] sd 9:0:0:0: [sdd] Bad block number requested
[ 7599.986190] sd 9:0:0:0: [sdd] Bad block number requested
...

etc..

I think this might be relevant...

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Now that the 7.10 Gutsy Gibbon release of Ubuntu is out, we were wondering if you can still reproduce this issue. Could you please download and try the new version of Ubuntu from http://www.ubuntu.com/getubuntu/download and report back your results. If the issue is still present in the new release, please attach the following information:
* uname -a > uname-a.log
* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log
Please be sure to attach each file as a separate attachment. For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

Changed in linux-source-2.6.20:
status: New → Incomplete
Revision history for this message
Hans van Dok (dok) wrote :

attachment #1

Revision history for this message
Hans van Dok (dok) wrote :

attachment #2

Revision history for this message
Hans van Dok (dok) wrote :

attachment #3

This one is not fun. It just keeps going like that too.

Revision history for this message
Hans van Dok (dok) wrote :

attachment #4

Kees Cook (kees)
Changed in linux-source-2.6.20:
status: Incomplete → New
Kees Cook (kees)
Changed in linux-source-2.6.20:
status: New → Incomplete
Revision history for this message
Hans van Dok (dok) wrote :

Please close this bug. I decided to do a fresh install from the 7.10 CD and everything works now.
Thank you for the attention.

Revision history for this message
Brian Murray (brian-murray) wrote :

This bug report is being closed due to your last comment regarding this being fixed with a reinstall. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the drop down box. You can learn more about bug statuses at http://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

Changed in linux-source-2.6.20:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.