Find the answer to your Linux question:
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 11
Hi, I've been using Slackware 11.0, my first Linux dist, for about a week. You could say I am somewhat of a beginner. The problem I come to you with ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Dec 2006
    Posts
    13

    CD-ROM won't mount


    Hi, I've been using Slackware 11.0, my first Linux dist, for about a week. You could say I am somewhat of a beginner.

    The problem I come to you with is that I cannot mount my cd-rom. When I choose the option 'mount', there is a progress bar but then nothing happens except that an empty cd-rom directory opens (although the CD has a lot of files that Linux can read, so it shouldn't be empty). The information in the bottom of the window says: Unmounted cd-rom.

    dmesg gives:
    Code:
    kComplete Error }
    hdc: command error: error=0x54
    end_request: I/O error, dev 16:00 (hdc), sector 10
    hdc: command error: status=0x51 { DriveReady SeekComplete Error }
    hdc: command error: error=0x54
    end_request: I/O error, dev 16:00 (hdc), sector 11
    hdc: command error: status=0x51 { DriveReady SeekComplete Error }
    hdc: command error: error=0x54
    end_request: I/O error, dev 16:00 (hdc), sector 12
    hdc: command error: status=0x51 { DriveReady SeekComplete Error }
    
    //It keeps on going like this for some hundred lines, going through sector after sector, until it reaches 0, whereby it reads:
    
    end_request: I/O error, dev 16:00 (hdc), sector 0
    FAT: unable to read boot sector
    UMSDOS: msdos_read_super failed, mount aborted.
    hdc: command error: status=0x51 { DriveReady SeekComplete Error }
    hdc: command error: error=0x54
    end_request: I/O error, dev 16:00 (hdc), sector 0
    FAT: unable to read boot sector
    and etc/fstab says:
    Code:
    /dev/hda3        swap             swap        defaults                   0   0
    /dev/hda2        /                    ext3         defaults                    1   1
    /dev/hdb1        /ntfs              ntfs           users,ro                   0   0
    /dev/hdc          /mnt/cdrom  auto         noauto,users,ro        0   0
    /dev/fd0           /mnt/floppy   auto         noauto,owner           0   0
    devpts             /dev/pts        devpts     gid=5,mode=620      0   0
    proc                /proc             proc         defaults                     0   0
    and etc/group says:
    Code:
    root::0:root
    bin::1:root,bin,daemon
    daemon::2:root,bin,daemon
    sys::3:root,bin,adm
    adm::4:root,adm,daemon
    tty::5:
    disk::6:root,adm
    lp::7:lp
    mem::8:
    kmem::9:
    wheel::10:root
    floppy::11:root
    mail::12:mail
    news::13:news
    uucp::14:uucp
    man::15:
    audio::17:
    video::18:
    cdrom::19:root,user
    games::20:
    slocate::21:
    utmp::22:
    smmsp::25:smmsp
    mysql::27:
    rpc::32:
    sshd::33:sshd
    gdm::42:
    shadow::43:
    ftp::50:
    pop::90:pop
    scanner::93:
    nobody::98:nobody
    nogroup::99:
    users::100:
    console::101:
    Anyone with more experience who'd be willing to lend a hand?
    I have tried using all sorts of cd's and DVD's without any luck.

  2. #2
    Linux Enthusiast
    Join Date
    Jun 2005
    Posts
    668
    /dev/hdc is possibly not your cdrom device

    it looks like a dos or fat partition, and probably has /dev/hdc{1,2,3,x} etc.

    find out the correct device for your cdrom and edit /etc/fstab accordingly

  3. #3
    Just Joined!
    Join Date
    Dec 2006
    Posts
    13
    Quote Originally Posted by kern
    /dev/hdc is possibly not your cdrom device

    it looks like a dos or fat partition, and probably has /dev/hdc{1,2,3,x} etc.

    find out the correct device for your cdrom and edit /etc/fstab accordingly
    Hi, thanks for your reply.
    Correct me if I'm wrong, but hdc is standard for the master of the secondary IDE right? That's namely the channel I'm using for the cd-rom. But maybe there is no official standard when it comes to naming devices? How can I check which device name the cdrom uses then?

  4. #4
    Linux Guru Juan Pablo's Avatar
    Join Date
    Mar 2006
    Location
    /home/south_america/ecuador/quito
    Posts
    2,064
    post the output of "fdisk -l" to find out
    Put your hand in an oven for a minute and it will be like an hour, sit beside a beautiful woman for an hour and it will be like a minute, that is relativity. --Albert Einstein
    Linux User #425940

    Don't PM me with questions, instead post in the forums

  5. #5
    Just Joined!
    Join Date
    Dec 2006
    Posts
    13
    Quote Originally Posted by Juan Pablo
    post the output of "fdisk -l" to find out
    Hi.

    'fdisk -l' gives:
    Code:
    Disk /dev/hda: 160.0 GB, 160041885696 bytes
    255 heads, 63 sectors/track, 19457 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/hda1   *           1       10199    81923436    7  HPFS/NTFS
    /dev/hda2           10200       18346    65440777+  83  Linux
    /dev/hda3           18347       19457     8924107+  82  Linux swap
    
    Disk /dev/hdb: 250.0 GB, 250059350016 bytes
    255 heads, 63 sectors/track, 30401 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/hdb1               1       30400   244187968+   7  HPFS/NTFS
    As far as I can see, there is only the HDD's showing? Does this mean anything?

    /Rahiiyja

  6. #6
    Linux Enthusiast
    Join Date
    Jun 2005
    Posts
    668
    /dev/hdc is indeed secondary master

    'dmesg | grep hd' straight after boot will show your ide devices.

    Have you only two hard disks? try 'fdisk -l /dev/hdc' .. it might be a hard drive.

  7. #7
    Just Joined!
    Join Date
    Dec 2006
    Posts
    13
    Quote Originally Posted by kern
    /dev/hdc is indeed secondary master

    'dmesg | grep hd' straight after boot will show your ide devices.

    Have you only two hard disks? try 'fdisk -l /dev/hdc' .. it might be a hard drive.
    Hi.
    'dmesg | grep hd' produces nothing after boot, it just begins a new line. Without any errors.

    One thing I noticed is that early during boot I can see the following (not a 100% accurate copy of the text, but should be enough):
    Code:
    /dev/hda - 150 gb harddrive
    /dev/hdb - 250 gb harddrive
    /dev/hdc - NEC DVD-player
    That would mean that /dev/hdc is the DVD-player I guess? Since it recognizes the manufacturer and all.

  8. #8
    Linux Enthusiast
    Join Date
    Jun 2005
    Posts
    668
    try this for me:

    put a normal ISO9660 CDROM in , and type this

    'mount /dev/hdc -tiso9660 /mnt/cdrom'

    check the last few lines of 'dmesg' does it say its mounted an iso filesystem etc.

    check the directory /mnt/cdrom for files

    this method is manual and doesn't use /etc/fstab, so it'll be a bit of diagnosis.

  9. #9
    Just Joined!
    Join Date
    Dec 2006
    Posts
    13
    Quote Originally Posted by kern
    try this for me:

    put a normal ISO9660 CDROM in , and type this

    'mount /dev/hdc -tiso9660 /mnt/cdrom'

    check the last few lines of 'dmesg' does it say its mounted an iso filesystem etc.

    check the directory /mnt/cdrom for files

    this method is manual and doesn't use /etc/fstab, so it'll be a bit of diagnosis.
    Hi.

    Dmesg gives:
    Code:
    ion: 0.5
    pciehp: PCI Express Hot Plug Controller Driver version: 0.5
    pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    shpchp: shpc_init : shpc_cap_offset == 0
    shpchp: shpc_init : shpc_cap_offset == 0
    shpchp: shpc_init : shpc_cap_offset == 0
    shpchp: shpc_init : shpc_cap_offset == 0
    shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
    pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    pciehp: PCI Express Hot Plug Controller Driver version: 0.5
    pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    shpchp: shpc_init : shpc_cap_offset == 0
    shpchp: shpc_init : shpc_cap_offset == 0
    shpchp: shpc_init : shpc_cap_offset == 0
    shpchp: shpc_init : shpc_cap_offset == 0
    shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
    pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    pciehp: PCI Express Hot Plug Controller Driver version: 0.5
    pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    shpchp: shpc_init : shpc_cap_offset == 0
    shpchp: shpc_init : shpc_cap_offset == 0
    shpchp: shpc_init : shpc_cap_offset == 0
    shpchp: shpc_init : shpc_cap_offset == 0
    shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
    
    // It goes on like this until:
    
    pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    pciehp: PCI Express Hot Plug Controller Driver version: 0.5
    uhci.c: USB Universal Host Controller Interface driver v1.1
    usb-uhci.c: $Revision: 1.275 $ time 02:01:41 Sep  1 2006
    usb-uhci.c: High bandwidth mode enabled
    usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
    usb.c: registered new driver usbkbd
    usbkbd.c: :USB HID Boot Protocol keyboard driver
    scsi singledevice 4 0 0 0
    scsi singledevice 4 0 1 0
    scsi singledevice 4 0 2 0
    scsi singledevice 4 0 3 0
    scsi singledevice 4 0 4 0
    scsi singledevice 4 0 5 0
    scsi singledevice 4 0 6 0
    scsi singledevice 4 0 7 0
    scsi singledevice 0 0 0 0
    scsi singledevice 0 0 1 0
    scsi singledevice 0 0 2 0
    scsi singledevice 0 0 3 0
    scsi singledevice 0 0 4 0
    scsi singledevice 0 0 5 0
    scsi singledevice 0 0 6 0
    scsi singledevice 0 0 7 0
    scsi singledevice 1 0 0 0
    scsi singledevice 1 0 1 0
    scsi singledevice 1 0 2 0
    scsi singledevice 1 0 3 0
    scsi singledevice 1 0 4 0
    scsi singledevice 1 0 5 0
    scsi singledevice 1 0 6 0
    scsi singledevice 1 0 7 0
    scsi singledevice 2 0 0 0
    scsi singledevice 2 0 1 0
    scsi singledevice 2 0 2 0
    scsi singledevice 2 0 3 0
    scsi singledevice 2 0 4 0
    scsi singledevice 2 0 5 0
    scsi singledevice 2 0 6 0
    scsi singledevice 2 0 7 0
    scsi singledevice 3 0 0 0
    scsi singledevice 3 0 1 0
    scsi singledevice 3 0 2 0
    scsi singledevice 3 0 3 0
    scsi singledevice 3 0 4 0
    scsi singledevice 3 0 5 0
    scsi singledevice 3 0 6 0
    scsi singledevice 3 0 7 0
    mask = 3
    keyboard: Timeout - AT keyboard not present?(f4)
    keyboard: Timeout - AT keyboard not present?(f3)
    keyboard: Timeout - AT keyboard not present?(f4)
    keyboard: Timeout - AT keyboard not present?(f4)
    keyboard: Timeout - AT keyboard not present?(f3)
    keyboard: Timeout - AT keyboard not present?(f4)
    mask = 3
    hdc: command error: status=0x51 { DriveReady SeekComplete Error }
    hdc: command error: error=0x54
    end_request: I/O error, dev 16:00 (hdc), sector 64
    isofs_read_super: bread failed, dev=16:00, iso_blknum=16, block=32
    ISO 9660 Extensions: Microsoft Joliet Level 3
    ISOFS: changing to secondary root
    The message is different, but the mount doesn't seem to have worked.
    When I mounted I got no error messages though.

    When I open /mnt/cdrom I get files though.
    Problem solved or not?
    There seems to be some error even if I can access the cd.

  10. #10
    Linux Enthusiast
    Join Date
    Jun 2005
    Posts
    668
    scratched cd, dodgy IDE cable ? dying drive? not sure

    if you can see the files the cd is obviously mounted, but the read errors point to a problem, could be bad chipset support, or the problems above. What kernel is this by the way? 2.4?

    you need to blacklist the 'pciehp' and 'shpchp' modules because you are getting a lot of junk in dmesg output you dont need

    you can do that by entering:

    pciehp
    shpchp

    into the end of /etc/hotplug/blacklist

Page 1 of 2 1 2 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •