Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 565790 - sys-kernel/hardened-sources - blk_update_request: I/O error, dev sdb, sector
Summary: sys-kernel/hardened-sources - blk_update_request: I/O error, dev sdb, sector
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: The Gentoo Linux Hardened Kernel Team (OBSOLETE)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-14 22:51 UTC by Lagu
Modified: 2015-11-25 00:07 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
blkid (blkid,882 bytes, text/plain)
2015-11-14 22:51 UTC, Lagu
Details
emerge --info (emerge-info,21.36 KB, text/plain)
2015-11-14 22:51 UTC, Lagu
Details
hwinfo (hwinfo,206.82 KB, text/plain)
2015-11-14 22:51 UTC, Lagu
Details
lspci-vvvv (lspci-vvvv,30.86 KB, text/plain)
2015-11-14 22:52 UTC, Lagu
Details
lsusb (lsusb,624 bytes, text/plain)
2015-11-14 22:52 UTC, Lagu
Details
lsusb-vvvv (lsusb-vvvv,56.72 KB, text/plain)
2015-11-14 22:52 UTC, Lagu
Details
usb-devices (usb-devices,3.57 KB, text/plain)
2015-11-14 22:52 UTC, Lagu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lagu 2015-11-14 22:51:07 UTC
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.
Comment 1 Lagu 2015-11-14 22:51:25 UTC
Created attachment 416984 [details]
blkid
Comment 2 Lagu 2015-11-14 22:51:43 UTC
Created attachment 416986 [details]
emerge --info
Comment 3 Lagu 2015-11-14 22:51:59 UTC
Created attachment 416988 [details]
hwinfo
Comment 4 Lagu 2015-11-14 22:52:15 UTC
Created attachment 416990 [details]
lspci-vvvv
Comment 5 Lagu 2015-11-14 22:52:28 UTC
Created attachment 416992 [details]
lsusb
Comment 6 Lagu 2015-11-14 22:52:45 UTC
Created attachment 416994 [details]
lsusb-vvvv
Comment 7 Lagu 2015-11-14 22:52:59 UTC
Created attachment 416996 [details]
usb-devices
Comment 8 Anthony Basile gentoo-dev 2015-11-22 18:13:37 UTC
Okay cc-ing upstream.  They should have enough to debug.
Comment 9 PaX Team 2015-11-22 19:39:32 UTC
how is this related to grsec? are there any logs pointing at it? also what happened to the vanilla sources experiment?
Comment 10 Lagu 2015-11-22 22:58:52 UTC
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.
Comment 11 Lagu 2015-11-25 00:07:22 UTC
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.