Incessant bad block requests
Bug #153344 reported by
Hans van Dok
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?
Changed in linux-source-2.6.20: | |
status: | New → Incomplete |
Changed in linux-source-2.6.20: | |
status: | Incomplete → New |
Changed in linux-source-2.6.20: | |
status: | New → Incomplete |
To post a comment you must log in.
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...