IBM T30.  I can mount,read and boot off of CDs, but not cd-rs, no matter
where burned or at what speed.  Below are some error msgs.  Some kind
soul spotting any clue greatly appreciated.  Thanks.

Upon inserting a Knoppix disc, from /var/log/messages:
 
Sep 22 16:56:13 localhost kernel: [17180301.988000] cdrom: This disc
doesn't have any tracks I recognize!
 
Upon "mount -t iso9660 /dev/cdrom /media/cdrom, on the command line:
 
mount: block device /dev/cdrom is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/cdrom,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so
 
From /var/log/messages:

Sep 22 16:59:49 localhost kernel: [17180517.904000] attempt to access
beyond end of device
Sep 22 16:59:49 localhost kernel: [17180517.904000] hdc: rw=0, want=68,
limit=4
Sep 22 16:59:49 localhost kernel: [17180517.904000] isofs_fill_super:
bread failed, dev=hdc, iso_blknum=16, block=16

edj wrote:
> IBM T30.  I can mount,read and boot off of CDs, but not cd-rs, no matter
> where burned or at what speed.  Below are some error msgs.  Some kind
> soul spotting any clue greatly appreciated.  Thanks.
> 
> Upon inserting a Knoppix disc, from /var/log/messages:
>  
> Sep 22 16:56:13 localhost kernel: [17180301.988000] cdrom: This disc
> doesn't have any tracks I recognize!
>  
> Upon "mount -t iso9660 /dev/cdrom /media/cdrom, on the command line:
>  
> mount: block device /dev/cdrom is write-protected, mounting read-only
> mount: wrong fs type, bad option, bad superblock on /dev/cdrom,
>        missing codepage or other error
>        In some cases useful info is found in syslog - try
>        dmesg | tail  or so
>  
> From /var/log/messages:
> 
> Sep 22 16:59:49 localhost kernel: [17180517.904000] attempt to access
> beyond end of device
> Sep 22 16:59:49 localhost kernel: [17180517.904000] hdc: rw=0, want=68,
> limit=4
> Sep 22 16:59:49 localhost kernel: [17180517.904000] isofs_fill_super:
> bread failed, dev=hdc, iso_blknum=16, block=16
> 
> 
Sounds like you used the wrong command to burn em.

On Sat, 23 Sep 2006 02:57:57 +0100, The Natural Philosopher staggered
into the Black Sun and said:
> edj wrote:
>> IBM T30.  I can mount, read, and boot off of CDs, but not cd-rs, no
>> matter where burned or at what speed.  Below are some error msgs.

>> Upon inserting a Knoppix disc, from /var/log/messages:
>> Sep 22 16:56:13 localhost kernel: [17180301.988000] cdrom: This disc
>> doesn't have any tracks I recognize!
  
>> From /var/log/messages:
>> localhost kernel: attempt to access beyond end of device
>> localhost kernel: hdc: rw=0, want=68, limit=4
>> localhost kernel: isofs_fill_super: bread failed, dev=hdc,
>> iso_blknum=16, block=16
> Sounds like you used the wrong command to burn em.

There are (or at least there were) some cheaper DVD-+Rs that read
CD-ROMs fine but refuse to read CD-Rs.  This is really a hardware
limitation in that the gain control and/or laser don't read the pits and
lands in the CD-R properly.  What's the spec on the optical drive in
this T30?  The cheaper DVD-+Rs *will* read CD-RWs, or at least they
should.  Try a CD-RW if you have a blank lying around.  

-- 
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin /    mail: TRAP + SPAN don't belong
http://www.brainbench.com     / I don't practice what I preach, because I'm
-----------------------------/  not the kind of person I'm preaching to.

Dances With Crows wrote:

edj wrote:
>> IBM T30.  I can mount, read, and boot off of CDs, but not cd-rs, no
>> matter where burned or at what speed.  Below are some error msgs.
> 
> There are (or at least there were) some cheaper DVD-+Rs that read
> CD-ROMs fine but refuse to read CD-Rs.  This is really a hardware
> limitation in that the gain control and/or laser don't read the pits and
> lands in the CD-R properly.  What's the spec on the optical drive in
> this T30?  The cheaper DVD-+Rs *will* read CD-RWs, or at least they
> should.  Try a CD-RW if you have a blank lying around.

