Possible probings of my CDROM?

Hi list,

Here is the snippit from my dmesg:

thdb: media error (bad sector): status=0x51 { DriveReady SeekComplete Error }
hdb: media error (bad sector): error=0x34 { AbortedCommand LastFailedSense=0x03 }
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 1173936
Buffer I/O error on device hdb, logical block 293484
hdb: media error (bad sector): status=0x51 { DriveReady SeekComplete Error }
hdb: media error (bad sector): error=0x34 { AbortedCommand LastFailedSense=0x03 }
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 1173940
Buffer I/O error on device hdb, logical block 293485
hdb: media error (bad sector): status=0x51 { DriveReady SeekComplete Error }
hdb: media error (bad sector): error=0x34 { AbortedCommand LastFailedSense=0x03 }
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 1173944
Buffer I/O error on device hdb, logical block 293486
hdb: media error (bad sector): status=0x51 { DriveReady SeekComplete Error }
hdb: media error (bad sector): error=

I wonder if that is something to do with LVM? When CD in CDROM drive, it boots just fine. I have uncommented the line in /etc/lvm/lvm.conf
Just in case, here is my lvm.conf file:

# This is an example configuration file for the LVM2 system. # It contains the default settings that would be used if there was no

# /etc/lvm/lvm.conf file.
#
# Refer to 'man lvm.conf' for further information including the file layout.
#
# To put this file in a different directory and override /etc/lvm set
# the environment variable LVM_SYSTEM_DIR before running the tools.

# This section allows you to configure which block devices should

# be used by the LVM system.
devices {

# Where do you want your volume groups to appear ? dir = "/dev"

# An array of directories that contain the device nodes you wish # to use with LVM2.
scan = [ "/dev" ]

# A filter that tells LVM2 to only use a restricted set of devices. # The filter consists of an array of regular expressions. These # expressions can be delimited by a character of your choice, and # prefixed with either an 'a' (for accept) or 'r' (for reject). # The first expression found to match a device name determines if # the device will be accepted or rejected (ignored). Devices that # don't match any patterns are accepted.

# Be careful if there there are symbolic links or multiple filesystem # entries for the same device as each name is checked separately against # the list of patterns. The effect is that if any name matches any 'a' # pattern, the device is accepted; otherwise if any name matches any 'r' # pattern it is rejected; otherwise it is accepted.
# An array of directories that contain the device nodes you wish

    # to use with LVM2.
    scan = [ "/dev" ]

# A filter that tells LVM2 to only use a restricted set of devices. # The filter consists of an array of regular expressions. These # expressions can be delimited by a character of your choice, and # prefixed with either an 'a' (for accept) or 'r' (for reject). # The first expression found to match a device name determines if # the device will be accepted or rejected (ignored). Devices that # don't match any patterns are accepted.

# Be careful if there there are symbolic links or multiple filesystem # entries for the same device as each name is checked separately against # the list of patterns. The effect is that if any name matches any 'a' # pattern, the device is accepted; otherwise if any name matches any 'r' # pattern it is rejected; otherwise it is accepted.

# Remember to run vgscan after you change this parameter to ensure # that the cache file gets regenerated (see below).

# By default we accept every block device:
filter = [ "a/.*/" ]

# Exclude the cdrom drive
filter = [ "r|/dev/cdrom|" ]

# When testing I like to work with just loopback devices:
# filter = [ "a/loop/", "r/.*/" ]

# Or maybe all loops and ide drives except hdc:
# filter =[ "a|loop|", "r|/dev/hdc|", "a|/dev/ide|", "r|.*|" ]

# Use anchors if you want to be really specific
# The results of the filtering are cached on disk to avoid

    # rescanning dud devices (which can take a very long time).  By
    # default this cache file is hidden in the /etc/lvm directory.
    # It is safe to delete this file: the tools regenerate it.
    cache = "/etc/lvm/.cache"

# You can turn off writing this cache file by setting this to 0. write_cache_state = 1

# Advanced settings.

# List of pairs of additional acceptable block device types found # in /proc/devices with maximum (non-zero) number of partitions. # types = [ "fd", 16 ]
# If sysfs is mounted (2.6 kernels) restrict device scanning to

    # the block devices it believes are valid.
    # 1 enables; 0 disables.
    sysfs_scan = 1

# By default, LVM2 will ignore devices used as components of # software RAID (md) devices by looking for md superblocks. # 1 enables; 0 disables.
md_component_detection = 1
}

# This section that allows you to configure the nature of the

# information that LVM2 reports.
log {

# Controls the messages sent to stdout or stderr.
# There are three levels of verbosity, 3 being the most verbose.

Any ideas? Thanks in advance.
Dmitry.

Seems fine. (And no filter lines redefine it later.) Does the /dev/cdrom symlink actually exist?

norbi

I would be greatful to find out how I can determine that. Thanks fot the reply.

Dmitry.

Type in a shell command line:

ls -l /dev/cdrom

If the symlink exists, it looks similar to this:

lrwxrwxrwx 1 root root 3 Oct 9 21:17 /dev/cdrom -> hdc

norbi

yes, it is:

ls -l /dev/cdrom
lrwxrwxrwx 1 root root 3 Oct 31 06:39 /dev/cdrom -> hdb

any ideas? I don't remember exactly, but I was playing with couple of lvm tools, and I have always has some sort of wornings about CDROM, so it might be likely that I have this problem because of LVM. Thanks again.

Dmitry.