cdrecord help

DebianUser · 08-03-2010, 11:08 AM

I burnt a file using cdrecord

Code:

cdrecord -eject dev=1000,0,0 -v /usr/local/testfile
wodim: No write mode specified.
wodim: Asuming -tao mode.

Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
FIFO size      : 12582912 = 12288 KB
Track 01: data     0 MB         padsize:  598 KB
Total size:        0 MB (00:04.02) = 302 sectors
Lout start:        1 MB (00:06/02) = 302 sectors
Current Secsize: 2048

Starting to write CD/DVD at speed  24.0 in real TAO mode for single session.
Last chance to quit, starting real write in    0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
Performing OPC...
Starting new track at sector: 0
Track 01:    0 of    0 MB written.
WARNING: padding up to secsize.
Track 01: writing 598 KB of pad data.
Track 01: Total bytes read/written: 1885/614400 (300 sectors).
Writing  time:   11.337s
Average write speed   1.3x.
Fixating...
Fixating time:   19.481s
BURN-Free was never needed.
wodim: fifo had 1 puts and 1 gets.
wodim: fifo was 0 times empty and 0 times full, min fill was 100%.

however the disc isn't readable under windows and can't mount in linux

Code:

mount /dev/cdrom /mnt/cdrom
mount: you must specify the filesystem type

or

mount /dev/cdrom -t iso9660 -r /mnt/cdrom
wrong fs type, bad option, bad superblock on /dev/hda,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

sure it's some silly bit i've missed off but any help would be great.

GrapefruiTgirl · 08-03-2010, 11:18 AM

You might try mounting it as UDF format - but I'm not really sure what format would be the default; I would have assumed ISO9660. So, I don't really know exactly what type of disc you have just created

Maybe if you explained what is the purpose of burning a 1.8Mb file to an entire CD, we could suggest an alternate way of doing what you're trying to do? For example, if you wanted to be able to take a file from the Linux machine, put it on a disc, and be able to access it with a Windows machine, I would suggest formatting the CD with a UDF filesystem, and then copying the file onto it later.

DebianUser · 08-11-2010, 04:01 AM

Hi

It was merely a test burn hence the small file, fstab shows

/dev/hdb /media/cdrom0 udf,iso9660 user,noauto 0 0

for some reason in /media I have cdrom/ and cdrom0/ and in /dev I have cdrom and cdrw

GrapefruiTgirl · 08-11-2010, 05:05 AM

It's common for there to be an abundance of /dev/nodes for all sorts of 'devices' you do not have, and it is also common on many distros for there to be a whole bunch of mount points in /mnt and /media that you don't use.

If you do an `ls -l` on the /dev directory, you will see what sorts of block and character devices there are in there, such as those /dev/cdrw/ and /dev/cdrom devices; perhaps one of them is a packet device (udf read+write) while the other is a read-only cdrom device. Or, maybe both nodes point to the same thing, and if you're interested, you can find the list of "Linux kernel device allocations" via Google or perhaps on your machine somewhere (like a /doc folder), to identify exactly what type of device each is. You'd want the major & minor numbers to figure that out - here's a snippet of my /dev directory:

Code:

lrwxrwxrwx 1 root  root           3 Aug  5 12:38 cdr -> sr0
lrwxrwxrwx 1 root  root           3 Aug  5 12:38 cdr1 -> sr0
lrwxrwxrwx 1 root  root           3 Aug  5 12:38 cdrom -> sr0
lrwxrwxrwx 1 root  root           3 Aug  5 12:38 cdrom1 -> sr0
lrwxrwxrwx 1 root  root           3 Aug  5 12:38 cdrw -> sr0
lrwxrwxrwx 1 root  root           3 Aug  5 12:38 cdrw1 -> sr0
lrwxrwxrwx 1 root  root           3 Aug  5 12:38 cdwriter -> sr0
lrwxrwxrwx 1 root  root           3 Aug  5 12:38 cdwriter1 -> sr0

# look at all the above 'devices' pointing at /dev/sr0 which is a CD-DVD RW drive..

brw-rw---- 1 root  cdrom    11,   0 Aug  5 12:38 sr0

#  above is /dev/sr0 which is a block device, major# 11, minor# 0

Hope this helps a bit, but if you tell us what you were trying to 'test' we might be able to offer a particular syntax of burn command to get you the result you want.