On the T30, & using a 4x CD-RW, I ran:

cdrecord speed=2 -v -eject -tao -data dev=ATA:1,0,0 SimplyMEPIS_6.0_i386.iso

It burned flawlessly and could be read on another Linux machine, but
couldn't be read on the T30.  So, the drive will burn but not mount.  I
don't get it.

Ed <edjlb@yahoo.com> writes:

>Dances With Crows wrote:

>edj wrote:
>>> IBM T30.  I can mount, read, and boot off of CDs, but not cd-rs, no
>>> matter where burned or at what speed.  Below are some error msgs.
>> 
>> There are (or at least there were) some cheaper DVD-+Rs that read
>> CD-ROMs fine but refuse to read CD-Rs.  This is really a hardware
>> limitation in that the gain control and/or laser don't read the pits and
>> lands in the CD-R properly.  What's the spec on the optical drive in
>> this T30?  The cheaper DVD-+Rs *will* read CD-RWs, or at least they
>> should.  Try a CD-RW if you have a blank lying around.

>On the T30, & using a 4x CD-RW, I ran:

>cdrecord speed=2 -v -eject -tao -data dev=ATA:1,0,0 SimplyMEPIS_6.0_i386.iso

>It burned flawlessly and could be read on another Linux machine, but
>couldn't be read on the T30.  So, the drive will burn but not mount.  I
>don't get it.

Sure you do. It is defective. Throw it away and buy a better one. You just
do not want to accept that. There is no magic incantiation anyone is going
to be able to give you to make defective hardware suddenly not be
defective.

On 24 Sep 2006 23:46:51 GMT, Unruh staggered into the Black Sun and
said:
> Ed <edjlb@yahoo.com> writes:
>>Dances With Crows wrote:
>>> There are (or at least there were) some cheaper DVD-+Rs that read
>>> CD-ROMs fine but refuse to read CD-Rs.  This is really a hardware
>>> limitation in that the gain control and/or laser don't read the pits
>>> and lands in the CD-R properly.
>>On the T30, & using a 4x CD-RW, I ran:
>>cdrecord speed=2 -v -eject -tao -data dev=ATA:1,0,0
>>SimplyMEPIS_6.0_i386.iso

Interesting; the ATA: device naming spec doesn't always work properly
IME.  It's usually better/easier to give the normal device name, like
"dev=/dev/hdc", even though Joerg complains about it.

>>It burned flawlessly and could be read on another Linux machine, but
>>couldn't be read on the T30.  So, the drive will burn but not mount.
>>I don't get it.

All right, if it can successfully burn a CD-RW but not read one, there's
something weird going on.  How are you mounting it?  Does a simple
command like "dd if=/dev/hdc of=/dev/null bs=512 count=1" return some
sort of read error?  If dd works, it's something dumb happening within
mount.  Or a bad filesystem--I have a DVD here burned by a friend with
an OS X app, and mount can't seem to determine the filesystem
automatically; I have to manually specify -t iso9660 or it won't mount.

> Sure you do. It is defective. Throw it away and buy a better one. You
> just do not want to accept that. There is no magic incantiation anyone
> is going to be able to give you to make defective hardware suddenly
> not be defective.

Devices that fit in an Ultrabay are a lot more expensive than standard
5.25" devices.  So, the next thing to try is to upgrade the device's
firmware (if possible).  The firmware on IBM devices, while usually OK,
can have many bugs.  (A friend of mine admins AIX for a living, and has
told me extensive stories of things like a SAN dropping all of its disks
because of a firmware bug.)  The firmware upgrade procedure may require
Windows; hope you have that sitting around somewhere.  HTH anyway,

-- 
   "Right now i got approx. 3 KB RAM left, still enough to do a lot of
   useful stuff."
   --Olaf Christ, who hacked up the first TCP/IP-enabled Lego brick.
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see