| Summary: | sys-kernel/hardened-sources - blk_update_request: I/O error, dev sdb, sector | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Lagu <felipematas> |
| Component: | [OLD] Core system | Assignee: | The Gentoo Linux Hardened Kernel Team (OBSOLETE) <hardened-kernel+disabled> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | hardened, kernel, pageexec |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
blkid
emerge --info hwinfo lspci-vvvv lsusb lsusb-vvvv usb-devices |
||
Created attachment 416984 [details]
blkid
Created attachment 416986 [details]
emerge --info
Created attachment 416988 [details]
hwinfo
Created attachment 416990 [details]
lspci-vvvv
Created attachment 416992 [details]
lsusb
Created attachment 416994 [details]
lsusb-vvvv
Created attachment 416996 [details]
usb-devices
Okay cc-ing upstream. They should have enough to debug. how is this related to grsec? are there any logs pointing at it? also what happened to the vanilla sources experiment? mm, for the moment i can't reproduce it with the kernel upgrade (4.2.6), i'll notify if i can get it again. Thx. Hi, well now i can get some info. I can get the error message but with other circustances, basically unpluging the hdd without unmount it, but the question in this case is ¿why the is disconnected?, in this case obvioulsly i disconet it, but in the main issue that was along.... Are a probability of the cable but the pc and the hdd was in a stand, and i was seeing videos on the tv so i can't move it accidently.......... An appart issue is ¿why the error message show always the same device (sdc, sdd, etc) when it change with every reconnection? Cya. |
Hi ppl, here a bug, i'm using an extern enclosure with a notebook hdd, but for some reason start this error messages, i already check smart info and i run fsck to check logical problems but the hdd is fine, when this happend the hdd it seems to be disconected and coneted again from the kernel, and the letters change (sdb then sdd and others), but you can see al the errors show the same device, sdb2, but in this moment blkid don't show uny sdb2 or sdb device but i know is it. When i take the logs this is the usb port of the enclosure: Bus 004 Device 009: ID 174c:1053 ASMedia Technology Inc. The next days i'll try with vanilla sources to check it. nov 13 20:07:45 jbx4mY1Exa kernel: blk_update_request: I/O error, dev sdb, sector 0 nov 13 20:07:45 jbx4mY1Exa kernel: Buffer I/O error on dev sdb2, logical block 205553664, lost sync page write nov 13 20:07:45 jbx4mY1Exa kernel: JBD2: Error -5 detected when updating journal superblock for sdb2-8. nov 13 20:07:45 jbx4mY1Exa kernel: Aborting journal on device sdb2-8. nov 13 20:07:45 jbx4mY1Exa kernel: Buffer I/O error on dev sdb2, logical block 205553664, lost sync page write nov 13 20:07:45 jbx4mY1Exa kernel: JBD2: Error -5 detected when updating journal superblock for sdb2-8. nov 13 20:49:30 jbx4mY1Exa kernel: blk_update_request: I/O error, dev sdb, sector 0 nov 13 20:49:31 jbx4mY1Exa kernel: Buffer I/O error on dev sdb2, logical block 205553664, lost sync page write nov 13 20:49:31 jbx4mY1Exa kernel: JBD2: Error -5 detected when updating journal superblock for sdb2-8. nov 13 20:49:31 jbx4mY1Exa kernel: Aborting journal on device sdb2-8. nov 13 20:49:31 jbx4mY1Exa kernel: Buffer I/O error on dev sdb2, logical block 205553664, lost sync page write nov 13 20:49:31 jbx4mY1Exa kernel: JBD2: Error -5 detected when updating journal superblock for sdb2-8. nov 14 17:59:43 jbx4mY1Exa kernel: blk_update_request: I/O error, dev sdb, sector 784097760 nov 14 17:59:43 jbx4mY1Exa kernel: blk_update_request: I/O error, dev sdb, sector 0 nov 14 17:59:43 jbx4mY1Exa kernel: blk_update_request: I/O error, dev sdb, sector 784098000 nov 14 17:59:45 jbx4mY1Exa kernel: Buffer I/O error on dev sdb2, logical block 205553664, lost sync page write nov 14 17:59:45 jbx4mY1Exa kernel: JBD2: Error -5 detected when updating journal superblock for sdb2-8. nov 14 17:59:45 jbx4mY1Exa kernel: Aborting journal on device sdb2-8. nov 14 17:59:45 jbx4mY1Exa kernel: Buffer I/O error on dev sdb2, logical block 205553664, lost sync page write nov 14 17:59:45 jbx4mY1Exa kernel: JBD2: Error -5 detected when updating journal superblock for sdb2-8. Thx.