Jim Beard
2016-08-03 13:46:15 UTC
Last night I installed kernel-desktop-4.4.16-1.mga5-1-1.mga5, and this
morning found error messages for /dev/sd7. A look at journalctl turned
up additional messages for /dev/sr.
Neither of these is mounted, and the cd/dvd burner had no disk in it.
Deleting the date and machine name from the left of the journalctl line,
it looks like this:
kernel: sr 6:0:0:0: [sr1] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
kernel: sr 6:0:0:0: [sr1] tag#0 Sense Key : Medium Error [current]
kernel: sr 6:0:0:0: [sr1] tag#0 Add. Sense: Unrecovered read error
kernel: sr 6:0:0:0: [sr1] tag#0 CDB: Read(10) 28 00 00 00 90 48 00 00 02
00
kernel: blk_update_request: critical medium error, dev sr1, sector 147744
kernel: sr 6:0:0:0: [sr1] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
kernel: sr 6:0:0:0: [sr1] tag#0 Sense Key : Medium Error [current]
kernel: sr 6:0:0:0: [sr1] tag#0 Add. Sense: Unrecovered read error
kernel: sr 6:0:0:0: [sr1] tag#0 CDB: Read(10) 28 00 00 00 90 48 00 00 02
00
kernel: blk_update_request: critical medium error, dev sr1, sector 147744
kernel: Buffer I/O error on dev sr1, logical block 18468, async page read
kernel: sd 7:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR
driverbyte=DRIVER_SENSE
kernel: sd 7:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current]
[descriptor]
kernel: sd 7:0:0:0: [sdc] tag#0 Add. Sense: No additional sense
information
kernel: sd 7:0:0:0: [sdc] tag#0 CDB: ATA command pass through(16) 85 06
20 00 00 00 00 00
kernel: sd 7:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR
driverbyte=DRIVER_SENSE
kernel: sd 7:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current]
[descriptor]
kernel: sd 7:0:0:0: [sdc] tag#0 Add. Sense: No additional sense
information
kernel: sd 7:0:0:0: [sdc] tag#0 CDB: ATA command pass through(12)/Blank a1
06 20 da 00 00
An attempt to umount sdc7 yields the journalctl message
Aug 03 09:34:19 jdb.home.invalid udisksd[2545]: Cleaning up mount point /
run/media/jim/mblanguage (device 8:39 is not mounted)
The error messages for sdc7 repeat every 10 seconds. The sr1 messages
have not repeated in 50 minutes.
Both devices are old. The cd/dvd burner is on my main machine purchased
fall 2009 and /dev/sdc is an external USB 1TB drive purchased for backup
about that time.
Has anyone else see something like this with the new kernel?
Any ideas why error messages are being generated for a partition and cd
burner that are idle/unmounted?
Suggestions?
Cheers!
jim b.
morning found error messages for /dev/sd7. A look at journalctl turned
up additional messages for /dev/sr.
Neither of these is mounted, and the cd/dvd burner had no disk in it.
Deleting the date and machine name from the left of the journalctl line,
it looks like this:
kernel: sr 6:0:0:0: [sr1] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
kernel: sr 6:0:0:0: [sr1] tag#0 Sense Key : Medium Error [current]
kernel: sr 6:0:0:0: [sr1] tag#0 Add. Sense: Unrecovered read error
kernel: sr 6:0:0:0: [sr1] tag#0 CDB: Read(10) 28 00 00 00 90 48 00 00 02
00
kernel: blk_update_request: critical medium error, dev sr1, sector 147744
kernel: sr 6:0:0:0: [sr1] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
kernel: sr 6:0:0:0: [sr1] tag#0 Sense Key : Medium Error [current]
kernel: sr 6:0:0:0: [sr1] tag#0 Add. Sense: Unrecovered read error
kernel: sr 6:0:0:0: [sr1] tag#0 CDB: Read(10) 28 00 00 00 90 48 00 00 02
00
kernel: blk_update_request: critical medium error, dev sr1, sector 147744
kernel: Buffer I/O error on dev sr1, logical block 18468, async page read
kernel: sd 7:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR
driverbyte=DRIVER_SENSE
kernel: sd 7:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current]
[descriptor]
kernel: sd 7:0:0:0: [sdc] tag#0 Add. Sense: No additional sense
information
kernel: sd 7:0:0:0: [sdc] tag#0 CDB: ATA command pass through(16) 85 06
20 00 00 00 00 00
kernel: sd 7:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR
driverbyte=DRIVER_SENSE
kernel: sd 7:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current]
[descriptor]
kernel: sd 7:0:0:0: [sdc] tag#0 Add. Sense: No additional sense
information
kernel: sd 7:0:0:0: [sdc] tag#0 CDB: ATA command pass through(12)/Blank a1
06 20 da 00 00
An attempt to umount sdc7 yields the journalctl message
Aug 03 09:34:19 jdb.home.invalid udisksd[2545]: Cleaning up mount point /
run/media/jim/mblanguage (device 8:39 is not mounted)
The error messages for sdc7 repeat every 10 seconds. The sr1 messages
have not repeated in 50 minutes.
Both devices are old. The cd/dvd burner is on my main machine purchased
fall 2009 and /dev/sdc is an external USB 1TB drive purchased for backup
about that time.
Has anyone else see something like this with the new kernel?
Any ideas why error messages are being generated for a partition and cd
burner that are idle/unmounted?
Suggestions?
Cheers!
jim b.
--
UNIX is not user-unfriendly; it merely
expects users to be computer-friendly.
UNIX is not user-unfriendly; it merely
expects users to be computer-friendly.