[nSLUG] Replaced CD drive - won't boot, won't play, players don't recognize

Robert Ashley rb.ashley at gmail.com
Tue Jul 31 14:52:53 ADT 2007


On 7/31/07, Bill Davidson <billdavidson at eastlink.ca> wrote:
> err, no, he meant the kernel modules.  Try /sbin/lsmod to see what
> kernel modules are loaded.

Thanks for the clarification Bill.

bob at ashley:/sbin$ lsmod
Module                  Size  Used by
isofs                  32796  0
ipv6                  236256  8
ppdev                   8580  0
lp                     10884  0
button                  7952  0
ac                      5220  0
battery                10020  0
dm_snapshot            16420  0
dm_mirror              20116  0
dm_mod                 52556  2 dm_snapshot,dm_mirror
loop                   15880  0
snd_emu10k1_synth       6944  0
snd_emux_synth         30976  1 snd_emu10k1_synth
snd_seq_virmidi         6752  1 snd_emux_synth
snd_seq_midi_emul       5888  1 snd_emux_synth
snd_emu10k1           122944  4 snd_emu10k1_synth
snd_seq_dummy           3748  0
snd_seq_oss            29248  0
tsdev                   7520  0
snd_seq_midi            8160  0
snd_seq_midi_event      6880  3 snd_seq_virmidi,snd_seq_oss,snd_seq_midi
snd_seq                46160  9
snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_rawmidi            22400  3 snd_seq_virmidi,snd_emu10k1,snd_seq_midi
firmware_class          9408  1 snd_emu10k1
snd_ac97_codec         92356  1 snd_emu10k1
parport_pc             32740  1
ac97_bus                2272  1 snd_ac97_codec
snd_pcm_oss            39168  1
snd_mixer_oss          15328  2 snd_pcm_oss
parport                33672  3 ppdev,lp,parport_pc
snd_pcm                71940  3 snd_emu10k1,snd_ac97_codec,snd_pcm_oss
snd_seq_device          7596  8
snd_emu10k1_synth,snd_emux_synth,snd_emu10k1,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq,snd_rawmidi
snd_timer              20868  3 snd_emu10k1,snd_seq,snd_pcm
snd_page_alloc          9512  2 snd_emu10k1,snd_pcm
snd_util_mem            4544  2 snd_emux_synth,snd_emu10k1
psmouse                34952  0
snd_hwdep               8548  2 snd_emux_synth,snd_emu10k1
rtc                    12760  0
serio_raw               6564  0
snd                    48132  15
snd_emux_synth,snd_seq_virmidi,snd_emu10k1,snd_seq_oss,snd_seq,snd_rawmidi,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_device,snd_timer,snd_hwdep
emu10k1_gp              3744  0
iTCO_wdt                9956  0
gameport               14984  2 emu10k1_gp
soundcore               7424  3 snd
intel_agp              23004  1
agpgart                32168  1 intel_agp
pcspkr                  3136  0
shpchp                 30996  0
pci_hotplug            29088  1 shpchp
evdev                   9216  4
ext3                  120904  1
jbd                    55208  1 ext3
mbcache                 8164  1 ext3
ide_cd                 36512  0
cdrom                  32768  1 ide_cd
ide_disk               15584  3
ata_generic             8100  0
libata                109172  1 ata_generic
scsi_mod              133740  1 libata
generic                 4804  0 [permanent]
usbhid                 23488  0
hid                    23680  1 usbhid
floppy                 54820  0
e100                   32488  0
mii                     5280  1 e100
piix                    9508  0 [permanent]
ide_core              115016  4 ide_cd,ide_disk,generic,piix
uhci_hcd               22608  0
usbcore               123272  3 usbhid,uhci_hcd
thermal                14120  0
processor              30888  1 thermal
fan                     4868  0

> Well, you could look through the boot-time messages (dmesg | less) to
> see what is being detected, but I don't think that is your problem since
> some stuff sort-of works.

$ dmesg | less
--snip--
Probing IDE interface ide1...
hdc: CREATIVE CD-RW RW1210E, ATAPI CD/DVD-ROM drive
--snip--
hdc: ATAPI 32X CD-ROM CD-R/RW drive, 2048kB Cache, DMA
Uniform CD-ROM driver Revision: 3.20
--snip--
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
ATAPI device hdc:
  Error: Illegal request -- (Sense key=0x05)
  Illegal mode for this track or incompatible medium -- (asc=0x64, ascq=0x00)
  The failed "Read 10" packet command was:
  "28 00 00 03 91 20 00 00 02 00 00 00 00 00 00 00 "
end_request: I/O error, dev hdc, sector 935040
Buffer I/O error on device hdc, logical block 233760
Buffer I/O error on device hdc, logical block 233761
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown

> Why are you looking for /media in /dev? Try man 5 fstab.

Neophytic stab in the dark? I'm still learning file structures and
relations, neophytically.

> The first
> field specifies the block special device you want to mount, the second
> field is the mount point, and for /dev/hdc it is /media/cdrom0.  Try "ls
> -l /media".

bob at ashley:~$ ls -l /media
total 16
lrwxrwxrwx 1 root root    6 2007-01-15 11:41 cdrom -> cdrom0
drwxr-xr-x 2 root root 4096 2007-01-15 11:41 cdrom0
drwxr-xr-x 2 root root 4096 2007-01-15 11:41 cdrom1
lrwxrwxrwx 1 root root    7 2007-01-15 11:41 floppy -> floppy0
drwxr-xr-x 2 root root 4096 2007-01-15 11:41 floppy0
lrwxrwxrwx 1 root root    4 2007-01-15 11:41 usb -> usb0
drwxr-xr-x 2 root root 4096 2007-01-15 11:41 usb0

> > I'd just as soon start over if I could, do a complete reinstall of the
> > distribution, but I can't even boot from the CD.
>
> Nahh, you don't want to do that.  All that is going to do is get you
> back to where you are now.  I mean, what would change?

I suppose I'm under the assumption (erroneous, evidently) that
something else I've fiddled with over the last bit has got me into
this mess, and that a fresh install would at least be untainted by my
rustic paws.

> >  Wouldn't that suggest
> > something awry in the BIOS itself?
>
> No.  It is highly unlikely that anything would be wrong in the BIOS.
> But something is wrong at the hardware level.  You say it is a brand-new
> drive, so let's assume for now that it is good.  People keep asking if
> you are using known-good media, i.e., disks that you can read in another
> system, but I haven't heard a definite answer.

I haven't been explicit. Yes, all the disks work in other machines,
cd-players etc.

> That said, the errors you are getting are not just about the media, but
> about sense errors and controller errors.  Double check that the ribbon
> cable is plugged in correctly and solidly.  Remove it and check for bent
> pins.  If that all looks good try a new cable.  Then try the drive in
> another system (surely someone in Berwick or your office has a computer
> into which you can temporarily install a drive).

If the ribbon cable wasn't seated, that would make too poor
connections in a row, because the problem is exactly the same, old
drive/new drive. I'll check for bent pins and try your "drive as
slave" test.

> Good luck with all this.

Hey, thanks for your enduring patience. It amazes me, all the diverse
diagnostic angles or approaches different people take. I realize this
must be a virtue of Linux as in there's
"more-than-one-way-to-skin-cat", but I get lost in the woods pretty
quick.

Bob

>
> --
> Bill Davidson <billdavidson at eastlink.ca>
> _______________________________________________
> nSLUG mailing list
> nSLUG at nslug.ns.ca
> http://nslug.ns.ca/cgi-bin/mailman/listinfo/nslug
>



More information about the nSLUG mailing list